My Oracle Support Banner

DIP Unable To Start "Unable To Locate The DIP Sync Profile Mbean" in logs (Doc ID 2444128.1)

Last updated on OCTOBER 16, 2019

Applies to:

Oracle Internet Directory - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.7.0 version, OID LDAP Server

DIP unable to start "Unable to locate the DIP Sync profile mbean"


ERRORS
----------
Exception: "Unable to locate the DIP Sync profile mbean" is seen in the AdminServer-diagnostic.log

The managed server log (example wls_ods1.log)  shows the following errors:
- - - -
<xxxxxxxxxxxxxxx> <1531094731901> <BEA-001129> <Received exception while creating connection for pool "schedulerDS": IO Error: NL Exception was generated.> 
<Jul 8, 2018 8:05:31 PM EDT> <Info> <JDBC> <> <> <xxxxx> <xxxxxxx>

<BEA-001156> <Stack trace associated with message 001129 follows: 
java.sql.SQLRecoverableException: IO Error: NL Exception was generated
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:489)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:234)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:359)
. . . . .
Caused By: oracle.net.ns.NetException: NL Exception was generated
at oracle.net.resolver.AddrResolution.resolveAddrTree(AddrResolution.java:632)
at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:427)
at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:711)
at oracle.net.ns.NSProtocol.connect(NSProtocol.java:257)
at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1229)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:326)
. . . . .

Changes

The issue occurred after the following steps
1. Create a new Non-Production test node using T2P copyConfig / PasteConfig process
2. Note DIP and Mbeans still reference the Production host, port
3. Note DIP scheduler and MBeans appear down in EM/ FMW Control
4. The managed server starts, but MBean related errors are seen

If is also possible this issue can be seen outside of the cloning process if hostnames or network topology has changed.
 

Cause

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
Symptoms
Changes
Cause
Solution
References


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