DETAILED ADDM REPORT FOR TASK 'TASK_12669' WITH ID 12669
          --------------------------------------------------------

              Analysis Period: 12-JAN-2007 from 14:00:02 to 15:00:04
         Database ID/Instance: 2384218455/1
      Database/Instance Names: O102EE1/o102ee1
                    Host Name: hpap0601
             Database Version: 10.2.0.3.0
               Snapshot Range: from 5486 to 5489
                Database Time: 2263 seconds
        Average Database Load: .6 active sessions

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


FINDING 1: 49% impact (1109 seconds)
------------------------------------
Individual database segments responsible for significant user I/O wait were
found.

   RECOMMENDATION 1: Segment Tuning, 49% benefit (1109 seconds)
      ACTION: Run "Segment Advisor" on TABLE "SCOTT.EMP" with object id 16095.
         RELEVANT OBJECT: database object with id 16095
      ACTION: Investigate application logic involving I/O on TABLE "SCOTT.EMP"
         with object id 16095.
         RELEVANT OBJECT: database object with id 16095
      RATIONALE: The I/O usage statistics for the object are: 3982 full object
         scans, 24095340 physical reads, 0 physical writes and 0 direct reads.
      RATIONALE: The SQL statement with SQL_ID "9a5wbppva8npu" spent
         significant time waiting for User I/O on the hot object.
         RELEVANT OBJECT: SQL statement with SQL_ID 9a5wbppva8npu
         SELECT ENAME FROM EMP WHERE EMPNO = :num

   SYMPTOMS THAT LED TO THE FINDING:
      SYMPTOM: Wait class "User I/O" was consuming significant database time.
               (49% impact [1109 seconds])

FINDING 2: 24% impact (544 seconds)
-----------------------------------
SQL statements consuming significant database time were found.

   RECOMMENDATION 1: SQL Tuning, 91% benefit (2056 seconds)
      ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
         "9a5wbppva8npu".
         RELEVANT OBJECT: SQL statement with SQL_ID 9a5wbppva8npu and
         PLAN_HASH 3956160932
         SELECT ENAME FROM EMP WHERE EMPNO = :num
      ACTION: Investigate the SQL statement with SQL_ID "9a5wbppva8npu" for
         possible performance improvements.
         RELEVANT OBJECT: SQL statement with SQL_ID 9a5wbppva8npu and
         PLAN_HASH 3956160932
         SELECT ENAME FROM EMP WHERE EMPNO = :num
      RATIONALE: SQL statement with SQL_ID "9a5wbppva8npu" was executed 1000
         times and had an average elapsed time of 0.54 seconds.
      RATIONALE: Waiting for event "read by other session" in wait class "User
         I/O" accounted for 44% of the database time spent in processing the
         SQL statement with SQL_ID "9a5wbppva8npu".
      RATIONALE: Waiting for event "db file scattered read" in wait class
         "User I/O" accounted for 11% of the database time spent in processing
         the SQL statement with SQL_ID "9a5wbppva8npu".

FINDING 3: 24% impact (541 seconds)
-----------------------------------
Time spent on the CPU by the instance was responsible for a substantial part
of database time.

   RECOMMENDATION 1: SQL Tuning, 91% benefit (2056 seconds)
      ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
         "9a5wbppva8npu".
         RELEVANT OBJECT: SQL statement with SQL_ID 9a5wbppva8npu and
         PLAN_HASH 3956160932
         SELECT ENAME FROM EMP WHERE EMPNO = :num
      ACTION: Investigate the SQL statement with SQL_ID "9a5wbppva8npu" for
         possible performance improvements.
         RELEVANT OBJECT: SQL statement with SQL_ID 9a5wbppva8npu and
         PLAN_HASH 3956160932
         SELECT ENAME FROM EMP WHERE EMPNO = :num
      RATIONALE: SQL statement with SQL_ID "9a5wbppva8npu" was executed 1000
         times and had an average elapsed time of 0.54 seconds.
      RATIONALE: Waiting for event "read by other session" in wait class "User
         I/O" accounted for 44% of the database time spent in processing the
         SQL statement with SQL_ID "9a5wbppva8npu".
      RATIONALE: Waiting for event "db file scattered read" in wait class
         "User I/O" accounted for 11% of the database time spent in processing
         the SQL statement with SQL_ID "9a5wbppva8npu".
      RATIONALE: Average CPU used per execution was 0.54 seconds.

FINDING 4: 8.6% impact (194 seconds)
------------------------------------
Individual SQL statements responsible for significant user I/O wait were
found.

   RECOMMENDATION 1: SQL Tuning, 91% benefit (2056 seconds)
      ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
         "9a5wbppva8npu".
         RELEVANT OBJECT: SQL statement with SQL_ID 9a5wbppva8npu and
         PLAN_HASH 3956160932
         SELECT ENAME FROM EMP WHERE EMPNO = :num
      ACTION: Investigate the SQL statement with SQL_ID "9a5wbppva8npu" for
         possible performance improvements.
         RELEVANT OBJECT: SQL statement with SQL_ID 9a5wbppva8npu and
         PLAN_HASH 3956160932
         SELECT ENAME FROM EMP WHERE EMPNO = :num
      RATIONALE: SQL statement with SQL_ID "9a5wbppva8npu" was executed 1000
         times and had an average elapsed time of 0.54 seconds.
      RATIONALE: Waiting for event "read by other session" in wait class "User
         I/O" accounted for 44% of the database time spent in processing the
         SQL statement with SQL_ID "9a5wbppva8npu".
      RATIONALE: Waiting for event "db file scattered read" in wait class
         "User I/O" accounted for 11% of the database time spent in processing
         the SQL statement with SQL_ID "9a5wbppva8npu".
      RATIONALE: Average time spent in User I/O wait events per execution was
         0.19 seconds.

   SYMPTOMS THAT LED TO THE FINDING:
      SYMPTOM: Wait class "User I/O" was consuming significant database time.
               (49% impact [1109 seconds])

FINDING 5: 7.3% impact (164 seconds)
------------------------------------
The SGA was inadequately sized, causing additional I/O or hard parses.

   RECOMMENDATION 1: DB Configuration, 7.3% benefit (164 seconds)
      ACTION: Increase the size of the SGA by setting the parameter
         "sga_target" to 384 M.

   ADDITIONAL INFORMATION:
      The value of parameter "sga_target" was "256 M" during the analysis
      period.

   SYMPTOMS THAT LED TO THE FINDING:
      SYMPTOM: Wait class "User I/O" was consuming significant database time.
               (49% impact [1109 seconds])
      SYMPTOM: Hard parsing of SQL statements was consuming significant
               database time. (2.2% impact [50 seconds])


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

          ADDITIONAL INFORMATION
          ----------------------

Wait class "Application" was not consuming significant database time.
Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.

The analysis of I/O performance is based on the default assumption that the
average read time for one database block is 10000 micro-seconds.

An explanation of the terminology used in this report is available when you
run the report with the 'ALL' level of detail.