ADDM Report for Task 'TASK_509832'

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

Analysis Period
---------------
AWR snapshot range from 169463 to 169559.
Time period starts at 20-NOV-24 08.00.07 AM
Time period ends at 21-NOV-24 08.00.19 AM

Analysis Target
---------------
Database 'XLRPL1' with DB ID 300648730.
Database version 19.0.0.0.0.
ADDM performed an analysis of instance XLRPL12, numbered 2 and hosted at
cbtcnbexadb02.

Activity During the Analysis Period

-----------------------------------
Total database time was 1317482 seconds.
The average number of active sessions was 15.25.

Summary of Findings
-------------------
Description Active Sessions Recommendations
Percent of Activity
------------------------------ ------------------- ---------------
1 Top SQL Statements 5.26 | 34.52 5
2 Session Connect and Disconnect 1.28 | 8.38 1
3 "User I/O" wait Class .61 | 3.98 0
4 Unusual "Other" Wait Event .53 | 3.5 3
5 Shared Pool Latches .49 | 3.22 0

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

Findings and Recommendations

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

Finding 1: Top SQL Statements

Impact is 5.26 active sessions, 34.52% 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.01 active sessions, 13.18% of total activity.
--------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the CREATE TABLE statement with SQL_ID
"czz2ur44t1chq".
Related Object
SQL statement with SQL_ID czz2ur44t1chq.
CREATE TABLE TEMP_VOUCHER_LC_TO_FR NOLOGGING AS
SELECT /*+parallel (a,4) */ a.* FROM VOUCHER a WHERE
a.VOUCHER_STATUS='LC' AND V_STATUS_DATE BETWEEN SYSDATE-(1/24/60*40)
AND SYSDATE-(1/24/60*10)
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.

Recommendation 2: SQL Tuning

Estimated benefit is 1.06 active sessions, 6.97% of total activity.
-------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the UPDATE statement with SQL_ID
"9zg9qd9bm4spu".
Related Object
SQL statement with SQL_ID 9zg9qd9bm4spu.
update user$ set spare6=DECODE(to_char(:2, 'YYYY-MM-DD'),
'0000-00-00', to_date(NULL), :2) where user#=:1
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 "9zg9qd9bm4spu" was executed 1826744 times and
had an average elapsed time of 0.026 seconds.

Recommendation 3: SQL Tuning

Estimated benefit is .73 active sessions, 4.81% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"2vfw24c80ckbr".
Related Object
SQL statement with SQL_ID 2vfw24c80ckbr.
/* null_GuideBucket_getBucketByBucketId_4 */ SELECT
RPM_BUCKET.CURRENCY, RPM_BUCKET.POLICY_CODE, RPM_BUCKET.BE,
RPM_BUCKET.ADD_BONUS_IND, RPM_BUCKET.INSTALMENT_IND,
RPM_BUCKET.DEBT_IND, RPM_BUCKET.RCG_IND, RPM_BUCKET.LOAN_IND,
RPM_BUCKET.FIRST_RCG_IND, RPM_BUCKET.LAST_ONGOING_DATE,
RPM_BUCKET.LAST_ONGOING_STEP, RPM_BUCKET.LAST_RCG_DATE,
RPM_BUCKET.BAL_EXP_DATE, RPM_BUCKET.LAST_RCG_EXP_ID,
RPM_BUCKET.BUCKET_STATUS, RPM_BUCKET.STATUS_DATE,
RPM_BUCKET.BUCKET_ID, RPM_BUCKET_ID.PCN, RPM_BUCKET_ID.ATM_BUCKET_ID,
RPM_BUCKET_ID.CRM_EXTERNAL_ID, RPM_BUCKET_ID.BEN, RPM_BUCKET_ID.IMSI,
RPM_BUCKET_ID.BAN, RPM_BUCKET_ID.CUSTOMER_ID, RPM_BUCKET_ID.PCN_NAME,
RPM_BUCKET.BILL_CYCLE, RPM_BUCKET.PARTITION_ID,
RPM_BUCKET.L9_POST_IND, RPM_BUCKET.L9_OLC_IND,
RPM_BUCKET.L9_CREDIT_LIMIT, RPM_BUCKET.L9_BONUS_ACCUM,
RPM_BUCKET.L9_LAST_BONUS_DATE FROM RPM_BUCKET, RPM_BUCKET_ID WHERE
RPM_BUCKET.BUCKET_ID=RPM_BUCKET_ID.BUCKET_ID AND
RPM_BUCKET.BUCKET_ID=:1
Rationale
The SQL spent 96% 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: 97% for SQL
execution, 3% for parsing, 0% for PL/SQL execution and 0% for Java
 execution.
Rationale
SQL statement with SQL_ID "2vfw24c80ckbr" was executed 381257213 times
and had an average elapsed time of 0.000058 seconds.

Recommendation 4: SQL Tuning

Estimated benefit is .72 active sessions, 4.74% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"bywc4b8xgwhz9".
Related Object
SQL statement with SQL_ID bywc4b8xgwhz9.
/* null_SubscriberBasic_findByResourceTypeAndValueSubscriberNotCancel
led_7 */ SELECT RPM_SUBSCRIBER.SUB_PIN,
RPM_SUBSCRIBER.PRIM_RESOURCE_TP, RPM_SUBSCRIBER.PRIM_RESOURCE_VAL,
RPM_SUBSCRIBER.SUB_STATUS, RPM_SUBSCRIBER.STATUS_DATE,
RPM_SUBSCRIBER.SUBSCRIBER_NO, RPM_SUBSCRIBER.APPLIED_ACTIVITIES,
RPM_SUBSCRIBER.L9_ACTV_ATTEMPTS, RPM_SUBSCRIBER.L9_FNF_FLAG,
RPM_SUBSCRIBER.L9_POST_IND, RPM_SUBSCRIBER.L9_FIRST_RCG_IND,
RPM_SUBSCRIBER.L9_MULTI_PCN, RPM_SUBSCRIBER.L9_C2CBLOCK_IND,
RPM_SUBSCRIBER.L9_LAST_RCHG_AMOUNT, RPM_SUBSCRIBER.L9_INIT_RCHG_DATE,
RPM_SUBSCRIBER.L9_INIT_BAL_DATE, RPM_SUBSCRIBER.L9_HYBRID_IND,
RPM_SUBSCRIBER.L9_HYBRID_STS_DATE FROM RPM_SUBSCRIBER WHERE
RPM_SUBSCRIBER.PRIM_RESOURCE_VAL=:1 AND
RPM_SUBSCRIBER.PRIM_RESOURCE_TP=:2 AND
RPM_SUBSCRIBER.SUB_STATUS!=:3
Rationale
The SQL spent 96% 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: 97% for SQL
execution, 3% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "bywc4b8xgwhz9" was executed 326407796 times
and had an average elapsed time of 0.000073 seconds.

Recommendation 5: SQL Tuning

