Script to Check the Status or State of the JVM within a Multi-tenant Database
(Doc ID 2347527.1)
Last updated on MARCH 31, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterOracle Database Exadata Express Cloud Service - Version N/A and later
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 Backup Service - Version N/A and later
Generic UNIX
Goal
To get the status of the Oracle JVM component in a CDB/PBD set up by using Oracle provided "catcon.pl" script.This will collect the JVM status in all containers (CDB's and PDB's) in single step rather then running the script individually in each containers. This is equivalent of the script in the <note 456949.1> and its just that it will be invoked using "catcon.pl" script.
Note: The queries in this script are restricted to just the relevant parts of the Oracle DB JVM Component. It does reflect the status of other components that may depend on the JVM nor does it reflect the status of java objects in customer schemas. Once the JVM Component is valid, you can modify the individual queries to check the other components or customer objects but the DB JVM Support team is not the proper team to investigate any of those issues.
Solution
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
| Goal |
| Solution |
| References |