During TRANS_COMMIT, Delay On DM_AQ Causes DM_ORACLE To Timeout
(Doc ID 1501141.1)
Last updated on JUNE 02, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
In a Siebel--> AIA --> JCA --> BRM setup where BRM is configured with multiple external publishing DMs (Data Managers) along with DM_ORACLE,
when an opcode is executed from Siebel, for a scenario where dm_aq delays more than 1 minute to enqueue the event, dm_oracle will result in timeout causing PIN_ERR_STREAM_IO error.
Any reason why dm_oracle times out before committing the transaction even though the actual delay caused was on external DM_AQ side?
Note: In the above scenario, dm_trans_timeout parameter in dm_oracle/pin.conf is set 1
- dm dm_trans_timeout 1
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