16 Upgrading BRM 15.x to BRM 16.26.0

Learn how to upgrade Oracle Communications Billing and Revenue Management (BRM) 15.0, 15.1, or 15.2 to BRM 16.26.0 and to roll back the upgrade.

Topics in this document:

Note:

To do a full installation of BRM 16.26.0, see "Installing BRM".

About Upgrading to BRM 16.26.0

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, 15.1, or 15.2 or a later BRM 15.0, 15.1, or 15.2 release to BRM 16.26.0. For example, you could upgrade a BRM 15.0.1 system to BRM 16.26.0.

Note:

Direct upgrades from BRM 12.x to BRM 16.26.0 are not supported. You must upgrade from BRM 12.x to BRM 15.x before upgrading from 15.x to 16.26.0.

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

Tasks Involved in the Upgrade Process

This section provides a list of tasks required to upgrade from BRM 15.x to BRM 16.26.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 to upgrade your BRM system:

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

  2. Turn off service authentication and authorization. See "Turning Off BRM Service Authentication and Authorization".

  3. Create a backup of your BRM and Pipeline Manager 15.x databases. See "Backing Up Your BRM and Pipeline Manager 15.x Databases".

  4. Create a new schema in BRM 16.26.0. See "Creating the Database for Your New Version".

  5. Import your BRM 15.x data. See "Importing Your BRM 15.x Data".

  6. Install Java. See "Installing Java".

  7. Install Perl. See "Installing Perl".

  8. Obtain the JDBC driver. See "Downloading the JDBC Driver".

  9. Set the environment variables. See "Setting the Environment Variables for Upgrade".

  10. Set the BRM wallet location in sqlnet.ora. See "Setting BRM Wallet Location in sqlnet.ora".

  11. Obtain the BRM software. See "Downloading the BRM Software".

  12. Install the upgrade package. See "Installing BRM and Pipeline Manager for Upgrade".

  13. Point your BRM 16.26.0 installation to the new database schema. See "Pointing the BRM 16.26.0 Installation to the Database Schema".

  14. Upgrade the BRM database schema to the BRM 16.26.0 schema. See "Upgrading the BRM Database Schema to the New Version".

  15. Upgrade the Pipeline Manager database schema to the BRM 16.26.0 schema. See "Upgrading the Pipeline Manager Database Schema to the New Version".

  16. Install BRM 16.26.0 client applications. See "Installing the BRM 16.26.0 Client Applications".

  17. Add optional components. See "Adding Optional Components".

  18. Check other database configurations. See "Updating Configurations".

  19. Upgrade Account Migration Manager for multischema systems. See "Upgrading AMM in a Multischema System".

  20. Restore customizations in BRM 16.26.0. See "Restoring Customizations".

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.

Turning Off BRM Service Authentication and Authorization

Note:

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

To maintain a controlled environment for pre-upgrade testing, cut off interaction between your BRM system and your customers.

Backing Up Your BRM and Pipeline Manager 15.x Databases

Note:

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

  • Additionally, record the system time of each backup file so that you can match that time entry when you import the backup data into the appropriate system for your new version.

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.

In addition to the backup, use the Oracle export exp or expdb utility to export all BRM 15.x tables. This helps to restore individual tables, if necessary. For more information about the exp and expdb utilities, see the discussion on export and import utilities in the appropriate version of the Oracle Database Utilities document.

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.

Creating the Database for Your New Version

Note:

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

Create a blank BRM database into which you will import the backup you created.

Importing Your BRM 15.x Data

Note:

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

After you have successfully created a new schema, create a BRM database user (which is the same as the database user in BRM 15.x), and then import the backup data you created in "Backing Up Your BRM and Pipeline Manager 15.x Databases". When you import the backup data, check the system time of each backup file to ensure that the data is imported into the appropriate system in BRM 16.26.0.

Use the imp or impdb utility to import the backup data. For more information about the imp and impdb utilities, see the discussion on export and import utilities in the appropriate version of the Oracle Database Utilities document.

After you complete the import process, make sure that there are no invalid objects in the database schema. If there are any invalid objects, try to compile them.

Setting the Environment Variables for Upgrade

Before installing the upgrade, ensure that the environment variables are set correctly. For information about the latest compatible versions of Java, Perl, and Kafka, see "BRM Software Compatibility" in BRM Compatibility Matrix.

To set the environment variables, perform the following for all users you are going to use to install or run the BRM server:

Note:

