Tibero System Waits Test

This test monitors the system 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.


In the Exclude text box, provide a comma-separated list of wait events that need not be monitored. For example, your specification can be: Data_file_init_write,db_file_single_write. By default, 'none' is displayed here indicating that all system wait events are monitored, by default.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

New waits

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


High waits indicate a problem, but not always. Sometimes waits are just a normal part of database operations. For example, high waits on ‘db file sequential read’ events may indicate a disk bottleneck, but you must check your average disk queue length for each disk spindle to be sure that these waits are abnormal.

If a high number of waits are observed on a specific event, you can use the detailed diagnosis capability of the Tibero Session Waits test to figure out whether any current connections have contributed to the increase in waits.

Total wait timeouts

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. Use the Tibero-specific documentation to probe the cause of the timeout.

Average time waited

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


By comparing the value of this measure across all monitored wait events, you can determine where the database spends most of its time.

Time waited

Indicates the total amount of time for which the waits on this wait event persisted.