SAP Knowledge Base Article - Preview

2006441 - A process in "latch sleep" is blocking and cannot be killed - SAP ASE

Symptom

  • sp_who shows that a process was stuck in the 'latch sleep' status:

1> sp_who
2> go
 

fid spid status      loginame           origname           hostname blk_spid dbname         tempdbname     cmd                  block_xloid      threadpool
--- ---- ----------- ------------------ ------------------ ------------------------------ -------- -------------- -------------- ----------------- ----------- ---------------    
0 1948 latch sleep xxxlight           xxxlight           l56858n01.aaa.bb.cc.com           0 sybsystemprocs qutempdb        OPEN CURSOR                 0     syb_default_pool

  • The process could not be killed and was blocking other processes.
     
  • When attempting to kill spid we get the following message: 

1> kill 1948
2> go
 
Killing spid: 1948 will not be immediate because it is waiting for a latch held by spid: 1948.


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.7

Product

SAP Adaptive Server Enterprise 15.7

Keywords

CR746528, 746528, "self deadlock" , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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.