SAP Knowledge Base Article - Preview

3073215 - Stack trace at omni_ct_cancel and Signal 11 after kill with force is executed - SAP ASE BS

Symptom

  • Log full situation was found on SID database, there was an open transaction and it was decided to execute a kill with force to terminate that transaction:
    server Process id xxxx killed with force by Hostname xxxxxx, Host process id xxxx.
  • After that it was printed a stack trace on the database log containing the functions:
    upyield
    kctCheckAsync
    ksct_startio
    usctcancel
    omni_ct_cancel
    CtlibRemoteAccess::startRpcScan
    RPCRemoteAccess::startScan
    LeScanOp::_LeOpNext
    LeRestrictOp::_LeOpNext
    LeEmitSndOp::_LeOpNext
    LePlanNext
  • The subsequent stack trace Signal 11 containing the functions:
    np_err_string
    ct__error
    ct__50cont_results
    ct_async_exec_stack
    ct_poll
    kctCheckAsync
    ksct_startio
    usctcancel
    omni_ct_cancel
    rdes_free
    omnipss_free
    dso_disconnect_handler
    terminate_process
    upyield


Read more...

Environment

SAP Adaptive Server Enterprise on Business Suite (ASE BS) 16.0

Product

SAP ERP 6.0

Keywords

KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.