DSXchange

What does "not working" mean in this context? What error message is generated? Why are you setting $LegacyDBUserID for each of the three parameters? That's almost certain not to be correct. Have you proven that each of these environment variables is set? For example echo $LegacyDBUserID Have you tri...

That is correct. DataStage jobs run on the server. Since you posted that your server was Windows-based, I mentioned those monitoring tools only.

Windows Task Manager (in which you can select what you want to see on the Processes tab - DataStage jobs and active stages run uvsh.exe). Windows Performance Monitor. There are "hooks" available from DataStage server jobs into the Windows performance monitor, but these are only five counters of thin...

Same table as source?

Talk to your UNIX system administrator. "File table overflow" suggests that either the file table or the inode table has become full.

You can't do much while this condition is true.

You basically do the same thing in a parallel job. Set the Lookup Failed rule in your Lookup stage to Continue then, in the downstream Transformer stage, test whether the key looked up is null (assuming that it can't be null otherwise). The other tests you would build into constraint or output colum...

No. A hashed file accessed via a Hashed File stage can only return that row that matches its primary key value. And even with a UniVerse stage you'd have to use some pretty hairy user-defined SQL, for example WHERE CAST(? AS VARCHAR) LIKE '%' in the SELECT statement, to return every row for each inp...

IF the default answer is Y (which I'm unable to ascertain for dsexport at the moment), then you can use this trick to deliver an infinite number of "Enter" presses. Redirect stdin from NUL (which is /dev/null if you're on UNIX).

I'm tending more towards unsupported data type. What is the data type of DIM_ACC_PRICE_PLAN_WLESS_3 ?

I think you need to involve your DBA on this one, to enable tracing to find out which parameter might be causing such a warning to be thrown. There may be some assistance in the errors manual for DB2, if you lookup SQL0304N (or error code -304, which is the same thing).

Firstload? Do you mean Fastload?

Disagree. The -jobstatus option is a wait option. It's not that.

That's good. The moderator will probably do the needful here.

Commit after complete load is achieved by setting rows/transaction to 0. Restart has to be designed - you have to keep records about how many rows were successfully sent to Oracle, or select these from the Oracle table before (as part of) the restart run. Facilitate this by keeping track of which jo...