ADDM Report for Task 'TASK_36565'

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

Analysis Period
---------------
AWR snapshot range from 36561 to 36562.
Time period starts at 26-JAN-17 02.00.58 PM
Time period ends at 26-JAN-17 03.00.01 PM

Analysis Target
---------------
Database 'MBLPROD' with DB ID 359300053.
Database version 11.2.0.3.0.
ADDM performed an analysis of instance mblprod, numbered 1 and hosted at
MBLDRDB.

Activity During the Analysis Period

-----------------------------------
Total database time was 1170 seconds.
The average number of active sessions was .33.

Summary of Findings
-------------------
Description Active Sessions Recommendation
s
Percent of Activity
---------------------------------------- ------------------- --------------
-
1 Virtual Memory Paging .33 | 100 1
2 "User I/O" wait Class .13 | 39.37 0
3 Commits and Rollbacks .09 | 28.78 2
4 Top SQL Statements .08 | 25.44 4
5 PL/SQL Execution .02 | 6.14 1
6 Top Segments by "User I/O" and "Cluster" .01 | 3.79 1

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

Findings and Recommendations

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

Finding 1: Virtual Memory Paging

Impact is .33 active sessions, 100% of total activity.
------------------------------------------------------
Significant virtual memory paging was detected on the host operating system.

Recommendation 1: Host Configuration

Estimated benefit is .33 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: "User I/O" wait Class
Impact is .13 active sessions, 39.37% of total activity.
--------------------------------------------------------
Wait class "User I/O" was consuming significant database time.
The throughput of the I/O subsystem was not significantly lower than expected.
The Oracle instance memory (SGA and PGA) was adequately sized.

No recommendations are available.

Finding 3: Commits and Rollbacks

Impact is .09 active sessions, 28.78% 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 .09 active sessions, 28.78% 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 11878 transactions per minute with an
average redo size of 1481 bytes per transaction.

Recommendation 2: Host Configuration

Estimated benefit is .09 active sessions, 28.78% 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 0 milliseconds.
Rationale
The total I/O throughput on redo log files was 305 K per second for
reads and 713 K per second for writes.
Rationale
The redo log I/O throughput was divided as follows: 0% by RMAN and
recovery, 70% by Log Writer, 0% by Archiver, 0% by Streams AQ and 29% by
all other activity.

Symptoms That Led to the Finding:

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

Finding 4: Top SQL Statements

Impact is .08 active sessions, 25.44% 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 .04 active sessions, 11.4% of total activity.
------------------------------------------------------------------
Action
 Run SQL Tuning Advisor on the UPSERT statement with SQL_ID
"8ay4bmph696fu".
Related Object
SQL statement with SQL_ID 8ay4bmph696fu.
MERGE INTO F_LOCKING USING DUAL ON (RECID = :RECID)
WHEN MATCHED THEN UPDATE SET XMLRECORD=XMLTYPE(:XMLRECORD, NULL, 1,
1)
WHEN NOT MATCHED THEN INSERT VALUES(:RECID, XMLTYPE(:XMLRECORD, NULL,
1, 1))
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: 54% for SQL
execution, 0% for parsing, 46% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "8ay4bmph696fu" was executed 420479 times and
had an average elapsed time of 0.00029 seconds.

Recommendation 2: SQL Tuning

Estimated benefit is .02 active sessions, 5.26% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"2kaz764k4gawx".
Related Object
SQL statement with SQL_ID 2kaz764k4gawx.
SELECT t.XMLRECORD.getClobVal() FROM FBNK_LIMIT t WHERE RECID =:RECID
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 "2kaz764k4gawx" was executed 14443 times and
had an average elapsed time of 0.0025 seconds.
Rationale
I/O and Cluster wait for TABLE "MBLLIVE.FBNK_LIMIT" with object ID
1356790 consumed 83% of the database time spent on this SQL statement.

Recommendation 3: SQL Tuning

Estimated benefit is .01 active sessions, 4.39% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the UPSERT statement with SQL_ID
"0m7h1gv2dca7h".
Related Object
SQL statement with SQL_ID 0m7h1gv2dca7h.
MERGE INTO FBNK_PM_DRILL_DOWN USING DUAL ON (RECID = :RECID)
WHEN MATCHED THEN UPDATE SET XMLRECORD=XMLTYPE(:XMLRECORD, NULL, 1,
1)
WHEN NOT MATCHED THEN INSERT VALUES(:RECID, XMLTYPE(:XMLRECORD, NULL,
1, 1))
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 "0m7h1gv2dca7h" was executed 26761 times and
had an average elapsed time of 0.0015 seconds.

Recommendation 4: SQL Tuning

Estimated benefit is .01 active sessions, 4.39% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"25bqrc9pvapz9".
Related Object
SQL statement with SQL_ID 25bqrc9pvapz9.
SELECT t.XMLRECORD.getClobVal() FROM FBNK_EB_C004 t WHERE RECID
=:RECID
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 "25bqrc9pvapz9" was executed 5494 times and
had an average elapsed time of 0.0078 seconds.

Finding 5: PL/SQL Execution

Impact is .02 active sessions, 6.14% of total activity.
-------------------------------------------------------
PL/SQL execution consumed significant database time.

Recommendation 1: SQL Tuning

Estimated benefit is .02 active sessions, 6.14% of total activity.
------------------------------------------------------------------
Action
Tune the entry point PL/SQL "SYS.XMLTYPE.XMLTYPE#4" of type "TYPE" and
ID 5029. Refer to the PL/SQL documentation for addition information.
Rationale
71 seconds spent in executing PL/SQL "SYS.XMLTYPE.XMLTYPE#4" of type
"TYPE" and ID 5029.

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

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

Recommendation 1: Segment Tuning

Estimated benefit is .01 active sessions, 3.79% of total activity.
------------------------------------------------------------------
Action
Investigate application logic involving I/O on TABLE
"MBLLIVE.FBNK_LIMIT" with object ID 1356790.
Related Object
 Database object with ID 1356790.
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 "2kaz764k4gawx" is responsible for 100% of "User I/O" and
"Cluster" waits for this segment.

Symptoms That Led to the Finding:

---------------------------------
Wait class "User I/O" was consuming significant database time.
Impact is .13 active sessions, 39.37% 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.