Tibero Transactions Test

Rollbacks are costly operations on the database. This test monitors the percentage of rollbacks happening for user transactions with a database instance.

Target of the test : A Tibero Database server

Agent deploying the test :An internal agent

Outputs of the test : One set of results for the target Tibero 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
User commits	Indicates the number of user commits that have happened during the last measurement period.	Number
User rollbacks	Indicates the number of user rollbacks that have happened during the last measurement period.	Number	Ideally, there should be few user rollbacks happening. Typically, whenever a delete, insert or update operation is performed on the database, Undo tablespace is consumed, I/O overheads increase, and considerable server time is spent in performing that operation. When such operations are rolledback, these resources are wasted! To conserve resources, its best to keep rollbacks at a minimum.
Percent rollbacks	Indicates The number of user rollbacks as a percentage of the total user transactions (user commits + user rollbacks) with the database.	Percent	The closer the percentage of rollbacks is to zero, the lower the overhead on the database due to rollbacks. The acceptable value of rollbacks will vary from one instance to another and will have to be configured based on the patterns of requests being handled by the database instance.