DSXchange

Reject the records on code=1, write to a file/table. Use this file/table for lookup for the second run.
Further Runs depend on your requirement.
So what is the case for for third,fourth,.... runs.

Thanks Ray. could you please give an example or two where the above assumptions may not hold good/valid. Or did I miscommunicate regarding backstage processes.
Please correct me.

I commend on Joining the tables in the sourcing query, which is faster & efficient. If a join stage is used, it will burden Perfomance as there will be more backstage processes running. To design the job more simpler(visually) & improve performance all the possible logics(Business Rules) are...

It has been discussed umpteen times.
Please do search.

Log into Unix Server

Container is used as Seq ---->>Shared_container---->>>Seq.file.

But in Link mapping, no Links are visible.

I have created a parallel Shared Container having OE---->Copy====>>1.Seq file 2.Dataset. And would like to use as Seq--->>Container--->>seq. In the Container properties page, Map to Link drop down menu is not displaying any Links in container. As we can see from design, it has 3 links. Any idea for ...

Another way to handle complex queries would be to create views in source DB & fire SELECT * FROM VIEW, so query would fetch the required fields.

Just Curious. Does this frequent Abort & Kill affect the Job performance in the Long Run?

And whether the Job should start from previous abort point( Check Point Run) OR Start afresh

Did you try searching for the same error messages in the Forum..

Some leads for you:

viewtopic.php?t=118664

viewtopic.php?t=122642

Thanks for you posted the Error mesage in the first post !!!!!
Everybody here is to help you.

Are you trying to connect to Datastage from Oracle or while running the job your were thrown this error.

Could you throw light on the Metadata for the columns.
Try with declaring the Nullable field as varchar2.

Aggregator stage is not feasible for Characters but only for Numbers.

Please eloborate on Job design.

Addendum to d.r.murthy's post:--- Also there is difference in the processes in backstage. Px has a PX engine runnning a OSH script, whereas Server jobs run by BASIC programs. Summing it up, One can ask for what is the commonality between PX & Server Jobs.And the answer is 1.both are from the IBM...

Try to read the Records from Data Viewer. If your able to view through Data Viewer, then the schema and other Credentials are supplied correctly. If there is any error, that would be displayed in the error message.