GIMR (Management Database) Registers Into Same Service that the Database Instance also registers On RAC
(Doc ID 2024572.1)
Last updated on DECEMBER 28, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Symptoms
On 12.1.0.2, GIMR (mgmtdb) database created by default during GI installation. The GI installation had been done using infradb as cluster name. Later on on the top of this cluster a RAC database called INFRADB was created.
On the node that GIMR database is running it is dynamically registered into listener under same service as database instance (see below).
It causes time to time connection issue because the client is redirected to pluggable GIMR database instead of RAC db instance. The corresponding output from lsnrctl status command on affected db node is below:
From "lsnrctl service listener "output:
Service "infradb" has 2 instance(s).
Instance "-MGMTDB", status READY, has 1 handler(s) for this service...
Instance "INFRADB1", status READY, has 1 handler(s) for this service...
On the second node of the cluster (mgmtdb is not running on this node), note that the same output does not:
Service "INFRADB" has 1 instance(s).
Instance "INFRADB2", status READY, has 1 handler(s) for this service...
If the mgmtdb is relocated to node 2, then mgmtdb is registers to the INFRADB service on node 2 and not on node 1 as expected.
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 |