Purging Mechanism is Missing for Base Tables.
(Doc ID 2696458.1)
Last updated on NOVEMBER 15, 2022
Applies to:
Oracle Banking Digital Experience - Version 18.2.0.0.0 to 18.2.0.0.0 [Release 18]Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Purging Mechanism is not implemented for below list of base tables, so they have huge data volume. While retrieving data from these voluminous tables, CPU and memory utilization are going high for Database Server.
DIGX_CO_MAILBOX_MESSAGE_USER
DIGX_CO_MAILBOX_MESSAGE_ALERT
DIGX_CO_MAILBOX_MESSAGE
DIGX_FW_USERSESSION
DIGX_CO_MESSAGE_CONTENT
DIGX_CO_MAILBOX_MESSAGE_MAIL
EXPECTED BEHAVIOR
---------------
Purging Mechanism should be implemented for high volume base tables.
STEPS
-----------------------
The issue can be reproduced at will with the following steps if purging is not happening and OBDX tables have huge data:
1. Login to OBDX application with retail/corporate user.
2. Perform random transactions.
3. After sometime observe the CPU and memory utilization for database server.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |