eG Monitoring
 

Measures reported by OraRacResUsgeTest

This test monitors how effectively each instance on the Oracle Cluster database server utilizes the session and process resources it is configured with. If the maximum limit to which the resource allocation can grow is violated, it is bound to deteriorate the performance of the server, as the server might not have the bandwidth to handle the additional sessions/processes.

Outputs of the test : One set of results for the session and process resources allocated to each Oracle database instance on the target Oracle Cluster being monitored

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Initial_allocation Indicates the number of sessions/processes allocated at the time of creating the Oracle database instances. Number  
Cur_utilization Indicates the number of sessions/processes currently active on this Oracle database instance. Number If the value of the Current utilization measure exceeds the value of the Initial allocation measure, the additional required resources are allocated from the shared pool, where they must compete for space with other resources.

During SGA reservation/initialization, a place is reserved in SGA for the INITIAL_ALLOCATION of resources.

Based on usage, this allocation can later be changed using the SESSIONS and PROCESSES parameters in the init database parameter file. The Configured limit measure of this test reports this new configuration only.

For most resources, the INITIAL_ALLOCATION value and the Configured limit will be the same.

However, if the resource allocation is to be changed later, it is good practice to check the maximum utilization limit that Oracle prescribes for the database, and then make the change. This limit signifies the maximum number of sessions and processes the database can handle, given its current memory capacity. The Maximum utilization limit measure reports this Oracle-recommended value.

If the value of the Current utilization measure, exceeds the Maximum utilization limit, then the performance of your database is bound to deteriorate. Therefore, ensure that the Config_Limit is always well within the Maximum utilization limit.
Max_utilization_limit Indicates the maximum number of sessions/processes that can be allowed to run on this Oracle database instance. Number If you want to allocate more sessions/processes to your database than what is recommended by Oracle, then its best that you enhance the memory capacity of your database, before altering the resource configurations.
Config_limit Indicates the number of sessions/processes this Oracle database instance is currently configured to handle. Number
Pct_util Indicates the percentage of the configured number of sessions/processes (i.e., the Configured limit) that are currently utilized by this Oracle database instance. Percent Ideally, the value of this measure should be low. If this measure shows high value, then DBA should increase the configuration value of the SESSIONS & PROCESSES parameter in the database parameter file. Otherwise, DBA should identify idle sessions and terminate them, so as to make more space available for new sessions/processes.