How to properly remove the JVM from 11gR2 and newer standalone database instances
(Doc ID 2541088.1)
Last updated on DECEMBER 13, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
The JVM is installed by default and yet many customers do not even use it. There are other components that use it such as Oracle Multimedia, Oracle Spatial or OLAP but if those components are not used then it makes sense to remove it, especially if you do not wish to schedule downtime every quarter to apply an OJVM Patchset Update. In fact, this is the most common reason to remove the JVM. The purpose of this note is to provide a certified method for removing the JVM Component and the 2 or 3 other Components that were installed with it. Be aware that it will also remove the Java objects from any other schema.
If you have any of the following optional database components installed, they will need to be removed BEFORE following the steps in this note or a standard removal of these components afterwards may fail since the specific removal scripts may depend on dbms_java.drop_java which will have been removed with the JVM:
Oracle Multimedia (ORDSYS, ORDIM)
Oracle Spatial (MDSYS)
Oracle Ultra Search (WKSYS)
Oracle Data Mining (DMSYS)
Oracle Warehouse Builder (OWBSYS)
To identify any JVM dependent schema (Oracle Provided or custom) that will be impacted by a removal of the JVM, use the following query:
SELECT owner, object_type, status, COUNT(*)
WHERE object_type LIKE '%JAVA%'
AND owner NOT in ('SYS','OJVMSYS', 'EXFSYS')
GROUP BY owner, object_type, status
ORDER BY owner, object_type, status;
Additionally, this note is not intended for removal and then reinstall of the JVM. If you intend to reinstall the JVM immediately after removal in an attempt to repair the JVM, then follow :
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