2938994 - Signal 11 in sort_write() - SAP ASE 16.0

• A client connection is unexpectedly terminated.
• ASE errorlog contains an "Infected with Signal 11" error in the module sort_write() with a stack trace:

Current process (0x411f2b77) infected with signal 11 (SIGSEGV)
Address 0x0x0000000001bedad4 (sort_write+0x44), siginfo (code, address) = (128, 0x(nil))

  The stack trace includes the following functions:

sort_write
mergeruns
mergenodes
startsort
sort
LeStoreOp::_buildIndex
LeStoreOp::_LeOpOpen
LeDMLOp::printXMLCostMetrics
LeSequencerOp::_LeOpOpen
LeEmittOp::_LeOpOpen
LeEmitSndOp::_LeOpOpen
LePlanOpen
exec_lava
s_execute

• The errorlog reports the following message for the same connection:

Invalid OAM page (OAMINVALID_1) stat 4: pageno=534017, sdes_stat=16, pstat=0x101, dbid=102, pptnid=-1314652161, pindid=0, expected ptnid=-1314652161

  with a stack trace that includes the following functions:

pg__objdeall_validate_obj
pg_ptndeall
closetable
close_range
s_cleanframe
clean_process
kill_proc
terminate_process
kisignal

• The ASE may later crash due to a spid hitting an "infected with signal 11" error in the module bufsearch_cache_getlatch():

Current process (0x4c25072e) infected with signal 11 (SIGSEGV)
Address 0x0x0000000001afe667 (bufsearch_cache_getlatch+0x497), siginfo (code, address) = (1, 0x0x0000000000000018)

  with a stack trace that includes the following functions:

bufsearch_cache_getlatch
getpage_with_validation
bt__latchrootpage
bt__traverse
bt__getstartpg
bt_getnext
dol_bt_getnext
getnext
dropallconstr
dropo
dropobject

  and leaving an unreleased Spinlock tempdb_cache:

Spinlocks held by kpid 1277495086
Spinlock tempdb_cache at address 0x00002aaac0ba0480 owned by 1277495086 

SAP Adaptive Server Enterprise (ASE) 16.0

Sybase, infected, signal, SEGV, SIGSEGV, segment violation, storage access violation, kisignal, CR821745, CR#821745, 821745, CR821747, CR#821747, 821747, traceflag, trace, flag, 897 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed