PCM_OP_CUST_UPDATE_SERVICES Fails On Multi-Db Environment

(Doc ID 961743.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.1]
Information in this document applies to any platform.
Checked for relevance on 15-Jul-2011
***Checked for relevance on 24-Dec-2012***


Problem Statement:
Call PCM_OP_CUST_UPDATE_SERVICES on a previously created account to delete ALIAS_LIST entries for the account's services, it fails to complete.

Issue is reported in a multi-db environment (Primary, db1, db2), pricing, general and config tables are replicated via db_link mechanism (materialized views) but uniqueness is handled only on the primary database. Secondary databases have uniqueness tables too but these tables contain only one entry for the ROOT account.

CM is configured for a multi-db environment and to handle uniqueness on the primary, and db_link name have been specified on the secondary DM conf file.

Steps To Reproduce:
-Create a client on multi-db with some alias_list entries for a service
-Call UPDATE_SERVICE on the newly created account/service to delete the alias_list entries.


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