SAP Knowledge Base Article - Preview

3618167 - Signal 11 in Optimize after SIGSEGV is caught by VEH_Optimize - SAP ASE

Symptom

  • The ASE error log reports a sequence that shows
  • A signal 11 at address Optimize
  • Which was preceded by SIGSEGV is caught by VEH_Optimize
  • Error log entries include:

    SIGSEGV is caught by VEH_Optimize()
    ...
    Return VXACTION_CONTINUE from VEH_Optimize()
    The Adaptive Server will continue its execution as signal 11 is handled by vectored exception handler

    Current process (0x21b7022d) infected with signal 11 (SIGSEGV)
    Address 0x0x00000000016b5e52 (Optimize+0x3f2), siginfo (code, address) = (1, 0x(nil))

    lasterror = 0 preverror = 0 transtate = 1

    with a stack that only contains 'Optimize' as the meaningful function, other than generic error handling functions like kisignal:

    kisignal+0xac7()
    Optimize+0x3f2()


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE)
    • 16.0 SP04
    • 16.1 SP00

Product

SAP Adaptive Server Enterprise 16.0.4 ; SAP Adaptive Server Enterprise 16.1

Keywords

sigsegv, veh_optimize, adaptive server enterprise, signal 11, trace flag 16995, csmd, internal error, veh re-entry, sap ase, query processing, sap adaptive server enterprise, ase16 sp04 pl08, error log, vectored exception handler , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Known Error

About this page

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

Search for additional results

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