My Oracle Support Banner

Scenario failure with ORA-12838 cannot read/modify an object after modifying it in parallel (Doc ID 2630734.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Financial Services Behavior Detection Platform - Version 8.0 and later
Information in this document applies to any platform.

Symptoms

While running the scenario in one of our upgraded 8.0.7 environment. The issue is coming consistently for a particular segment even after multiple reruns. 
Scenario - ML-ChkMiSequentialNumber-fCU
Type: Sequence Matcher
Focus- Customer
Version: FCCM 8.0.7
Server: Exadata

Scenario Job Log
Error Msg :-> ORA-12801: error signaled in parallel query server P182, instance x042db02.svr.us.jpmchase.net:xuy04aml2 (2)
ORA-12829: Deadlock - itls occupied by siblings at block 2766818365 of file 1024
Error Msg :-> ORA-12838: cannot read/modify an object after modifying it in parallel
11/23/2019 21:01:19 FATAL : Thread ID = 140684136806144: Sequence Matcher: File = mantas.cc: Line = 476: caught exception:
ERROR: { module: Sequence Matcher } { subsystem: BREAK_BINDG_TEMP32456701 } { message: ERROR-> Failed to commit the query UPDATE BREAK_BINDG_TEMP32456701 SET VALUE_TX = :VALUE_TX WHERE BREAK_ID = :BREAK_ID AND BINDG_NM = :BINDING_NM

Cause

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
Symptoms
Cause
Solution
References


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