OID 10g 10.1.4.3 OID Locks, Stops Responding, Consumes High CPU, Slow Searches Filtering On Objectclass inetorgperson Or groupofuniquenames, Or OID Hangs On ldapsearch Requests Every Few Hours
(Doc ID 789069.1)
Last updated on JANUARY 28, 2021
Applies to:Oracle Internet Directory - Version 10.1.4.3 to 10.1.4.3 [Release 10gR3]
Information in this document applies to any platform.
Oracle Internet Directory (OID) 10g version 10.1.4.3 (patchset) displays symptoms which can include any or all of the following:
- OID stops responding
- OID locks up
- Oracle or OID (oidldapd) processes consume high or 100% CPU, consistently or periodically
- OID hangs completely on ldapsearch requests every few hours
- Searches with filters such as objectclass=inetorgperson or objectclass=groupofuniquenames are slow
The output of the top command may show oidldapd and/or oraclesid process consuming 100% CPU.
After restarting database and/or OID, OID may work for the next few hours until the issue reoccurs.
There may or may not be a problem SQL on the Database (DB) at the time. An example of an offending SQL statement related can be:
RP_DN)INDEX(dn PN_DN) ORDERED FIRST_ROWS */ store.entryid, store.attrname,
NVL(store.attrval,' '), NVL(store.attrstype, ' ') FROM ct_dn dn,
ds_attrstore store WHERE dn.entryid in ((SELECT /*+ INDEX(at1
VA_objectclass) FIRST_ROWS */ at1.entryid FROM ct_objectclass at1 WHERE
(at1.attrvalue = 'inetorgperson' ) ) ) AND ( dn.parentdn like :bdn ESCAPE '\' OR
(dn.rdn = :rdn and dn.parentdn = :pdn) ) AND dn.entryid = store.entryid AND
dn.entryid = :entryThreshold AND store.attrkind ='u'
In this case, a similar SQL query without NL hints may work and does not cause the problem.
The problem may reproduce with command line ldapsearch, for example, with filter of objectclass=inetorgperson or objectclass=groupofuniquenames, i.e.:
Searches with filter objectclass=* may not experience the problem.
The CPUJAN2009 Patch 7592360 could be applied to the database, which is the default/standard 10.1.0.5 version.
Already verified that all the tuning for OID 10.1.4.3.0 required for Oracle Access Manager (OAM) has already been applied, as per Document 558040.1 Oracle Internet Directory Tuning for Oracle Access Manager, and OID tuning done as per recommendations in Document 458703.1 OID Performance Tuning Checklist.
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