Primary key violation and Deadlock issue

[SibaP]

Hi All

There were some jobs fetches Primary Key violation error and some other jobs fetches Dead lock error, Can anyone please help me with the possible Root Cause-RCA for this.

[Sruti_P]

Hi Siba,

If you enable bulk loader it will grey out the 2nd tab options " delete data from table before loading", only one tab can be workable here.

As both the options does same this while bulk loader being truncate. So you can go for the it - truncate.

Regards,

Sruti

[SibaP]

Hello Sruti, This truncate option can be applicable to nonrecurring jobs but what to do for recurring jobs ? Regards, Siba

[Sruti_P]

Hi Siba,

This a common error presuming the target as SQL. You can update the target in the mapping in the bulk loader tab as "Truncate". If the Truncate option is already enabled and you are still getting error you can increase the maximum rejects value in the form under the bulk loader tab with 1000 or more. It will write the duplicate values in BODS error log and will not write it in SQL DB but this will decrease the performance time of the job. If none of this is option for you the data has to be fixed or filtered from the source to avoid the PRIMARY KEY constraint.

Dead lock can be cleared by SQL DB ream you can connect with them and provide the updates of DB and the deadlock ID to kill it in DB side.

Regards,

Sruti

[SibaP]

Hi Sruti,

Thanks for providing such detailed explanation.

Actually the option "Delete data from table before loading" in Options tab in 2 Target tables (in 2 DF) already checked with row per commit 10000.

So while trying to check option Truncate in Bulk loader tab, the option "Delete data from table before loading" in Option tab has became unchecked.

So in this case what to do?

Regards,

Siba