Page History
...
| Description | |
|---|---|
| What to do next | Perform one of the following options:
|
| Advice | To reduce the Range Skip Scan resource consumption consider:
|
...
| Description | |
|---|---|
| What to do next | Perform one of the following options:
|
| Advice | To avoid a Cartesian Join verify that you have provided the proper Join conditions in the statement's WHERE clause. |
...
Several Object tab findings exist to help the user. The Objects tab includes the following findings:■ Heavy
...
...
- Full Scan Reading Deleted Blocks
...
- Index Clustering Factor Very High
...
- Buffer Wait Contention
...
- Object or Row Lock Contention
...
- Bottleneck in RAC Wait
...
- Many Chained Rows
...
- Statistics Not Updated on Object
...
- Changes Detected in Object Structure
...
- Table Grew
...
- Considerable
...
- Partition Is Accessed Extensively
...
- Segment Hit Ratio Very Low
...
- Extensive Activity on Non-explained Statements
...
- Extensive Index Range Scan Access
...
- Extensive Full Index Scan Access
...
- Extensive Fast Full Index Scan Access
...
- Extensive Index Skip Scan Access
Heavy Index Overhead
Most of the I/O wait on indexes is due to the fetching of index pages from disk that reflect changes made by INSERT, DELETE, UPDATE, or MERGE statements. The index does not appear in the execution plan.
...