SAP Knowledge Base Article - Preview

1920548 - spid waiting for a latch cannot be killed immediately - SAP ASE


  • Why does ASE show many spid's in LATCH SLEEP state?
  • Killing a spid in 'latch sleep' will not be immediate because it is waiting for a latch held by another spid.
    For example: Background House Keeper process HK GC in 'latch sleep' status locked lot of spids. Restarting ASE resolved the bottleneck.
  • Why did this happen?
  • How to avoid it in future?
  • What is the best way to resolving the "latch sleep" other than restarting ASE?



SAP Sybase Adaptive Server Enterprise (ASE)


SAP Adaptive Server Enterprise all versions ; Sybase Adaptive Server Enterprise all versions


non-transactional, synchronization, mechanisms, physical, consistency, page, latch, wait, housekeeper, dbcc, lock_release, dbreboot , 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.