Scribd
Upload
44 views4 pages

ADDM Report - 0700 - 083

The ADDM report for database 'DB19C' analyzed performance from 06-03-2025 07:00:20 to 06-03-2025 08:30:25, identifying key areas for improvement. Major findings include high activity from top SQL statements, session connect/disconnect calls, and commits/rollbacks, with recommendations for SQL tuning and application logic analysis. The report emphasizes the need for segment tuning and highlights that CPU and other wait classes were not significant bottlenecks.

Uploaded by

ristyanaku
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
44 views4 pages

ADDM Report - 0700 - 083

The ADDM report for database 'DB19C' analyzed performance from 06-03-2025 07:00:20 to 06-03-2025 08:30:25, identifying key areas for improvement. Major findings include high activity from top SQL statements, session connect/disconnect calls, and commits/rollbacks, with recommendations for SQL tuning and application logic analysis. The report emphasizes the need for segment tuning and highlights that CPU and other wait classes were not significant bottlenecks.

Uploaded by

ristyanaku
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/ 4

ADDM Report for Task 'ADDM_0700_0830'

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

Analysis Period
---------------
AWR snapshot range from 18783 to 18786.
Time period starts at 06-03-2025 07.00.20
Time period ends at 06-03-2025 08.30.25

Analysis Target
---------------
Database 'DB19C' with DB ID 2268247066.
Database version 19.0.0.0.0.
Analysis was requested for all instances, but ADDM analyzed instance db19c,
numbered 1 and hosted at dev-esb-db.
See the "Additional Information" section for more information on the requested
instances.

Activity During the Analysis Period


-----------------------------------
Total database time was 6281 seconds.
The average number of active sessions was 1,16.
ADDM analyzed 1 of the requested 1 instances.

Summary of Findings
-------------------
Description Active Sessions Recommendations
Percent of Activity
---------------------------------------- ------------------- ---------------
1 Top SQL Statements ,33 | 28,48 2
2 Session Connect and Disconnect ,32 | 27,52 1
3 Commits and Rollbacks ,1 | 8,89 2
4 Top Segments by "User I/O" and "Cluster" ,04 | 3,48 1

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

Findings and Recommendations


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

Finding 1: Top SQL Statements


Impact is ,33 active sessions, 28,48% of total activity.
--------------------------------------------------------
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.

Recommendation 1: SQL Tuning


Estimated benefit is ,3 active sessions, 26,06% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"3j9ycxyh0zgnf".
Related Object
SQL statement with SQL_ID 3j9ycxyh0zgnf.
SELECT a.JUMLAH, a.FROM_GROUP_USER, a.DESCRIPTION, a.CMD FROM
VIEW_NOTIFICATION_APPROVAL1 a WHERE USER_CREATED_BRANCH = 'ID0010002'
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "3j9ycxyh0zgnf" was executed 2640 times and
had an average elapsed time of 0.38 seconds.
Rationale
Full scan of TABLE "EXA.REG_CIF_MAINTENANCE" with object ID 73911
consumed 33% of the database time spent on this SQL statement.

Recommendation 2: SQL Tuning


Estimated benefit is ,03 active sessions, 2,42% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"5dqz0hqtp9fru".
Related Object
SQL statement with SQL_ID 5dqz0hqtp9fru.
select /*+ connect_by_filtering index(sysauth$ i_sysauth1) */
privilege#, bitand(nvl(option$, 0), 72), grantee#, level from
sysauth$ connect by grantee#=prior privilege# and privilege#>0 start
with grantee#=:1 and privilege#>0
Action
Use bigger fetch arrays while fetching results from the SELECT statement
with SQL_ID "5dqz0hqtp9fru".
Related Object
SQL statement with SQL_ID 5dqz0hqtp9fru.
select /*+ connect_by_filtering index(sysauth$ i_sysauth1) */
privilege#, bitand(nvl(option$, 0), 72), grantee#, level from
sysauth$ connect by grantee#=prior privilege# and privilege#>0 start
with grantee#=:1 and privilege#>0
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "5dqz0hqtp9fru" was executed 70737 times and
had an average elapsed time of 0.0007 seconds.

Finding 2: Session Connect and Disconnect


Impact is ,32 active sessions, 27,52% of total activity.
--------------------------------------------------------
Session connect and disconnect calls were consuming significant database time.

Recommendation 1: Application Analysis


Estimated benefit is ,32 active sessions, 27,52% of total activity.
-------------------------------------------------------------------
Action
Investigate application logic for possible reduction of connect and
disconnect calls. For example, you might use a connection pool scheme in
the middle tier.
Finding 3: Commits and Rollbacks
Impact is ,1 active sessions, 8,89% of total activity.
------------------------------------------------------
Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
were consuming significant database time.

Recommendation 1: Application Analysis


Estimated benefit is ,1 active sessions, 8,89% of total activity.
-----------------------------------------------------------------
Action
Investigate application logic for possible reduction in the number of
COMMIT operations by increasing the size of transactions.
Rationale
The application was performing 299 transactions per minute with an
average redo size of 7574 bytes per transaction.

Recommendation 2: Host Configuration


Estimated benefit is ,1 active sessions, 8,89% of total activity.
-----------------------------------------------------------------
Action
Investigate the possibility of improving the performance of I/O to the
online redo log files.
Rationale
The average size of writes to the online redo log files was 1 K and the
average time per write was 2 milliseconds.
Rationale
The total I/O throughput on redo log files was 62 K per second for reads
and 89 K per second for writes.
Rationale
The redo log I/O throughput was divided as follows: 0% by RMAN and
recovery, 58% by Log Writer, 0% by Archiver, 0% by Streams AQ and 41% by
all other activity.

Symptoms That Led to the Finding:


---------------------------------
Wait class "Commit" was consuming significant database time.
Impact is ,1 active sessions, 8,89% of total activity.

Finding 4: Top Segments by "User I/O" and "Cluster"


Impact is ,04 active sessions, 3,48% of total activity.
-------------------------------------------------------
Individual database segments responsible for significant "User I/O" and
"Cluster" waits were found.

Recommendation 1: Segment Tuning


Estimated benefit is ,04 active sessions, 3,48% of total activity.
------------------------------------------------------------------
Action
Run "Segment Advisor" on TABLE "EXA.REG_CIF_MAINTENANCE" with object ID
73911.
Related Object
Database object with ID 73911.
Action
Investigate application logic involving I/O on TABLE
"EXA.REG_CIF_MAINTENANCE" with object ID 73911.
Related Object
Database object with ID 73911.
Action
Look at the "Top SQL Statements" finding for SQL statements consuming
significant I/O on this segment. For example, the SELECT statement with
SQL_ID "3j9ycxyh0zgnf" is responsible for 100% of "User I/O" and
"Cluster" waits for this segment.
Rationale
The I/O usage statistics for the object are: 2642 full object scans,
80572887 physical reads, 0 physical writes and 80571672 direct reads.

Symptoms That Led to the Finding:


---------------------------------
Wait class "User I/O" was consuming significant database time.
Impact is ,04 active sessions, 3,48% of total activity.

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

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

Miscellaneous Information
-------------------------
Wait class "Application" 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.
Hard parsing of SQL statements was not consuming significant database time.

You might also like