SAP Knowledge Base Article - Preview

2937702 - Infected with 11 (SIGSEGV) in StCtlgAPIMgr::_StCtlgConvertStats - SAP ASE

Symptom

  • A client connection is unexpectedly terminated.
  • An "infected with signal 11" error in StCtlgAPIMgr::_StCtlgConvertStats() together with a stack trace is reported in the ASE errorlog:

Current process (0x5b002e) infected with signal 11 (SIGSEGV)
Current Process is running on Engine 0
Address 0x0x0000000001adc1f8 (StCtlgAPIMgr::_StCtlgConvertStats(OptBlock*, GttTable*, st_colstat*, VirtualFixedArray<short>*, short, short, int, double)+0xf8), siginfo (code, address) = (1, 0x0x0000000000000020)

  • The stack trace includes the following functions:

StColstat*StCtlgAPIMgr::_StCtlgConvertStats
StCtlgAPIMgr::StCtlgCopyStats
GttTable::GttUsefulIndex
GttTable::GtInitIndexAndStats
GtsState::GtsInitIndex
OptBlock::OptPhase1cInit

  Note: Full stack trace details are available under Attachments.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0
  • SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0 for Business Suite 

Product

SAP ERP 6.0

Keywords

Sybase, infected, signal, SEGV, SIGSEGV, segment violation, storage access violation, kisignal, CR820930, CR#820930, 820930 , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

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.