Scribd
Upload
52 views

Awr

awr

Uploaded by

edenfray
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
52 views

Awr

awr

Uploaded by

edenfray
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

ADDM Report for Task 'TASK_16209'

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

Analysis Period
---------------
AWR snapshot range from 5056 to 5064.
Time period starts at 04-DEC-18 12.00.02 AM
Time period ends at 04-DEC-18 08.00.16 AM

Analysis Target
---------------
Database 'NBLN' with DB ID 1035290214.
Database version 12.1.0.2.0.
ADDM performed an analysis of instance NBLN1, numbered 1 and hosted at
scmbozdbclient02.

Activity During the Analysis Period


-----------------------------------
Total database time was 2880955 seconds.
The average number of active sessions was 99.98.

Summary of Findings
-------------------
Description Active Sessions Recommendations
Percent of Activity
-------------------------- ------------------- ---------------
1 Unusual "Other" Wait Event 92.52 | 92.53 4

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

Findings and Recommendations


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

Finding 1: Unusual "Other" Wait Event


Impact is 92.52 active sessions, 92.53% of total activity.
----------------------------------------------------------
Wait event "rdbms ipc reply" in wait class "Other" was consuming significant
database time.

Recommendation 1: Application Analysis


Estimated benefit is 92.52 active sessions, 92.53% of total activity.
---------------------------------------------------------------------
Action
Investigate the cause for high "rdbms ipc reply" waits. Refer to
Oracle's "Database Reference" for the description of this wait event.

Recommendation 2: Application Analysis


Estimated benefit is 92.52 active sessions, 92.53% of total activity.
---------------------------------------------------------------------
Action
Investigate the cause for high "rdbms ipc reply" waits in Module "JDBC
Thin Client".

Recommendation 3: Application Analysis


Estimated benefit is 92.52 active sessions, 92.53% of total activity.
---------------------------------------------------------------------
Action
Investigate the cause for high "rdbms ipc reply" waits in Service
"NBLN".

Recommendation 4: Application Analysis


Estimated benefit is 30.52 active sessions, 30.52% of total activity.
---------------------------------------------------------------------
Action
Investigate the cause for high "rdbms ipc reply" waits with P1
("from_process") value "2052".

Symptoms That Led to the Finding:


---------------------------------
Wait class "Other" was consuming significant database time.
Impact is 93.33 active sessions, 93.34% of total activity.

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

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

Miscellaneous Information
-------------------------
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.
CPU was not a bottleneck for the instance.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
The network latency of the cluster interconnect was within acceptable limits
of 1 milliseconds.
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 24% of the analysis
period.

You might also like