Hi All,
I am trying to design a job to trap my database rejected records like that :
SourceStage----readlink---->TransformerStage-----insertlink----->TargetR
SourceStage----readlink---->TransformerStage-----insertlink----->DBMS
rejectlink
SeqFileStage
So, I have checked the box "Reject Row" for the link to the reject file.
The job does reject the records into the flat file but it also generates a warning for every rejected records!!! Then, after 50 warnings, it aborts.
Is there any way to avoid all these warnings??
I was expected to get only one warning indicating that N rows have been rejected.
Thanks
Josy
Reject handling sybase
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
Josy,
In the constraint, instead of marking the row as the reject row, you could do something like this:
DSLink4.DBMSCODE <> 0
You can find DBMSCODE by right clicking in the constraint menu, pick Link Variables, then Outputs, click on the plus sign next to the link name and you'll see DBMSCODE.
Good Luck,
Tony
In the constraint, instead of marking the row as the reject row, you could do something like this:
DSLink4.DBMSCODE <> 0
You can find DBMSCODE by right clicking in the constraint menu, pick Link Variables, then Outputs, click on the plus sign next to the link name and you'll see DBMSCODE.
Good Luck,
Tony
Re: Reject handling sybase
No. Your Target stage is generating the error messages and it will do so regardless of the presence of a Reject Row. All the Reject Row does is allow you to capture the rejected data and (as a special added bonus!) automatically logs the number of rejected rows.josy wrote:Is there any way to avoid all these warnings??
I was expected to get only one warning indicating that N rows have been rejected.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
Re: Reject handling sybase
Thanks for your reply.chulett wrote:No. Your Target stage is generating the error messages and it will do so regardless of the presence of a Reject Row. All the Reject Row does is allow you to capture the rejected data and (as a special added bonus!) automatically logs the number of rejected rows.josy wrote:Is there any way to avoid all these warnings??
I was expected to get only one warning indicating that N rows have been rejected.
But is there any way that the job rejects the records in the "Reject link" without generating warnings for every single row rejected?
Regards
Josy
Josy - That was basically the question I was answering and, unfortunately, the answer is still no. Your target stage is the one generating and logging the warnings. This will happen with or without a Reject link.
Not to be facetious, but the only thing you can do is everything in your power to ensure your data will not cause errors before sending them off to the database - making sure required fields are not null, you are not creating duplicate records, etc. Because when they do create problems, those problems will be logged.
Not to be facetious, but the only thing you can do is everything in your power to ensure your data will not cause errors before sending them off to the database - making sure required fields are not null, you are not creating duplicate records, etc. Because when they do create problems, those problems will be logged.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers