How to Reload the JVM in 11.1.0.x
(Doc ID 457279.1)
Last updated on JANUARY 31, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.1]
Oracle Database Cloud Schema 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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
This article details how to completely de-install and then re-install the JVM in Oracle11g Release 1 on UNIX and Windows NT/2000/XP.
If looking for the same information with regards to Oracle 11g Release 2, please refer to How to Reload the JVM in 11.2.0.x (Doc ID 1112983.1).
SCOPE & APPLICATION
The actions detailed in this article are highly destructive and so 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 previously had the InterMedia (ORDSYS), UltraSearch (WKSYS) Data Mining (DMSYS), Spatial (MDSYS) or (EXFSYS) options installed, then these will need to be re-installed to reload their java dependencies.
Steps for reinstalling any of these components is addressed in:
<NOTE:472937.1> Information On Installed Database Components and Schemas
In addition, as removing the JVM removes ALL user owned JAVA objects also, 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 here.
<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 in unless specifically required by your application, as these products were included in the JVM from 10.1.0.x.
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