Process for Performing a Non-Default JVM Reinstallation (Troubleshooting the JVM in an Oracle Applications environment)
(Doc ID 191123.1)
Last updated on NOVEMBER 26, 2019
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 21-Jun-2017***
This note should not be used on 11.2 and newer database installations. Please use "Safe repair/reinstall of the JVM Component in 11.2 and up (Doc ID 2314363.1)"
Assist users in reinstalling the core JVM, in the event the currently installed jvm has a problem, when no other options for a 'supported' or 'official' JVM re-installation are available. A 'supported' JVM re-installation process would involve the running of rmjvm.sql and initjvm.sql, but that action will remove ALL java objects in the database. The process mentioned in this document will attempt to replace the core JVM while leaving the user-defined java objects in the database untouched.
When Should This Process Should be Attempted?
The following statements should be true before deciding to follow this action plan:
1) The missing or problematic SYS-owned java object(s) was introduced by the $ORACLE_HOME/javavm/install/initjvm.sql script.
This determination can be made by checking your problematic/missing objects against the lists found in MOS documents:
<Note 181130.1> - List of Java Objects Introduced by INITJVM.SQL in Version 8.1.7.x
<Note 258054.1> - List of Java Objects Introduced by INITJVM.SQL in Version 9.0.1.x
<Note 258056.1> - List of Java Objects Introduced by INITJVM.SQL in Version 9.2.x
<Note 458247.1> - List of Java Objects Introduced by INITJVM.SQL in Version 10.2.x
<Note 458880.1> - List of Java Objects Introduced by INITJVM.SQL in Version 11.1.x
2) You have no way of replacing the user-defined java classes within your database so a full 'supported' JVM re-installation would be problematic.
Note: All efforts should be made to get hold of the java files and/or jar files for the user-defined java objects introduced into the database as part of your application so that a typical jvm reinstallation can be performed instead of using this method. This methodology should be considered a last resort.
If you are using Application Install - Version: 11.5.9 to 11.5.10
Please refer to <Note 468565.1> - How To Reload The APPS Java Class Objects In An Oracle Applications Environment
This should only be necessary if the JVM was rebuilt for some reason. The solution can also be helpful for customers that have some invalid APPS Java Classes.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!