DSXchange

With write cache disabled you will (I predict) see a slower load rate (than with write cache enabled) that doesn't decline suddenly at the end.

Monitor your server machine to see whether its resource consumption, particularly CPU and memory, is up near 100%

Hi Mister Hasty. If the OP is using File Pattern this implies sequential files and this implies no key.

Rename the wrong user_lib and kill the perpetrator so it doesn't happen again. Then re-install DataStage server.

Did you check the Force compile option?

WHAT "other numeric value"? Pi?

Your question currently falls into "there a red light on on my dashboard". More information is needed for cogent diagnosis.

... in particular the Orchestrate Operators manual.

These do not ship with DataStage. You can search the forum to find a link to a web site from which you can download them. Make sure you get the right version for your DataStage (e.g. 7.5 or 7.1).

What you see in Director is not the actual status but the last reported status. If the job has failed without being able to update its status to DataStage, it will appear to be running forever. Clear the status file in this case.

No evidence that they'd searched at all, so I had to point it out.

IF your job sequence (note, not "sequencer") is as you describe, with no dependency between the four streams, then four simultaneous streams of jobs should run. Please check the start times of the 16 jobs in Director and verify your assertion of consecutive processing. Is there any constraint on the...

Typical Oracle script; loads itself into LD_LIBRARY_PATH and leaves out everything else.
What it should be is

You will just need to find where lib32 is - typically $ORACLE_HOME/lib

An exact match Search on -03113 got 13 hits. Perhaps one of these will help?

Unable to check this week (no QS). Hopefully someone else can. If not, I'll check at the end of next week.

Possibly that qsrtmngr is not running. This is the component that DataStage uses as a special case of a "real time interface" to invoke QualityStage jobs via the QualityStage plug-in.

The column names and/or sizes (or start column in the latter case) that you have used in your QualityStage file definition do not match those you have used in your DataStage job definition. Did you import them from the same place? Check both of them side by side, as it were.