SAP Knowledge Base Article - Preview

2835051 - Infected with signal 11 in ssql_lookup with server crash due to SSQLCACHE_SPIN spinlock - SAP ASE 16.0

Symptom

  • A client connection is unexpectedly terminated.
  • Infected with signal 11" error in the module ssql_lookup() together with a stack trace is reported in the ASE errorlog:

Current process (0x88b0446) infected with signal 11 (SIGSEGV)
Address 0x0x0000000001052f5e (ssql_lookup+0x43c), siginfo (code, address) = (1, 0x0x000000000000004e)

  • The stack trace includes the following functions:

ssql_lookup
sqt_get_from_stmtcache
s__xoltp_dynprepare

or

ssql_lookup
s_xform_to_execute
s_normalize

   Note: A complete stack trace example of the first instance is available under Attachments.

  • ASE then shuts down due to infected process holding spinlock SSQLCACHE_SPIN:

Spinlocks held by kpid 143328326
Spinlock SSQLCACHE_SPIN at address 0x00002aaaafb0bd00 owned by 143328326


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 16.0

Keywords

Sybase, infected, signal, SEGV, segment violation, storage access violation, kisignal, CR819729, CR#819729, 819729 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , Bug Filed

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.