|
Measures reported by OraRacTransaTest
Rollbacks are costly operations on the database. This test monitors the percentage of rollbacks happening for user transactions with each node in the target cluster.
Outputs of the test : One set of results for each node in the target Oracle cluster being monitored.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Pct_rollbacks |
Indicates the number of user rollbacks as a percentage of the total user transactions (user commits + user rollbacks) with this node. |
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. |
| User_commits |
Indicates the number of user commits that have happened on this node during the last measurement period |
Number |
|
| User_rollbacks |
Indicates the number of user rollbacks that have happened on this node 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. |
|