1. Installation Guide
  2. Upgrading BRM
  3. Upgrading BRM 15.0 to a Later Release of BRM 15.0

16 Upgrading BRM 15.0 to a Later Release of BRM 15.0

Learn how to upgrade an Oracle Communications Billing and Revenue Management (BRM) 15.0 release to a later BRM 15.0 release and to roll back the upgrade.

Topics in this document:

Note:

About Installing the Later Release

Note:

Test the later release on a non-production system before you deploy it on a production system.

The BRM installer allows you to upgrade from BRM 15.0 or a later BRM 15.0 release to the latest release. For example, you could upgrade a BRM 15.0.0 system to BRM 15.0.1.

When you do an upgrade, only files that have been changed are updated. The installer makes a backup of any file it updates. You use the backup files to merge your customizations and to uninstall the later release. The pre-upgrade version of each updated file is stored with the extensions GA and TGA and is left in its original directory. For example, when you install BRM 15.0.1 to upgrade Pipeline Manager, the existing sample.reg file is renamed to sample.reg.TGA.

The installer contains multiple packages to upgrade different BRM and Pipeline Manager components. You can install or upgrade these components by installing their corresponding packages:

  • BRM

  • BRM SDK

  • Pipeline Manager

Performing a Zero Downtime Upgrade

Note:

  • If you perform the zero downtime upgrade, billing might fail for some accounts. In that case, rerun billing for the failed bill units by running the billing utility with the -retry option.

  • If your upgrade fails due to resource busy or timeout errors in the database, consult your DBA about increasing the value of the DDL_LOCK_TIMEOUT parameter for your database.

You can use the zero downtime upgrade method to upgrade your existing BRM installation with very minimal disruption to your existing installation and the services that are provided to your customers.

Before you perform the zero downtime upgrade, ensure the following:

  • You have two instances of the existing BRM 15.0 release on your system; for example, two instances of BRM 15.0.0.

  • Both BRM instances are currently running. This includes the primary and secondary instances and all the applications in the components connected to your BRM system.

  • Both BRM instances are connected to the same BRM and Pipeline Manager database schemas.

To perform the zero downtime upgrade:

Note:

Do not shut down the applications in the components connected to your BRM system while the upgrade is running.

  1. Route all the traffic (for example, phone calls or data usage) from the primary instance to the secondary instance.

  2. Upgrade the primary instance and the BRM database schema to the new release of BRM 15.0; for example, BRM 15.0.1. See "Upgrading to the New Release" for instructions.

  3. Start the primary instance. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide for instructions.

  4. Reroute all traffic from the secondary instance to the primary instance.

    Caution:

    During the database upgrade on the primary instance, ensure that the services or operations in the secondary instance are running until all of the requests are rerouted to the primary instance.

  5. Upgrade the secondary instance to the new release. See "Upgrading to the New Release" for instructions.

    Note:

    Because you have already upgraded the BRM database schema during the primary instance upgrade, you can skip "Upgrading the BRM Database Schema to the New Release".

  6. Perform post-upgrade tasks on both primary and secondary instances. See "Post-Upgrade Procedures for the New Release" for instructions.

Note:

Batch operations, such as billing, might fail for a few accounts during the upgrade. You must restart the applications to complete your batch operations.

Tasks Involved in the Upgrade Process for a New Release

This section provides a list of tasks required to upgrade from BRM 15.0 to a new release of BRM 15.0. Some tasks are optional or apply only to certain system configurations. Be sure to check whether a task is required for your system.

Caution:

When upgrading a multischema system, pay close attention to the system on which each task is performed.

Complete these tasks before upgrading your BRM system. See "Preparing for the Upgrade to the New Release" for more information.

  1. Shut down the current instance of BRM.

  2. Turn off service authentication and authorization.

  3. Create a complete backup of your BRM data.

  4. Install the latest compatible version of Java if it is different from the one for your current release.

  5. Install the latest compatible version of Perl if it is different from the one for your current release.

  6. Install any optional components you want to add to the old release. It is recommended to add any optional components to the instance you are upgrading from before the upgrade, because you cannot add them while you are doing the upgrade.

