SYSTEM STATISTICS (TABLE) NOTES:
  • Statistic Name - Name of the statistic
  • Bytes - Size

  • This query provides information on the full table scan activity. If your application is OLTP only, having long full table scans can be an indicator of having missing or incorrect indexes or untuned SQL.
  • Table fetch by rowid reflect the cumulative number of rows fetched from tables using a TABLE ACCESS BY ROWID operation.
  • Table fetch continued row reflect the cumulative number of continued rows fetched. This value is incremented when accessing a row that is longer than a block in length and when accessing "migrated" rows. Migrated rows are rows that were relocated from their original location to a new location because of an update that increased their size to the point where they could no longer be accommodated inside their original block. Access to migrated rows will cause this statistic's value to increment only if the access is performed by ROWID. Full table scans of tables that contain migrated rows do not cause this counter to increment.
  • Table scan blocks gotten reflect the cumulative number of blocks read for full table scans.
  • Table scans rows gotten reflect the cumulative number of rows read for full table scans.
  • Table scans (cache partitions) is used with the Parallel Query Option. The number of RowID ranges corresponds to the number of simultaneous query server processes that scan the table.
  • Table scans (long scans) indicate a full scan of a table that has > 5 database blocks.
  • Table scans (rowid ranges) is used with the Parallel Query Option. The number of RowID ranges corresponds to the number of simultaneous query server processes that scan the table.
  • Table scans (short scans) indicate a full scan of a table that has <= 5 database blocks.