|
Measures reported by OraRacDataFileTest
This test indicates the level of read/write activity on each datafile in the shared cluster storage.
Outputs of the test : One set of results for every datafile in the shared cluster storage monitored.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Phy_block_read_rate |
Indicates the rate at which disk blocks are being read from this datafile. |
Blocks/Sec |
A scenario in which more than 50% of blocks are being read from a single datafile could signify a problem. |
| Phy_block_write_rate |
Indicates the rate at which disk blocks are being written to this datafile. |
Blocks/Sec |
A scenario in which more than 50% of blocks are being written to a single datafile could signify a problem. Too much activity to a specific datafile can result in reduced database performance. To improve performance, consider balancing I/O across disks, and reorganize tables across tablespaces to reduce activity to a specific datafile. |
| Pct_total_IO |
Indicates the percentage of total I/O operations on the database server that were handled by this data file. |
Percent |
Disk reads and writes are expensive operations and all I/Os should be balanced across the different data files of an Oracle database for optimal performance. This metric reports the percentage of all I/O of an Oracle database that are happening on each of the data files of the Oracle database. This metric allows an Oracle administrator to determine which is/are the hot data file(s) (e.g., which data file is handling 80% of the total I/O). |
|