Database_request_timeout_duration After Parameter Is Set, Request Timeout Which Cause Cm Connection (Doc ID 1484848.1)

Last updated on FEBRUARY 18, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Information in this document applies to any platform.
**Checked for relevance on 24-Sep-2012***
**Checked for Relevance on 26th May 2014***
*** Checked for relevance on 11-18-2015 ***


In dm_oracle pin.conf, configuration is as follows:

BRM doesn't need to be restarted, but it can continue working after the client connection pool must reconnect to CM.

Question is - once the request timeout occurs, should we re-initialize all CM connection?


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