DSXchange

Why 'remove' them? What is the NLS_LANG setting of your Oracle database? Is your DataStage install NLS enabled?

What exact version of the Oracle client is installed on the DataStage server?

If we're still talking the Server stage, its behaviour depends on the 'mode' setting - Manual or Automatic. Manual means create the .ctl and .dat files and nothing more. Automatic performs the actual load without instantiating those files.

What value were you expecting to get from that macro? How about using the DSJobName macro instead?

In other words, search the forums for UNNEST to find the syntax that will help.

Then what makes you think you can use the DSJobInvocationId macro? What are you trying to accomplish here?

Did you 'check' this suggestion? Putting an expression in a trigger isn't going to help as you can't actually change the $CommandOutput value from there.

Is this a multi-instance job? Did you supply an Invocation ID when you ran it? Post your derivation for that column as well, please.

To capture output, search for "COMO ON" and you'll find "COMO OFF" as well. Output will be written to the "&COMO&" directory in the attached project.

Trying to.

Hmmm... none of those are 'unsupported'. According to the docs, it doesn't support: BLOB, FILE, LOB, LONG, LONG RAW, MSLABEL, OBJECT, RAW, REF or ROWID.

One of those must be in your job or target table. Is this a runtime or compile time error?

Not from the command line.

The latter.

Search the forums for "not found in input schema" and see if any of those matches help, this has been discussed here before.

Or just put the commands in a ".bat" or "batch" file, the Windows equivalent of a shell script.

Sounds like you're doing this directly in the Loop Definition "To:" field and, while this can work in a Trigger expression, you cannot do it directly in the Loop Definition. You'd either need to send this in as a job parameter to the Sequence job and use the job parameter in the Start Loop...