SAP Knowledge Base Article - Preview

2421926 - sp_monitorconfig: Num_active and Max_Used incorrectly reported for "number of open objects" and "number of open indexes" - SAP ASE

Symptom

  • Num_active and Max_Used counters for the "number of open objects" and "number of open indexes" in the sp_monitorconfig output exceed configuration values:

Parameter Name                 Default     Memory Used Config Value Run Value    Unit                 Type
------------------------------ ----------- ----------- ------------ ------------ -------------------- --------------------
number of open indexes                 500       19028         3502         3502 number               dynamic
number of open objects                  500       40442         3531         3531 number               dynamic

 Name                      Num_free    Num_active  Pct_act Max_Used    Reuse_cnt   Instance_Name
------------------------- ----------- ----------- ------- ----------- ----------- ------------------------------
number of open indexes                0        3609  100.00        3609           0 NULL
number of open objects           6341        9957  100.00        9957           0 NULL 

  • Pct_act counter shows 100%.
  • Reuse_cnt  counter remains 0.
  • This issue has been noticed after ASE migration from process to threaded kernel mode.


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.7

Product

SAP Adaptive Server Enterprise 15.7

Keywords

CR806700, CR#806700, 806700, mempool, des, Ides , 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.