FINDING 4: 25% impact (2924 seconds)
------------------------------------
Individual database segments responsible for significant user I/O wait were
found.

   RECOMMENDATION 1: Segment Tuning, 12% benefit (1431 seconds)
      ACTION: Investigate application logic involving I/O on TABLE
         "L2000.ORDERS" with object id 12906.
         RELEVANT OBJECT: database object with id 12906
      RATIONALE: The I/O usage statistics for the object are: 6 full object
         scans, 511370 physical reads, 188 physical writes and 0 direct reads.
      RATIONALE: The SQL statement with SQL_ID "22bmtfpykv40c" spent
         significant time waiting for User I/O on the hot object.
         RELEVANT OBJECT: SQL statement with SQL_ID 22bmtfpykv40c

SELECT * FROM V$SQL WHERE SQLID = '22bmtfpykv40c'

SQL>select sql_text from v$sql where sql_id='22bmtfpykv40c'

SQL> select * from test where object_id < 1000;

853 rows selected.


Statistics
----------------------------------------------------------
        288  recursive calls
          0  db block gets
        724  consistent gets
        571  physical reads
          0  redo size
      38396  bytes sent via SQL*Net to client
       1001  bytes received via SQL*Net from client
         58  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
        853  rows processed

SQL>

SQL> select * from test where object_id < 1000;

853 rows selected.


Statistics
----------------------------------------------------------
          0  recursive calls
          0  db block gets
        631  consistent gets
          0  physical reads
          0  redo size
      38396  bytes sent via SQL*Net to client
       1001  bytes received via SQL*Net from client
         58  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
        853  rows processed

SQL>