DSXchange

This is because you cannot limit the number of rows via this method in Parallel jobs, only for server jobs.

Your width per line is over the default of 80. Try "SET.TERM.TYPE WIDTH 132".

What does "truss -p 20832" show?

There are several things I would do. Ask your DBA to see if sessions are open to SQL Server, and check to see if the job is still running as a UNIX process. Are any of these processes using CPU or IO? Use "truss" or your OS's equivalent to see which system calls are being used. That's for starters, ...

The question is rather vague, so I would say (with regards to metrics) that COBOL is a 13 while DataStage is a 23. Seriously, what are you looking for? Total effort required for each? Shortest project runtime? Least resources? Best looking code? Is the DB2 target on the host or on a UNIX machine? Do...

You might be able to use the command line "dsadmin -createproject", but I would suggest contacting support on this issue. I had a similar case many months ago and we were in contact with support. We had even done a fresh install with the same issue. Unfortunately I cannot remember what finally happe...

It probably defaults to the longest string when "creating" a new column. Have you tried using CAST to limit this to a CHAR(3)?

The PX engine documentation uses "nodes" and "partitions" interchangeably to mean the same thing.

Memory usage can be monitored with system tools. The normal method of starting many other jobs is thorugh use of a job sequence. If you call the jobs from a transform they will most likely all get started at roughly the same time unless you build in a "-wait". How much memory is half of your server'...

Are you using LOAD method in the Oracle stage? The message seems to indicate the Oracle stage, but you can test by replacing it with a peek to see if the error remains.

That is a strange scenario. What collection algorithm did you specify in the link collector?

DB2 allows you to split the SQL over several calls, as it keeps the connected session "alive", whilst sqlplus does not. The internet is alive with examples of how to use sqlplus from the command line.

The exact format depends upon which sql command line program you use. For the moment, just open up a DOS "CMD" window. If you can enter and execute a one-liner from there then you can do so from DataStage as well.

These patches are available through IBM; I do not know of a public location where these are accessible. But the problem you describe is known and is fixed in a patch, if that is any consolation.

I looked at the "to_date" and thought to myself that this cannot be server. I guess it isn't PX, either