17 Rolling Back Your BRM Database Upgrade

Learn how to roll back your Oracle Communications Billing and Revenue Management (BRM) 16.26.0 database upgrade to its prior version.

Topics in this document:

About Rolling Back Your BRM Database

The rollback feature allows you to revert your BRM database and other supported components to their previous stable state if issues occur after an upgrade. For example, if you upgrade your database from BRM 15.2 to BRM 16.26.0 and encounter problems, you can roll it back to BRM 15.2.

Note:

You can roll back your BRM database only to the exact version that existed before the upgrade. For instance, if you upgrade from BRM 15.2 to 16.26.0, you can roll back only to 15.2. You cannot roll back to 15.1.

Before rolling back your BRM database, carefully review all prerequisites. Avoid making changes to system keys between the upgrade and rollback, and ensure you complete any rollbacks before making further schema or environment changes. In particular:

  • Do not add secondary schemas to your BRM database before performing a rollback. Adding a schema first may hinder the rollback process.

  • Do not rotate root keys between the upgrade and rollback.

  • Do not add new optional managers to your existing BRM setup between the upgrade and rollback.

  • Run the rollback script using BRM 16.26.0 (the current BRM version). After the database schema rollback completes successfully, revert to the previous file system and verify that the supported database server and client are in place before you restart services.

The BRM database rollback feature has the following limitations:

  • Rolling back is supported only for BRM 15.2 or later. You cannot roll back from BRM 15.1 or earlier versions.

  • Rolling back can be performed only immediately after an upgrade.

  • Rolling back is not supported for full BRM installations. To revert after a full installation, you must reinstall the earlier version of the software.

After rolling back your BRM database, you can:

  • Start using the previous BRM release. See "About Reusing Your Old BRM Installation".

  • In case you want to upgrade your BRM database again, you can upgrade to the same release you had rolled back from or a higher version.

    For example, if you roll back from BRM 16.26.0 to BRM 15.0, you can subsequently upgrade again to BRM 16.26.0 or later, but you cannot upgrade to BRM 15.1.

Database Rollback Tasks

The following lists the tasks required to roll back your BRM database to a previously installed release version.

  1. Ensure the upgrade to BRM 16.26.0 completed successfully.

    If the upgrade failed, resolve all issues before proceeding. The rollback procedure cannot be used in the middle of the upgrade flow.

  2. Stop all BRM daemons, processes, and managers.

    See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

  3. Go to the BRM_home/setup/scripts directory.

  4. Run the BRM database rollback script:

    perl pin_rollback.pl

  5. Adjust your environment to point to the previously installed release version:

    • Restore all third-party software to versions supported by the previous release.

    • Update your environment variables, including those for Perl and Java, to reference the appropriate supported versions.

    For supported software versions, see the BRM Compatibility Matrix for your version of the software.

  6. Verify that the database rollback completed successfully. Check that the ROLLBACK_STATUS field in the BRM_PS_T table is set to 1.

  7. If rolling back a minor upgrade, such as from 15.2 to 15.1, restore the previous BRM environment's file system:

    cd BRM_home/brm_backup
sh fileSystemRollback.sh

  8. Return the BRM wallet location to BRM_home/wallet/client in the sqlnet.ora file by doing the following:

    1. Open the sqlnet.ora file on the BRM machine. The file is located in the directory specified by $TNS_ADMIN (typically $ORACLE_HOME/network/admin).

    2. Set these entries:

      SQLNET.WALLET_OVERRIDE = TRUE
WALLET_LOCATION=(
   SOURCE=(METHOD=FILE)
   (METHOD_DATA=(DIRECTORY=$PIN_HOME/wallet/client))
)

    3. Save and close the file.

  9. Restart all BRM services.

    Note:

    If rolling back a major upgrade, such as from BRM 16.26.0 to 15.2, restart BRM services using the previous version's file system. For example, if you rolled back from 16.26.0 to 15.2, use the 15.2 file system.

About Reusing Your Old BRM Installation

After successfully rolling back your BRM database, you can resume using your system. However, before launching BRM, creating accounts, or running billing, go to the BRM_home/sys/data/config directory and run the load_pin_notify utility.

For information about the utility's syntax and parameters, see "load_pin_notify" in BRM Managing Customers.