eG Monitoring
 

Measures reported by OraScanTest

Full table scans on a database instance can degrade the performance of the database. This test monitors the extent of full table scans happening on the database.

 

Measurement Description Measurement Unit Interpretation
Pct_long_table_scans The percentage of long table scans happening in the database. Percent Ideally, this value should be lower than 10%. If more than 20% of scans are happening on long tables, the database/accesses to the database may need to be tuned.

Full table scans may happen due to several reasons. For instance, the indexes of a table may not be used properly in queries. By tuning the queries, the full table scans can be reduced and the database performance significantly improved.
Long_table_scans The number of long table scans that happened on the database instance during the last measurement period. Number  
Short_table_scans The number of short table scans that happened on the database instance during the last measurement period. Number  
Full_table_scans Indicates the number of full table scans that happened on the database instance during the last measurement period. Number Full table scans may happen due to several reasons. For instance, the indexes of a table may not be used properly in queries. By tuning the queries, the full table scans can be reduced and the database performance significantly improved.

The detailed diagnosis of this measure provides details of the SQL ID, Hash Value, Address, SQL Query that is used to perform this scan, the number of times the Executions were performed, etc.