Professional Documents
Culture Documents
---------------------------------Analysis Period
--------------AWR snapshot range from 59825 to 59829.
Time period starts at 06-NOV-15 04.30.43 PM
Time period ends at 06-NOV-15 05.30.07 PM
Analysis Target
--------------Database 'MABDB' with DB ID 1027027449.
Database version 11.2.0.3.0.
ADDM performed an analysis of instance mabdb2, numbered 2 and hosted at
db02-rac02.
Activity During the Analysis Period
----------------------------------Total database time was 10305 seconds.
The average number of active sessions was 2.89.
Summary of Findings
------------------Description
s
Active Sessions
Recommendation
Percent of Activity
---------------------------------------- ------------------- -------------1
2
3
4
5
5
0
2
1
1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Findings and Recommendations
---------------------------Finding 1: Top SQL Statements
Impact is 1.29 active sessions, 44.75% 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 .45 active sessions, 15.47% of total activity.
------------------------------------------------------------------Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"ca7xydktw0a0v".
Related Object
SQL statement with SQL_ID ca7xydktw0a0v.
SELECT --Refund
TRNREF.*,
TRN.*,NVL(COIN.COIN,:"SYS_B_00") AS RCOIN
FROM (
Cur_Amt,
Sav_Amt,
Fix_Amt,
SP_Amt,
CP_Amt,
Domes_Amt,
FCur_Amt,
FSav_Amt,
FFix_Amt,
FSP_Amt,
FCP_Amt,
FDomes_Amt,
Cust_gl,
trn_desc,
user_id,
related_account
from (
select A.trn_ref_no,
XREFID,
A.ac_no,
(CASE WHEN length(ac_no)!=:"SYS_B_181" and
(substr(ac_no,:"SYS_B_182",:"SYS_B_183") like :"SYS_B_184" or
substr(ac_no,:"SYS_B_185",:"SYS_B_186") like :"SYS_B_187" or
substr(ac_no,:"SYS_B_188",:"SYS_B_189") like :"SYS_B_190") then
(lcy_amount) end) as Cur_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_191" and
substr(ac_no,:"SYS_B_192",:"SYS_B_193") like :"SYS_B_194" then
(lcy_amount) end) as Sav_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_195" and
substr(ac_no,:"SYS_B_196",:"SYS_B_197") like :"SYS_B_198" then
(lcy_amount) end) as Fix_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_199" and
substr(ac_no,:"SYS_B_200",:"SYS_B_201") like :"SYS_B_202" then
(lcy_amount) end) as SP_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_203" and
substr(ac_no,:"SYS_B_204",:"SYS_B_205") like :"SYS_B_206" then
(lcy_amount) end) as CP_Amt,
(CASE WHEN length(ac_no)=:"SYS_B_207" then (lcy_amount) end) as
Domes_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_208" and
(substr(ac_no,:"SYS_B_209",:"SYS_B_210") like :"SYS_B_211" or
substr(ac_no,:"SYS_B_212",:"SYS_B_213") like :"SYS_B_214" or
substr(ac_no,:"SYS_B_215",:"SYS_B_216") like :"SYS_B_217") then
(fcy_amount) end) as FCur_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_218" and
substr(ac_no,:"SYS_B_219",:"SYS_B_220") like :"SYS_B_221" then
(fcy_amount) end) as FSav_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_222" and
substr(ac_no,:"SYS_B_223",:"SYS_B_224") like :"SYS_B_225" then
(fcy_amount) end) as FFix_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_226" and
substr(ac_no,:"SYS_B_227",:"SYS_B_228") like :"SYS_B_229" then
(fcy_amount) end) as FSP_Amt,
(CASE WHEN length(ac_no)!=:"SYS_B_230" and
substr(ac_no,:"SYS_B_231",:"SYS_B_232") like :"SYS_B_233" then
(fcy_amount) end) as FCP_Amt,
(CASE WHEN length(ac_no)=:"SYS_B_234" then (fcy_amount) end) as
FDomes_Amt,
A.trn_desc,
A.CUST_GL,
user_id,
related_account
from fbtb_txnlog_master M, acvws_all_acentries_desc A
where
A.trn_ref_no in (select reference_no from ictms_tdpayin_details where
multimode_payopt = :"SYS_B_235")
and txnactdet = A.ac_no
and A.AC_BRANCH = M.Branchcode
and M.Postingdate = A.TRN_DT
and txnccydet =:P_Currency
and A.TRN_DT =:P_Date
and ac_branch =:P_BranchCode
and DRCR_IND = :"SYS_B_236"
and ac_no not in (select gl_code from biv_cashcode)
and AC_NO not IN (:"SYS_B_237",:"SYS_B_238")
and M.Xrefid not in
(select external_ref_no from acvws_all_ac_entries
where ac_no in (select ac_no from acvws_all_ac_entries where event =
:"SYS_B_239" and TRN_DT = :P_Date)
and TRN_DT =:P_Date
and trn_code IN(:"SYS_B_240",:"SYS_B_241"))
and ac_entry_sr_no not in
(select ac_entry_sr_no
from acvws_all_acentries_desc
where substr(trn_ref_no, :"SYS_B_242", :"SYS_B_243") in
(:"SYS_B_244", :"SYS_B_245", :"SYS_B_246") and trn_code in
(:"SYS_B_247", :"SYS_B_248", :"SYS_B_249",:"SYS_B_250"))
and AC_ENTRY_SR_NO NOT IN
(SELECT AC_ENTRY_SR_NO
FROM acvws_all_acentries_desc trans WHERE AC_NO IN
(:"SYS_B_251",:"SYS_B_252") AND TRN_CODE = :"SYS_B_253")
and external_ref_no not in
(Select external_ref_no from acvws_all_ac_entries b where
event=:"SYS_B_254"
and AC_CCY =:P_Currency and b.external_ref_no is not null
and TRN_DT=:P_Date and AC_Branch =:P_BranchCode)) A
inner join BIV_TILL_DENO B on A.xrefid = B.XREF
--where b.TILL_ID in (:P_TillID)
) Depo
left join istms_instr_txn txn on depo.trn_ref_no =
txn.contract_ref_no)A
group by Till_ID
order by Till_ID
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 "1bdsm0jq3vjt8" was executed 1 times and had
an average elapsed time of 1494 seconds.
Rationale
At least 2 distinct execution plans were utilized for this SQL statement
during the analysis period.
Recommendation 3: SQL Tuning
Estimated benefit is .3 active sessions, 10.41% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"gb8dbmdrxwy9q".
Related Object
SQL statement with SQL_ID gb8dbmdrxwy9q.
Select trn_ref_no,AC_ENTRY_SR_NO,VALUE_DT as TRN_DT,TRN_CODE, AC_No,
(maturity_date-int_start_date) as Days, Case When
DRCR_IND=:"SYS_B_00" then DRCR_MNT * (-:"SYS_B_01") end WDL,Case
When DRCR_IND=:"SYS_B_02" then DRCR_MNT end DEP, Running_Bal, AC_NO
from (select ac.trn_ref_no,ac.AC_NO,ac.ac_ccy,ac.VALUE_DT,ac.AC_BRANC
H,ac.DRCR_IND,ac.LCY_AMOUNT,ac.FCY_AMOUNT,ac.AC_ENTRY_SR_NO,ac.extern
al_ref_no,ac.cust_gl,ac.TRN_CODE,ac.AMOUNT_TAG,ac.RELATED_ACCOUNT,ac.
event,sum(decode(ac.DRCR_IND,:"SYS_B_03",ac.LCY_AMOUNT,:"SYS_B_04",-(
ac.LCY_AMOUNT))) over ( partition by
substr(ac.AC_NO,:"SYS_B_05",:"SYS_B_06") order by ac.AC_ENTRY_SR_NO
range between unbounded preceding and current row )
running_bal,decode(ac.DRCR_IND,:"SYS_B_07",ac.LCY_AMOUNT,:"SYS_B_08",
-(ac.LCY_AMOUNT)) drcr_mnt from Acvws_All_Ac_Entries ac where
substr(ac_no,:"SYS_B_09",:"SYS_B_10") = :"SYS_B_11" and
substr(ac_no,:"SYS_B_12",:"SYS_B_13") = :"SYS_B_14" and
substr(ac_no,:"SYS_B_15",:"SYS_B_16")=:"SYS_B_17" and
ac.AC_ENTRY_SR_NO > :"SYS_B_18" group by ac.AC_NO, ac.VALUE_DT,
ac.ac_ccy, ac.AC_BRANCH, ac.DRCR_IND,ac.LCY_AMOUNT, ac.FCY_AMOUNT,
ac.trn_ref_no, ac.cust_gl, ac.AMOUNT_TAG, ac.event,
ac.RELATED_ACCOUNT, ac.TRN_CODE,ac.AC_ENTRY_SR_NO,ac.external_ref_no
order by ac.AC_ENTRY_SR_NO) INNER JOIN ictm_acc ON AC_No= ACC Where
AC_ENTRY_SR_NO >= :"SYS_B_19" and trn_ref_no not in (select
trn_ref_no from acvws_all_ac_entries where event=:"SYS_B_20") order
by AC_ENTRY_SR_NO
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 "gb8dbmdrxwy9q" was executed 19 times and had
an average elapsed time of 56 seconds.
Recommendation 4: SQL Tuning
Estimated benefit is .07 active sessions, 2.43% of total activity.
-----------------------------------------------------------------Action
Investigate the PL/SQL statement with SQL_ID "a54b1ppyyhv9u" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID a54b1ppyyhv9u.
BEGIN GWPKSS_SERVICE_ROUTER.PR_PROCESS_REQ_MSG(:1 ,:2 ,:3 ,:4 ); END;
Rationale
The SQL Tuning Advisor cannot operate on PL/SQL statements.
Rationale
Database time for this SQL was divided as follows: 16% for SQL
execution, 0% for parsing, 72% for PL/SQL execution and 12% for Java
execution.
Rationale
SQL statement with SQL_ID "a54b1ppyyhv9u" was executed 2038 times and
had an average elapsed time of 0.95 seconds.
object ID 514447.
Related Object
Database object with ID 514447.
Action
Investigate application logic involving I/O on TABLE
"FCUBSPROD.FBTB_TXNLOG_DETAILS" with object ID 514447.
Related Object
Database object with ID 514447.
Action
Look at the "Top SQL Statements" finding for SQL statements consuming
significant I/O on this segment. For example, the DELETE statement with
SQL_ID "96ka72ubs9bx8" is responsible for 52% of "User I/O" and
"Cluster" waits for this segment.
Rationale
The I/O usage statistics for the object are: 6 full object scans,
2335373 physical reads, 1720 physical writes and 0 direct reads.
Symptoms That Led to the Finding:
--------------------------------Wait class "User I/O" was consuming significant database time.
Impact is .53 active sessions, 18.21% of total activity.
Finding 4: Global Cache Messaging
Impact is .28 active sessions, 9.64% of total activity.
------------------------------------------------------Inter-instance messaging was consuming significant database time on this
instance.
Recommendation 1: Application Analysis
Estimated benefit is .28 active sessions, 9.64% of total activity.
-----------------------------------------------------------------Action
Look at the "Top SQL Statements" finding for SQL statements consuming
significant time on Cluster waits. For example, the SELECT statement
with SQL_ID "gb8dbmdrxwy9q" is responsible for 32% of Cluster wait
during the analysis period.
Symptoms That Led to the Finding:
--------------------------------Wait class "Cluster" was consuming significant database time.
Impact is .28 active sessions, 9.64% of total activity.
Finding 5: PL/SQL Execution
Impact is .14 active sessions, 4.67% of total activity.
------------------------------------------------------PL/SQL execution consumed significant database time.
Recommendation 1: SQL Tuning
Estimated benefit is .14 active sessions, 4.67% of total activity.
-----------------------------------------------------------------Action
Tune the entry point PL/SQL
"FCUBSPROD.GWPKS_SERVICE_ROUTER.PR_PROCESS_REQ_MSG#1" of type "PACKAGE"
and ID 518654. Refer to the PL/SQL documentation for addition
information.
Rationale
110 seconds spent in executing PL/SQL
"FCUBSPROD.CSPKS_REQ_UTILS.FN_GET_AMENDABLE_DETAILS" of type "PACKAGE"
and ID 516512.
Rationale
60 seconds spent in executing PL/SQL "FCUBSPROD.DEBUG.PR_DEBUG" of type
"PACKAGE" and ID 253326.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Additional Information
---------------------Miscellaneous 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.
CPU was not a bottleneck for the instance.
Wait class "Network" 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.