DSXchange

OK, then, try out your job, and if it doesn't finish in 2 seconds, let us know.

Stage variables are non-nullable and SetNull() is not supported until v8.5. The v7 jobs compiled OK with SetNull() and could abort when handling nulls. v8.1 flags it as an error when compiling (not sure about v8.0). The behavior and options you have are going to depend upon which 8.x release you are...

vamsi.4a6 wrote:The source is oracle

I guess the Oracle tidbit is irrelevant.

Not sure if this helps or not.... In sorting you can set the Nulls position so nulls will sort first or last.

I've run DataStage on AIX and Solaris servers without restarting the servers or having them restart unexpectedly for years at a time. I've never seen the DataStage Engine go down unexpectedly. I guess I've been lucky. My first concern here would be to address why the server would ever restart unexpe...

Try using Oracle's COALESCE() function in your SELECT statement.

10 million records in a sequential file may take 4 seconds. How much less time do you need?

I still think that the SAN / disk admin people should be able to fix it for you transparently, ... assuming that those are all read requests. In any case, ask them how many physical disk spindles that particular file system are sharing. Also ask for details of any memory cache that's built into the ...

Do you have a local admin to check with? How about support? Sounds like you've got problems... Try right-clicking on the palette and exploring options to load defaults or reset to factory default settings. If your job type is Parallel job, then the Processing category should show Pivot and Pivot Ent...

Step through running job1 and 2, then manually run the unix command from the command line to check the output. Can you post the actual unix command and its output? The command you posted doesn't look quite right.

How about using a Sequential File stage as the target instead of an awk command? Sequential File stage lets you choose delimiters and newline settings.

Try describing the rules you want to apply in your own words.

Can you post that with what you have tried and any questions?

The little button I mentioned is not there in your version 8.1 screen shot. Someone else will know...

Just make sure they're not on "the crappy disks" then!

Our servers don't have any local disks (no crappy disks). All SAN. Works very well...

What have you tried so far?

What is your question?

It sounds like you need to well more-than-double your disk space to allow for large sorts. Open the config file used by the job, or just look for it in the job log details. Find the resource scratchdisk entries per node. Then go out to your operating system and check the disk space for those locatio...