DSXchange

It's not a DataStage issue.

Your number, with thousands delimiters, is 322,665,901,919,233,341,505,776,723,281,119,128,249

This makes it clear that it has 39 digits.

You can simply NOT store this as NUMBER(38), which can accommodate a maximum of 38 digits.

You MUST use a larger data type.

Stop trying to put a 39-digit number into a field with precision 38.

Of course you CAN use SQL - via an ODBC driver for text file. Just don't expect it to be fast. But for sufficiently small text files performance may be acceptable.

The newer ORAOCIBL stage doesn't exist in version 4.x, however. To quote Mr Duke, the ORABULK stage serks!

The transition point is version 7.1; it's in this version that IBM claim to have enhanced performance of the Transformer stage. So, how good is your C++ compared to theirs? You can view the generated C++ if you wish; it's in a subdirectory called RT_SCnnnn, where nnnn is the job number. (RT_SC = run...

Compiling a parallel job generates osh and, possibly C++ source code that is compiled and linked and callable at run time. When the job starts the generated OSH and the currently selected configuration file are used as input to a set of execution instructions called the "score", which contains the o...

A zombie doesn't need to have any Repository locks, neither does a background process. It can simply be unable to die because it is unable to notify its (killed) parent.

As I understand it, the output should appear asfrom that input.

Get them to send two files - the data file then another, possibly empty file. Wait for the second file, then process the first. Given that they don't send the second file till after they've sent the first, you can be confident that all of the first file has been received when the second file arrives...

What's different between DEV and UAT?

<Deep Thought>
FORTY TWO
</Deep Thought>

Through Director I wouldn't bother, because I know that DataStage keeps all these statistics in the Repository database from which I can query them (using Director) any time I please.

Where required, I run a job that archives the logs prior to purging them.

Try it with Final Delimiter = End

Can you advise the format settings from the server job Sequential File stage that writes this file?

Create a shell script that acts as a wrapper to sqlplus and picks up the password from an environment variable that you've set elsewhere earlier in the same process. You'll need a "here script" within the shell script to respond to the sqlplus "Password:" prompt.

DSP.Close is one of theirs.
COMMON size mismatch in subroutine "DSP.Close". means that there's a bug, an incompatibility, between their modules.
"They" need to fix it.