18 Troubleshooting the BRM Upgrade

Learn how to solve problems that may occur in your Oracle Communications Billing and Revenue Management (BRM) system during or after an upgrade.

Topics in this document:

For more information, see "Reference Guide to BRM Error Codes" and "Resolving Problems in Your BRM System" in BRM System Administrator's Guide.

Problem: A Wallet Error Occurred When Upgrading the Database

When you run the pin_upgrade script to upgrade the database from BRM 12.0 to BRM 15.1, you may see an error like the following: 

WARNING : WALLET_FILE_STORAGE_T table is missing
EXISTING_WALLET_LOCATION Can not be empty

Possible Cause

This may happen if you run the database upgrade script from a different server than the one where you ran the installer for the upgrade.

Solution

To remove this error:

  1. Open the BRM_home/setup/pin_setup.values file in a text editor.

  2. Locate the following line in the file

    #$EXISTING_WALLET_LOCATION = "NA" ;

  3. Remove the comment from the line and replace NA with the path to your existing wallet (the one for the version you are upgrading from).

    For example if you are upgrading from BRM 12.0 and your BRM 12.0 wallet is located in /pinuser/opt/portal/BRM/wallet/client, update the line to read: 

    $EXISTING_WALLET_LOCATION = "/pinuser/opt/portal/BRM/wallet/client/" ;

  4. Save and exit the file.

  5. Run the pin_upgrade script again.

Problem: Missing Table While Upgrading the Database

When you upgrade BRM 12.0 to BRM 15.0 or later versions, you may encounter the following error in the dm_oracle log file while running the BRM 15.x installation script: 

ORA-12514, TNS:listener does not currently know of service requested in connect descriptor

Following this, when you run the pin_upgrade script to upgrade the database, the below error appears in the dm_oracle log file: 

ORACLE error: load_brm_root_wallet: PINStmtExecute: code 942, op 0
=ORA-00942: table or view does not exist

This indicates that the BRM 15.x installation script failed to create the WALLET_FILE_STORAGE_T table. This table is essential for the pin_upgrade script to create the root wallet.

Possible Cause

The table creation gets skipped due to a connectivity issue between the BRM server and the database.

Solution

To remove this error:

  1. Check the network connectivity between the designated BRM server and the database server before running the BRM 15.x installation script. This can be validated using the ping command.

  2. Ensure that tnsping, sqlplus, and jdbc connectivity is working correctly.

  3. Edit the sqlnet.ora file for the target database to increase the amount of time specified for the BRM server to connect with the database server and provide the necessary authentication information. If no units are specified, the value is in seconds. For example, to set the timeout to 120 seconds, update the parameter this way: 

    SQLNET.INBOUND_CONNECT_TIMEOUT=120

    The default value is 3.

  4. Rerun the BRM 15.x installation script.

  5. Verify that the WALLET_FILE_STORAGE_T table is present and contains the required data.

  6. Proceed with upgrading the database by running the pin_upgrade script.

For more information, see "Upgrading BRM and Pipeline Manager from BRM 12.0 to BRM 15.1" .