3559053 - Error 941 followed by 6103, causing blocking and/or signal 11 at pss_init which make ASE unresponsive - SAP ASE

• The ASE errorlog reports error 941 which is immediately followed by error 6103
• This can result in:
• Orphan spid that can causes blocking and holding syslogs
  and/or
• Some time later (hours) a signal 11 in a pss funtion is seen
• Which then causes the listener to terminate making ASE server unresponsive
  
  
• Below an overview of typical errors and stack functions
  

1. Error 941 with a stack trace sequence
   
   Error: 941, Severity: 20, State: 1
   Illegal database context operation.
   ...
   lasterror = 941
   
   with stack including
   
   closedb
   s_cleanframe
   
   
2. Error 6103 
   
   Error: 6103, Severity: 17, State: 1
   Unable to do cleanup for the killed process; received Msg 941. 
   
   
   
3. This may result in a signal 11 in a 'pss' function, most likely pss_init, which may be a considerable amount of time (hours) later
   
   Address 0x00000001032cc4c4 (pss_init.fdpr.chunk.4+0x148), siginfo (code, address) = (50, 0x00000000deadbabe)
   Current process (0x272f1398) infected with signal 11 (SIGSEGV)
   
   lasterror = 0 ...
   
   with a stack including
   
   pss_init
   pss_alloc
   spawn_conn_hdlr
   listener
   
   
4. Finally resulting in the listener terminating that makes ASE unresponsive:
   
   Listener with protocol tcp, host XXXXXX, port 5000 has been terminated due to timeslice error. You can start a new listener on the same port.

Adaptive Server Enterprise (ASE) 16.0 SP03 & SP04

closedb.fdpr.chunk , s_cleanframe.fdpr.chunk , s_cleanframe.fdpr.chunk.8+0xa4() , closedb.fdpr.chunk.4+0x2c() , pss_init.fdpr.chunk.4+0x148() , pss_alloc+0x40() , spawn_conn_hdlr+0x100() , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Known Error