|Oracle® Communications Billing and Revenue Management System Administrator's Guide
|PDF · Mobi · ePub|
If you did not enable event table partitioning when you installed Oracle Communications Billing and Revenue Management (BRM), follow the procedures in this chapter to upgrade from a nonpartitioned BRM database to a partitioned BRM database.
Note:Partitioning is available for Oracle databases only.
This chapter covers Oracle on UNIX (HP-UX, AIX, Linux, and Solaris) platform.
Before partitioning your event tables, read the following:
The nonpartitioning-to-partitioning upgrade splits event tables in an Oracle database into the following partitions:
partition_migrate: Holds all event objects created before the nonpartitioning-to-partitioning upgrade.
partition_historic: Holds nonpurgeable events created after the nonpartitioning-to-partitioning upgrade. Nonpurgeable events should not be purged from the database. See "Event Objects Stored in partition_historic".
partition_last: A spillover partition that is not intended to store event objects you want to purge or preserve. If you do not add purgeable partitions to your event tables before BRM resumes generating events, purgeable events created after the upgrade are stored in this partition.
Note:For information on how partitioning is enabled when you install BRM, see "Partitioning Overview".
Before performing the nonpartitioning-to-partitioning upgrade, you must install:
Third-Party software, which includes the PERL libraries and JRE required for installing BRM components. See "Installing the Third-Party Software" in BRM Installation Guide.
Oracle or Oracle 9i Release 2 with Oracle Partitioning.
To upgrade from a nonpartitioned database to a partitioned database, perform these tasks:
Before adding partitions to your event tables, you must increase the disk space allocated for the event tables and indexes in your BRM database.
Tip:Oracle recommends that you add enough space for 6 to 12 months of event data.
To install the nonpartitioning-to-partitioning upgrade scripts and files, follow the procedure:
Note:If you have already installed the upgrade package, features in that package which are already installed cannot be reinstalled without first uninstalling them. To reinstall a feature, uninstall it and then install it again.
To install the upgrade package:
Download the software to a temporary directory (temp_dir).
If you download to a Windows workstation, use FTP to copy the .bin file to a temporary directory on your UNIX server.
You must increase the heap size used by the Java Virtual Machine (JVM) before running the installation program to avoid ”Out of Memory” error messages in the log file. See "Increasing Heap Size to Avoid 'Out of Memory' Error Messages" in BRM Installation Guide.
Make sure no users are logged on to BRM.
Go to the directory where the Third-Party package is installed and source the source.me file.
Caution:You must source the source.me file to proceed with installation, otherwise ”suitable JVM not found” and other error messages appear.
Go to temp_dir and enter this command:
where platform is the operating system name.
Note:You can use the -console parameter to run the installation in command-line mode. To use the graphical user interface (GUI) for installation, make sure you have X Windows installed in your computer.
Follow the instructions displayed during installation. The default installation directory for the upgrade package is opt/portal/7.4.
Note:The installation program does not prompt you for the installation directory if BRM or the upgrade package is already installed on the machine and automatically installs the package at the BRM_Home location.
Go to the directory where you installed the upgrade package and source the source.me file:
The nonpartitioning-to-partitioning upgrade configuration file, partition.cfg, controls the parameters of your upgrade. If necessary, change these parameters to meet your business requirements.
To reconfigure the parameters in the partition.cfg file:
Log in as user pin, go to BRM_Home/upgrade/partition, and open the partition.cfg file in a text editor such as vi:
% su - pin % cd BRM_Home/upgrade/partition % vi partition.cfg
Change the default parameters as necessary. For information on each parameter, see the comments in the partition.cfg file.
Copy any customizations from your backed-up pin_setup.values file into the BRM_Home/setup/pin_setup.values file.
Make a complete offline backup of your BRM database, and make sure the backup is completely valid and usable. For more information on performing full database backups, see your database software documentation.
In addition to the backup, use the Oracle export utility to export all BRM tables. This helps you restore individual tables if necessary.
Upgrading from a nonpartitioned database to a partitioned database should take about 30 minutes. The size of your event tables does not affect the speed of this upgrade.
To partition your event tables, run the "partitioning.pl" script:
Run the partitioning.pl script with the -c parameter:
% cd Portal_home/upgrade/partitioning % perl partitioning.pl -c
This creates database objects such as tables, indexes, and stored packages that are required for the upgrade.
Run the partitioning.pl script with the -n parameter:
% perl partitioning.pl -n
This displays the event tables that will be partitioned during the upgrade. To add or delete tables from this list, see "partitioning.pl".
Run the partitioning.pl script with the -a parameter:
% perl partitioning.pl -a
This runs a series of scripts that perform the nonpartitioning-to-partitioning upgrade.
Check the log and pinlog files in the directory specified by the UPGRADE_LOG_DIR parameter in your partition.cfg file (by default, BRM_Home/upgrade/partition/sqllog). These log files show how long each script took to execute and list any errors that occurred.
Important:If any errors are reported, fix them, and run the script again.
Start all BRM processes. For more information, see "Starting and Stopping the BRM System".
Note:The object IDs of events generated in your newly partitioned version of BRM will be larger than the object IDs of events generated in your old, nonpartitioned version of BRM. (Depending on the table, object IDs are stored in either the POID_ID0 field or the OBJ_ID0 field.)
Table 26-1 lists the scripts and files used to upgrade your nonpartitioned BRM database to a partitioned BRM database. These scripts and files are in the BRM_Home/upgrade/partition folder.
Important:To upgrade custom database objects, you might need to create additional SQL scripts. To plug custom scripts into the upgrade, add appropriate SQL file entries to the nonpartitioning-to-partitioning upgrade configuration file, partition.cfg. For more information, see "(Optional) Reconfiguring the Parameters in partition.cfg".
|Script or file||Description|
SQL script that creates the pinlog files.
Configuration file in which you must enter details about the Oracle database configuration before you run the upgrade scripts. All the upgrade Perl scripts parse this file to get the database connection parameters.
Master Perl script for the upgrade process. This script calls other SQL scripts to perform the upgrade.
SQL script that creates the common routines needed for the upgrade.
SQL scripts that implement event table partitioning.
Perl script that performs many miscellaneous upgrade tasks related to the Oracle database.