SAP Knowledge Base Article - Preview

3213379 - SPIDS cannot be killed even though showing running status - SAP ASE

Symptom

  • Though sp_who shows spids as running, the Kill command is not working:
A SHUTDOWN command is already in progress. Please log off.
 fid spid status  loginame  origname  hostname                       blk_spid dbname tempdbname cmd    block_xloid threadpool
 --- ---- ------- --------- --------- ------------------------------ -------- ------ ---------- ------ ----------- ----------------
   0 1104 running mylogin mylogin myhost3.location.unit.xx        0 mydb  tempdb     INSERT           0 syb_default_pool
   0 1191 running mylogin mylogin myhost3.location.unit.xx        0 mydb  tempdb     INSERT           0 syb_default_pool
   0 2677 running mylogin mylogin myhost3.location.unit.xx        0 mydb  tempdb     INSERT           0 syb_default_pool
   0 3087 running mylogin mylogin myhost3.location.unit.xx        0 mydb  tempdb     INSERT           0 syb_default_pool

  • kill 1104
    Does not kill the process


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7
  • SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

unable un-killable unkillable P_KILLYOURSELF upyield runnable die  , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Known Error

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.