Tibero Session Waits Test

The test monitors the session level wait events on the Tibero database server and reports key performance statistics pertaining to every event. Effective wait analysis helps determine where the database spends most of its time, and which current connections are responsible for the reported waits.

Target of the test : A Tibero Database server

Agent deploying the test :An internal agent

Outputs of the test : One set of results for each target database 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 to which the specified host listens. By default, the port number is 8629.

User and Password

In order to monitor a Tibero database server, a special database user account has to be created in every Tibero database instance that requires monitoring. A Click here hyperlink is available in the test configuration page, using which a new Tibero 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 any dictionary and create session privileges.

The sample script we recommend for user creation for eG monitoring is:

create user tibeg identified by tibeg default tablespace <users> temporary tablespace<temp>;

grant create session, select any dictionary tibeg;

The name of this user has to be specified in the User text box, and the password of this user has to be entered in the Password text box. This login information is required to query Tibero's internal dynamic views, so as to fetch the current status / health of the various database components.

Confirm Password

Confirm the Password by retyping it here.

Tibero SID

Specify the SID of the target Tibero database instance that is to be monitored in this text box.


Here, provide a comma-separated list of wait events that need not be monitored. For example, your specification can be: buffer_busy_waits,SQL*Net_message_from_client. By default, 'none' is displayed here indicating that all wait events are monitored, by default.

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

New waits

Indicates the total number of times waits happened on this event since the last measurement period.


If the value of this measure is very high, then you can drill down further using the detailed diagnosis capability (if enabled) of the eG Enterprise to discover which current connections may be responsible for this. The detailed diagnosis of this measure reveals the session IDs of the sessions that caused the wait events to occur, the users who initiated the sessions, and the total number of waits, wait time, and the maximum wait time for every session.

Total waits timedout

Indicates the total number of waits on this event that timed out since the last measurement period.


A large number of timed out wait events is typically, undesirable.

Average time waited

Indicates the average duration for which the waits on this wait event persisted since the last measurement period.


Ideally, the value of this measure should be low. A very high value or a consistent increase in this value is indicative of a problem situation requiring further investigation. Use the detailed diagnosis capability to zoom into the session that has contributed to the abnormal increase in wait time.

Maximum time waited

Indicates the high watermark of wait time for this wait event.