SAP Knowledge Base Article - Preview

2719233 - Idle spid remains in sysprocesses or sp_who after issuing "kill <spid> with force" - SAP ASE

Symptom

  • When killing a idle spid using "kill <spid> with force", the spid remains in sysprocesses and sp_who output with "sleeping" status.
  • Use dbcc stacktrace on the hung spid you will see ths functions: soc_nclose, kscloseall, upkill, upprekill
  • The spid was unable to completely clean up and will remain in sysprocesses despite the connection has been dropped.


with force" - SAP ASE"> Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7 SP 140 and lower
  • SAP Adaptive Server Enterprise (ASE) 16.0 SP02 PL08 and lower
  • SAP Adaptive Server Enterprise (ASE) 16.0 SP03 PL06 and lower

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

kill spid, kill <spid>, kill spid with force, kill <spid> with force, recv sleep, sleeping, sp_who, sysprocesses,  idle process, idle spid, remain, remaining , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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.