Starting OID Processes in a High Availability 10g Environment (Doc ID 549364.1)

Purpose

It is not uncommon to see that during troubleshooting the OID processes to find that the ODS_PROCESS table has been truncated. In normal circumstances the OPMNCTL will properly maintain this table, which is used by OIDMON to startup the processes. But, when the table has been truncated you can use the command opmnctl startall to re-populate the ODS_PROCESS table with the default entries for oidldapd and the provisioning odisrv servers. In these examples you are required to start OIDREPLD and ODISRV for synchronization manually the first time in order to get the entries in the table.

Scope

These examples provide insight on when/how a virtual host may apply when starting OID processes.   Generally speaking, the processes on the host communicate with the database and processes using the local hostname.  The fact that a load balancer may be in the configuration has no meaning to OID processes.  The external users make LDAP requests to a virtual hostname that has been defined in a load balancer(LBR).  The LBR then does the transformation to which REAL hostname to forward the request.   

A simple test should be to perform ldapbind request on the OID node using the REAL hostname.   Then from a host OTHER than the oid host, perform an ldapbind to the LBR hostname/port.  It will transform the request to the REAL host/port as defined in the LBR rules.

Details

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