How to Reload the JVM in 11.2.0.x

(Doc ID 1112983.1)

Last updated on APRIL 23, 2018

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2]
Information in this document applies to any platform.
*** Checked for relevance on 14-Nov-2017 ***


This note is obsolete and is superseded by "Safe repair/reinstall of the JVM Component in 11.2 and up (Doc ID 2314363.1)"

The actions detailed in this article are highly destructive and should not be attempted by novice users.  Additionally, the actions performed in this article make direct changes to the underlying data dictionary tables which should not be attempted unless under the guidance of Oracle Support Services (OSS).

As with all destructive actions, Oracle Corporation strongly advises taking a FULL COLD BACKUP of the database before these actions are performed.

If you have any of the following optional database components installed, they will need to be re-installed after following the steps in this note in order to reload their java dependencies:

Here are some Notes to assist with those installs.


    <Note:1283861.1> Reinstalling Spatial Java Class objects after reloading JVM


    Run the script as SYS, located in the $ORACLE_HOME/ORD/IM/ADMIN/initimj.sql, that will reload those classes.


    <Note:296187.1> How To Manually Install Oracle OLAP In  9i, 10g Or 11g Database After The DB Has Been Created
    <Note:332351.1> How To Remove  The OLAP Option In 10g And 11g

In addition, as removing the JVM removes ALL user owned JAVA objects, such as APPS schema objects, an export dump of all user schemas containing JAVA objects should be taken if required, so that these objects can be reloaded once the JVM has been re-installed (please see the note detailed below):

<Note:183825.1> How to Backup and Restore Java Classes and Privileges only

Oracle Applications customers should contact Oracle Support Services (OSS) rather than attempt the actions in this article, see the following note for the procedure to follow:

<Note 191123.1> Process for Performing a Non-Default JVM Reinstallation

It is not necessary to install the XML Developers Kit (XDK) or the XML SQL Utility (XSU) into user schemas unless specifically required by your application, as these products were included in the JVM from 10.1.0.x.

JVM removal or reload shouldn't be performed when following errors occur

1) ORA-29548 [classes.bin in binaries is older than the database]
2) ORA-29516 java.lang.UnsatisfiedLinkError
3) ORA-00600:[26599][1][195]


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms