Tibero Rollbacks Test

The immediate availability of rollback segments for the various activities that occur in a database server is very critical. Contention for rollback segments can adversely impact the performance of a database server and hence, needs to be detected and reported immediately. To detect contention for rollback segments, the Tibero Rollbacks test monitors the degree of contention for buffers that contain rollback segment blocks.

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.
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.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
System segment waits	Indicates the ratio of the number of waits for acquiring a header block or a block of the SYSTEM rollback segment to the total number of requests for data, measured over a period of time.	Percent	If the number of waits for any class of block exceeds 1% of the total number of requests, the size of the SYSTEM rollback segment needs to be increased.
Non-system segment waits	Indicates the ratio of the number of waits for acquiring a header block or any other block of a non-SYSTEM rollback segment to the total number of requests for data, measured over a period of time.	Percent	If the number of waits for any class of block exceeds 1% of the total number of requests, the sizes of the existing rollback segments may need to be increased. Alternatively, additional rollback segments to may be created to reduce contention.