DSXchange

ODBC may or may not be relevant - if you are using the wired (thin) drivers, for example, it working means nothing. However, if you are using the thick (client-based) drivers for ODBC, that's another story.

:? I don't see how the two are related. There's a completely different message logged when a Sequence job is restarted with different parameter values, all it does is note the difference and move on. And it's not a fatal message or even a warning, it's a simple informational one. Searching the forum...

So, what have you done to prepare the way? Installed Oracle client? Edited your dsenv file? That should do it. Post the relevant section of your dsenv file if you're unsure you've done it right.

Note that it doesn't really "fix" anything, you've taken another path to your goal. As Shane noted, you "fix" the issue by leveraging the Index Mode option in the stage. For example you can emulate the typical process one would do outside of DataStage - drop the indexes, bulk loa...

Stage variables do not support nulls.

Yes, basically correct, it switches it back to a 'conventional' load using normal inserts and thus loses you any speed benefits you would get from a bulk load. It does, however, mean you don't have to futz with the indexes on the table. No clue how you set things up, just wanted to make sure you und...

Has the OCI stage ever worked? Meaning, did it work before and is broken now, or is this the first time you are attempting to use it?

Do you understand what "DIRECT=FALSE" means, does?

PI, HAL, MoFo and 411 all in the same post, not to mention 'eye-balled', 'smoking gun', 'hot ampin' and 'circle the wagons'. This amused me.

(HAL 9000, btw, unless you meant a much earlier model)

Ah... you mentioned 'Parallel' which I assumed meant something other than a Sequence job.

Have you contacted your official support provider for help with this? Seems like the next logical step to me.

8.1

OK, 'after stage' rather than directly in the transformer. Still, and again, why do it there as the only job 'status' you'll have at that point is Running.

Or the more traditional and perhaps easier to grok:

Too late in the 'Job Control' section as the job is already running at that point and any limit already set. Since you are running the job from the 'command line' I assume that means using dsjob yes? If so, simply adding -warn 1 to the command line will do the trick.