Oracle Access Manager (OAM) Multi Data Center (MDC) After Configuration, Why Is The Primary Server "ClusterId" Is Blank In the oam-config.xml File
(Doc ID 2860849.1)
Last updated on APRIL 12, 2022
Applies to:Oracle Access Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
The Primary Server in the Multi Data Center (MDC) environment, the oam-config.xml file shows the "ClusterId" is blank.
- Upgraded OAM 11g to 12c
- In the oam-config.xml on the clone, the “ClusterId” is set.
- Configured Oracle Access Manager (OAM) Multi Data Center (MDC), but the “ClusterId” on the Primary Server is still not set. (blank)
- Newly installed OAM 220.127.116.11 environment confiured for MDC, both Primary and Clone Servers oam-config.xml file have a value in ClusterID filed.
This will cause a problem when trying to configure Automated Policy Synchronization (APS), as it requires the Primary and Clone cluster ID values.
Why is the "ClusterID" value in the oam-config.xml file on the Primary Server blank, and how is it resolved?
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