|Oracle® Communications Billing and Revenue Management Installation Guide
|PDF · Mobi · ePub|
This chapter does the following:
Describes how to configure your Oracle database to work with the Oracle Communications Billing and Revenue Management (BRM) system.
Provides a task list to help you make configuration choices when installing Oracle.
Contains the pre-installation procedures for installing your BRM system.
This chapter is intended for network administrators, technicians, database administrators, and engineers who install and configure the Oracle software for use with BRM. The person installing the software should be familiar with the following topics:
UNIX commands and the UNIX operating system.
Database installation and configuration.
Network Management Systems.
A UNIX text editor, such as vi or vuepad.
You will need the following documents while installing and configuring the Oracle software:
Oracle 10g or Oracle 11g operating system installation documentation.
The current release notes for your Oracle software.
The Oracle Administrator's Guide for instructions on configuring the network.
A UNIX operating system reference guide.
As you install the Oracle software, record the following important information. You will need this information later, when you install BRM.
Host name of the Oracle database server.
IP address of the Oracle database server.
Port number of the Oracle database server.
User login name and password (the BRM defaults are pin and pin).
SID for the BRM database name (the BRM default is pindbhostname).
Oracle database alias/Global Database Name (for example, pindbhostname.BRM.com).
Before installing Oracle on your system, verify the following:
Your system meets the minimum hardware and software requirements.
You have all the software required to run BRM with an Oracle database.
This section explains how to install and configure your Oracle database for BRM.
Note:These lists are not a substitute for the Oracle documentation or the most recent release notes for the database.
Installing Oracle for BRM includes these major tasks:
Install Oracle according to the instructions in the Oracle documentation. When you install the software, pay particular attention to the following requirements.
Install the Oracle Enterprise Edition.
Choose a Customized installation. This option lets you configure Oracle with the AL32UTF8 database character set.
Important:If you installed your database before referring to this document and used the Typical installation option, your database might have been installed with another character set. See "Modifying Your Oracle Database Installation" for information on how to modify your existing database.
To configure discounts in BRM, install the following Oracle components:
Oracle XML DB. For more information, see the Oracle documentation.
Oracle XML Developer's Kit (XDK). For more information, see the Oracle documentation.
Install Oracle JServer as part of the Oracle Database installation.
To partition the event tables in your BRM database, you must install the Oracle Partitioning component. See "Partitioning Database Tables" in BRM System Administrator's Guide.
Create your database by using the Oracle Database Configuration Assistant, which can be started automatically by the Oracle installer or started manually. If you start it manually, choose the Custom option.
Note:BRM 7.5 supports AL32UTF8 as its default character set. It also continues to support the UTF8 character set for backward compatibility. The unicode character set AL32UTF8 is recommended for all new BRM 7.5 deployments.
As you create your database, pay particular attention to the following:
Specify a Global Database Name using the format DatabaseName.DomainName, where DatabaseName is the database name and DomainName is the network domain in which the database is located. For example, pindbhostname.brm.com. Most BRM databases use a DatabaseName of pindbhostname, but you can use another name.
Note:You can modify your machine's default domain name in the $ORACLE_HOME/network/admin/sqlnet.ora file. For information, see your Oracle documentation.
Specify a System Identifier (SID) for your database. For clarity, it should be the same as your Oracle database name. Most BRM databases are named pindbhostname, but you can use another name.
Set the Character Set to AL32UTF8.
Set the National Character Set to AL16UTF16.
For detailed instructions on how to create your database, see the Oracle documentation.
Set the 64-bit environment variables as shown in Table 5-1:
You have the option to configure your database manually or let the BRM installer configure your database automatically. Set up your database using one of the following options:
The BRM installer provides the option to automatically configure your database for demonstration or development systems. The installer configures your database by creating one data, one index, and one temporary tablespace; creating the BRM user; and granting connection privileges to the BRM user. If you want the BRM installer to configure your database, your Oracle installation is complete and you can go directly to "Installing BRM".
To configure your database so that it uses additional or larger tablespaces than those created automatically by the BRM installer, you must perform these general tasks:
For a simple demonstration BRM system, you must create a minimum of three tablespaces for BRM. The following section shows the steps required to create the following tablespaces:
pin00 (for data)
pinx00 (for indexes)
PINTEMP (for a temporary tablespace)
To create your tablespaces:
Create a directory for the tablespaces, such as /u02/oradata/pindb.
This directory is referred to as table_location.
Connect to the Oracle database with SQL*Plus:
% sqlplus system/manager@DatabaseAlias
Create the data, index, and temporary tablespaces, making sure:
Data tablespaces are at least 600 MB with an extent (”next”) size of 64 KB.
Index tablespaces are at least 400 MB with an extent size of 64 KB.
Temporary tablespaces are at least 100 MB with an extent size of 64 KB.
SQL> create tablespace pin00 datafile 'table_location/pin00.dbf' size 600M reuse autoextend on default storage( initial 64K next 64K pctincrease 0 ); Tablespace created. SQL> create tablespace pinx00 datafile 'table_location/pinx00.dbf' size 400M reuse autoextend on default storage( initial 64K next 64K pctincrease 0 ); Tablespace created. SQL> create temporary tablespace PINTEMP tempfile 'table_location/PINTEMP.dbf' size 100M reuse autoextend on maxsize unlimited storage(initial 64K next 64K pctincrease 0); Tablespace created.
Create a new BRM user who can access the Oracle database. The Oracle Data Manager (DM) gains access to the Oracle database by using the Oracle user pin. This Oracle user owns all the tables created and used by BRM.
Important:If you are installing a multischema system, the primary and secondary database schemas must not use the same user name. If they do, multischema installation will fail.
Usually, the BRM database is set up at the SQL*Plus command prompt with the user name and password pin, but you can choose another name and password.
Connect to the Oracle database with SQL*Plus:
% sqlplus system/manager@DatabaseAlias
Create the Oracle user pin, grant the user the resource to connect to Oracle with the username pin, and allow pin access to the pin00 and PINTEMP tablespaces:
SQL> create user pin identified by password; User created. SQL> grant resource, connect to pin; Grant succeeded. SQL> alter user pin default tablespace pin00; User altered. SQL> alter user pin temporary tablespace PINTEMP; User altered.
Type exit to exit SQL*Plus.
To create a production system, you must create multiple tablespaces for the BRM data and indexes. For information on how to estimate your database size, create multiple tablespaces, and map the tablespaces to BRM tables, see "Database Configuration and Tuning".
If you are installing your Oracle database and Oracle DM on separate machines, you must perform the following on the machine containing the Oracle DM:
Install the Oracle database client.
Important:For BRM installation to be successful:
Install an Oracle 10g database client if you have an Oracle 10g or Oracle 11g database server. An Oracle 11g database client must be used with an Oracle 11g database server.
Install the 32-bit version and 64-bit version of the Oracle database client.
Modify the $ORACLE_HOME/network/admin/tnsnames.ora file to include entries for connecting to your BRM database.
Use SQL*Plus to ensure that you can connect to your database.
For information, see the Oracle documentation.
If you installed your Oracle database before referring to this document and accepted the default options, your database installation might have defaulted to an unsupported character set. If this occurred, you must move your data to a database installation that supports the AL32UTF8 or the UTF8 character set. By default, BRM 7.5 uses the AL32UTF8 character set.
Caution:After you create a database, you cannot change the character set.
To export your existing data to a database installation that supports the AL32UTF8 character set:
Back up your existing database. See your Oracle documentation for details.
Uninstall your existing database. See your Oracle documentation for details.
Create a new Oracle database that supports the AL32UTF8 character set.
Use the Oracle Import utility to import your existing data to the new database.
See your Oracle documentation for more information.
Now that you have installed the database server software, you can install the BRM Server and client applications. See "Installing BRM" and "Installing BRM Client and Server Applications on UNIX".