The commands below are appropriate for the Bash shell. If you are using a different shell, adjust the commands accordingly.

  1. Set the JAVA_HOME environment variable to the directory in which the latest version of Java certified with BRM is installed by running the following command:

    export JAVA_HOME=javaPath

    where javaPath is the path to the directory in which the latest version of Java certified with BRM is installed; for example, /Linux/x86_64/packages/jdk/jdk-21.0.9.

  2. Verify the Java version by running the following command:

    java -version

    The Java version is displayed.

    If the latest version of Java certified with BRM is not displayed, the latest Java version is not installed in the directory specified by JAVA_HOME.

  3. Set the PERL_HOME environment variable to the directory in which the latest version of Perl certified with BRM is installed by running the following command:

    export PERL_HOME=perlPath

    where perlPath is the path to the directory in which the latest version of Perl certified with BRM is installed; for example, /perl_5_40_2/linux.

  4. Set the PATH environment variable by running the following command:

    export PATH=$JAVA_HOME/bin:$PERL_HOME/bin:${PATH}

  5. Set the BRM_CONF_WALLET and BRM_WALLET environment variables to the location of your BRM wallet on the secondary installation machine:

    export BRM_CONF_WALLET=BRM_home/wallet/config
export BRM_WALLET=BRM_home/wallet/config

  6. Set the TNS_SERVICE_NAME environment variable to the service name for your primary database:

    export TNS_SERVICE_NAME=serviceName

  7. Set the HOSTNAME environment variable by running the following command:

    export HOSTNAME=hostname

    where hostname is the fully qualified host name of the machine on which your current instance of BRM is installed.

  8. If you will be using the Kafka Data Manager (DM), set the Kafka environment variables:

    export KAFKA_HOME=KafkaPath
export KAFKA_BOOTSTRAP_SERVER_LIST=KafkaHost1:port1,KafkaHost2:port2

    where:

    • KafkaPath is the path to the directory in which the Kafka library JAR files are installed.

    • KafkaHost1:port1,KafkaHost2:port2 are the hosts and ports that the Kafka client will connect to in a bootstrap Kafka cluster the first time it starts. You can specify any number of hosts and ports in this list.

      You can alternatively set this list in the dm_kafka_config.xml file. See "Mapping Business Events to Kafka Topics" in BRM Developer's Guide.

Installing BRM and Pipeline Manager for Upgrade

To install BRM and Pipeline Manager for upgrade:

  1. Download the BRM software. See "Downloading the BRM Software".

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

    The Welcome window appears.

  3. Click Next.

    The Installation Location window appears.

  4. Enter the full path or browse to the directory in which BRM 16.26.0 is going to be installed. Click Next.

    The Installation Type window appears.

  5. Select Custom, and then click Next.

    The Feature Sets Selection window appears.

  6. From the components list, select Upgrade Manager Framework and then select the components that you already installed in BRM 15.x. Click Next.

    Upgrade Manager Framework contains the BRM server upgrade and the Pipeline Manager upgrade.

    Note:

    • Ensure that you select the components in Upgrade Manager Framework (Portalbase Upgrade for BRM and Pipeline Upgrade for Pipeline Manager) that correspond to the components already installed in your BRM 15.x or BRM 15.x patch set environment. In the rest of the list, you must also select the same components that are already installed in your BRM 15.x or BRM 15.x patch set environment. You can install any additional optional component after completing the BRM 16.26.0 upgrade. See "Adding Optional Components" for instructions on installing the optional components.

    • If the existing BRM components are installed on separate machines, install the 16.26.0 component on the machine on which the existing component is installed. For example, if the BRM server and Pipeline Manager are installed on separate machines, install the BRM 16.26.0 server on the machine on which the existing BRM server is installed and BRM 16.26.0 Pipeline Manager on the machine on which existing Pipeline Manager is installed.

    If you selected only the components in Upgrade Manager Framework, proceed to step 9.

    If you selected the components in Upgrade Manager Framework and other components from the components list, the Specify Prerequisite Libraries Location window appears.

  7. Specify the information in Table 16-1, and then click Next.

    Table 16-1 Specify Prerequisite Libraries Location

    Field Description

    Prerequisite Libraries

    Enter the absolute path of the ojdbc11.jar file.

    Enable SSL for BRM server

    If you do not want to enable secure communication between BRM server components, deselect the Enable SSL for BRM server check box.

    To enable secure communication between BRM server components, leave the Enable SSL for BRM server check box selected.

    The Specify Upgrade Wallet Details window appears.

  8. In the Specify Upgrade Wallet Details window, enter the details listed in Table 16-2 and then click Next.

    Table 16-2 Specify Upgrade Wallet Details

    Field Description
    SSL Server Wallet Location

    Enter the path to the server wallet.

    Note: The SSL server wallet is required only when SSL is enabled.

    Existing Client Wallet Location

    Enter the path to the BRM 15.x primary client wallet ($PIN_HOME/wallet/client).

    Existing Client Wallet Password

    Enter the password for the BRM 15.x primary client wallet password.

    Config Wallet Password

    Enter the password for the BRM 16.26.0 config wallet.

    Confirm Config Wallet Password

    Confirm the password for the BRM 16.26.0 config wallet.

  9. In the following windows, provide the requested information, and then click Next, with the following considerations for upgrade:

    • In the BRM Root User Details window, in the Root Password field, ensure that you enter the existing BRM root password that you provided during the BRM 15.x installation.

    • In the Select Running the pin_setup Script window, select Yes. This will create the appropriate pin.conf files for your new environment. Because you selected upgrade packages to install, this will not initialize the database.

    • Although it is recommended that you stop all services before running the upgrade, you can have the BRM 15.x environment running during the installation of BRM 16.26.0. If this is the case, or if the two environments are ever going to be running at the same time, ensure that you provide different port numbers for the feature sets than the ones used for BRM 15.x to avoid port conflict.

    See "Installing All BRM Components" for descriptions of the fields displayed. Continue moving through the windows until the Installation Summary window appears.

    Your responses are written to the BRM_home/setup/pin_setup.values file, where BRM_home is the directory in which the new BRM server software is installed.

  10. In the Installation Summary window, review your selections, and then click Install.

    The Installation Progress window appears, and the installation begins.

    Note:

    After the installation begins, you cannot stop or cancel the installation.

  11. When the installation is done, click Next.

    The Installation Complete window appears.

    The installer checks for all required software and displays errors if it detects any missing or unavailable components or if any connectivity issues occur.

  12. Click Finish to exit the installer.

