DSXchange

No, I believe that the OP does not understand the behaviour of outer join.

Go into your job log, right click on the warning message, and choose "add rule to message handler". A local message handler is specific to this job. You can also create named message handlers that you can attach to multiple jobs.

Can you parse the field into separate fields* using substring then use a Pivot stage?

* You will need enough of these to accommodate the longest possible input string.

In a word, No.

Version 8 requires that multiple DataStage servers be on separate machines.

You can have version 7.5 and version 8 co-resident, however.

Investigate the Fold() function.

This is an alert message. Negative int64 values will not be correctly represented as uint64. You can force the data type to be int64 everywhere, or demote this warning to informational - because of what you are doing you know it will never be a negative number.

What's the data type in Oracle table itself? VARCHAR2(40)? Make the metadata in your design match what's actually in the table. You do this by importing the table definition and never editing it.

Poor design. Underpowered server. Unrealistic expectations. Bottlenecks in machine/network. Competing processes. To name a few.

Please disable operator combination so you can tell which actual stage is throwing this error. It is not appropriate to try to diagnose errors from APT_CombinedOperatorController.

I'm sure you've asked this in the past and had it answered. In any case someone has, and a Search should find it.

That, too. What do you want to achieve?

Import the table definition using Orchestrate orchdbutil. Use the imported table definition without modification.

The only valid check for null is IsNull() or IsNotNull().

I do not attempt to diagnose any message from APT_CombinedOperatorController.

Have you given the stage variable an initial value, as well as a derivation?