OB BRANCH: Ej Log Data Not Getting Archived
(Doc ID 2941200.1)
Last updated on APRIL 11, 2023
Applies to:
Oracle Banking Branch - Version 14.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.5.0.0.0 version, Consulting
ACTUAL BEHAVIOR
---------------
OB BRANCH: ej log data not getting archived
We have maintained the archival parameter in select * from transaction.srv_tb_bc_archival as 3 days.
So the data should get moved to history table after three days. But system is not moving data to archive tables during branch batch closure.
Currently the ej log is not archived and too much data is making performance slow.
EXPECTED BEHAVIOR
-----------------------
System should move the data to archive tables during branch batch closure
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, ej log data not getting archived
Changes
Added query to find the archival dates based on the branch code and number of days
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 |
| Changes |
| Cause |
| Solution |
| References |