DSXchange

You either need a loopback adapter installed or to have your network card connected to any network that can serve you an IP address.
Search the forum for more information.
I'm assuming that you have the DataStage server installed on the same machine.

That's why I asked you to look in the log for the actual parameter as passed - then I would almost certainly have suggested escaping the characters that are meaningful to the shell. So, well done for solving it.

I'd search for a *.bad or *.log*bad file generated by sqlldr.

Everything currently available in jobs and job sequences and routines and all the other bits still works in version 8.0.

There are some good new bits also.

If you think the product should work differently submit an enhancement request. There's a forum here on DSXchange for doing that. You could, of course, detect the condition in a job sequence and trigger some remedial processing, email notification, or whatever - even abort the job sequence. Personal...

Show us precisely what you have done.

Also open the "job starting" event from the job log and show us the actual value used for the parameter.

Chances are you've not gotten the quotes right in the syntax for the IN clause.

Load Immediate = No

This means that the control and data files are generated but the loader is not invoked.
It has done precisely what you asked.

My thought is that you are using server job thinking. In server jobs a "fatal" error causes the job to abort. Not in parallel jobs, however. An operator (player process) may abort, but its section leader and conductor process do not. This enables control to be maintained, and clean up to be performed.

Did you really mean handle_null() ?
Or maybe you're replying to a different post?

DataStage has NLS set, and therefore requires that NLS_LANG be set for Oracle.

In the Modify stage the format string is given in square brackets, the input argument (field name) is given in parentheses. For example

Note that minutes are specified as %nn, not %mm.

To answer my question open the Administrator client, open the Parallel tab in your project properties, and determine the date, time and timestamp format strings recorded there. These are the defaults for your project. Chances are that the default date format is "%yyyy-%mm-%dd", which follows the ISO...

Can you try it from a different client machine, to isolate the possibility that it's the dsadmin executable (or one of its related dlls) on your machine?

Yes you do, it's immediately under the File property. And it's a mandatory property, so it will be there. It's only possible values are Overwrite and Append.

Version 8 is still very new. Bounce it off your support provider, supply a reproducible case, and let us know the outcome.

Have you specified Char with no length in the table definition? Some databases interpret that as Char(1).