Question on DM FrontEnd - BackEnd Connection Management
Last updated on AUGUST 25, 2016
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.
Checked for relevance on 25-Aug-2016.
How is it possible for PIN_FLD_DM_FE_STATE to have a State of 0 and PIN_FLD_DM_BE_STATE to have a State of 3?
Shouldn't the BackEnd connection be released from the transaction automatically when FrontEnd becomes Idle?
Here is the snippet of dm_status that is confusing:
It is suspected that a custom BRM code that caused CM to crash. When the CM children die, the front-end and back-end involved in the transaction end up in this state pair (FE 0, BE 3).
The possible values for PIN_FLD_DM_FE_STATE and PIN_FLD_DM_BE_STATE make sense when looking at them individually. That does not necessarily say that the combination of 0 and 3 is valid. In other words, when the back-end is busy and locked in a transaction but front-end is idle (ie NOT in state "2") then the net state between front-end and back-end becomes inconsistent. Backend will wait forever (and it does) and front-end is never going to send an abort or commit to the back-end.
The question is that why is the front-end not sending an abort command to the backend when the front-end looses its consumer, the CM child?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms