My Oracle Support Banner

Is it Possible to Suppress System Log Output from the check SLEE Binary? (Doc ID 2432178.1)

Last updated on AUGUST 08, 2018

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.

Goal

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), the check binary will always log alarms to the system log file (/var/adm/messages on Solaris and /var/log/messages on Linux).  For example:

bash-4.2$ /IN/service_packages/SLEE/bin/check 1
Aug 6 23:15:51 check(30888) SleeException=2 sleeError.cc@50: SleeException: Cannot find shared memory (3005) in sleeShmManager.cc at 246 by process id 30888 errno(2) - No such file or directory
Cannot find shared memory

bash-4.2$ sudo tail /var/log/messages
...
Aug 6 23:15:51 celvpvm06629 check: check(30888) CRITICAL SleeException=2 sleeError.cc@50: SleeException: Cannot find shared memory (3005) in sleeShmManager.cc at 246 by process id 30888 errno(2) - No such file or directory
Aug 6 23:15:51 celvpvm06629 check: check(30888) CRITICAL SleeException=2 sleeError.cc@50: SleeException: Cannot find shared memory (3005) in sleeShmManager.cc at 246 by process id 30888 errno(2) - No such file or directory
...

While this information may be useful in order to quickly determine if there are issues with the Service Logic Execution Environment (SLEE), it may be desirable to suppress this output to the system log in certain circumstances.

Solution

To view full details, 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 a vibrant support community of peers and Oracle experts.