OID 12c : OID Getting Crashed or Hung Due to DIP Synchronization Profile and DIP from EM Console is Unstable (Doc ID 2697706.1)

Last updated on AUGUST 22, 2022

Applies to:

Symptoms

On : 12.2.1.3.0 version

1. DIP Synchronization Profile Stopped Working, or DIP was unstable when access via EM console,  and also found OID instance used by DIP server getting crashed and auto restarted frequently.

2. Also it was observed that if the DIP profile used to synchronize ADtoOID is Disabled in DIP, then OID server doesn't crash.

3. In WLS Managed DIP server log wls_ods1_diagnostic.log file below errors shown:

<Jul 27, 2020 7:05:37,957 AM IST> <Error> <oracle.dip> <BEA-000000> <Directory Integration Platform is not able to get the context with the given details : OID host:<OID_HOSTNAME> Port: <OID_SSL_PORT> SSL mode:1.>
<Jul 27, 2020 7:05:37,958 AM IST> <Error> <oracle.dip.<PROVISIONING_PROFILE_NAME>> <DIP-10512> <Error in making a remote call to provisioning bean : {0}
javax.naming.CommunicationException: OID_HOSTNAME>:<OID_SSL_PORT> [Root exception is java.net.ConnectException: Connection refused (Connection refused)]

.......

3. 1 And also another DIP sync error for AD entry was repeated continuously.

[2020-07-26T16:24:49.497+05:30] [wls_ods1] [ERROR] [DIP-10007] [oracle.dip.<ODIException: Error Modifying Entry in Directory
at oracle.ldap.odip.gsi.LDAPWriter.checkNReplace(LDAPWriter.java:1350)
at oracle.ldap.odip.gsi.LDAPWriter.checkNReplace(LDAPWriter.java:1154)
at oracle.ldap.odip.gsi.LDAPWriter.modifyRadd(LDAPWriter.java:1113)
at oracle.ldap.odip.gsi.LDAPWriter.performWriteChanges(LDAPWriter.java:600)
at oracle.ldap.odip.gsi.LDAPWriter.writeChanges(LDAPWriter.java:271)
at oracle.ldap.odip.web.DIPSyncWriterThread.run(DIPSyncWriterThread.java:72)
Caused by: javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms.; remaining name 'cn=<CN VALUE>,ou=xx,ou=<GROUP_X>,ou=<GROUP_Y>,ou=xx,ou=<OU_X>,dc=<DOMAIN>,dc=com'
at com.sun.jndi.ldap.Connection.readReply(Connection.java:479)
at com.sun.jndi.ldap.LdapClient.processReply(LdapClient.java:881)
at com.sun.jndi.ldap.LdapClient.modify(LdapClient.java:955)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1471)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:277)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:192)
at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:172)
at oracle.ldap.odip.gsi.LDAPWriter.checkNReplace(LDAPWriter.java:1300)
... 5 more

4. Tried to stop/start OID 12c instances in following way but no change in issue behavior:

STOP SERVICES
1. stop managed server
2. sh stopComponent.sh oid1
3. Stop the WebLogic Administration Server
4. stop node manager
5. shutdown database
6. stop listener

START SERVICES
1. start listener
2. start database
3. startWeblogic.sh
4. startNodeManager.sh
5. sh startComponent.sh oid1
6. start managed server

Changes

 Due to OS patching all services on this Host were stopped and restarted. Post which this issue was seen.

Java on OS was upgraded to latest version but no Change in Java version used for OID/WLS  FMW components.

Cause

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