SAP Knowledge Base Article - Preview

3410811 - Log messages referring to "vectored exception handler" / VEH_Optimize - SAP ASE

Symptom

  • The ASE errorlog prints messages like :

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

  • They may be seen in isolation
  • Or can be seen around a 'full' signal 11 sequence - Current process (...) infected with signal 11 (SIGSEGV)
    • These are not limited to a particular stack pattern
    • But will often include a 'showplan' element or code functions from the Optimizer area

  • Below a shortened example
    • As per above, this is only an example.
      A wide variety of stack trace elements can be seen

      Address 0x0x0000000001c8eb93 (exc_callprint+0x83), siginfo (code, address) = (128, 0x(nil))
      Current process (0x49a300b3) infected with signal 11 (SIGSEGV)

      SQL Text: select show_plan(@SPID@,show_plan(@SPID@,-1,-1,-1),show_plan(@SPID@,show_plan(@SPID@,-1,-1,-1),-1,-1),-1)

      pcstkwalk
      ucstkgentrace
      ucbacktrace
      terminate_process
      kisignal

      The Adaptive Server will continue its execution as signal 11 is handled by vectored exception handler


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE)
    • 16.0 SP03 PL10 and above
    • 16.0 SP04 and above

Product

SAP Adaptive Server Enterprise 16.0

Keywords

show_plan , KBA , 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 for Me (Login required).

Search for additional results

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