Last updated on APRIL 21, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Core Billing
The user needs to keep their Application layer in DR (Disaster Recovery) site to be active (keep running BRM components) to entertain READ-ONLY calls. No data will be written to DB, as the DR DB will be READ-ONLY mode. They have done a PoC (Proof of concept) to demonstrate this behavior by making the following config change:
Enable "- cm login_audit 0" entry in the cm pin.conf file and restart CM.
This made sure no audit entries are attempted to write to the database. Testnap was able to connect successfully – PCM_OP_SEARCH and PCM_OP_READ_OBJ were both successfully executed as READ ONLY calls. The custom QUOTE API calls were also successfully read data from DB.
Need BRM Product team’s opinion on this approach to meet the business expectation of making the Billing Engine high available to end customers.
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