Rolling Back Your BRM Database Upgrade

21 Rolling Back Your BRM Database Upgrade

Learn how to roll back your Oracle Communications Billing and Revenue Management (BRM) database to previous release.

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 12.0.0.8.0 to BRM 15.2 and encounter problems, you can roll it back to BRM 12.0.0.8.0.

Note:

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

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.

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 is limited to BRM 12.0.0.4.0 or later. You cannot revert to earlier releases.
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 from BRM 15.2 to BRM 12.x, attempting to read BRM 15.2 events in BRM 12.x fails if the event version supported in BRM 12.x is lower than the version used in BRM 15.2. Because no automatic event downgrade occurs, you must manually convert the BRM 15.2 event format to the BRM 12.x event version before these events can be accessed in the rolled-back environment.

After rolling back your BRM database, you can:

Roll back the BRM application so you can start using the previous BRM release. See "About Reusing Your Previous 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 15.2 to BRM 15.0, you can subsequently upgrade again to BRM 15.2 or later, but you cannot upgrade to BRM 15.1.

Tasks for the Database Rollback Process

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

Note:

These instructions cover the BRM database rollback procedure. To roll back the BRM applications, run a Helm upgrade from the previous installation’s directories.

In your override-values.yaml file for your 15.2 version of oc-cn-init-db-helm-chart, set the following keys:
- ocbrm.is_rollback: Set this to true.
- ocbrm.is_upgrade: Set to this to false.
Run the helm install command for the 15.2 version of oc-cn-init-db-helm-chart:
```
helm install NewInitDbReleaseName oc-cn-init-db-helm-chart --values OverrideValuesFile --namespace BrmNameSpace
```
where:
- NewInitDbReleaseName is a new release name.
- OverrideValuesFile is the file name and path to your override-values.yaml file.
- BrmNameSpace is the namespace for oc-cn-helm-chart.
Verify that the database rollback completed successfully by checking that the ROLLBACK_STATUS field in the BRM_PS_T table is set to 1.

About Reusing Your Previous BRM Installation

Before you can start using your previous BRM installation, perform these steps:

Roll back your BRM applications. To do so, run the helm upgrade command for the release you rolled back to. For example, if you rolled back from BRM 15.2 to BRM 15.0, run the helm upgrade command for the BRM 15.0 release.
```
helm upgrade BrmReleaseName oc-cn-helm-chart --values PreviousOverrideValuesFile --namespace PreviousBrmNameSpace
```
where:
- BrmReleaseName is the release name used for the previous oc-cn-helm-chart install.
- PreviousOverrideValuesFile is the file name and path to your override-values.yaml file for the previous release.
- PreviousBrmNameSpace is the namespace that you used for your previous release.
Run the load_pin_notify utility through a configuration job.

Note:

All steps must use the release you rolled back to. For example, if you rolled back from BRM 15.2 to BRM 15.0, use the BRM 15.0 versions of the files, directories, Helm chart, and scripts.
1. Add the following lines to the oc-cn-helm-chart/config_scripts/loadme.sh script:
```
#!/bin/sh 
 
cd /oms/sys/data/config; load_pin_notify -v /oms/sys/data/config/pin_notify_file
exit 0;
```
  where pin_notify_file is the name of the notification file.
2. Move the pin_notify_file input file to the oc-cn-helm-chart/config_scripts directory.
3. In the override-values.yaml file for oc-cn-helm-chart, set ocbrm.config_jobs.run_apps to true.
4. Run the helm upgrade command for the release your rolled back to.
```
helm upgrade BrmReleaseName oc-cn-helm-chart --values PreviousOverrideValuesFile --namespace PreviousBrmNameSpace
```
5. Restart the CM by setting these keys in the override-values.yaml file and then run the helm upgrade command again.
  - ocbrm.config_jobs.restart_count: Increment the existing value by 1
  - ocbrm.config_jobs.run_apps: Set this to false

After successfully rolling back your BRM system, you can begin reusing your system. However, before launching BRM, creating accounts, or running billing operations, do the following: