Symptom
- The Max_Used value reported by sp_monitorconfig for the configuration "number of locks" can report a values differently on running multiple times. At times it may report lesser value than the earlier reported for the max_used column.
- On running multiple times we may see the below symptom. The max_used value decreased by 41 locks between these two samples.
-
First run date and time: Mar 30 2015 9:23AM.
sp_monitorconfig 'locks'
go
Name Num_free Num_active Pct_act Max_Used Reuse_cnt Instance_Name
------------------------- ----------- ----------- ------- ----------- ----------- ------------------------------
number of locks 198991 1009 0.50 48286 0 NULL
-
Now without restart the server, running second time may report like this.
Second run date and time: Mar 30 2015 1:15PM.
sp_monitorconfig 'locks'
go
Name Num_free Num_active Pct_act Max_Used Reuse_cnt Instance_Name
------------------------- ----------- ----------- ------- ----------- ----------- ------------------------------
number of locks 199053 1009 0.47 48245 0 NULL
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE)
- SAP Adaptive Server Enterprise Cluster Edition (ASE CE)
Product
SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 15.7 Cluster Edition ; SAP Adaptive Server Enterprise 16.0 ; SAP Adaptive Server Enterprise 16.0 Cluster Edition
Keywords
CR723588, CR#723588, 723588, CR#385854, 385854, CR385854 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , 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.