3338060 - SIGSEGV is caught by VEH_Optimize() with error 622 / signal 11 at bufallunkeep - SAP ASE

• The ASE error log reports a SIGSEGV is caught by VEH_Optimize
• Which may have other messages
  • Before : error 622
    and/or
  • After : signal 11 in function bufallunkeep
• Finally resulting in error 6103 and a phantom spid
• The errorlog entries may vary, these may be seen
  

  
  SIGSEGV is caught by VEH_Optimize()
  Return VXACTION_CONTINUE from VEH_Optimize()
  
  Error: 622, Severity: 20, State: 1
  Opentable was passed a varno of 250. Object '' in database 'tempdb03' already has that session descriptor in use. This occurred while opening object id -49741826 in database id 12.
  ...
  lasterror = 622 preverror = 0 transtate = 1

  Current process infected with signal 11 (SIGSEGV)
  Address 0x0x000000000172b729 (bufallunkeep+0x4a9), siginfo (code, address) = (1, 0x0x0000000072616873)

  WARNING: Pss 0x0x00007f1f62a63c98 found with open sdes. pspid 759, psuid 1, pcurdb 10, system table entry 1, sdesp 0x0x00007f1f1d41b098, objid 24.
  Error: 6103, Severity: 17, State: 1
  Unable to do cleanup for the killed process; received Msg 8201

SAP Adaptive Server Enterprise (ASE) 16.0

VEH_Optimize, Return VXACTION_CONTINUE , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem