SAP Knowledge Base Article - Preview

2464302 - ASE process is blocked by the other process and it goes to lock sleep.

Symptom

  • SAP ASE processes (spids) are blocked by one process (spid) and it goes to lock sleep.
  • sql command in blocked process is not performed correctly.
  • 1> sp_who
     2> go
     fid spid status     loginame    origname    hostname                       blk_spid dbname      tempdbname cmd               block_xloid threadpool
     --- ---- ---------- ----------- ----------- ------------------------------ -------- ----------- ---------- ----------------- ----------- ----------------
     
        0   18 send sleep NULL        NULL        NULL                                  0  user_db       tempdb     SELECT                      0 syb_default_pool
       
        0  397 lock sleep NULL        NULL        NULL                                  18 master      tempdb     DELETE                      0 syb_default_pool


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) All versions

Product

SAP Adaptive Server Enterprise 15.7

Keywords

'lock wait period' , 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.