Perform the following tasks to upgrade to the new release. See "Upgrading to the New Release" for more information.

  1. Set the environment variables, for example setting the variables for Java and Perl variables to the latest compatible version.

  2. Verify that the BRM wallet location in sqlnet.ora is correct.

  3. Obtain the BRM software.

  4. Install the upgrade package.

  5. Upgrade Business Operations Center.

  6. Upgrade the BRM database schema to the schema for the new release.

  7. If you are using Pipeline Manager, upgrade the Pipeline Manager database schema for the new release.

  8. Install BRM client applications.

  9. Add customizations.

After you upgrade to the new release of BRM 15.0, perform the following post-upgrade tasks. See "Post-Upgrade Procedures for the New Release" for more information.

  1. Configure SSL for the BRM Database.

  2. Remove invalid objects from the database.

Preparing for the Upgrade to the New Release

Complete these tasks before upgrading your BRM system:

  1. Shut down the current instance of BRM. See "Shutting Down the Current Instance" for instructions.

  2. Create a complete backup of your BRM data. See "Backing Up Your BRM and Pipeline Manager Databases" for instructions.

  3. Install the latest compatible version of Java if it is different from the one for your current release. See "Installing Java" for instructions.

  4. Install the latest compatible version of Perl if it is different from the one for your current release. See "Installing Perl" for instructions.

  5. Install any optional components you want to add to the old release. See "Installing Optional Components" for instructions.

Shutting Down the Current Instance

Note:

On multischema systems, first perform this task on the primary system, and then on the secondary systems.

To shut down the existing BRM instance:

  1. Ensure that no users are logged in.

    Users include customers, client applications, customer service representatives (CSRs), and so on.

  2. Stop all BRM processes. For more information, see "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

    Only the database instances should be running during the upgrade.

Backing Up Files

Note:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

In particular, ensure that you back up the following files:

  • All customized files, including any associated source code

  • Registry files

  • Policy files

  • start_all

  • pin.conf

  • pin_ctl.conf

  • pin_setup.values

  • Infranet.properties

  • All other files that contain any customizations used in your system

If any libraries that were used in a previous release are no longer needed for a later release, these libraries will be moved automatically to BRM_home/deleted_files for reference, so you do not need to back them up manually.

Backing Up Your BRM and Pipeline Manager Databases

Note:

In multischema systems, perform this task first on the primary database schema and then on the secondary database schemas.

Make a complete offline backup of your BRM database and, if you are using Pipeline Manager, also the Pipeline Manager database. Make the backup using the appropriate backup tools for your database version and ensure that the backup is completely valid and usable. The backup must contain both the database definition and all the database contents. See your database software documentation for more information on performing full database backups.

Note:

Store this backup in a safe location. The data in these files will become necessary if you encounter any issues in the upgrade process.

Installing Optional Components

Note:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

Before upgrading the BRM 15.0 release, install any optional components that you want to add to your BRM system. For example, if you want to add Collections Manager to your BRM system, install Collections Manager in your old release before you install the latest BRM 15.0 release.

See "Installing Individual BRM Components" for more information.

Upgrading to the New Release

Perform the following tasks to upgrade to the new release:

Caution:

When upgrading a multischema system, pay close attention to the system on which each task is performed.

  1. Set the environment variables, for example setting the variables for Java and Perl variables to the latest compatible version. See "Setting the Environment Variables for Upgrade" for instructions.

  2. Verify that the BRM wallet location in sqlnet.ora is correct. See "Setting BRM Wallet Location in sqlnet.ora" for instructions for updating this value.

  3. Obtain the BRM software. See "Downloading the BRM Software" for instructions.

  4. Install the upgrade package. See "Upgrading BRM for the New Release" or "Upgrading BRM for the New Release in Silent Mode" for instructions.

  5. Upgrade the BRM database schema to the BRM 15.0 schema. See "Upgrading the BRM Database Schema to the New Release" for instructions.

  6. Upgrade the Pipeline Manager database schema to the BRM 15.0 schema. See "Upgrading the Pipeline Manager Database Schema to the New Release" for instructions.

  7. Upgrade Business Operations Center. See "Upgrading Business Operations Center" in Business Operations Center Installation Guide for instructions.

  8. Install BRM 15.0 client applications. See "Installing the BRM 15.0 Client Applications" for instructions.

  9. Add customizations. See "Adding Customizations" for instructions.

Upgrading BRM for the New Release

Note:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

