Rejected rows

Archive of postings to DataStageUsers@Oliver.com. This forum intended only as a reference and cannot be posted to.

Moderators: chulett, rschirm

Locked
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Rejected rows

Post by admin »

Just a question, we have not gone completely live with our Datastage /
Redbrick applications. I am close to going live though, but something bothers me still.

It could happen that I try to load records that will be rejected - because
of foreign key constraints or data type mismatches, etc. I load most of
my data from text files.
How do you guys (and girls) normally handle rejected data ? Do you have an output link that receives all rejected rows ?

It should be easier doing it this way, than to try and isolate a record from a text file after it was rejected within a job.

Any ideas are welcome.
Thanks
Dirk


Dirk Moolman
Database Administrator
Reach Technologies
South Africa

www.thefuelgroup.co.za

"No pessimist ever discovered the secret of the stars, or sailed to an uncharted land, or opened a new doorway for the human spirit." -Helen Keller




==========================================================
This message contains information intended for the perusal, and/or use (if so stated), by the stated addressee(s) only. The information is confidential and privileged. If you are not an intended recipient, do not peruse, use, disseminate, distribute, copy or in any manner rely upon the information contained in this message (directly or indirectly). The sender and/or the entity represented by the sender shall not be held accountable in the event that this prohibition is disregarded. If you receive this message in error, notify the sender immediately by e-mail, fax or telephone representations contained in this message, whether express or implied, are those of the sender only, unless that sender expressly states them to be the views or representations of an entity or person, who shall be named by the sender and who the sender shall state to represent. No liability shall otherwise attach to any other entity or person. ==========================================================
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

If youre using the RedBrick stage, by the time errors occur its really out of DataStages control. Only if you automatically execute the rb_tmu command can you, in the same job, inspect the contents of the tmu error file, probably in an after stage or after job routine, or possibly in the controlling jobs job control code (this would be my preferred mechanism). If you delay executing rb_tmu - perhaps because you want to use rb_ptmu instead - then you need another mechanism (maybe another DataStage job started subsequently to the load) to identify whether any rows failed to load. Loading a Red Brick Decision Server database by means of INSERT statements via an ODBC stage is generally not the recommended approach, as Red Brick is not designed to be a transaction processing database.

-----Original Message-----
From: Dirk Moolman [mailto:dirkm@reach.co.za]
Sent: Monday, 22 October 2001 21:16
To: Datastage List
Subject: Rejected rows


Just a question, we have not gone completely live with our Datastage /
Redbrick applications. I am close to going live though, but something bothers me still.

It could happen that I try to load records that will be rejected - because
of foreign key constraints or data type mismatches, etc. I load most of
my data from text files.
How do you guys (and girls) normally handle rejected data ? Do you have an output link that receives all rejected rows ?

It should be easier doing it this way, than to try and isolate a record from a text file after it was rejected within a job.

Any ideas are welcome.
Thanks
Dirk


Dirk Moolman
Database Administrator
Reach Technologies
South Africa

www.thefuelgroup.co.za

"No pessimist ever discovered the secret of the stars, or sailed to an uncharted land, or opened a new doorway for the human spirit." -Helen Keller




==========================================================
This message contains information intended for the perusal, and/or use (if so stated), by the stated addressee(s) only. The information is confidential and privileged. If you are not an intended recipient, do not peruse, use, disseminate, distribute, copy or in any manner rely upon the information contained in this message (directly or indirectly). The sender and/or the entity represented by the sender shall not be held accountable in the event that this prohibition is disregarded. If you receive this message in error, notify the sender immediately by e-mail, fax or telephone representations contained in this message, whether express or implied, are those of the sender only, unless that sender expressly states them to be the views or representations of an entity or person, who shall be named by the sender and who the sender shall state to represent. No liability shall otherwise attach to any other entity or person. ==========================================================
Locked