DSXchange

Job design? How exactly are you using ODBC in it?

You need another set of eyes on site to check your work, everything you've posted looks fine so far. Not sure what else to tell you. What other settings are you using in the stage? Is "D_CAL" mentioned elsewhere, in your Sort Specification perhaps?

You are getting "the same error" when? Doing what? With what version of DataStage?

This is why you should start your own post rather than jump on the end of a similar one declaring you have "the same error".

It's not really all that general. It means that communication between your session and the database was interrupted. More than likely a network issue but could also be silly things like the instance being shutdown or some goofy sql core dumping - but that would be consistent rather than intermittent...

Possibly. Both the column names and data types must match for it to "map" properly. Do they?

Including the mentioned "D_CAL" column? Worst case delete the stage and set it up again from scratch.

Since you mentioned the OCI stage, is this also true for Server as well as Parallel jobs? That would be... odd.

How can a "business requirement" dictate a job design?

An ORA-03113 is not related to credentials. Did you lookup the actual error description, cause and action?

Holy thread necromancy, Batman.

Everything on the input link must exist on the output link.

We capture data from these views on a nightly basis and load it into staging tables in Oracle db. The quality of the data that we get is far from perfect. We've got all kind of problems - duplicate keys, null key values, domain integrity violations, data that is in clear violation of business rules...

What 8.x release are you running?

I'm trying to. You have to provide enough information so someone can help you. What "same error"? There's been no error mentioned yet.