Line Lock Issue And Difference Between DM_ORACLE pin.conf Parameters: database_request_timeout_duration And dm_trans_timeout
(Doc ID 1471590.1)
Last updated on OCTOBER 31, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.5.0.0.0 [Release 7.4.0 to 7.5.0]Information in this document applies to any platform.
Goal
Line lock statement:
select poid_DB, poid_ID0, poid_TYPE, poid_REV from bal_grp_t where bal_grp_t.account_obj_ID0 = :1 order by bal_grp_t.poid_id0 for update of bal_grp_t.poid_id0
select poid_DB, poid_ID0, poid_TYPE, poid_REV from bal_grp_t where bal_grp_t.account_obj_ID0 = :1 order by bal_grp_t.poid_id0 for update of bal_grp_t.poid_id0
Q1.How to avoid the line locking issue?
Q2: There are two parameters in the DM (Data Manager) configuration file :-
1. database_request_timeout_duration
2. dm_trans_timeout
How the two parameters work and how do they differ?
Solution
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
Goal |
Solution |
References |