DSXchange

Very nice.

Do you have to? No. The wired driver doesn't need a client. The "non-wired" one does but if you have the client installed you should be using the native Oracle stages rather than ODBC.

So... why ODBC? To me that's the "access of last resort", hence the question.

Usually it means a client tool blowed up. Can we get some kind of clue as to the where / when you see this? Google would turn information up on this as well, I would assume, seeing as how it's "Windows stuff" rather than "DataStage stuff", really.

That's not really a pivot. You could "pre-process" the data into a form that the pivot stage would like however, I would assume. Or perhaps do this all with stage variables in the transformer.

I'm short on time (and brains atm) so will leave the gory details to others...

Let's find out! :D

And are you certain you need the second "2"? That tells it how many contiguous fields to pull.

So... this isn't something the validator would catch?

"guernseys"? Can you speak English please?

Is that the island, the cow or something completely different?

No, not an Implementer and fresh out of coconuts.

Never had a need to.

Why grep for "node2" when you don't have anything with that name in the config file?

OK, then use the "&" as the delimiter. You'll need to set up the maximum number of occurances as stage variables and see which ones get populated.

My uderstanding is that zero will generate that warning but then work as desired. Try it, let us know. There are two ORAUPSERT variables, make sure you don't have the TIME one set as well. That and make sure you're actually doing "upserts" rather than "loads". You never specified...

FAILURE: Code not yet implemented. Talk to support, see what is implemented you can use for this.

Field() should work, looks like a "space delimited string" to me.

Has your config file been blessed by that "validation / checking" utility? Whatever the heck it is called?