Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
***Checked for relevance on 21-Dec-2011***
Checked for relevance on 31-Jul-2014
TIMOS may encounter the following problems while handling the connections with the associated instances of dm_oracle:
1) The status of dm_oracle (DMO) is not updated within TIMOS OMF when a dm_oracle is unavailable.
2) When all DMOs are killed, the AUTHORIZE/REAUTHORIZE requests are executed correctly but the STOP_ACCOUNTING requests are not.
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