DSXchange

Please do what I suggested (output to text file). You have provided no extra diagnostic information in your latest post.

1. No. 2. Define performance. Obviously the storage space will go up, since you now have three eight-byte pointers per record rather than three four-byte pointers per record. The perfect world scenario (a perfectly tuned hashed file) will continue to require 1.0 logical I/O operations per key access...

Draw us a picture. Use "ASCII art" enclosed in Code tags. Your explanation remains too vague to be of use in diagnosis.

And please delete the duplicate posts you have in the server forum.

Post some lines from this file. Also post what the structure (metadata) is.

And please delete the duplicate posts you have in the server forum.

Job status 3 means that the job is not in a runnable state (and must be reset). Job status 1, 2 or 21 mean that the job is in a runnable state (and need not be reset). Job status 0 means that the job is running, and can not therefore successfully process a run request. There are other status values,...

A Copy stage that does nothing will be optimized out. You won't see it in the score.

Importing table definitions through OCI is known to be inaccurate for decimal data type. Even IBM recommends that you import Oracle table definitions using Orchestrate (the orchdbutil utility).

Download blat.exe from the Web; it's a good SMTP client.

What's different between your client machine and theirs?

Clearly "nothing" is not the correct answer - otherwise they'd be behaving identically.

Insufficient information. Can you prove your assertions? What is the job doing? Try not to put too much faith in rows/sec as a meaningful metric (search the forum for reasons why not).

If they are extracte as VarChar and coming out like that, then that's how they are in that particular source file. NO conversion takes place for VarChar. Your problem is with your data.

FORGET re-compile. It is not necessary!

You can reset the job from dsjob.
You can even test whether it needs to be reset (Aborted = 3).

After resetting, the job status will be 21 (has been reset).
Then you can run the job normally.

No need to re-compile.

Are you listening?

Make the partitioning specific. Don't rely on (Auto) to preserve previous partitioning - it is just as likely to repartition using round robin.

Login with telnet. If that doesn't work, login on the server itself (maybe using Remote Console). Check the NLS settings. Make sure they match the code page set for the Windows environment on your client machine.

Re-boot the client machine to clear out any DLLs or OCXs with unattached handles from memory.

Are you running on Windows XP sp2? If so, do you have the patch needed to have Designer work properly with job sequences?