My Oracle Support Banner

EDQ - Multi EDQ Execution Generate DB Session Blocked (Doc ID 2907099.1)

Last updated on NOVEMBER 08, 2022

Applies to:

Oracle Financial Services Customer Screening - Version 8.0.8 and later
Information in this document applies to any platform.

Goal

EDQ 12.2.1.4.1

Steps to reproduce :

Step 1 : Execute CS Batch in 4 EDQ servers at the same time

Step 2 : Execute them in parallel

Step 3 : Check if any error as below.

Expected result :

Multi edq in parallel should work without any issue

Issue Encountered :

SEVERE: 01-Sep-2022 19:32:25: ORA-04021: timeout occurred while waiting to lock object EDQPRE4_EDQRESULTS.DN_T29968
[INSERT INTO dn_t29968 (output_group_id, output_group_size, output_relns_produced, review_relns_produced, total_working_records) VALUES (?, ?, ?, ?, ?)]
java.sql.BatchUpdateException: ORA-04021: timeout occurred while waiting to lock object EDQPRE4_EDQRESULTS.DN_T29968

Note : 
This issue occurred because the parameter commit_wait of the DB has set with NOWAIT value and if its is changed to WAIT it works but it takes same time in parallel than executing 1 by 1 in serial mode. At this point, it is clear that the problem of the lock objects is due to the commit in the redo logs, but cannot deactivate it in Production environment since it has 1 DB for EDQ and FCCM, and  need to have it active for FCCM.

Trying to process 16 million customers and if that is done in serial mode it takes more than 17 hours but need it to work in parallel

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.