Config.sh Cannot Create New OVD 11g Component as ovd2 Under Second Instance2 (Doc ID 1933722.1)

Last updated on MAY 22, 2024

Applies to:

Symptoms

On :  11.1.1.7.0 version, Identity Management suite. Problem on OVD but may exist for any IDM product.

Configuration Details:
 Env: Dev
 Domains:
    OAM Domain
    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:
    11.1.1.5:   http://docs.oracle.com/cd/E21764_01/core.1111/e12035/toc.htm


ACTUAL BEHAVIOR  
---------------
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: <ORACLE_HOME>/instances/ovdinst1/config/OVD/ovd1

OVD2 server: <ORACLE_HOME>/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.

EXPECTED BEHAVIOR
-----------------------
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.

BUSINESS IMPACT
-----------------------
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.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.