SAP Knowledge Base Article - Preview

2814689 - Infected with signal 11 (SIGSEGV) in lock_address() - SAP ASE

Symptom

  • ASE crash due to holding spinlock addrlockspins while infected with signal 11 (SIGSEGV) in lock_address() 
  • The following calls appear in the stacktrace that follows: 

lock_address()
getrootpage+0x723()
srchindex+0x3e5()
apl__startscan+0x42a()
startptnscan+0x788()
LeScanOp::_LeOpNext(ExeCtxt&)
LeRestrictOp::_LeOpNext(ExeCtxt&)
LeDMLOp::printXMLCostMetrics(ExeCtxt&)
LeNLJOp::_LeOpNext(ExeCtxt&)+0x95()
LeDMLOp::printXMLCostMetrics(ExeCtxt&)
LeSQFilterOp::_LeOpNext(ExeCtxt&)
LeUpdateOp::_LeOpNext(ExeCtxt&)
LeEmitNoSndOp::_LeOpNext(ExeCtxt&)
LePlanNext
exec_lava
s_execute

  • ASE log shows a high number of major faults
  • ASE is configured to use Huge Pages

Read more...

Environment

SAP Adaptive Server Enterprise (ASE) - 16.0

Product

SAP Adaptive Server Enterprise 15.7

Keywords

spinlock, shutdown, ueshutdown, crash, SIGSEGV , 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.