DM AQ/IFW Database Timeout Parameter is not Working
(Doc ID 2988278.1)
Last updated on NOVEMBER 21, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
The user is using database_request_timeout_duration to set database timeout after 20 sec for both dm_aq/dm_ifw_sync as below and does not see timeout happening after 20 seconds, instead it happens after 3 minutes.
- dm database_request_timeout_duration 20000
EXPECTED BEHAVIOR
-----------------------
dm_aq/dm_ifw_sync should time out after 20 seconds as configured in pin.conf.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Lock the AQ table with command "lock table aq_sync in exclusive mode;"
2. Create an account so that CustCreate business event gets created to be published to the AQ
3. dm_aq logs show timeout after 3 minutes and enqueue business event fails
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 |