Disabling Multi-DB In BRM Where It Is Already Enabled
(Doc ID 2555889.1)
Last updated on OCTOBER 10, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Consider a scenario wherein multi-DB module is enabled in the system but not used:
i) How to disable multi_db parameter?
ii) How can one deal with uniqueness table? Can it be purged?
Is there any required change on database before applying that change given that the database is in cluster active-active mode?
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