DSXchange

Often this type of problem can occur from incorrect DLLs in the DataStage client software and a re-installation can solve the problem. In many installations software updates are automatically applied and they can, occasionally, overwrite libraries with older/newer versions than what DataStage expect...

That message is the result of some other problem and not the cause of the problem itself. To analyze the real problem you'll have to post the other error messages as well. The message is just an informative one. Try doing a "reset" of the job and looking at the log entry starting with &quo...

How big is your /tmp or other temporary disk and how much space is left there? Also, in your project directory, how many Mb or Gb are available?

P0 and P1 are partitions 0 and 1, "OP" are operators. The confusions stems from a sequential operator that doesn't run on both nodes and operator combination of stages at runtime.

There are those caveats, but one doesn't need a cpp compiler installed in order to get a job running on a given machine.

This week had some classic bad SMS-style posts. I've started to ignore them; not really a nice thing since the questions asked are usually important to those asking but I draw the line somewhere...

I disagree, the cpp compiler does not need to be installed on production systems.

One of the sequential file settings is for fixed width output, then make sure you don't have any VarChar() columns.

Offhand I can only think of missing libraries being an issue with an object file compiled and loaded on machine A and then run on machine B, assuming the same OS is running on both machines.

Just define the correct character set for the data you are reading, that is usually enough. The only time in normal processing where the content of the data really plays a role is when interpreting numbers (i.e. the Germans use a "," for a decimal point) and sorting texts - the collation o...

I guess my answers there weren't good enough.

Is "Customer" in the source Sequential_File_9 file declared as VarChar(1)?

Nice link, thanks!

Field "Customer" is not a varchar, that data type does not give that error message.

It means you have a CHAR field defined, but there aren't enough characters in the file to fill it.