OID 11g Poor Performance After Database Upgrade.DB Disconnects Affecting OAM (timeouts). OID Log "Error = ORA-25408: can not safely replay call" Occurs Often / Sporadically and Seems Correlated to Hhigh CPU usage from One of the oidldapd Processes. (Doc ID 2217141.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

Severely degraded and poor performance from Oracle Internet Directory (OID) 11g after Database (DB) upgrade from, e.g., from 11g to 12c / 12.1.0.2.0.

All the other components, such as Application Servers, Oracle Access Manager (OAM) servers, etc, are working fine without issues, besides having problems communicating with the OID LDAP services.

Seeing disconnects from the database, and very high response times, so there are timeouts from OAM.

Solution from Document 2142279.1 does not make a difference.

The OID log shows, for example:

...<snip>...
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 18] ServerWorker (SPW):
Failover ended ...resuming services
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 18] ServerWorker (SPW): gslduufOCIPing * ORA-25408 error encountered.               Error = ORA-25408: can not safely replay call
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 18] ServerWorker (SPW): ServerWorker * OCIPing() failed
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 18] ServerWorker (SPW): ServerWorker : Requesting new database connection
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 18] ServerWorker (SPW): INFO : Waiting for new DB connection ...
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 19] ServerWorker (SPW):
Failover ended ...resuming services
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 19] ServerWorker (SPW): gslduufOCIPing * ORA-25408 error encountered.               Error = ORA-25408: can not safely replay call
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 19] ServerWorker (SPW): ServerWorker * OCIPing() failed
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 19] ServerWorker (SPW): ServerWorker : Requesting new database connection
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 0] Main:: gslduufOCIPing * ORA-25408 error encountered.               Error = ORA-25408: can not safely replay call
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 0] Main:: gslarutcPostPerfOCIping * OCIPing() failed.
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 19] ServerWorker (SPW): INFO : Waiting for new DB connection ...
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 0] Main:: gslarutcPostPerfOCIping * Requesting a new DB connection.
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 18] ServerWorker (SPW): INFO : Got New DB connection
[2016-12-21T13:01:53+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 19] ServerWorker (SPW): INFO : Got New DB connection
[2016-12-21T13:01:54+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 1] StatsCollector:  Failing Over ... Please stand by
[2016-12-21T13:01:54+00:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 28307] [tid: 1] StatsCollector:  Failover type was found to be SELECT
...<snip>...


The OID log ORA-25408 error occurred before the issue, but not like now. This may been seen when a node actually goes down and it fails over, but this is not the case now. It happens sporadically throughout the day, and seems correlated to high cpu from one of the oidldapd processes.

Once it happens, the CPU goes down and the ldap process starts to respond again.

Nothing in the DB alert log when this is happening.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms