3051772 - ASE cache corruption leading to in errors, including 208, and stack traces - SAP ASE

• Various ASE errors and / or stack traces are reported
• Due to random nature of the issue, symptoms can vary
• They can include, but are not limited to:
  
  
• Error 208
  

  Error: 208, Severity: 16, State: 1
  table_name / #temp_table_name not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).

• Error 8201 with stack trace
  

  Error: 8201, Severity: 26, State: 3
  Keep count of descriptor (objid=123456789, dbid=2) was expected to be 1. Instead 0 was found.

  des_rekeep
  proc_cacheplan

• Signal 11 at address senderror that can crash ASE due to secondary signal error:
  

  Current process (0x824691Y) infected with signal 11 (SIGSEGV)
  Address 0x0x000000000XXXXXXX (senderror+0xdYY) ...

  senderror
  s_procinstall_lwp

  FATAL UNHANDLED EXCEPTION: signal 0 hit while handling a previously hit signal. The server cannot continue and will shut down.

SAP Adaptiver Server Enterprise (ASE) 16.0 SP03 & SP04

error 208 not found crash FATAL UNHANDLED EXCEPTION kepanic kisignal senderror ex_printmsg ex__doprint exc_callprint s_procinstall_lwp s_renormalize s_recompile CR 824691 CR824691 , 824691 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed