Oracle Client Connections Test

This test reveals how much CPU and memory is utilized by the processes executed by the Oracle clients on the database server. In the event of excessive resource utilization on the database server, administrators can use this test and Oracle Processes test to determine which processes consume more server resources - the critical Oracle database server processes, or the client processes?

Note:

• This test works only on Unix platforms.

• This test is applicable for Oracle Database with Multi-tenancy i.e., CDB(Container Database) and PDB (Pluggable Database) configuration.

Target of the test : An Oracle server on Unix

Agent deploying the test :An internal agent

Outputs of the test : One set of results for every Oracle database server monitored.

Configurable parameters for the test

Parameter	Description
Test Period	How often should the test be executed
Host	The host for which the test is to be configured.
Port	The port at which the specified host listens. By default, this is NULL
Listener Name	Specify the Oracle listener name. By default, this value will be the same as the SID.
IsPassive	If the value chosen is yes, then the Oracle server under consideration is a passive server in an Oracle cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable" by the agent if the server is not up.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Processes running:	Indicates the number of client processes currently executing.	Number	This value indicates if too many or too few processes are executing on the host.
CPU usage:	Indicates the total percentage CPU utilization of the client processes.	Percent	A very high value could indicate that the client processes are consuming excessive CPU resources.
Memory usage:	The ratio of the resident set size of the client processes to the physical memory of the host system on which they execute, expressed as a percentage.	Percent	A sudden increase in memory utilization for the client processes may be indicative of memory leaks in the corresponding application.