SAP Knowledge Base Article - Preview

2155139 - Signal 11 in ct__tds_gd_process, leaving spid that cannot be killed - SAP ASE

Symptom

  • When terminating a session (kill isql, shutdown DBISQL, CTLRL-C Unix process etc.) and
  • SQL is accessing local and remote (proxy) tables
  • The process (spid) cannot be killed in the local ASE
  • ASE reports a stacktrace in the error log entries include (offsets will vary by platform) : 

Current process (0x1b000e) infected with signal 11 (SIGSEGV)
Address 0x0x000000000192017c (ct__tds_gd_process+0x15c), siginfo (code, address) = (1, 0x0x0000000000000090)


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0
  • Sybase Software Developer Kit (SDK) 15.7 and 16.0

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; SAP Adaptive Server Enterprise SDK 16.0 ; Sybase Software Developer Kit 15.7

Keywords

CR778660, CR#778660, 778660, traceflag, trace, flag, 11297, 11227 , KBA , memory corruption , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-SDK , SDK , 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.