To upgrade to the new release:

  1. Go to the directory where you downloaded the BRM installer, and start the installer. See "Starting the BRM GUI Installer".

  2. In the Welcome window, click Next.

  3. In the Installation Location window, enter the full path or browse to the directory in which you installed BRM 15.0 and then click Next.

  4. In the Specify Prerequisite Libraries Location window, specify the following library information and then click Next.

    Field Description

    Prerequisite Libraries

    Enter the full path or browse to the directory in which the prerequisite libraries are stored.

    Enable SSL for BRM server

    You must set this to the same value used for the instance you are upgrading from.

  5. In the Oracle Wallet Details window, enter the following information for accessing the Oracle wallets in BRM and then click Next.

    Field Description

    Wallet Password

    Enter the password for the client Oracle wallet for the existing 15.0 installation.

    Wallet Location

    Enter the path or browse to the directory in which the client Oracle wallet for the existing 15.0 installation is located.

  6. In the Database SSL Options window, select the same value (Yes One Way, Yes Two Way, or No) that was used for the instance you are upgrading from.

  7. In the following windows, provide the requested information, and then click Next.

  8. In the Installation Summary window, review the selections you have made in the preceding windows and then click Install.

    The Installation Progress window appears.

    Note:

    After installation begins, clicking Cancel stops the installation process, but the files that are already copied are not removed. You must manually remove the files. For instructions, see the steps to remove the files in "Rolling Back the New BRM Release".

  9. When the installation is done, click Next. The Installation Complete window appears.

    Note the provided URL. You will use this URL to access BRM.

  10. Click Finish to complete and exit.

Upgrading BRM for the New Release in Silent Mode

If you want to upgrade the BRM release, using the same configuration, in multiple environments. Silent install mode does not use the GUI and it runs in the background.

In this mode, you use a response file template that contains a predefined set of values to upgrade BRM to the new release. You can generate a response file that contains the parameters and values during the GUI installation.

Creating a Response File

To create a response file:

  1. Create the response file by doing one of these:

    • Create a copy of the response file that was generated during the GUI upgrade. See "Upgrading BRM for the New Release" for more information.

      Note:

      The GUI Installer does not store passwords provided during installation in the response file. You must manually add the passwords after creating a copy of the response file.

    • Create a response file using the template by running the following command:

      Java_home/bin/java -jar jarFile -getResponseFileTemplates

      where:

      • Java_home is the directory in which you installed the latest compatible Java version.

      • jarFile is the BRM installer file. For example: 

        brmserver_15.0.0.0.0_linux_generic_full.jar

      A response file is created with the default values.

    You can create as many response files as needed.

  2. Open the file in a text editor.

  3. Modify the response file you copied by specifying the key-value information for the parameters you want in your installation.

    Note:

    • The response file template contains guidelines and examples on how to enter the values in the parameters.

    • The Installer treats incorrect context, format, and type values in a response file as if no value were specified.

  4. Save and close the response file.

Upgrading the Release in Silent Mode

To upgrade the BRM release in silent mode:

  1. Create the response file. See "Creating a Response File".

  2. Copy the response file you created to the machine on which you run the silent installation.

  3. On the machine on which you are running the silent installation, go to the directory where you downloaded the BRM software, and run the following command:

    Java_home/bin/java -jar jarFile -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc [parameter=value] -responseFile path -silent

    where:

    • Java_home is the location of the compatible version of Java.

    • jarFile is the BRM installer file. For example: 

      brmserver_15.0.0.0.0_linux_generic_full.jar

    • Inventory_home is the location of the Oracle inventory.

    • parameter is the name of an installation parameter.

    • value is the value of the installation parameter.

    • path is the absolute path to the response file.

    For example: 

    $JAVA_HOME/bin/java -jar brmserver_15.0.0.0.0_linux_generic_full.jar -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc INSTALL_TYPE=Complete -responseFile /tmp/brm_complete.rsp  -silent

    The installation runs silently in the background.

    Note:

    For a complete list of the available parameters for the [parameter=value] clause, and for information about optional debugging parameters, run the following command: 

    Java_home/bin/java -jar jarFile -help

Upgrading the BRM Database Schema to the New Release

The database objects associated with the optional components that are not already installed are not created or updated. To upgrade the BRM database schema, perform one of these procedures:

Upgrading the Schema on Single-Schema Systems

