How to Reload the JVM in 12.1.0.x
(Doc ID 1612279.1)
Last updated on APRIL 05, 2021
Applies to:Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup 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 as Oracle 12c non-multitenant database on UNIX and Windows.
There are similar notes for previous releases:
***Checked for relevance on 23 Apr 2018***
Fully remove and re-load the Oracle JVM component within an existing non-multitenant database. Not appropriate when there is customer or non-Oracle maintained java code that should be retained. For that case, "Safe repair/reinstall of the JVM Component in 11.2 and up (Doc ID 2314363.1)" should be used instead.
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).
If you have any of the following optional database components installed, they may need to be re-installed after following the steps in this note in order to reload their java dependencies:
- Oracle Multimedia (ORDSYS, ORDIM)
- Oracle Spatial (MDSYS)
- Oracle Warehouse Builder (OWBSYS)
1. Starting with Oracle Database 11g, the Data Mining Option is automatically installed and is tightly coupled with the database. The objects are no longer installed into the DMSYS schema but are owned by SYS and no longer have a dependency on the OJVM.
2. Starting with Oracle Database 12c, the Expression Filter (EXF) feature which has a dependency on the OJVM is de-supported and no longer installed with the database.
Fully removing the JVM removes ALL user owned JAVA objects, such as APPS schema objects. If such objects are present one should consider using "Safe repair/reinstall of the JVM Component in 11.2 and up (Doc ID 2314363.1)" instead of the current document. Otherwise, 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
2) ORA-29516 java.lang.UnsatisfiedLinkError sun.net.PortConfig.getLower0
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