Pointing the BRM 16.26.0 Installation to the Database Schema

Note:

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

Before you run the BRM database upgrade script, verify that the Oracle Data Manager (DM) is configured correctly as this DM provides the interface to the BRM 16.26.0 database. The Oracle DM should point to the BRM 16.26.0 database in which you imported your BRM 12.0 backup data, as described in "Importing Your BRM 15.x Data".

Verify that Oracle DM is configured properly by starting dm_oracle. You should ensure that Oracle DM starts and stops correctly because upgrade scripts start and stop Oracle DM while making changes to the database schema.

Upgrading the BRM Database Schema to the New Version

Note:

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

To upgrade the BRM 15.x database schema to a BRM 16.26.0 database schema, complete one of the following:

Upgrading the Schema on Single-Schema Systems

To upgrade the BRM schema on single-schema systems:

  1. Grant 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. Edit the BRM_home/setup/scripts/pin_setup.values file and ensure that the following values are set: 

    $SETUP_INIT_DB=YES
$SETUP_DROP_ALL_TABLES=NO
$CREATE_DATABASE_TABLES=NO

    Also set or verify the following values:

    • (Optional) Set PIN_TEMP_DIR to the directory in which you want to create the temporary files. Ensure that the directory is set with full write permissions.

    • (Optional) Set PIN_LOG_DIR to the directory in which you want to create the BRM log files.

    • Validate the other information in the file, especially the information about the database.

  3. Save and close the file.

  4. Run the source command on the source.me file:

    • For Bash Shell:

      source source.me.sh

    • For C shell:

      source source.me.csh

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

    Note:

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

    • Ensure that the WALLET_FILE_STORAGE_T table is present in the database before running this script.

    perl script

    where script is pin_upgrade_16.pl for BRM 16.26.0.0.

    Note:

    Do not press any button until the command prompt asks for the BRM wallet password in the next step. Otherwise, the script will consider whatever key you have pressed to be the BRM wallet password.

  6. At the "Enter Password for the wallet" prompt, enter the BRM client wallet password (which should be the same for both 15.x and 16.26.0) and wait for the script to finish.

  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, you upgrade the primary database schema and then the secondary database schemas.

To upgrade the primary database schema, perform the tasks in "Upgrading the Schema on Single-Schema Systems" on your primary schema.

To upgrade each secondary database schema, perform the following on each secondary BRM installation system:

  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. Before you upgrade the secondary schema, set the BRM_WALLET environment variable to the BRM wallet in the primary schema:

    setenv BRM_WALLET BRM_home/wallet/config

  3. Perform the tasks in "Upgrading the Schema on Single-Schema Systems" on your secondary schema.

To configure your entire multischema system, perform the following on the appropriate BRM instances:

  1. On the primary BRM instance, edit the BRM_home/apps/multi_db/config_dist.conf file and 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, using the correct schema names for your environment:

    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" ;

  2. On the primary BRM instance, edit the CM pin.conf file to include the following entries for each secondary dm-oracle application: 

    - cm dm_pointer db_no ip multiSecHost multiSecPort
- cm dm_attributes db_no scoped,assign_account_obj,searchable

    where:

    • db_no is the database number of the secondary schema, for example 0.0.0.2.

    • multiSecHost is the host name or IP address of the secondary system.

    • multiSecPort is the port number on the secondary system.

    For example:

    - cm dm_pointer 0.0.0.2 ip cagbu-phx-772.snphxprshared1.gbucdsint02phx.oraclevcn.com 33624
- cm dm_attributes 0.0.0.2 scoped,assign_account_obj,searchable

  3. In the primary dm-oracle pin.conf file, add the following entry for each secondary dm-oracle application: 

    - dm schema db_no SecondarypinDBUser

    where SecondarypinDBUser is the pin user for the secondary system.

    For example:

    - dm schema 0.0.0.2 pin2124m2

  4. Ensure that the DM pin.conf file on each secondary BRM instance has the following entry: 

    - dm schema 0.0.0.1 prim_owner

    where prim_owner is the owner of the primary database.

  5. Stop and restart all of the services on the primary BRM instance and all secondary instances.

  6. On the primary BRM instance, connect to SQL*Plus and run the following scripts:

    @create_procedures_character_set.plb
grant_permissions_oracle.plb
grant_permissions('sec_owner')
    where:

    • character_set specifies the database character set, either UTF8 or AL32UTF8.

    • sec_owner is the owner of the secondary schema.

    Run the last command for the owner of each secondary schema.

  7. On each secondary BRM instance, connect to SQL*Plus and run the following scripts:

    @create_procedures_character_set.plb
grant_permissions_oracle.plb
grant_permissions('prim_owner')
    where:

    • character_set specifies the database character set, either UTF8 or AL32UTF8.

    • prim_owner is the owner of the primary schema.

  8. On the primary BRM instance, do the following for each secondary schema:

    1. Edit the BRM_home/sys/dd/data/device_framework_primary_schema_75ps4.sql script and update all instances of SEC_SCHEMA_NAME to the name of the secondary database schema owner.

    2. Connect to the primary database schema and run the edited script in SQL*Plus.

  9. On each secondary BRM instance, connect to the secondary database schema and run the BRM_home/sys/dd/data/device_framework_secondary_schema_75ps4.sql script in SQL*Plus.

Upgrading the Pipeline Manager Database Schema to the New Version

Note:

Run the database upgrade script on the primary schema and then on the secondary schemas.

To upgrade the Pipeline Manager database schema:

  1. Create a temporary directory for use during the upgrade by going to Pipeline_home/upgrade and creating the Pipeline_home/upgrade/tmp directory.

  2. Update the Pipeline_home/upgrade/pipeline_upgrade.cfg file and set the following values: 

    $PIN_TEMP_DIR = "temp_path"
$MAIN_DB{'user'} = "db_user";
$PIPELINE_TBLSPACE = "tablespace pipeline_tablespace";
    where:

    • temp_path is the directory you just created.

    • db_user is the primary database user.

    • pipeline_tablespace is the tablespace containing pipeline data.

    Ensure that you also update the database information as appropriate.

  3. Grant the required access to the user pin on the Pipeline Manager tables and sequences, if you have not already done so. See "Loading the Tailor-Made Stored Procedure" for more information about the Pipeline Manager tables and sequences that you should grant user pin access to.

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

    Note:

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

    • Ensure that the WALLET_FILE_STORAGE_T table is present in the database before running this script.

    perl script

    where script is pin_upgrade_16.pl for BRM 16.26.0.

    This script runs a series of scripts that upgrade Pipeline Manager data from 15.x to 16.26.0. The log files will be located in the temporary directory you created.

  5. In SQL*Plus, run the Pipeline_home/database/Oracle/Scripts/create_pricing_discountmodel_procedures.plb script in the Pipeline schema.

Installing the BRM 16.26.0 Client Applications

When you install client applications, be sure to update the BRM 16.26.0 Infranet.properties and INI files with any 16.26.0 customizations. See "Installing BRM Thick Clients" for more instructions.

Note:

You must upgrade all existing client applications and optional components to BRM 16.26.0 before you install additional client applications and optional components in BRM 16.26.0.

To upgrade custom client applications, recompile them with BRM 16.26.0 libraries. See "Updating Custom Applications" for more information.

Adding Optional Components

At this point, add the optional components that you plan to use in the new version of BRM. See "Installing Individual BRM Components" for instructions.

Note:

