primary key constraint to be considered as a warning

dnat · Post by **dnat** » Sun Jan 03, 2010 11:53 pm

I have a job to insert records into a target table with oracle sequence.next val value for the primary key. The oracle sequence is cyclic, and if i get the primary constraint violation for few number of records(ex 50 records out of 1 million), then i dont want to abort the job, rather i want to run the job for 1mil-50 records..

how can i do that.

also apart fromd atastage log, how can i capture the records which got errored out?

chulett · Post by **chulett** » Mon Jan 04, 2010 12:06 am

Set your warning limit appropriately when you run the job and set up a Reject link from the OE stage to capture the problem records wherever you like.

dnat · Post by **dnat** » Mon Jan 04, 2010 9:31 pm

will the job not abort if it is a primary key violation error?

chulett · Post by **chulett** » Mon Jan 04, 2010 9:38 pm

What does your testing show?