Tibero System Wait Events Test

This test monitors system wait classes for the number and average time of system wait events. Using this test, administrators can nail the wait class on which the Tibero database server spends more time and why, so that performance tuning decisions can be taken.

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 system wait class monitored on the Tibero Database server.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	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.
Exclude	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 wait events	This measure indicates the number of waits for each wait class during this measurement period.	Number
Average time waited	Indicates the average time in seconds for each wait event in this class, during this measurement period.	Secs	If the value of this measure is unusually high, then you can get the identify time-consuming wait event, using the detailed diagnosis of this measure.
Maximum time waited	Indicates the maximum time in seconds for each wait event in this class persisted during the last measurement period.	Secs