My Oracle Support Banner

First Active Active Identity Management Install Fails in DIPCA with Connection refused (Doc ID 785157.1)

Last updated on APRIL 27, 2018

Applies to:

Oracle Fusion Middleware High Availability - Version: to - Release: AS10gR2 to AS10gR2
z*OBSOLETE: Microsoft Windows Server 2003
z*OBSOLETE: Microsoft Windows 2000
Microsoft Windows 2000Microsoft Windows Server 2003


- This is the first installation of active-active OracleAS Clusters for Identity Management
- Metadata Repository is installed remotely on separate nodes.
- The install is failing in the Directory Integration and Provisioning Configuration Assistant (DIPCA) with the following error reported in dipca.log:


oracle.ldap.oidinstall.backend.OIDCAException: Cannot connect to OID server.:javax.naming.CommunicationException: host.domain:636 [Root exception is Connection refused: connect]
at oracle.ldap.oidinstall.backend.OIDConfiguration.sslbind(
at oracle.ldap.oidinstall.backend.OIDConfiguration.<init>(
at oracle.ldap.oidinstall.backend.OIDConfigWrapper.configDIP(
at oracle.ldap.oidinstall.OIDCA.doSilent(
at oracle.ldap.oidinstall.OIDCA.main(


In addition %ORACLE_HOME%\ldap\log\oidldapd01sxxx.log shows:

 * ServerListener :2 * sgsluscNTReadPort:ReadFile() failed, OS error = 109
 * ServerListener :2 * FATAL : ServerListener : OS 2 : Unable to contact dispatcher
 * ServerController:0 * WARNING : ServerController : Processing shutdown notification
 * ServerWorker (REG):3 * FATAL * ServerWorker * Processing shutdown notification

- 'opmnctl status' shows that Oracle Internet Directory (OID)  is Alive.
-  ldapbind to OID via the load balancer works in both ldap and ldaps modes.


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

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