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.

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

TEST PERIOD - How often should the test be executed Host – The host for which the test is to be configured Port - The port on which the specified host is listening listenername - 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. SSL- By default, this flag is set to No, as the target Oracle database is not SSL-enabled by default. If the target database is SSL-enabled, then set this flag to Yes. SSL Cipher-This parameter is applicable only if the target Oracle database is SSL-enabled, if not, set this parameter to none. A cipher suite is a set of cryptographic algorithms that are used before a client application and server exchange information over an SSL/TLS connection. It consist of sets of instructions on how to secure a network through SSL (Secure Sockets Layer) or TLS (Transport Layer Security). In this text box, provide a comma-seperated list of cipher suites that are allowed for SSL/TLS connection to the target database. By default, this parameter is set to none. TRUSTSTORE FILE- This parameter is applicable only if the target Oracle database is SSL-enabled, if not, set this parameter to none. TrustStore is used to store certificates from Certified Authorities (CA) that verify and authenticate the certificate presented by the server in an SSL connection. Therefore, the eG agent should have access to the truststore where the certificates are stored to authenticate and connect with the target database and collect metrics. For this, first import the certificates into the following default location <eG_INSTALL_DIR>/lib/security/mytruststore.jks. To know how to import the certificate into the truststore, refer toPre-requisites for monitoring Oracle Cluster. Then, provide the truststore file name in this text box. For example: mytruststore.jks. By default, none is specified against this text box. TRUSTSTORE TYPE-This parameter is applicable only if the target Oracle database is SSL-enabled, if not, set this parameter to none.Specify the type of truststore that contains the certificates for server authentication in this text box. For eg.,JKS. By default, this parameter is set to the value none. TRUSSTORE PASSWORD-This parameter is applicable only if the target Oracle database is SSL-enabled, if not, set this parameter to none. If a Truststore File name is provided, then, in this text box, provide the password that is used to obtain the associated certificate details from the Truststore File. By default, this parameter is set to none.

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.