ADDM Report

   

DETAILED ADDM REPORT FOR TASK 'TASK_212' WITH ID 212

----------------------------------------------------

   

Analysis Period: 17-JUL-2009 from 13:02:17 to 14:00:21

Database ID/Instance: 1173970302/1

Database/Instance Names: ORCL/orcl

Host Name: edrsr4p1.us.oracle.com

Database Version: 10.2.0.1.0

Snapshot Range: from 29 to 30

Database Time: 1889 seconds

Average Database Load: .5 active sessions

   

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

   

   

FINDING 1: 83% impact (1568 seconds)

------------------------------------

PL/SQL execution consumed significant database time.

   

RECOMMENDATION 1: SQL Tuning, 83% benefit (1568 seconds)

ACTION: Tune the PL/SQL block with SQL_ID "2r93h0jt0jy5t". Refer to the

"Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User's Guide

and Reference"

RELEVANT OBJECT: SQL statement with SQL_ID 2r93h0jt0jy5t

begin

for i in 1..100000000 loop

for j in 1..100000000 loop

dbms_output.put_line(3/4/5/6);

end loop;

end loop;

end;

   

FINDING 2: 80% impact (1514 seconds)

------------------------------------

Time spent on the CPU by the instance was responsible for a substantial part

of database time.

   

RECOMMENDATION 1: SQL Tuning, 80% benefit (1514 seconds)

ACTION: Tune the PL/SQL block with SQL_ID "2r93h0jt0jy5t". Refer to the

"Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User's Guide

and Reference"

RELEVANT OBJECT: SQL statement with SQL_ID 2r93h0jt0jy5t

begin

for i in 1..100000000 loop

for j in 1..100000000 loop

dbms_output.put_line(3/4/5/6);

end loop;

end loop;

end;

   

   

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

   

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.

Wait class "User I/O" was not consuming significant database time.

Session connect and disconnect calls were not consuming significant database

time.

Hard parsing of SQL statements was 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.