          ADDM Report for Task 'TASK_472'
          -------------------------------

Analysis Period
---------------
AWR snapshot range from 349 to 350.
Time period starts at 04-AUG-08 11.53.01 AM
Time period ends at 04-AUG-08 11.55.03 AM

Analysis Target
---------------
Database '15V' with DB ID 1635817246.
Database version 11.1.0.6.0.
ADDM performed an analysis of instance 15v, numbered 1 and hosted at stade50.

Activity During the Analysis Period
-----------------------------------
Total database time was 743 seconds.
The average number of active sessions was 6.09.

Summary of Findings
-------------------
   Description             Active Sessions      Recommendations
                           Percent of Activity
   ----------------------  -------------------  ---------------
1  Undersized Shared Pool  6.09 | 100           1
2  CPU Usage               6.09 | 100           2
3  Soft Parse              .77 | 12.63          2


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


          Findings and Recommendations
          ----------------------------

Finding 1: Undersized Shared Pool
Impact is 24.89 active sessions, 408.82% of total activity.
-----------------------------------------------------------
Hard parses due to an inadequately sized shared pool were consuming
significant database time.
The value of parameter "shared_pool_size" was "92 M" during the analysis
period.

   Recommendation 1: Database Configuration
   Estimated benefit is 6.09 active sessions, 100% of total activity.
   ------------------------------------------------------------------
   Action
      Increase the shared pool size by setting the value of parameter
      "shared_pool_size" to 128 M.

   Symptoms That Led to the Finding:
   ---------------------------------
      Hard parsing of SQL statements was consuming significant database time.
      Impact is 3.92 active sessions, 64.32% of total activity.
         Contention for latches related to the shared pool was consuming
         significant database time.
         Impact is 4.15 active sessions, 68.13% of total activity.
            Wait class "Concurrency" was consuming significant database time.
            Impact is 4.15 active sessions, 68.16% of total activity.


Finding 2: CPU Usage
Impact is 6.09 active sessions, 100% of total activity.
-------------------------------------------------------
Host CPU was a bottleneck and the instance was consuming 80% of the host CPU.
All wait times will be inflated by wait for CPU.
Host CPU consumption was 95%.  CPU runqueue statistics are not available from
the host's OS. This disables ADDM's ability to estimate the impact of this
finding.  The instance spent significant time on CPU. However, there were no
predominant SQL statements responsible for the CPU load.

   Recommendation 1: Host Configuration
   Estimated benefit is 6.09 active sessions, 100% of total activity.
   ------------------------------------------------------------------
   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: Application Analysis
   Estimated benefit is .5 active sessions, 8.28% of total activity.
   -----------------------------------------------------------------
   Action
      Parsing SQL statements were consuming significant CPU. Please refer to
      other findings in this task about parsing for further details.


Finding 3: Soft Parse
Impact is .77 active sessions, 12.63% of total activity.
--------------------------------------------------------
Soft parsing of SQL statements was consuming significant database time.

   Recommendation 1: Application Analysis
   Estimated benefit is .77 active sessions, 12.63% of total activity.
   -------------------------------------------------------------------
   Action
      Investigate application logic to keep open the frequently used cursors.
      Note that cursors are closed by both cursor close calls and session
      disconnects.

   Recommendation 2: Database Configuration
   Estimated benefit is .77 active sessions, 12.63% of total activity.
   -------------------------------------------------------------------
   Action
      Consider increasing the maximum number of open cursors a session can
      have by increasing the value of parameter "open_cursors".
   Action
      Consider increasing the session cursor cache size by increasing the
      value of parameter "session_cached_cursors".
   Rationale
      The value of parameter "open_cursors" was "52" during the analysis
      period.
   Rationale
      The value of parameter "session_cached_cursors" was "50" during the
      analysis period.

   Symptoms That Led to the Finding:
   ---------------------------------
      Contention for latches related to the shared pool was consuming
      significant database time.
      Impact is 4.15 active sessions, 68.13% of total activity.
         Wait class "Concurrency" was consuming significant database time.
         Impact is 4.15 active sessions, 68.16% of total activity.



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

          Additional Information
          ----------------------

Miscellaneous Information
-------------------------
Wait class "Application" was not consuming significant database time.
Wait class "Commit" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.