To upgrade the schema on single-schema systems:

  1. Grant an additional permission to the BRM database user:
    1. Connect to the primary database instance using SQL*Plus:
      % sqlplus system@databaseAlias as sysdba
    2. Run the following command:
      SQL> GRANT SELECT ON V_$SESSION TO BRM_user;
Grant succeeded.
SQL> commit;
Commit complete.
    3. Exit SQL*Plus.

  2. Open the BRM_home/setup/scripts/pin_tables.values file in a text editor.

  3. Set these parameters to local: 

    # For indexes on event tables
    $PIN_CONF_PARTITION_IND             = "local";
# For indexes on non event tables
    $PIN_CONF_NON_EVENT_PARTITION_IND   = "local";

  4. Save and close the file.

  5. Go to BRM_home and source the source.me file:

    • Bash shell: 

      source source.me.sh

    • C shell: 

      source source.me.csh

  6. Go to the BRM_home/setup/scripts directory and run this script:

    Note:

    Ensure that you do not run the upgrade script in the background.

    perl script

    where script is either pin_upgrade_15.pl for BRM 15.0.0 or pin_upgrade_15psx.pl for a maintenance release with x as the maintenance release, such as 1 for BRM 15.0.1, 2 for BRM 15.0.2, and so on. For example, if you are upgrading to BRM 15.0.1, run the following command: 

    perl pin_upgrade_15ps1.pl

    This script runs a series of scripts that upgrade the BRM data to the new release.

  7. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

Upgrading the Schema on Multischema Systems

To upgrade the schema on multischema systems:

  1. On the primary BRM installation machine, do this:

    1. Grant an additional permission to the BRM database user:
      1. Connect to the primary database instance using SQL*Plus:
        % sqlplus system@databaseAlias as sysdba
      2. Run the following command:
        SQL> GRANT SELECT ON V_$SESSION TO BRM_user;
Grant succeeded.
SQL> commit;
Commit complete.
      3. Exit SQL*Plus.

    2. Ensure that the DMs in your secondary BRM installation machines are up and running.

    3. Ensure that the PERL_VERSION environment variable is set to the latest version of Perl certified with BRM.

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

    5. Set these parameters:

      $SETUP_DROP_ALL_TABLES = "NO";
$SETUP_INIT_DB = "YES";
$SETUP_CONFIGURE = "YES";
$SETUP_DATABASE_TABLES = "NO";

    6. Save and close the file.

    7. Open the BRM_home/setup/scripts/pin_tables.values file in a text editor.

    8. Set these parameters to local: 

      # For indexes on event tables
    $PIN_CONF_PARTITION_IND             = "local";
# For indexes on non event tables
    $PIN_CONF_NON_EVENT_PARTITION_IND   = "local";

    9. Save and close the file.

    10. Go to BRM_home and source the source.me file:

      Bash shell: 

      source source.me.sh

      C shell: 

      source source.me.csh

    11. Go to the BRM_home/apps/multi_db directory and run this script: 

      ./install.sh

      Follow the on-screen instructions, entering this information for the primary schema and for each secondary schema when requested:

      – Schema user name

      – Schema password

      – Schema SID (the BRM database alias of the schema)

      Note:

      Repeat the "Do you have secondary schema to process" step for each secondary schema in your system.

      The install script fixes any data errors caused by conflicting storable class IDs. The errors might have occurred during extended architecture (XA) transactions involving multiple schemas or when accounts were migrated from one schema to another.

      Note:

      As the install script runs, it generates the BRM_home/apps/multi_db/fix_multi_schema.log file. To view the progress of the script, display the log file in a different console window.

    12. Go to the BRM_home/setup/scripts directory and run this script:

      Note:

      Ensure that you do not run the upgrade script in the background.

      perl script

      where script is either pin_upgrade_15.pl for BRM 15.0.0 or pin_upgrade_15psx.pl for a maintenance release with x as the maintenance release, such as 1 for BRM 15.0.1, 2 for BRM 15.0.2, and so on. For example, if you are upgrading to BRM 15.0.1, run the following command: 

      perl pin_upgrade_15ps1.pl

      This script runs a series of scripts that upgrade the BRM data from BRM 12.0 to BRM 15.0.x.

    13. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

    14. Ensure that the BRM processes are not running.

  2. On each secondary BRM installation machine, do this:

    1. Grant an additional permission to the BRM database user:
      1. Connect to the primary database instance using SQL*Plus:
        % sqlplus system@databaseAlias as sysdba
      2. Run the following command:
        SQL> GRANT SELECT ON V_$SESSION TO BRM_user;
