Activity Log Not Loading For Very High Number Of Transactions (Bulk Records)
(Doc ID 2941852.1)
Last updated on APRIL 21, 2023
Applies to:
Oracle Banking Digital Experience - Version 21.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 21.1.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
Activity Log Not Loading For Very High Number Of Transactions (Bulk Records)
If there is a very high volume of transactions performed for the day or qualifying for the activity log filter criteria, the request gets timed out (503 - Service Unavailable) and the activity log is not loaded.
Data: 7000+ Bulk Records.
EXPECTED BEHAVIOR
-----------------------
Application should load even in case of high volume of transactions.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform high value of transactions in obdx (e.g 7000+ bulk records )
2. Login into obdx and check activity log by filter criteria
3. request getting timeout (503 - Service Unavailable )
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot view activity log.
Changes
No Changes done on environment.
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 |