SAP Knowledge Base Article - Preview

2503834 - Signal 11 in module uwconnect() - SAP ASE

Symptom

  • Parallel Processing is configured on ASE server
  • Receiving an "Infected with signal 11" error in the module uwconnect() followed by a stack trace for spid 644:

Current process (0x64c30360) infected with signal 11 (SIGSEGV)
Address 0x0x0000000001d8c12e (uwconnect+0x31e), siginfo (code, address) = (1, 0x0x0000000000000034)

Note 1: See a complete stack in the attachment stacktrace_spid_644.txt.

  • ASE server goes down due to an unreleased spinlock by spid 815:

timeslice -2001, current process infected at 0x1d8c04e (uwconnect+0x23e)
...
Spinlocks held by kpid 1879114663
Spinlock Kernel->kwt->kwt_spinlock at address 0x00002aaaacfbaf00 owned by1879114663

Note 2: See a complete stack in the attachment stacktrace_spid_815.txt.

  • Timeslice errors are reported for other spids, for example:

timeslice -2001, current process infected at 0x1d7c113 (pausenonatomic+0x9)


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 16.0

Keywords

SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, registers , 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.