SAP Knowledge Base Article - Preview

2938994 - Current process infected with signal 11 at sort_write() - SAP ASE

Symptom

  • Client connection unexpectedly terminated
  • Errorlog contains an Infected with Signal 11 (SIGSEGV) error at sort_write() with a stack trace that includes the following functions:

terminate_process
kisignal
sort_write
mergeruns
mergenodes
startsort
sort
LeStoreOp::_buildIndex(ExeCtxt&)
LeStoreOp::_LeOpOpen(ExeCtxt&)
LeDMLOp::printXMLCostMetrics(ExeCtxt&) 
LeSequencerOp::_LeOpOpen(ExeCtxt&)
LeEmittOp::_LeOpOpen(ExeCtxt&)
LeEmitSndOp::_LeOpOpen(ExeCtxt&)
LePlanOpen
exec_lava
s_execute

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

server Invalid OAM page (OAMINVALID_1) stat 4: pageno=534017, sdes_stat=16, pstat=0x101, dbid=102, pptnid=-1314652161, pindid=0, expected ptnid=-1314652161
pcstkwalk
ucstkgentrace
ucbacktrace
pg__objdeall_validate_obj
pg_ptndeall
closetable
close_range
s_cleanframe
clean_process
kill_proc
terminate_process
kisignal

  • The ASE may later crash with current process infected with signal 11 (SIGSEGV) at bufsearch_cache_getlatch

Spinlocks held by  kpid 1277495086
Spinlock tempdb_cache at address 0x00002aaac0ba0480 owned by 1277495086
bufsearch_cache_getlatch
getpage_with_validation
bt__latchrootpage
bt__traverse
bt__getstartpg
bt_getnext
dol_bt_getnext
getnext
dropallconstr
dropo
dropobject



            


Read more...

Environment

SAP Adaptive Server Enterprise 16.0

Product

SAP Adaptive Server Enterprise 16.0

Keywords

Sybase, infected, signal, SEGV, SIGSEGV, segment violation, storage access violation, kisignal, CR821745, CR821747 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.