OEM (13.2.2) Guided Discovery Of A 3-Node (22.214.171.124_RU) RAC DB Finds 3rd Node In Upper Case.
(Doc ID 2648241.1)
Last updated on MARCH 11, 2020
Applies to:Enterprise Manager for Oracle Database - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
A 3-node Oracle 12cR2 Cluster was built long ago on an Exadata DBM (DataBase Machine), which is currently running
Oracle Linux 6.10 (UEK, on Exadata Image 188.8.131.52), and the Cluster has _always been 3 nodes, from the beginning
(none added or dropped). Cluster is using ASM, and both ASM (GI) & DB Homes are 184.108.40.206 (w/Oct '19 RU Patches).
More and more RAC Databases have been added to this Cluster over time (now totalling over 50), and most have been
Discovered (in EM 13cR2, using EM 13.2.2 DB Plugins) without problems, but a few (~ 4) have been discovered with
inconsistent case. For this particular DB, the EM Targets from Nodes 1 & 2 came in lower-case (as expected), but
those from Node 3 came in UPPER-case instead (and seemed to be treated as a separate Cluster DB).
Tried dropping the problem RAC DB Targets, applying all the latest recommended EM (13.2) Bundle Patches (from OMS,
Agent, & Plugins), then rediscovering, but no change, still got the same inconsistent case. Also tried dropping
and re-Discovering using Declarative Process (instead of Guided Process), but still got mixed-cases.
Problem DB was created via migration cloning (outside of EM), then Discovered by EM after.
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