DSXchange

The privileges are required so that DataStage can determine the partitioning to be used when you specify a Partition Table property.

SELECT privileges to system tables are harmless; they do not allow you to break anything, and therefore should be granted by all but the most paranoid of DBAs.

It's not enough to check disk space "now" - you must check while the job is running. You can have lots of free space "now" that is all consumed while the job is running. From the Administrator client, at a time when you have exclusive access to the project, execute the command DS.CHECKER (this is th...

This approach requires careful setting of the Format in the target Sequential File stage; set both field delimiter and quote character properties to 000 and output just one VarChar column. Why aren't you using a Pivot stage? You may as well use a server job; what you are doing would be faster, and t...

These intermittent "terminated unexpectedly" with no further information are even more infuriating to try to diagnose than most intermittent errors. I think we need to begin a concerted campaign to make sure that the support organization gets to hear of every one of them in the hope that better diag...

The stage goes to DB2 and checks the partitioning of the table whose name you supply via the tool to the right of the partitioning algorithm. Make sure that an appropriate table name is given (typically the table you're proposing to load).

Search would have revealed to you that Decimal data are always displayed with leading an trailing non-significant zeroes, so that you can be sure that precision and scale are working correctly, and so that they can correctly populate fixed-width format files. Such decimal values can correctly be lo...

Have you tried multiple readers with delimited text files? Allegedly it became possible (version 7.5.1?).

... or a server Shared Container containing a server Transformer.

A server Transformer is not the same as a BASIC Transformer; one supports lookups and the other does not.

The documentation will tell you that these codes must be integers. You can add a Modify stage downstream; use lookup_string_from_int16() to convert your SmallInt (or lookup_string_from_int32() to convert your Integer) values to the string of your choice.

Looks like there's a problem with partial deletion of the Data Set.

Try deleting it using the GUI or orchadmin command before running the job sequence that populates it.

Are you using the same configuration file when populating the Data Set as when reading from it?

Version 7.5x2 may or may not run on Windows 2000. It is not supported on that platform and is not guaranteed to run there. It is supported only on Windows 2003. Some people have got it running on Windows XP, but again this is not a supported platform for DataStage server; only for DataStage client.

op4 and op5 look like buffers to me. These have probably been inserted to avoid deadlocks due to different throughput rates. The Sequential File stage (import operator) uses the C I/O STREAMS module, and is very fast compared to all other read mechanisms. Also, be very wary of rows/sec as a metric; ...

$ENV tells DataStage to load the value from the executing user's operating system environment - you would have had to set up the environment variable in that user's .profile file, for example. To have DataStage load the value you set up in the Administrator, make the default value of the job paramet...

It wasn't clear to me that that was a resolution - only something else that the OP had tried. Yes, it looks like it should have addressed the issue, but was it a satisfactory resolution?