The frequency of data being changed for several tables in the new Billing application is very unpredictable. A different approach to manage Runstats for these objects is desired. To provide additional information on update patterns for the new Billing Application, the DBA can use what information to better understand the unpredictable workload patterns on the tablespaces?
The access path chosen for a query shows a table space scan, when it appears that there is an index available that would provide a more efficient access path. What situation could have caused a table space scan to be chosen instead of the index?