My Oracle Support Banner

OJVM in PDB Fails With ORA-29532:BootstrapMethodError, ORA-07445:[joevm_invokevirtual] or Other Errors When Moving to Newer Release or Patch Level (Doc ID 2488247.1)

Last updated on SEPTEMBER 01, 2024

Applies to:

Oracle Database Cloud Exadata Service - Version N/A to N/A [Release 1.0]
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Gen 2 Exadata Cloud at Customer - Version All Versions to N/A [Release All Releases]
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 19.23.0.0.0 [Release 12.1 to 19]
Information in this document applies to any platform.

Symptoms

The purpose of this note is to aid in identifying pluggable databases (PDB)s where the data dictionary has been corrupted by bug 28745878 and providing a solution for repairing such PDBs.  The subject of the note includes some common symptoms of this situation but it should be recognized that there can be other symptoms and that any of these symptoms may have other causes.  When present in a multitenant database (CDB), bug 28745878 can cause corruption of the system dictionary in a PDB when the PDB is created.  Even if the bug itself is subsequently fixed in the CDB, affected PDBs will remain corrupted until the solution given in this note is applied.  The corruption will typically be asymptomatic at first.  Only when the CDB containing the PDB has been upgraded to a new release level or patched to a new PSU or RU level in which java system classes have changed are symptoms liable to be observed.  The symptoms therefore often manifest for the first time during the upgrade or patch post installation actions.  The corruption only occurs in PDBs that are created by plugging a non-CDB into a CDB in which bug 28745878 is present.  Additionally, the corruption occurs only if long identifiers are in use in the CDB  but were not yet in use in the non-CDB.  When any of the symptoms described here occur in any other context, particularly in the root container, they are due to some cause other than bug 28745878.  The solution given in this note should not be attempted in such cases.  In particular the solution can cause irreversible damage if attempted in the root container.

After applying an OJVM PSU or RU in a Multitenant database the post installation steps in one or more pluggable databases fail with

ORA-29532: Java call terminated by uncaught Java exception: java.lang.BootstrapMethodError or ORA-03113 where the underlying cause of the latter as seen in the alert log or trc file is 

ORA-07445:[joevm_invokevirtual].

ORA-07445: exception encountered: core dump [eoa_mark_obj_as_needed()+590] 

When upgrading a Multitenant database the statement "create or replace java system" fails in a PDB with one of the above errors.

Other symptoms are also possible.  Any of these symptoms can also occur for other reasons.  See the Cause section below.

 

Changes

Upgraded or applied an OJVM patch on a Multitenant database.

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


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