Grant succeeded.
SQL> commit;
Commit complete.
      3. Exit SQL*Plus.

    2. Ensure that the BRM processes are not running.

    3. Open the BRM_home/setup/scripts/pin_tables.values file in a text editor.

    4. Set these parameters to local: 

      # For indexes on event tables
    $PIN_CONF_PARTITION_IND             = "local";
# For indexes on non event tables
    $PIN_CONF_NON_EVENT_PARTITION_IND   = "local";

    5. Save and close the file.

    6. Go to BRM_home and source the source.me file:

      Bash shell: 

      source source.me.sh

      C shell: 

      source source.me.csh

    7. Copy the BRM_home/setup/scripts/pin_multidb.conf file from the primary environment to the same location in the secondary environment.

      Note:

      After you copy this file manually to the secondary environment, the upgrade script will refresh the views by reading the copied file.

    8. Go to the BRM_home/setup/scripts directory and run this script:

      Note:

      Ensure that you do not run the upgrade script in the background.

      perl script

      where script is either pin_upgrade_15.pl for BRM 15.0.0 or pin_upgrade_15psx.pl for a maintenance release with x as the maintenance release, such as 1 for BRM 15.0.1, 2 for BRM 15.0.2, and so on. For example, if you are upgrading to BRM 15.0.1, run the following command: 

      perl pin_upgrade_15ps1.pl

      This script runs a series of scripts that upgrade the BRM data to the new release.

    9. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

  3. On the primary BRM installation machine, do this:

    1. Go to the BRM_home/apps/multi_db directory and open the config_dist.conf file in a text editor.

    2. Add a line specifying the schema name at the end of each block in the file. For example, if you have two database schemas, your file might look like this:

      DB_NO = "0.0.0.1" ;        # 1st database config block.
PRIORITY = 1 ;
MAX_ACCOUNT_SIZE = 100000 ;
STATUS = "OPEN" ;

DB_NO = "0.0.0.2" ;        # 2nd database config block.
PRIORITY = 1 ;
MAX_ACCOUNT_SIZE = 100000 ;
STATUS = "OPEN" ;

      Update the file to look more like the following:

      DB_NO = "0.0.0.1" ;        # 1st database config block.
PRIORITY = 1 ;
MAX_ACCOUNT_SIZE = 100000 ;
STATUS = "OPEN" ;
SCHEMA_NAME = "pin01" ;

DB_NO = "0.0.0.2" ;        # 2nd database config block.
PRIORITY = 1 ;
MAX_ACCOUNT_SIZE = 100000 ;
STATUS = "OPEN" ;
SCHEMA_NAME = "pin02" ;

      using the correct schema names for your environment.

    3. Save and exit the config_dist.conf file.

    4. Go to the BRM_home/setup/scripts directory and run this command: 

      pin_multidb.pl -i

    5. At this prompt, enter y, which begins the configuration: 

      Do you want to start the configuration now? (y/n):   y

    6. At this prompt, enter 2, which initializes the primary database: 

      Please enter the starting step (0-8). If you don't know, enter 0:   2

    7. Follow the instructions displayed and exit the pin_multidb.pl script.

      The refresh groups are recreated in the primary database.

    8. Run this command:

      pin_multidb.pl -R all

      The Connection Managers (CMs) in your secondary BRM installation machines are now started. The views, based on the information in the refresh groups, are re-created in the secondary databases.

Upgrading the Pipeline Manager Database Schema to the New Release

Note:

In multischema systems, run the database upgrade script on the primary schema and then on the secondary schemas.

To upgrade your Pipeline Manager database schema:

  1. Open the Pipeline_home/upgrade/pipeline_upgrade.cfg file in a text editor, where Pipeline_home is the directory in which Pipeline Manager is installed.

  2. Set the values of the following parameters:

    • Set PIN_TEMP_DIR to the directory in which you want to create the temporary files.

    • Set the $PIPELINE_TBLSPACE environment variable to the tablespace where you want to create pipeline database objects.

    • In the Information about the databases section, configure the following database settings as required: 

      $MAIN_DB{'vendor'} = "oracle";
