OID 11g Intermittent Timeouts From Applications or LDAP Searches (ldapsearch). OID Server Log Shows: OID-5019: Cataloging For Attr <attribute> Was Not Performed, As Resource Is Busy. Alert Log Shows High OPTime
(Doc ID 2396734.1)
Last updated on MAY 09, 2018
Applies to:Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) 11g, e.g., 22.214.171.124.0.
OID servicing multiple applications and users for authentication and synchronization.
Since going to production, applications are getting timeouts while communicating with OID.
Sometimes it takes a while to open ldap entries in ldap browsers.
When using command line ldapsearch it is almost always fast (responds in milliseconds), but sometimes it also times out.
The OID server logs show the following messages, for example:
gslbCallCatalog: OID-5019: Cataloging for attr memberof was not performed, as resource is busy.
[2018-05-07T13:16:22.703381+02:00] [OID] [NOTIFICATION:16]  [OIDLDAPD] [host: myoidhost.example.com] [pid: 181206] [tid: 19] ServerWorker (REG):[[
ConnID:4564 mesgID:2 OpID:1 OpName:search ConnIP:::ffff:<IP Address:Port> ConnDN:cn=user1,cn=users,dc=example,dc=com
gslbmAutoCatalog: Initiated catalog with status = 2 for attribute memberof:OID-5019: Cataloging for attr memberof was not performed, as resource is busy.
The alert logs show high or negative high OPTime (operation times):
[2018-05-07T13:59:30.246265][PID:181210][TID:8][connDN:cn=orcladmin][connID:4636][connAddr:::ffff:<IP Address:Port>][ECID:<ECID number>][OP:Search][BaseDN:dc=example,dc=com][Filter:(objectclass=top)][scp:2][ra:cn orclguid ][nentries:9722][OPTime:8163848 micro sec]
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