Oracle RAC Long Running Queries Test

This test tracks the currently executing queries on each node of an Oracle cluster and determines the number of queries that have been running for a long time and on which node.

Target of the test : Oracle Cluster

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each node in the Oracle cluster being monitored

Configurable parameters for the test
  1. TEST PERIOD - How often should the test be executed
  2. Host – The host for which the test is to be configured
  3. Port - The port on which the server is listening
  4. orasid - The variable name of the oracle instance
  5. service name - A ServiceName exists for the entire Oracle RAC system. When clients connect to an Oracle cluster using the ServiceName, then the cluster routes the request to any available database instance in the cluster. By default, the service name is set to none. In this case, the test connects to the cluster using the orasid and pulls out the metrics from that database instance which corresponds to that orasid. If a valid service name is specified instead, then, the test will connect to the cluster using that service name, and will be able to pull out metrics from any available database instance in the cluster.

    To know the ServiceName of a cluster, execute the following query on any node in the target cluster:

    select name, value from v$parameter where name =’service_names’

  6. User – In order to monitor an Oracle RAC, a special database user account has to be User – In order to monitor an Oracle database server, a special database user account has to be created in every Oracle database instance that requires monitoring. A Click here hyperlink is available in the test configuration page, using which a new oracle database user can be created. Alternatively, you can manually create the special database user. When doing so, ensure that this user is vested with the select_catalog_role and create session privileges.

    The sample script we recommend for user creation (in Oracle database server versions before 12c) for eG monitoring is:

    create user oraeg identified by oraeg create role oratest;

    grant create session to oratest;

    grant select_catalog_role to oratest;

    grant oratest to oraeg;

    The sample script we recommend for user creation (in Oracle database server 12c) for eG monitoring is:

    alter session set container=<Oracle_service_name>;

    create user <user_name>identified by <user_password> container=current default tablespace <name_of_default_tablespace> temporary tablespace <name_of_temporary_tablespace>;

    Grant create session to <user_name>;                                 

    Grant select_catalog_role to <user_name>;

    The name of this user has to be specified here.

  7. Password – Password of the specified database user
  8. Confirm password – Confirm the password by retyping it here.
  9. elapsed time - In the ELAPSED TIME text box, specify the duration (in seconds) for which a query should have executed for it to be regarded as a long running query. The default value is 10.
  10. displayquery fulltext - The detailed diagnosis of this test lists the queries that have been running for a long time. In the detailed diagnosis page by default, query strings that are very long are truncated to display the first 1000 characters of the query alone. This is why, the displayquery fulltext flag is set to No by default. To view the full query in the detailed diagnosis page, set this flag to Yes. Note that setting this flag to ‘Yes’ may increase the size of your eG database.  
  11. SSL- By default, this flag is set to Yes, as the target Oracle cluster is SSL-enabled by default. If the target cluster is not SSL-enabled, then set this flag to No.
  12. TRUSTSTORE PATH- This parameter is applicable only if the target Oracle Cluster 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 cluster and collect metrics. For this, provide the full path to this file in this text box. By default, the location of this file is: <eG_INSTALL_DIR>/lib/security/cacerts. To know how to import the certificate into the truststore, refer toPre-requisites for monitoring Oracle Cluster.
  13. TRUSTSTORE TYPE-Specify the type of truststore that contains the certificates for server authentication in this text box. By default, this parameter is set to the value JKS, which implies that the Java Truststore is by default used for storing the certificates. If the certificates in your environment are contained within a different type of truststore, then specify the exact type here - eg., PKCS12.
  14. TRUSSTORE PASSWORD-If a Truststore File path is provided, then, in this text box, provide the password that is used to obtain the associated certificate details from the Truststore File. If none is specified against Truststore Path, then, set this parameter to none.
  15. To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Long running queries:

Indicates the number of queries currently executing on the this cluster node that have been running for more time than the configured ELAPSED TIME.


The detailed diagnosis for this measure indicates the exact queries and which user is executing the queries. This information can be very useful in identifying queries that may be candidates for optimization.

Maximum elapsed time per execution

Indicates the maximum time taken for the query execution.



Average elapsed time

Indicates the average time taken for the query execution