My Oracle Support Banner

OJVM Datapatch failure with "ORA-04020: deadlock detected while trying to lock object" leading to JAVA, XDK and Spatial Invalidation (Doc ID 2992604.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.20.0.0.0 and later
Information in this document applies to any platform.

Symptoms

After applying the OJVM RU 19.20, datapatch log log shows deadlock errors for one of the PDB.

Leaving several objects and components INVALID including JAVA, XDK and Spatial.

And this error is also observed whenever they try to recompile any of the invalid Java class:
"ORA-04020: deadlock detected while trying to lock object"

call sys.dbms_java.loadjava('-v -f -r -s -g PUBLIC rdbms/jlib/aqapi.jar')
*
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-04020: deadlock detected while trying to lock object
SYS.oracle/xml/parser/v2/XMLDocument

-----------------------------------------------------------

@?/md/admin/sdoloadj.sql,

call dbms_java.loadjava('-resolve -synonym -schema MDSYS -grant PUBLIC
*
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-04020: deadlock detected while trying to lock object SYS.oracle/xml/parser/v2/DocumentBuilder
-----------------------------------------------------------

 

Changes

 Applied 19.20 OJVM RU Patch to Multitenant DB.

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
Changes
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.