DETAILED ADDM REPORT FOR TASK 'TASK_14876' WITH ID 14876
          --------------------------------------------------------

              Analysis Period: 02-APR-2007 from 20:01:05 to 20:09:18
         Database ID/Instance: 2384218455/1
      Database/Instance Names: O102EE1/o102ee1
                    Host Name: hpap0601
             Database Version: 10.2.0.3.0
               Snapshot Range: from 7478 to 7479
                Database Time: 1871 seconds
        Average Database Load: 3.8 active sessions

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


FINDING 1: 100% impact (1871 seconds)
-------------------------------------
Host CPU was a bottleneck and the instance was consuming 77% of the host CPU.
All wait times will be inflated by wait for CPU.

   RECOMMENDATION 1: Host Configuration, 100% benefit (1871 seconds)
      ACTION: Consider adding more CPUs to the host or adding instances
         serving the database on other hosts.
      ACTION: Also consider using Oracle Database Resource Manager to
         prioritize the workload from various consumer groups.

   RECOMMENDATION 2: SQL Tuning, 3% benefit (57 seconds)
      ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
         "8zt0p6avg76yz".
         RELEVANT OBJECT: SQL statement with SQL_ID 8zt0p6avg76yz and
         PLAN_HASH 1396384608
         SELECT COUNT(ename) FROM emp3 WHERE emp3no = 1
      RATIONALE: SQL statement with SQL_ID "8zt0p6avg76yz" was executed 1000
         times and had an average elapsed time of 0.077 seconds.
      RATIONALE: Average CPU used per execution was 0.056 seconds.

   ADDITIONAL INFORMATION:
      Host CPU consumption was 94%.  CPU runqueue statistics are not available
      from the host's OS. This disables ADDM's ability to estimate the impact
      of this finding.

FINDING 2: 14% impact (271 seconds)
-----------------------------------
Individual database segments responsible for significant user I/O wait were
found.

   RECOMMENDATION 1: Segment Tuning, 14% benefit (271 seconds)
      ACTION: Run "Segment Advisor" on TABLE "SCOTT.EMP1" with object id
         15339.
         RELEVANT OBJECT: database object with id 15339
      ACTION: Investigate application logic involving I/O on TABLE
         "SCOTT.EMP1" with object id 15339.
         RELEVANT OBJECT: database object with id 15339
      RATIONALE: The I/O usage statistics for the object are: 15926 full
         object scans, 3254786 physical reads, 0 physical writes and 0 direct
         reads.

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

FINDING 3: 4.2% impact (78 seconds)
-----------------------------------
SQL statements consuming significant database time were found.

   RECOMMENDATION 1: SQL Tuning, 3% benefit (57 seconds)
      ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
         "8zt0p6avg76yz".
         RELEVANT OBJECT: SQL statement with SQL_ID 8zt0p6avg76yz and
         PLAN_HASH 1396384608
         SELECT COUNT(ename) FROM emp3 WHERE emp3no = 1
      RATIONALE: SQL statement with SQL_ID "8zt0p6avg76yz" was executed 1000
         times and had an average elapsed time of 0.077 seconds.

FINDING 4: 4% impact (76 seconds)
---------------------------------
Hard parsing of SQL statements was consuming significant database time.

   NO RECOMMENDATIONS AVAILABLE

   ADDITIONAL INFORMATION:
      Hard parses due to cursor environment mismatch were not consuming
      significant database time.
      Hard parsing SQL statements that encountered parse errors was not
      consuming significant database time.
      Hard parses due to literal usage and cursor invalidation were not
      consuming significant database time.
      The SGA was adequately sized.


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

          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.