Config.sh Cannot Create New OVD 11g Component as ovd2 Under Second Instance2
Last updated on MARCH 08, 2017
Applies to:Enterprise Manager for Fusion Middleware - Version 18.104.22.168.0 and later
Oracle Fusion Middleware - Version 22.214.171.124.0 and later
Oracle Virtual Directory - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Identity Management suite. Problem on OVD but may exist for any IDM product.
Identity Domain (OVD)
Servers: ServerA and ServerB
ServerA: Running the AdminServer (Admin Server to manager the Identity Domain i.e. ODSM and OVD), OAM2, ODSM1 and OVD1
ServerB: Running the Admin Server (Admin Server to manager Oracle Access Manager), OAM1, ODSM2 and OVD2
Followed EDG Guide Link:
The instances/components are operational, but after OVD instances are registered using opmnctl, EM is showing instance name as 'ovd1' for both instances on both nodes.
The below directory structure for OVD1 and OVD2 instances is then found to only show ovd1:
OVD1 server: /opt/ora/appsovd/instances/ovdinst1/config/OVD/ovd1
OVD2 server: /opt/ora/appsovd/instances/ovdinst2/config/OVD/ovd1
When registering the OVD instances using opmnctl, it is checking "config/OVD/ovd1" directory structure to show the name in EM console.
Expect to see unique/different instance name and component name for ovd (ovd2) on the second host. If it is not automatic based on instance number, it is expected to have an option on the screen to set a custom ovd name such as ovd2.
Due to this issue, unable to properly monitor/manage second instance/component in EM, as they have the same name as in the first node.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms