DSXchange

No-one here can really help. You have to track that person down and have their authentication to IBM support services transferred. Even if anyone here had a hack that could defeat the Information Server authentication mechanism, I doubt that they would be willing to admit it publicly. I certainly do...

Does the metadata on the input and output links of the Aggregator stage indicate that either of these fields (or any other) is nullable?

Is it the DataStage server or a database server that is "getting crashed"? And what, precisely, does "getting crashed" involve?

Use an "In-band null" - a value that is valid for the data type, that represents null and that will not otherwise appear in the data. Convert this to an actual null in a downstream Modify stage using handle_null() or a Transformer stage.

Target field has min=8, Source field has min=0. That, I'm guessing, is where the mismatch has been detected. Is one a Char and the other a VarChar?

Can you be totally sure that /tmp has not become full even ever so transiently?

Can you set the path of the temporary directory to somewhere else?

Obviously it does exist, as your inspection of the generated OSH reveals.

Has this job been modified from an earlier one, perhaps using copy/paste?

Without seeing your job design and/or generated OSH it's not possible to offer any more advice - you will need to do some detective work.

You can install side by side. Change your 7.5x2 to use a different shared memory key.

Is the data type of the field/stage variable Date or Timestamp?

You might also review this post

Moderator: please move to server forum

Somewhere there's a VarChar(255). Examine the generated OSH to see if you can spot it. Otherwise please post your job design.

Why do you think changing the NLS map would resolve this? The map does not affect SQL data types.

Perhaps there is an unneeded space in the pathname (or perhaps you put this in for emphasis or inadvertently when applying a color tag). "Shared library failed to load" messages can mean that the shared library search path (LD_LIBRARY_PATH or SHLIB_PATH or LIBPATH) environment variable needs more en...

How, precisely, are you "checking" in the project directory? I have COMO files many MB in size (mainly trace files, admittedly).

Look in the configuration file.

If the fastname property has the same value for all nodes, then you are on an SMP configuration. If there are differences, then you are on an MPP environment.

This changes a bit if the hardware is a grid, where the configuration file needs to be dynamic.

Note: if your DataStage server is on Windows, then you will not have a .odbc.ini file - instead, ODBC.INI is a Registry entry. It is maintained using the ODBC Administrator (odbcad32.exe) on the DataStage server machine.