My Oracle Support Banner

ODSEE - LDAP User Store Is Not Functioning With [LDAP: error code 32 - No Such Object] (Doc ID 2159316.1)

Last updated on NOVEMBER 01, 2018

Applies to:

Oracle Directory Server Enterprise Edition - Version and later
Information in this document applies to any platform.


ODSEE User Store DS Instance is not functioning after the Solaris patching

Two LDAP Instance user stores - one is working fine whereas the other one is not.

Throwing an error in front end

"An error occurred in the system"

and no apparent reason for what caused this issue.

Unix patching activity was performed on these servers.

In client application server logs error 32 messages -

[LDAP: error code 32 - No Such Object]


In DS Instance access log -

[18/Jun/2016:21:50:05 -0500] conn=40087 op=-1 msgId=-1 - fd=102 slot=102 LDAP connection from xx.xx.xx.xx:39470 to xx.xx.xx.xx
[18/Jun/2016:21:50:05 -0500] conn=40087 op=0 msgId=1 - BIND dn="cn=admin,cn=Administrators,cn=config" method=128 version=3
[18/Jun/2016:21:50:05 -0500] conn=40087 op=0 msgId=1 - RESULT err=32 tag=97 nentries=0 etime=0
[18/Jun/2016:21:50:05 -0500] conn=40087 op=1 msgId=0 - RESULT err=80 tag=120 nentries=0 etime=0
[18/Jun/2016:21:50:05 -0500] conn=40087 op=-1 msgId=-1 - closing from xx.xx.xx.xx:39470 - A1 - Client aborted connection -
[18/Jun/2016:21:50:05 -0500] conn=40087 op=-1 msgId=-1 - closed.



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.