Before you install a new optional component, in case you changed the database password after the previous installation, ensure that the database password is the same in all configuration entries in the Oracle wallet. To change the database password in the configuration entries, see "About Oracle Wallet" in BRM System Administrator's Guide for more information.

Updating Configurations

Complete the steps in this section that are appropriate for your new BRM environment.

Update the Default Settings for the pin_rel Utility

If you use Rated Event (RE) Loader, ensure that the database configuration settings are updated.

To update the default settings for the pin_rel utility:

  1. Go to the BRM_home/apps/pin_rel directory.

  2. Open the Infranet.properties file.

  3. Check and, if necessary, update the entries for the following:

    infranet.rel.dbname = DATABASE_NAME
infranet.rel.userid = USERNAME

  4. Save and close the file.

Updating the Settings for the pin_virtual_time Utility

If you are testing the upgrade on a test system, ensure that you uncomment all entries for the pin_virtual_time utility in the configuration files associated with your BRM test system.

If you are upgrading your production system, ensure that you remove all entries for the pin_virtual_time utility from the configuration files associated with your BRM production system.

Upgrading AMM in a Multischema System

If you have a multischema system and it includes Account Migration Manager (AMM), run the AMM installation scripts to upgrade your multischema system.

To upgrade AMM in a multischema system:

  1. Log in as user pin and go to the BRM_home/setup/scripts directory.

  2. Run the pin_amt_install script: 

    perl pin_amt_install.pl

Restoring Customizations

Note:

You must first incorporate customizations on the primary schema and then on the secondary schemas.

Incorporate any customizations you made to your Release 12.0 policy source code, configuration files, invoicing, reports, and general ledger reporting. See "Transferring Customizations to the New Release" for more information.

Post-Upgrade Procedures for the New Release

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

  1. Create large indexes. See "Creating Large Indexes" for instructions.

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

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

  4. If you intend to migrate legacy account information into BRM, run a database script to prepare. See "Preparing to Migrate Legacy Account Data" for instructions.

Creating Large Indexes

For performance reasons, you must create some indexes manually after the upgrade.

To create the indexes in the default tablespace, use the following commands: 

CREATE INDEX i_purchased_discount_acc_obj__id ON purchased_discount_t (account_obj_id0);
CREATE INDEX i_purchased_product_acc_obj__id ON purchased_product_t (account_obj_id0);
CREATE UNIQUE INDEX i_billinfo_id_code__id ON billinfo_t (identification_code);
CREATE INDEX i_event_rerate_obj__id ON event_t (rerate_obj_id0);

To create the indexes in another tablespace (for example, the index tablespace), use the following commands:

CREATE INDEX i_purchased_discount_acc_obj__id ON purchased_discount_t (account_obj_id0) tablespace tablespace_name;
CREATE INDEX i_purchased_product_acc_obj__id ON purchased_product_t (account_obj_id0) tablespace tablespace_name;
CREATE UNIQUE INDEX i_billinfo_id_code__id ON billinfo_t (identification_code) tablespace tablespace_name;
CREATE INDEX i_event_rerate_obj__id ON event_t (rerate_obj_id0) tablespace tablespace_name;

where tablespace_name is the name of the tablespace that should contain the indexes.

Configuring SSL for the BRM Database

You can configure secure sockets layer (SSL) for the BRM database by creating wallets for storing certificates and then modifying the following configuration files in the Oracle_home/network/admin directory, where Oracle_home is the directory in which the Oracle database is installed, to point to the appropriate wallet:

  • sqlnet.ora

  • tnsnames.ora

  • listener.ora

You can use the Orapki utility to create the wallets.

For information about configuring SSL for the Oracle database, see the Oracle Database documentation.

Removing Invalid Objects from the Database

After installing the new version of BRM, run the create_procedures script to remove any invalid objects in the BRM database.

In a multischema system, perform this task on the primary Oracle DM machine.

To run the create_procedures script:

  1. Go to the BRM_home/sys/dm_oracle/data directory.

  2. Run the following command, which opens SQL*Plus:

    sqlplus login@ORACLE_SID
Enter password: password

    where:

    • login is the user name for the BRM database schema.

    • password is the password for the specified user name.

    • ORACLE_SID is the database alias of the BRM database schema.

  3. Run the following command:

    @create_procedures_character_set.plb

    where character_set specifies the database character set of either UTF8 or AL32UTF8.

Preparing to Migrate Legacy Account Data

Note:

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

If you intend to migrate legacy account information into BRM:

  1. Go to the BRM_home/sys/dd/data directory.

  2. Open SQL*Plus as the BRM database user.

  3. Run this command:

    SQL> @update_due_amount_oracle.sql