Handling rejected Records

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Srilakshmi
Participant
Posts: 2
Joined: Fri Apr 28, 2006 12:45 am
Location: Hyderabad
Contact:

Handling rejected Records

Post by Srilakshmi »

Hi ,
I have got a query. Iam new to parallel extenders. The source and target is oracle . How do I handle the rejected records from the source and how do I reprocess the rejected records.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

The source won't have any rejected records, but when writing to the target in PX you can (in most cases) put a link coming out of the target stage that will contain the rejects. This is documented in the Parallel Job Developer's Guide in the section for the particular database stage.
rony_daniel
Participant
Posts: 36
Joined: Thu Sep 01, 2005 5:44 am
Location: Canada

Post by rony_daniel »

ArndW wrote:The source won't have any rejected records, but when writing to the target in PX you can (in most cases) put a link coming out of the target stage that will contain the rejects. This is documented in the Parallel Job Developer's Guide in the section for the particular database stage.
Hi ArndW,

If my source stage is a sequential file stage and suppose I have a date datatype filed in it. Some of the records in the source has invalid date value (say "2006-02-31"), then those records are droped at source stage itself. Can we not call these records rejects at the source?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

That's a different question. The OP's source was Oracle - you don't get any rejects from a SELECT statement.

With a Sequential File stage you can have a rejects output link which captures, in raw format, any row that does not satisfy the metadata of the primary output link. Without a rejects output link these rows are, as you noted, dropped (or you can abort the job). Use the Reject Mode property (in the Options group) to determine disposal of such rows.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Srilakshmi
Participant
Posts: 2
Joined: Fri Apr 28, 2006 12:45 am
Location: Hyderabad
Contact:

Post by Srilakshmi »

Hi Arnd,
My first question is answered. my second question is how are the rejected records reprocessed.
Thanks
sanjay
Premium Member
Premium Member
Posts: 203
Joined: Fri Apr 23, 2004 2:22 am

Post by sanjay »

Hi
If record is rejected due to date invalid. wht is the process u have . I mean whether u will correct that record.

Sanjay
Srilakshmi wrote:Hi Arnd,
My first question is answered. my second question is how are the rejected records reprocessed.
Thanks
vmcburney
Participant
Posts: 3593
Joined: Thu Jan 23, 2003 5:25 pm
Location: Australia, Melbourne
Contact:

Post by vmcburney »

You've got to assume that if a record is rejected that reprocessing it will have the same result, since the data has not been changed. If you are changing data then you are manually altering it to differ to what is in source systems which is a dangerous path to take.

Have a look at my data quality firewall blog on how to get some meaningful metrics out of your reject links and how to build rules to keep or drop invalid rows.

The best fix is to go back and fix the problem in the source system and pick up the change through normal extracts or change capture.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

DataStage does not process rejected records automatically in any way. It delivers them onto the rejects-handling output link of the stage in question. For Sequential File stage at least, the record is delivered as Raw - you can further process these rows by converting from Raw to something else, but remember that the row is there in the first place because it did not match the given metadata. You can certainly convert to string, and write to another text file.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply