SAP Knowledge Base Article - Preview

2986131 - Column "BlockeyBy" on MDA table "monLocks" doesn't report correct blocking spid number - SAP ASE

Symptom

Column "BlockeyBy" on MDA table "monLocks" doesn't report correct blocking spid number. For example, here spid 16 is being blocked by spid 15:

=====

1> sp_who
2> go
 fid    spid     status               loginame         origname         hostname         blk_spid         dbname       tempdbname           cmd                                block_xloid            threadpool
 ------ -------- -------------------- ---------------- ---------------- ---------------- ---------------- ------------ -------------------- ---------------------------------- ---------------------- --------------------------------
   0      15     recv sleep           sa               sa               redhead                 0         db01         tempdb               AWAITING COMMAND                             0            syb_default_pool
   0      16     lock sleep           sa               sa               redhead                15         db01         tempdb               SELECT                                       0            syb_default_pool

=====

But query on MDA table reports:

=====

1> select SPID, BlockedBy from monLocks where BlockedBy > 0
2> go
 SPID        BlockedBy
 ----------- -----------
          16          30

(1 row affected)


=====


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

Column BlockeyBy MDA table monLocks report incorrect blocking spid number lock object ID LOID , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.