Listing 1
DETAILED ADDM REPORT FOR TASK 'TASK_2024' WITH ID 2024
------------------------------------------------------
Analysis Period: 16-MAY-2004 from 22:00:31 to 23:01:54
Database ID/Instance: 3607854283/1
Database/Instance Names: STARZ10/starz10
Host Name: starz
Database Version: 10.1.0.2.0
Snapshot Range: from 1863 to 1865
Database Time: 1123 seconds
Average Database Load: .3 active sessions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FINDING 1: 93% impact (1041 seconds)
------------------------------------
SQL statements consuming significant database time were found.
RECOMMENDATION 1: SQL Tuning, 93% benefit (1041 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"8np5s8nvpv7v3".
RELEVANT OBJECT: SQL statement with SQL_ID 8np5s8nvpv7v3 and
PLAN_HASH 101258408
select cust_name from bookings o
where status not in
(select status from bookings_hist
where folio_id = o.folio_id
and last_mod_time = o.last_mod_time)
FINDING 2: 89% impact (1000 seconds)
------------------------------------
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
RECOMMENDATION 1: SQL Tuning, 89% benefit (1000 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"8np5s8nvpv7v3".
RELEVANT OBJECT: SQL statement with SQL_ID 8np5s8nvpv7v3 and
PLAN_HASH 101258408
select cust_name from bookings o
where status not in
(select status from bookings_hist
where folio_id = o.folio_id
and last_mod_time = o.last_mod_time)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ADDITIONAL INFORMATION
----------------------
Wait class "Administrative" was not consuming significant database time.
Wait class "Application" was not consuming significant database time.
Wait class "Cluster" 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 "Scheduler" was not consuming significant database time.
Wait class "Other" was not consuming significant database time.
Wait class "User I/O" 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.
|
Articles
Printer View