Estimated benefit is .63 active sessions, 4.13% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the INSERT statement with SQL_ID
"9rgd6pazbyx82".
Related Object
SQL statement with SQL_ID 9rgd6pazbyx82.
INSERT INTO RPM_RECHARGES (RPM_RECHARGES.PRIM_RESOURCE_TP,
RPM_RECHARGES.SUBSCRIBER_NO, RPM_RECHARGES.PRIM_RESOURCE_VAL,
RPM_RECHARGES.BUCKET_ID, RPM_RECHARGES.PYM_CHANNEL_NO,
RPM_RECHARGES.EXTERNAL_ID, RPM_RECHARGES.BEN, RPM_RECHARGES.BAN,
RPM_RECHARGES.CUSTOMER_ID, RPM_RECHARGES.PCN_NAME,
RPM_RECHARGES.BAL_EXP_DATE, RPM_RECHARGES.BUCKET_KEY,
RPM_RECHARGES.RCG_ID, RPM_RECHARGES.PERIOD_KEY,
RPM_RECHARGES.INSTL_AMT, RPM_RECHARGES.ADD_BONUS_AMT,
RPM_RECHARGES.CREATE_CHARGE_AMT, RPM_RECHARGES.REG_BONUS_AMT,
RPM_RECHARGES.REDUCE_AMT, RPM_RECHARGES.DEBT_AMT,
RPM_RECHARGES.LOAN_AMT, RPM_RECHARGES.REL_RCG_ID,
RPM_RECHARGES.REL_RCG_TYPE, RPM_RECHARGES.RCG_STATUS,
RPM_RECHARGES.CD_CANCEL_REF_ID, RPM_RECHARGES.LAST_STS_UPDATE,
 RPM_RECHARGES.CANCEL_RCG_TYPE, RPM_RECHARGES.RAD_TIME_STAMP,
RPM_RECHARGES.CLIENT_TIME_STAMP, RPM_RECHARGES.RPL_TIME_STAMP,
RPM_RECHARGES.RMD_VALS, RPM_RECHARGES.RMD_MAIN_ID,
RPM_RECHARGES.CD_VALS, RPM_RECHARGES.CD_MAIN_ID,
RPM_RECHARGES.CD_UNIQUE_ID, RPM_RECHARGES.SUB_ID_VALS,
RPM_RECHARGES.SPLIT_RCG_SEQ, RPM_RECHARGES.RCG_TYPE,
RPM_RECHARGES.METHOD_TYPE, RPM_RECHARGES.CHANNEL_CODE,
RPM_RECHARGES.METHOD_CODE, RPM_RECHARGES.METHOD_GROUP,
RPM_RECHARGES.BAL_EXP_DATE_CALC, RPM_RECHARGES.RCG_NUM_OF_DAYS,
RPM_RECHARGES.PPS_BALANCE, RPM_RECHARGES.RCG_CHL_AMT,
RPM_RECHARGES.PPS_NEW_BALANCE, RPM_RECHARGES.INPUT_AMOUNT,
RPM_RECHARGES.PPS_AMT, RPM_RECHARGES.OUTPUT_CURRENCY,
RPM_RECHARGES.INPUT_CURRENCY, RPM_RECHARGES.RCG_REQ_DATE,
RPM_RECHARGES.PROCESS_DATE, RPM_RECHARGES.RCG_REF_DATE,
RPM_RECHARGES.LOGICAL_DATE, RPM_RECHARGES.L9_BONUS_AMOUNT,
RPM_RECHARGES.L9_POLICY_CODE, RPM_RECHARGES.L9_INPUT_RCG_AMT,
RPM_RECHARGES.L9_GRACE_DATE, RPM_RECHARGES.L9_ALLOWANCE_TYPE,
RPM_RECHARGES.L9_BONUS_ALLOWANCE, RPM_RECHARGES.L9_RCG_ALLOWANCE,
RPM_RECHARGES.L9_DEALER_CGI, RPM_RECHARGES.L9_UNIQUE_ID,
RPM_RECHARGES.L9_TERM_CGI, RPM_RECHARGES.L9_DEALER_IP,
RPM_RECHARGES.L9_DEALER_NAME, RPM_RECHARGES.L9_MERCHANT_ID,
OPERATOR_ID, APPLICATION_ID, DL_SERVICE_CODE, DL_UPDATE_STAMP,
SYS_CREATION_DATE, SYS_UPDATE_DATE) VALUES (:1 , :2 , :3 , :4 , :5 ,
:6 , :7 , :8 , :9 , :10 , :11 , :12 , :13 , :14 , :15 , :16 , :17 ,
:18 , :19 , :20 , :21 , :22 , :23 , :24 , :25 , :26 , :27 , :28 , :29
, :30 , :31 , :32 , :33 , :34 , :35 , :36 , :37 , :38 , :39 , :40 ,
:41 , :42 , :43 , :44 , :45 , :46 , :47 , :48 , :49 , :50 , :51 , :52
, :53 , :54 , :55 , :56 , :57 , :58 , :59 , :60 , :61 , :62 , :63 ,
:64 , :65 , :66 , :67 , :68 , :69 , :70 , :71 , :72 , SYSDATE, NULL)
Rationale
The SQL spent 92% 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: 99% for SQL
execution, 1% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "9rgd6pazbyx82" was executed 14254722 times
and had an average elapsed time of 0.0012 seconds.

Finding 2: Session Connect and Disconnect

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

Recommendation 1: Application Analysis

Estimated benefit is 1.28 active sessions, 8.38% 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: "User I/O" wait Class

Impact is .61 active sessions, 3.98% of total activity.
-------------------------------------------------------
Wait class "User I/O" was consuming significant database time.
The buffer cache was not undersized.
The streams pool was adequately sized.
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: Unusual "Other" Wait Event

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

Recommendation 1: Application Analysis

Estimated benefit is .53 active sessions, 3.5% 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 .53 active sessions, 3.5% of total activity.
-----------------------------------------------------------------
Action
Investigate the cause for high "rdbms ipc reply" waits in Service
"XLRPL1_SRV".

Recommendation 3: Application Analysis

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

Symptoms That Led to the Finding:

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

Finding 5: Shared Pool Latches

Impact is .49 active sessions, 3.22% of total activity.
-------------------------------------------------------
Contention for latches related to the shared pool was consuming significant
database time.
Waits for "library cache lock" amounted to 3% of database time.

No recommendations are available.

Symptoms That Led to the Finding:

---------------------------------
Wait class "Concurrency" was consuming significant database time.
Impact is .5 active sessions, 3.27% 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 "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.
Hard parsing of SQL statements was not consuming significant database time.

The database's maintenance windows were active during 16% of the analysis
period.