SAP Knowledge Base Article - Preview

2266726 - monProcessStatement: APF reads not included in PhysicalReads - SAP ASE

Symptom

  • PhysicalReads column from monProcessActivity and monProcessStatement monitoring tables
    • does not include Asynchronous Prefetch (APF) values for utility commands such as dbcc checks
    • only show regular physical reads and no APF reads.
  • This output example illustrates a discrepancy when comparing the statistics io output with PhysicalReads value in monProcessStatement
     
    • set statistics io output shows :
       
         Table: l_tab scan count 1, logical reads: (regular=2732 apf=0 total=2732),
         physical reads: (regular=8 apf=2724 total=2732), apf IOs used=2724
       
    • monitoring from another isql session :
       
         select PhysicalReads from monProcessStatement
         go
       
         PhysicalReads
         -------------
                     8
       
  • Only the regular physical reads are included in monProcessStatement - it should show 2732 : 8 (regular) + 2724 (apf).
  • PhysicalReads never surpasses the regular value from query statistics.


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0.

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

MDA, 780628, CR780628 , 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.