ADDM Report for Task 'TASK_44517'

--------------------------------Analysis Period
--------------AWR snapshot range from 23253 to 23255.
Time period starts at 28-MAR-14 02.00.46 PM
Time period ends at 28-MAR-14 04.01.06 PM
Analysis Target
--------------Database 'ITC8' with DB ID 3297652282.
Database version 11.2.0.2.0.
ADDM performed an analysis of instance ITCP, numbered 1 and hosted at ITC08.
Activity During the Analysis Period
----------------------------------Total database time was 99529 seconds.
The average number of active sessions was 13.79.
Summary of Findings
------------------Description
1
2
3
4
5

--------------------Virtual Memory Paging

Top SQL Statements
"User I/O" wait Class
Undersized SGA
Commits and Rollbacks

Active Sessions
Percent of Activity
------------------13.79 | 100
4.41 | 32
4.41 | 31.97
1.51 | 10.94
.43 | 3.15

Recommendations
--------------1
5
0
1
1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Findings and Recommendations
---------------------------Finding 1: Virtual Memory Paging
Impact is 13.79 active sessions, 100% of total activity.
-------------------------------------------------------Significant virtual memory paging was detected on the host operating system.
Recommendation 1: Host Configuration
Estimated benefit is 13.79 active sessions, 100% of total activity.
------------------------------------------------------------------Action
Host operating system was experiencing significant paging but no
particular root cause could be detected. Investigate processes that do
not belong to this instance running on the host that are consuming
significant amount of virtual memory. Also consider adding more physical
memory to the host.
Finding 2: Top SQL Statements
Impact is 4.41 active sessions, 32% 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 2.89 active sessions, 20.98% of total activity.
-------------------------------------------------------------------Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"f264tw1svchq4".
Related Object
SQL statement with SQL_ID f264tw1svchq4.
select ramt into :b0 from wipcustrate where (((offernum=:b1 and
outlet=:b2) and ratecd=:b3) and ratesign='+')
Rationale
The SQL spent 99% 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 "f264tw1svchq4" was executed 19123 times and
had an average elapsed time of 1 seconds.
Recommendation 2: SQL Tuning
Estimated benefit is .47 active sessions, 3.38% of total activity.
-----------------------------------------------------------------Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"9dbjy80as6f98".
Related Object
SQL statement with SQL_ID 9dbjy80as6f98.
select promo_id ,ratecd ,TO_CHAR(offernum)
,to_char(promo_remove_date,'YYYY-MM-DD') ,promo_remove_type into
:b0,:b1,:b2,:b3:b4,:b5 from wipcustpromos where (((offernum in
(select max(offernum) from wipcustpromos where (((cust_acct=:b6 and
ratecd=:b1) and promosign=:b8) and promo_remove_date is not null ))
and outlet=:b9) and promosign=:b8) and ratecd=:b1)
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 "9dbjy80as6f98" was executed 24296 times and
had an average elapsed time of 0.12 seconds.
Recommendation 3: SQL Tuning
Estimated benefit is .4 active sessions, 2.89% of total activity.
----------------------------------------------------------------Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"4a36ba0rkvwks".
Related Object
SQL statement with SQL_ID 4a36ba0rkvwks.
SELECT * FROM NGA_CAS.zn_nagratrig_1 WHERE progid IN ('707', '772',
'777', '706', '111','720','792') and Status Is null and (stbno is not
null or sccno is not null) AND GROUP1 = 'R' AND trxgrp = (SELECT
trxgrp FROM (SELECT * FROM NGA_CAS.zn_nagratrig_1 WHERE GROUP1 = 'R'
ORDER BY priority, trxno) WHERE rownum < 2 AND progid IN ('707',

'772', '777','706', '111', '720','792') AND status IS NULL AND GROUP1

= 'R' GROUP BY trxgrp)ORDER BY priority, trxgrp, trxno, createdate
ASC
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 "4a36ba0rkvwks" was executed 4161 times and
had an average elapsed time of 0.67 seconds.
Recommendation 4: SQL Tuning
Estimated benefit is .35 active sessions, 2.54% of total activity.
-----------------------------------------------------------------Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"796u6tmxw6hkr".
Related Object
SQL statement with SQL_ID 796u6tmxw6hkr.
select * from (select * from NGA_CAS.zn_nagratrig_2 where progid in
('720', '752') And Status Is null AND subcmd <> 'TST' and trxgrp =
(select trxgrp from (select * from NGA_CAS.zn_nagratrig_2 WHERE
subcmd <> 'TST' order by priority, trxgrp, trxno) where rownum < 2
and progid in ('720','752') and status is null AND subcmd <> 'TST'
group by trxgrp) order by trxgrp, trxno, createdate ASC)
Rationale
The SQL spent 99% 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 "796u6tmxw6hkr" was executed 8099 times and
had an average elapsed time of 0.32 seconds.
Recommendation 5: SQL Tuning
Estimated benefit is .3 active sessions, 2.17% of total activity.
----------------------------------------------------------------Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"d4xqgqfj2rk3p".
Related Object
SQL statement with SQL_ID d4xqgqfj2rk3p.
select promo_id into :b0 from wipcustpromos where (((offernum=:b1
and outlet=:b2) and ratecd=:b3) and ratesign='+')
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 "d4xqgqfj2rk3p" was executed 17001 times and
had an average elapsed time of 0.11 seconds.

Finding 3: "User I/O" wait Class

Impact is 4.41 active sessions, 31.97% of total activity.
--------------------------------------------------------Wait class "User I/O" was consuming significant database time.
Waits for I/O to temporary tablespaces were not consuming significant database
time.
The throughput of the I/O subsystem was not significantly lower than expected.
No recommendations are available.
Finding 4: Undersized SGA
Impact is 1.51 active sessions, 10.94% of total activity.
--------------------------------------------------------The SGA was inadequately sized, causing additional I/O or hard parses.
The value of parameter "sga_target" was "38912 M" during the analysis period.
Recommendation 1: Database Configuration
Estimated benefit is .55 active sessions, 3.96% of total activity.
-----------------------------------------------------------------Action
Increase the size of the SGA by setting the parameter "sga_target" to
43776 M.
Symptoms That Led to the Finding:
--------------------------------Wait class "User I/O" was consuming significant database time.
Impact is 4.41 active sessions, 31.97% of total activity.
Finding 5: Commits and Rollbacks
Impact is .43 active sessions, 3.15% of total activity.
------------------------------------------------------Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
were consuming significant database time.
Recommendation 1: Host Configuration
Estimated benefit is .43 active sessions, 3.15% 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 20 K and the
average time per write was 5 milliseconds.
Rationale
The total I/O throughput on redo log files was 634 K per second for
reads and 614 K per second for writes.
Rationale
The redo log I/O throughput was divided as follows: 0% by RMAN and
recovery, 49% by Log Writer, 0% by Archiver, 0% by Streams AQ and 50% by
all other activity.
Symptoms That Led to the Finding:
--------------------------------Wait class "Commit" was consuming significant database time.
Impact is .43 active sessions, 3.15% 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.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.