This rule measures the Processes Summary Total Limit, the percentage of the process limit is being used at the time of running the Sessions Summary collection.
When the number of connections exceeds the limit defined in the init.ora file, then new connections to the database may be refused.
The rule uses the following registry values are thresholds
- DBO_Proc_Sum_Total_Limit_Low for the Warning alarm
- DBO_Proc_Sum_Total_Limit_Medium for the Critical alarm
- DBO_Proc_Sum_Total_Limit_High for the Fatal alarm
To calculate the alarm result
- The Sessions Summary collection first counts the number of current processes in the Oracle database by querying the v$process view. Essentially, this tells you how many processes are currently being used.
- The agent then gets the value of the processes parameter. This parameter defines the maximum number of processes allowed by the Oracle database. It is set in the database configuration and represents the upper limit of processes that can be created.
- The agent then calculates the percentage of the maximum process limit that is currently being used.
- The rule then compares this value to the thresholds set in the registry to determine if an alarm should be fired.
Example
If the number of current processes returns 50 and the limit of maximum allowed processes is set to 200, then the total_processes_limit would be calculated as: 100 * 50 / 200 = 25. If DBO_Proc_Sum_Total_Limit_Low were set to 20, then the Warning alarm should be fired.
