Orastory.files.wordpress.com



DETAILED ADDM REPORT FOR TASK 'TASK_2315' WITH ID 2315

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

Analysis Period: 07-FEB-2007 from 00:00:26 to 02:00:38

Database ID/Instance: 160101898/1

Database/Instance Names: xxxxxxxxx/xxxxxxxx

Host Name: xxxxxxxxx

Database Version: 10.2.0.3.0

Snapshot Range: from 328 to 330

Database Time: 28158 seconds

Average Database Load: 3.9 active sessions

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

FINDING 1: 100% impact (28158 seconds)

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

Host CPU was a bottleneck and the instance was consuming 97% of the host CPU.

All wait times will be inflated by wait for CPU.

RECOMMENDATION 1: Host Configuration, 100% benefit (28158 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.

ADDITIONAL INFORMATION:

Host CPU consumption was 97%. 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.

FINDING 2: 100% impact (28121 seconds)

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

PL/SQL execution consumed significant database time.

RECOMMENDATION 1: SQL Tuning, 100% benefit (28149 seconds)

ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID

"37273f70f5g29".

RELEVANT OBJECT: SQL statement with SQL_ID 37273f70f5g29 and

PLAN_HASH 915946702

select column_value from

table(cast(ctxsys.drvparx.ParallelPopuIndex(cursor(select /*+

PARALLEL(base 4) FULL(base) */ rowid, NULL, NULL, NULL, 'N' from

"xxxxxx"."xxxx" base), :idxid, :idxown, :idxname,

:ixpname,:popstate) as sys.odcivarchar2list))

ACTION: Investigate the SQL statement with SQL_ID "37273f70f5g29" for

possible performance improvements.

RELEVANT OBJECT: SQL statement with SQL_ID 37273f70f5g29 and

PLAN_HASH 915946702

select column_value from

table(cast(ctxsys.drvparx.ParallelPopuIndex(cursor(select /*+

PARALLEL(base 4) FULL(base) */ rowid, NULL, NULL, NULL, 'N' from

"xxxxxx"."xxxxx" base), :idxid, :idxown, :idxname,

:ixpname,:popstate) as sys.odcivarchar2list))

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

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 database's maintenance windows were active during 100% of the analysis

period.

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.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download