Siebel Long Run Queries Test

This test tracks the currently executing queries on the Oracle Database server which is the backend database of the target Siebel Application server and determines the number of queries that have been running for a long time.

This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Siebel Application (7.x) as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the << button to move the test to the ENABLED TESTS list. Finally, click the Update button.


This test will report metrics only if the backend database of the target Siebel Application Server being monitored is an Oracle Database server.

Target of the test : A Siebel Application server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the target Siebel Application Server being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


The port number at which the specified host listens to. By default, this is 1199.

Oracle Server IP

Specify the IP address of the Oracle Database server which is the backend database of the target Siebel Application server.

Oracle Port No

Specify the port number of the Oracle Database server.

Oracle SID

Specify the SID of the Oracle Database server.

Oracle UserName

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.

Oracle Password

Password of the specified database user.

Confirm Password

Confirm the password by retyping it here.

Elapsed Time (Secs)

For a query to be regarded as a long running query, in the Elapsed Time text box, specify the duration (in seconds) beyond which the query continued execution. The default value is 10.

DD Row Count

By default, the detailed diagnosis of this test, if enabled, will report only the top-10 records. This is why, the DD Row Count parameter is set to 10 by default. If you want to include more or less records in detailed diagnosis, then change the value of this parameter accordingly.

Detailed Diagnosis

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 run queries

Indicates the number of queries currently executing on the database server 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.