My Oracle Support Banner

Connectivity Problems Between CM and dm_fusa After Upgrading to BRM 12 (Doc ID 2744142.1)

Last updated on JANUARY 15, 2021

Applies to:

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

Symptoms

On : Billing and Revenue Management (BRM) 12.0.0.3.0 version, Paymentech Manager

For an environment which has been upgraded from BRM 7.5 PS17, during the upgrade process, the procedure mentioned in Upgrade Guide was executed to continue using the legacy AES encryption method in BRM 12.
See here: https://docs.oracle.com/en/industries/communications/billing-revenue/12.0/upgrade-guide/upgrading-brm-and-pipeline-manager1.html#GUID-154AAD28-5C82-4FA5-917B-14926D11AB30
After upgrade finished with no errors, processes were started without problems on 12.0.0.3.0 environment.

When PCM_OP_SEARCH opcode is executed from testnap for credit card tokenization, the following error is logged in cm.pinlog:

Steps to reproduce:

1. during the upgrade process, before executing database schema upgrade script (pin_upgrade_12ps3.pl), executed the procedure mentioned in Upgrade Guide (backup CRYPTKEY_T table from 7.5 env, generate new AES key on BRM 12 and configure it to dm_oracle pin.conf etc)
2. execute database schema upgrade script (pin_upgrade_12ps3.pl)
3. run the remaining steps of upgrade process
4. start all processes
5. execute PCM_OP_SEARCH from testnap for credit card tokenization

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution


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