SAP Knowledge Base Article - Preview

2133657 - ASE infected with signal 11 (SIGSEGV) in ubo_slotscan_getnext - SAP ASE

Symptom

  • Execution of sp_sysmon system procedure
  • Execution of query against the monTask table in master with the KTID and/or ThreadPoolID columns specified
  • ASE error log reports signal 11 error in module ubo_slotscan_getnext:

     kernel  Current process (0x1c3300de) infected with signal 11 (SIGSEGV)
     kernel  Address 0x00000000803c4f3c (ubo_slotscan_getnext+0x1c), siginfo (code, address) = (1, 0x0000000000000000)

  • Stack trace may include modules similar to:

    kisignal
    ubo_slotscan_getnext
    _$o1cfalI0.mda_populate_monTask
    mda_exec
    int VTABRemoteAccess::mdaStartScan
    void VTABRemoteAccess::startScan

Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7
  • SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

VTABRemoteAccess mda_populate_monTask ThreadPoolID monTask , KBA , mda , monitoring table , 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.