PCM_OP_CUST_UPDATE_SERVICES Fails To Update Alias On A Multi-DB Environment
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 126.96.36.199.1
Information in this document applies to any platform.
On Multi-DB environment, when the services to be updated are on secondaries databases and the uniqueness table entries are kept on the primary database, PCM_OP_CUST_UPDATE_SERVICES fails to update alias with an error : PIN_ERR_TRANS_ALREADY_OPEN.
A read obj of the /uniqueness entry (on primary database) is done while a transaction is already open on a secondary database, which is causing the opcode to fail.
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