DSXchange

Keep in mind the fact that in Server jobs the transformer (the active stage) always "generates the error" regardless of the actual source of the problem.

Sorry, but you need no quotes and no dollar sign as a simple search of the forums here would reveal.

If you installed the hex editor on your client PC, then you'll need to copy the file there before you can look at it. You can also do an "od -h" directory on the UNIX server if you like.

Simply getting more records out of the join than went in isn't an error, per se. Please explain the nature of the "join" you are doing.

First thing you always need to mention for something like this is - is this the first time you are attempting to use the OE stage and it just doesn't work or have you used it successfully in the past and this is a new error? For the latter, does it occur in only one job or all jobs that use the stage?

Other than the idea already given? No. Check the docs.

Then I would think you forgot to install this optional plugin when you reinstalled the datastage. For 7.x I would say "Rerun the install and make sure it is selected"... I assume that still works in 8.x.

Sorry, but you need to continue the conversation there, not start all over again because you didn't like the answers so far. First thing that's going to happen is those "constructive inputs" will be repeated or we'll have two compeating threads on the same subject. No thanks. And that's al...

Welcome. Node is a logical rather than a physical concept and while the number of CPUs plays a part here it is not equivalent to a CPU. Think of it as the number of "invocations" or "instances" or "copies" of a job to run, each one sharing the workload and transforming ...

Well, at least they match which is a Good Thing but not necessarily always the case, hence the question. And the only reason I brought it up is because I personally have seen intermittent core dump issues like this myself caused by a buggy Oracle client. So as you're trying to solve this, keep that ...

Seems to be. Try.

Try changing your metadata to what it found it to be.

Ok... wrong choice of words. What version of Oracle are you connecting to? I can't answer your question until you answer mine. And just to double-check, your 'lookups' are all from hashed files, yes?

The "OCI" stage is a Server stage. For PX you would use the OE or Oracle Enterprise stage.

I'm curious why you "need" to do this, care to share? Perhaps there is a more better solution to whatever problem you are trying to solve.