3123917 - Signal 11 in senddone() and mda_update_stmt_metrics() - SAP ASE 16.0

• ASE reported two "infected with signal 11" errors.
• The first Signal 11 error was reported in the module senddone() with the stack trace:
  

  Current process (0x49970048) infected with signal 11 (SIGSEGV)
  Address 0x0x000000000187e0b9 (senddone+0xa59), siginfo (code, address) = (128, 0x(nil))

• The stack trace included the following functions:
  
  kisignal
  senddone
  conn_hdlr

• It was followed by the second Signal 11 error in the module mda_update_stmt_metrics() with the stack trace:
  
  Current process (0xad31c49) infected with signal 11 (SIGSEGV)
  Address 0x0x000000000172e4d6 (mda_update_stmt_metrics+0x3c9), siginfo (code, address) = (128, 0x(nil))
  
  
• This stack trace included the following functions:
  

  kepanic
  kisignal
  mda_update_stmt_metrics
  mda_nap_start
  upsleepgeneric
  ussflush
  usseom
  terminate_process

• Then the ASE server went down:
  
  FATAL UNHANDLED EXCEPTION: signal 11 hit while handling a previously hit signal. The server cannot continue and will shut down.
  
  
•  Related parameters in the ASE configuration file:
  • statement cache size > 0
  • enable stmt cache monitoring =1 
  • secondary signal handling = DEFAULT (0)                                              

SAP Adaptive Server Enterprise (ASE) 16.0 SP03

825828, CR825828, CR#825828, secondary, handling, SEGV, segmentation, storage, access, violation, fault, segfault, stacktrace   , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem