i have a source stage (oracle), a transformer and 3 target oracle stages. My requirement is that i have to capture rejects of first target ONLY into second oracle table. I tried using otherwise in transformer (with the link ordering as first target, second target reject table, third target),but it didnt seem to work, coz once the same row is accepted into another target table, it will not be considered a reject anymore. (surprisingly, according to manuals the link marked as 'otherwise' should capture rejects of output links ABOVE it in link order, but it doesnt in my case.
Also, i tried to use linkname.REJECTED in the constraint for the second reject table link, but it seems this is not available in parallel jobs, though the manual says i can use it. I am getting a syntax error when i use it..
anybody who did this, please help me out. Thanks.
P.S: Now most might wonder why i am not using the direct reject link of the target table and why i am using another target oracle stage to capture rejects..well, my objective here is to just capture the row_id's, job name, table name details into this reject table, so i can just lookup the row_id in source to troubleshoot the error.
capturing rejects in px jobs
Moderators: chulett, rschirm, roy
Re: capturing rejects in px jobs
Can you post the syntax error for:
though I may not be able help U much ..jreddy wrote: Also, i tried to use linkname.REJECTED in the constraint for the second reject table link, but it seems this is not available in parallel jobs, though the manual says i can use it. I am getting a syntax error when i use it..