DMSTOOL Does Not Report Any OC4J Metrics On Second Instance
(Doc ID 394710.1)
Last updated on JULY 10, 2024
Applies to:
Oracle Fusion Middleware - Version 10.1.3.0.0 to 10.1.3.1.0 [Release AS10gR3]Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
Certain DMS (Dynamic Montoring) metrics are not showing for any other instance other than primary instance in Oracle Application Server (AS) Cluster.
Steps to Reproduce
Node 1:
- ORACLE_HOME_1
- Loaded installer
- Select "Advanced install"
- Select "Integrated Web Server, J2EE Server and Process Management"
- Selected "Configure this as an Administration OC4J Instance"
- Instance Name: IAS1013J1
- Default instance: home
- Configure this instance to be part of an AS Cluster topology ipaddress: <IPADDRESS:PORT>
Node 2:
- ORACLE_HOME_2
- Select Advanced install
- Selected 'J2EE Server and Process Management'
- "Configure this as an Administration Instance" - deselected
- Instance name: IAS1013J2
- Default instance: home
- Cluster topology info: ipaddress: <IPADDRESS:PORT>
- Selected "Access this OC4J server from a separate HTTP Server"
The DMS statistics can be dumped for the JVM on the first install (ORACLE_HOME_1)
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |