Don't want to abort job due to integrity constraints or any

getsatish_gk · Post by **getsatish_gk** » Sat Sep 06, 2008 3:27 am

Hi,

Job fails While loading into oracle table if referential integrity for some records could not meet, thats fine. i can take those records into peek stage.

But i don't want to abort the job.

I am using reject records=true at oracle enterprise stage and passing into sharecontainer where it logges into some other table.

Please advice.

ray.wurlod · Post by **ray.wurlod** » Sat Sep 06, 2008 3:53 am

Prevention is better than cure. Rows that would cause a referential integrity violation should never reach Oracle.

getsatish_gk · Post by **getsatish_gk** » Sat Sep 06, 2008 3:59 am

Don't even want to insert those records instead i am happy to collect in peek stage. but can affort to abort the job.
I hope you have the answer for this.

getsatish_gk · Post by **getsatish_gk** » Sat Sep 06, 2008 3:59 am

I mean, Don't want to abort the job

ray.wurlod · Post by **ray.wurlod** » Sat Sep 06, 2008 4:43 am

There's no such thing as "collect in Peek stage".

Your ETL stream should (must) check that RI will not be violated. End of story. What you do with those rows is immaterial, so long as you don't send them to the target table.