DSXchange

Or know the rules. Auto gives: Round Robin if the link is from sequential to parallel or from parallel to sequential. Same if the link is from parallel to parallel with the same degree of parallelism, or Round Robin otherwise. Entire if the link is a reference input link to a Lookup stage. Hash if t...

You really do need to learn about the score - it's the single most useful diagnostic tool for parallel jobs. It's the osh that's actually run (which is almost certainly not the osh from your design). To get the score, set the environment variable APT_DUMP_SCORE. The score is the most recent entry in...

Have you tried using an ODBC stage rather than an OLEDB stage?

Not a function, but some stage variables. Make sure that the input data are sorted by the keys on which your "duplicate" decision is based, and detect whether each row is the same as or different from the previous one using the stage variables.

Yes

Post your score, so we can see where the modify operators are.

Disable operator combination, run the job again, and post the real error message.

Posting the same question more than once won't get any more or any better answers.

Please refrain from doing so. The other instance is here

myukassign wrote:Hi ray, I gone through the post and I found, i should change the characterset in the code page of the dsx header.

Is that correct?

Yes

Have you undertaken a Search of DSXchange for "Could not load dsstpora.so"?

Dependencies are added to job sequences when you add job activities from the Palette or the Repository. But it appears that this does not occur - or at least not reliably - if you copy/paste a job activity. This is probably a bug.

Marginally clearer. You have no option than to use two jobs. One populates the hashed file. The other uses it to feed the reference input link. It can not be readily achieved in one job. But it still appears that you're joining Table A to itself. What am I missing? If this is true, you could do it w...

Try fewer terms and "all terms". Maybe "job" and "migration" would be a good combination.

Open each of the supplied transforms and note the expected format of input.

Please also post a message showing how you resolved this, since you have marked the thread as Resolved.

Can you explain (in English, not DataStage) what this is intended to accomplish? What populates the hashed file? Is TableA the hashed file? Something like the following may be what you require. Source------>Transformer------>HashedFile (Table A lookup) | | V Source->Transformer->Table A ----...