Oracle Transactions Test
Rollbacks are costly operations on the database. This test monitors the percentage of rollbacks happening for user transactions with a database instance.
This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Oracle Database as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the << button to move the test to the ENABLED TESTS list. Finally, click the Update button.
Target of the test : An Oracle server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every SID monitored.
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
User commits: |
The number of user commits that have happened during the last measurement period |
Number |
|
User rollbacks: |
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: |
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. |