Finding 1: I/O Throughput
Impact is .87 active sessions, 58.65% of total activity.
--------------------------------------------------------
The throughput of the I/O subsystem was significantly lower than expected.

   Recommendation 1: Host Configuration
   Estimated benefit is .87 active sessions, 58.65% of total activity.
   -------------------------------------------------------------------
   Action
      Consider increasing the throughput of the I/O subsystem. Oracle's
      recommended solution is to stripe all data files using the SAME
      methodology. You might also need to increase the number of disks for
      better performance.
   Rationale
      During the analysis period, the average data files' I/O throughput was
      1.1 M per second for reads and 1 M per second for writes. The average
      response time for single block reads was 57 milliseconds.

   Recommendation 2: Host Configuration
   Estimated benefit is .79 active sessions, 53.66% of total activity.
   -------------------------------------------------------------------
   Action
      The performance of some data and temp files was significantly worse than
      others. If striping all files using the SAME methodology is not
      possible, consider striping these file over multiple disks.
   Rationale
      For file /odb/rrw03/oradata02/RRWDB02T/datafile/o1_mf_eipinfod_696xqxwj_
      .dbf, the average response time for single block reads was 99
      milliseconds, and the total excess I/O wait was 3049 seconds.
      Related Object
         Database file
         "/odb/rrw03/oradata02/RRWDB02T/datafile/o1_mf_eipinfod_696xqxwj_.dbf"
   Rationale
      For file /odb/rrw03/oradata01/RRWDB02T/datafile/o1_mf_system_68f0gld5_.d
      bf, the average response time for single block reads was 143
      milliseconds, and the total excess I/O wait was 310 seconds.
      Related Object
         Database file
         "/odb/rrw03/oradata01/RRWDB02T/datafile/o1_mf_system_68f0gld5_.dbf"
   Rationale
      For file /odb/rrw03/oradata01/RRWDB02T/datafile/o1_mf_sysaux_68f0glo5_.d
      bf, the average response time for single block reads was 134
      milliseconds, and the total excess I/O wait was 145 seconds.
      Related Object
         Database file
         "/odb/rrw03/oradata01/RRWDB02T/datafile/o1_mf_sysaux_68f0glo5_.dbf"
   Rationale
      For file /odb/rrw03/oradata02/RRWDB02T/datafile/o1_mf_rev_tbs_696xr92m_.
      dbf, the average response time for single block reads was 208
      milliseconds, and the total excess I/O wait was 105 seconds.
      Related Object
         Database file
         "/odb/rrw03/oradata02/RRWDB02T/datafile/o1_mf_rev_tbs_696xr92m_.dbf"

   Symptoms That Led to the Finding:
   ---------------------------------
      Wait class "User I/O" was consuming significant database time.
      Impact is 1.03 active sessions, 69.82% of total activity.

File name | avg response time, single block reads (ms) | total excess I/O wait (sec)
/odb/rrw03/oradata02/RRWDB02T/datafile/o1_mf_eipinfod_696xqxwj_.dbf	 99    3049
/odb/rrw03/oradata01/RRWDB02T/datafile/o1_mf_system_68f0gld5_.dbf	143	310
/odb/rrw03/oradata01/RRWDB02T/datafile/o1_mf_sysaux_68f0glo5_.dbf	134	145
/odb/rrw03/oradata02/RRWDB02T/datafile/o1_mf_rev_tbs_696xr92m_.dbf	208	105