$MAIN_DB{'alias'} = ( $ENV{'ORACLE_SID_PIN'} or $ENV{'ORACLE_SID'} );
$MAIN_DB{'user'} = "USERNAME";
$MAIN_DB{'Database'} = "DATABASE_NAME";
$MAIN_DB{'Host'} = ( $ENV{'ORACLE_SID_PIN'} or $ENV{'ORACLE_SID'} );

  3. Save and close the file.

  4. Grant the required access to user pin on the Pipeline Manager tables and sequences, if you have not already done so.

    See "Loading the Tailor-Made Stored Procedure" in BRM Installation Guide for more information about the Pipeline Manager tables and sequences that you should grant user pin access to.

  5. Go to the Pipeline_home/setup/scripts directory and run the following command: 

    perl script

    where script is either pin_upgrade_15.pl for BRM 15.0.0 or pin_upgrade_15psx.pl for a maintenance release with x as the maintenance release, such as 1 for BRM 15.0.1, 2 for BRM 15.0.2, and so on. For example, if you are upgrading to BRM 15.0.1, run the following command: 

    perl pin_upgrade_15ps1.pl

    This script runs a series of scripts that upgrade Pipeline Manager data to the new release.

Adding Customizations

Note:

In multischema systems, incorporate customizations first on the secondary BRM installation machines and then on the primary BRM installation machine.

Incorporate any customizations you made, including source code, policy, pin.conf, pin_ctl.conf, pin_setup.values, and Infranet.properties files, if you have not already incorporated them.

(Production system only) Remove all entries for the pin_virtual_time utility from the configuration files.

Post-Upgrade Procedures for the New Release

After you install the new release of BRM 15.0, perform the following postinstallation tasks:

  1. Configure SSL for the BRM Database. See "Configuring SSL for the BRM Database" for instructions.

  2. Remove invalid objects from the database. See "Removing Invalid Objects from the Database" for instructions.

Installing Optional Components After the Release Upgrade

Typically, you install optional components before installing the new release. However, if you have already installed the new BRM release and you want to install any optional components:

  1. Set the PERL_HOME environment variable to the directory in which Perl is installed by running this command:

    setenv PERL_HOME Perl_path

    where Perl_path is the path to the directory in which Perl is installed, for example /perl_5_36.0/linux.

    For the compatible Perl version, see "Additional Software Requirements (BRM)" in BRM Compatibility Matrix.

  2. Install the required optional components. See "Installing Optional Components".

  3. Unset the PERL5LIB environment variable.

  4. Go to the BRM_home/setup directory and run this command: 

    ./pin_setup -GA

  5. Upgrade the optional component to the BRM 15.0 release you want to install. See "Upgrading to the New Release".

  6. Set the PERL5LIB environment variable to the directory in which Perl is installed.

Rolling Back the New BRM Release

To roll back the BRM release upgrade:

  1. Ensure that you take an offline backup of the data and customizations added after the new release installation.

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

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

  3. Log in as user pin.

  4. Run this command:

    ./deinstall.sh

    The Distribution to Uninstall window appears.

  5. Select the release and the components that you want to uninstall.

    Note:

    Do not use the Select All option to select the release or components. If you use this option, the initial release and the new release are selected for uninstallation.

    Ensure that you have selected only the components for the new release that you want to uninstall.

  6. Click Uninstall.

    The Welcome window appears.

    Note:

    The Welcome window displays the uninstaller version as 15.0.0.0.0. You can ignore the version displayed in this window.

  7. Click Next.

    The Uninstallation Summary window appears.

  8. Click Uninstall.

    The Uninstallation Progress window appears.

  9. Click Next.

    The Uninstallation Complete window appears.

  10. Click Finish.

    The new release is uninstalled and the backup files are stored in the system with the .GA extension.

  11. To remove the backup files, run this command:

    BRM_home/setup/scripts/RevertMe.pl 0 0 Oracle_home

    where Oracle_home is the directory in which the Oracle database is installed.

  12. If BRM and Pipeline Manager are installed on separate locations, run this command from the location in which Pipeline Manager is installed:

    IFW_home/setup/scripts/RevertMe.pl 0 0 Oracle_home

    where IFW_home is the directory in which Pipeline Manager is installed.

The backup files are removed and the BRM release is rolled back. The rollback process removes the new BRM release and reverts the BRM software to the previous version. However, this process does not affect the database. To return the database schema to the previous version, restore the database using the backup you took at the beginning of the upgrade.