SLEE Processes Report Various Shared Memory Errors

(Doc ID 1366209.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

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


SLEE processes will log error or exception messages like the ones below, concerning semaphores or shared memory:

slee_acs(5366) ERROR: shmAttach: Cannot attach to shmKey 0
ERROR: Error processing SleeEvent: SleeException: Semaphore operation failed (1005) in at 118 by process id 22697 errno(22) - Invalid argument
  • Other messages are possible. These examples may be expanded as new ones are identified

  • The "Cannot attach to shmKey 0" error may be repored by other NCC processes as a result of smsStatsDaemon not running. See <1506022.1>>

These will normally occur when the SLEE is started but may also happen when an individual process is restarted (manually or by the watchdog process).

When the SLEE and all background NCC processes are stopped on the machine, which may be done while attempting to resolve this issue, the ipcs command will show that there are still shared memory resources reserved by Solaris:

root@ube02# ipcs
IPC status from <running system> as of Fri Oct 7 23:45:45 GMT 2011
Message Queues:
Shared Memory:
m 15 0x41f76    --rw-rw-rw- ccs_oper    esg
m 13 0xba7d541c --rw-r-----   oracle    dba
m 10 0x11100f3  --rw-rw-rw-     root   root
m  0 0x55000033 --rw-r--r--     root   root
s 30 0x1472     --ra-ra-ra- ccs_oper    esg
s 29 0x643433   --ra-ra-ra- smf_oper    esg

s 19 0xbadc5458 --ra-r-----   oracle    dba
s 15 0x11100f3  --ra-ra-ra-     root   root
s  5 0xc9e03647 --ra-r--r--     root   root
Note the resources owned by the NCC *_oper users.


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