Table Scans: Problem Analysis (Oracle) 
The Table Scans entry that appears in the Database Alert Monitor and the Database Monitor shows the number of sequential read operations on tables per day. If the number of sequential read operations per day is very high, you should perform further analyses. Sequential data access is generally not very efficient, which is why you should try to minimize the number of full table scans.
Causes
See also:
Missing IndexesTo identify tables affected by sequential read operations:
Alternatively, use transaction code
ST04 .You reach the Database Alert Monitor.
If the processes belong to an Oracle user (for example, SYS ), the table scans are actually caused by the database. Processes belonging to the SAP user SAPR3 are important for further analysis.
From the R/3 main screen, choose Tools ® Administration ® Monitor ® System monitoring ® Process overview.
Alternatively, use transaction code SM50 ( Work Process Load Monitor: Overview).
There are two ways of doing this:
-
Start the report with an activated SQL trace-
Analyze the program.See also:
Missing IndexesIf none of these tables have indexes missing, the table scans are probably caused by an SQL statement in the report that has not been optimized.
See also:
Table Scans/Table Fetch (Oracle) Monitoring Table Access Methods (Oracle) Monitoring the Shared SQL Area (Oracle)