DSXchange

OK, please post the exact error message that orchadmin emits.

We need to see the exact wording of the error message that DataStage generates in order to be of any useful help.

We need to see the exact wording of the error message that DataStage generates in order to be of any useful help.

Introduce a job parameter to the job for the plant identifier. Replace the hard-coded plant identifier within the job design with a reference to the job parameter. To process all plants, create a loop in a job sequence the cycles through the plant identities (a Start Loop activity with a "list of th...

Learn patience. Particularly on weekends.

The ",9" following the name of the buffer operator tells you that the problem occurred on the tenth-named node in your configuration file (the nodes are numbered beginning from 0).

Your source data in the UAT environment contains a decimal number larger that the largest permissible integer (2147483647).

Why the semi-colon ?

If you have a network error you have to get the network error fixed.

Welcome aboard. A segmentation fault is memory-related, and can be caused by such things as trying to shoehorn too large a string into a column buffer (for example "ABCDEFGHIJKLM" into a Char(10) or VarChar(10) column would do it), trying to load a NULL into a not nullable column, and various other ...

Does this work with DataStage not involved in the process, for example in TOAD, SQL Navigator or sqlplus ?

You need to check permissions both in the project directory and also in the XMETA database.

Please note that the cache referred to in this document is not accessible from DataStage routines.

You can execute the AVAIL command as a TCL command. Edit (resulting from ag_ram's quibble): This will show total size of file systems and, most importantly for DataStage, available free space. The best way to determine space occupied by DataStage is through monitoring. Measure free space before and ...

Yes. Just.