My Oracle Support Banner

Error From pin_rate_change In A Multi-DB Environment (Doc ID 1088815.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


In a multi-DB environment, the price is changed, BRM create a /rate_change object on the primary database. After snapshot replication, the object is present on the secondary database.

Launched the pin_rate_change, connecting to a CM -> DM on the secondary database. Getting error because it wants to update the status of the /rate_change on the secondary database and it's not possible because it is a view.

See the dm_oracle message :

Which type of CM the pin_rate change have to be connected ?

Since pin_rate_change does modify/update the /rate_change object and since the actual /rate_change object is in the primary database, the pin_rate_chance application should also be run against the primary database. This is not just for pin_rate change, but any application that reads and updates an object should connect to the DB where the object actually resides.

But, after some internal analysis, a problem was found for pin_rate_change in a multi-DB environment. If the /rate_change object is in the primary DB then if you running pin_rate_change might not pick up the /purchased_products for accounts in the secondary DBs. This is because the search is doing a PCM_OP_SEARCH instead of a PCM_OP_GLOBAL_SEARCH.

As a confirmation, only the primary account are searched (but there is no such account in that DB).


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.