On Machines Running the 11g Database SLEE Processes Sometimes do not Shutdown Correctly when Aborted by the Watchdog (Doc ID 1547348.1)

Last updated on SEPTEMBER 12, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.0 and later
Information in this document applies to any platform.

Symptoms

SLEE processes aborted by the watchdog may not shut down correctly and can hang/linger for hours in an inoperable state, causing a service outage.

(this has been reported for xmsTrigger but could occur with any SLEE process monitored by the watchdog)

An MDB trace on the process or core file shows that a signal handler (skgesig_sigactionHandler) in the libclntsh library (database) is being called. It will appear to loop if the process itself is traced.

 See KM <note 1511413.1> for more information on MDB.

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