In the PX I see link variable -->output -->Otherwise in the transformer. But I dont understand "What otherwise is suppose to achieve". The manual is sometimes difficult to follow.
What the job needs is the following:
1 - Do insert only without clearing in the target if COL_ID is not null.
2 - In the Error Table capture rows that are null for COL_ID or any row rejected on the Target table.
How do I capture the rejects besides the Null for COL_ID in PX and send it to the Error table? Any guidence would be much appreciated.
In px, database stages support reject links. You need a link coming out of your target database stage going into the error table. This way two links will be feeding to the error table. One from the transformer where the null checking is done and the other from your target database stage if the insert fails.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
No problem. Use another DRS stage to load the same error table. Or collect your rejects in a single file and then load it to the error table in another job or so.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
DSguru2B wrote:No problem. Use another DRS stage to load the same error table. Or collect your rejects in a single file and then load it to the error table in another job or so.
I thought that I could create a reject link going to a seq file and in another job used this DataSet file to load into the Error table however,When I try to create a link from the source stage (Target table ) it give a message
The source stage does not support non-reject output links whilst it has input links
What if I checked the little box in the transformer that says otherwise / log - where I put the constraint for if not null then load into the target. then get a reject link out of transformer to a dataset. Would it then capture rows rejected other then the not null into this link?
Database rejects will NOT go down the reject link of a Transformer stage.
The rejects link (which is NOT the same thing as the Otherwise/Log link) handles input rows that cause an exception in the stage, for example an attempt to divide by zero or to take the square root of a negative number.
Database rejects are captured in the reject link of an Enterprise stage. Try using the SQL Server Enterprise stage instead of the Dynamic RDBMS stage.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
