Database Versions 10.2.0.x DBMS_LDAP Calls Consume High CPU Resource
(Doc ID 811609.1)
Last updated on FEBRUARY 19, 2019
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.
- The CPU usage on the OID Server goes very high
- Using 10.2 version of Database
- There is an oracle process spinning to read data, due to a dbms_ldap call. This consumes a lot of cpu.
The problem has been reported on multiple scenarios like
- Oracle E-Business Suite intance integrated with OID
- Custom applications using DBMS_LDAP calls (against any LDAP Server)
In all the cases, the database version was 10.2.0.x
An example stack trace given below shows a session which is waiting for 'DBMS_LDAP:LDAP operation' which uses high CPU resource.
SO: c00000013c760780, type: 4, owner: c00000013da70fc8, flag: INIT/-/-/0x00
(session) sid: 2021 trans: c00000013aeac710, creator: c00000013da70fc8, flag: (8000041) USR/-
DID: 0001-0233-000002A2, short-term DID: 0001-0233-000002A3
txn branch: 0000000000000000
oct: 47, prv: 0, sql: c0000000e81ad728, psql: c00000013e2c12f0, user: 0/SYS
O/S info: user: applprod, term: unknown, ospid: 29890, machine: <machine_name>
program: JDBC Thin Client
client info: 82 0
application name: fnd.preferences.server.PreferencesAM, hash value=173592914
action name: 29890, hash value=889299756
waiting for 'DBMS_LDAP: LDAP operation ' blocking sess=0x0000000000000000 seq=13824
wait_time=0 seconds since wait started=2229
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