This chapter provides reference information for Oracle Communications Billing and Revenue Management (BRM) multischema utilities.
Use this utility to load the configuration/distribution table for database schema priorities into a BRM multischema system. You define the schema priorities in the BRM_home/apps/multi_db/config_dist.conf file.
Note:
You cannot load separate /config/distribution objects for each brand. All brands use the same object.Caution:
You must stop the pin_config_distribution utility before you run the load_config_dist utility.
The load_config_dist utility overwrites the existing schema priorities table. If you are updating schema priorities, you cannot load new priorities only. You must load the complete schema priorities table each time you run the load_config_dist utility.
Important:
To connect to the BRM database, the load_config_dist utility needs a configuration file in the directory from which you run the utility.Use this utility to update the /uniqueness object in a BRM multischema system when the object is not synchronized with the /service object in the schema.
Caution:
The pin_multidb.pl script calls this utility to create a /uniqueness object from a /service object in a multischema environment; therefore, stop the pin_multidb.pl script before you run the load_pin_uniqueness utility.
The load_pin_uniqueness utility overwrites existing /uniqueness objects. If you are updating /uniqueness objects, you cannot load new /uniqueness objects only. You must load complete sets of /uniqueness objects each time you run the load_pin_uniqueness utility.
Important:
To connect to the BRM database, the load_pin_uniqueness utility needs a configuration file in the directory from which you run the utility.Use this utility to update the multischema configuration object (the /config/distribution object). You can update the configuration at regular intervals by running the utility with the cron command.
To run pin_config_distribution directly, edit BRM_home/apps/multi_db/pin.conf and run the command from that directory.
Important:
For multischema systems, you must run the utility separately against each schema in your system.Use this utility to monitor and regulate the thread activity of a BRM multithreaded application (MTA) without interrupting the application. You must start the MTA before you run the pin_mta_monitor utility.
Note:
To connect to the BRM database, pin_mta_monitor uses the configuration file of the MTA that it monitors. For example, if you use pin_mta_monitor to track the thread activity of pin_inv_export, pin_mta_monitor uses the pin.conf file of pin_inv_export. See "Configuring Your Multithreaded Application" in BRM Developer's Guide.You must run pin_mta_monitor from the same directory from which you run the MTA.
This utility runs in an interactive mode. In this mode, you enter single-letter commands to perform individual actions. To run pin_mta_monitor for an MTA, you must be at the monitor ((mon)>) prompt.
Use the following command to enter into the monitor prompt:
pin_mta_monitor [mta_application]
where mta_application is the MTA that pin_mta_monitor tracks.
The (mon)> prompt appears.
Table 31-1 lists the commands that you can enter at the monitor prompt.
Table 31-1 pin_mta_monitor Commands
| Command | Description |
|---|---|
|
p |
Starts monitoring mta_application. The utility prints the thread activity for mta_application to stdout. See the discussion on multithreaded applications in BRM System Administrator's Guide. |
|
t [+|-] number |
Regulates the thread load on your MTA utility, where number specifies the number by which you want to increase or decrease the number of threads that mta_application uses.
|
|
? |
Displays the pin_mta_monitor utility's commands. |
|
q |
Stops monitoring mta_application and exits the utility. |
Use this script to configure a BRM multischema system. You use this script for the initial configuration of a new multischema system and to configure additional secondary schemas when necessary.
Important:
Before running pin_multidb.pl, edit the BRM_home/apps/multiDB/pin_multidb.conf file.
Run pin_multidb.pl on the machine that hosts the CM and Data Manager (DM) of the multischema system.
For more information about installing a multischema BRM system, see "Installing a Multischema System" in BRM Installation Guide.
Important:
To fully configure a multischema system, run the script with -i, and then run it again with -f.Initializes the primary and secondary schemas.
Finalizes the multischema installation.
-R all: Re-creates all refresh groups.
Note:
After you run pin_multidb.pl -R all, run the create_procedures_character_set.plb script and the grant_permissions_oracle.plb script, which sets up the schema qualifications for payment processing, where character_set specifies the database character set of either UTF8 or AL32UTF8.See the discussion about setting up schema qualifications in BRM Installation Guide.
-R group: Re-creates the specified refresh group, where group can be any of the values listed in Table 31-2:
| -R Group Value | Description |
|---|---|
|
CONFIG |
Refreshes configuration objects |
|
PRICE |
Refreshes pricing objects |
|
UNIQUENESS |
Refreshes uniqueness objects |
|
GENERAL |
Refreshes general objects |
The refresh frequencies are specified in the pin_multidb.conf file.
Forces a refresh of the specified group of objects, where group can be any of the values listed in Table 31-3:
| -r Group Value | Description |
|---|---|
|
CONFIG |
Configuration objects |
|
PRICE |
Pricing objects |
|
UNIQUENESS |
Uniqueness objects |
|
GENERAL |
General objects |
The refresh frequencies are specified in the pin_multidb.conf file.
Displays the syntax and parameters for this script.
If the pin_multidb.pl script does not notify you that it was successful, check that the data in both schemas is the same, or look in the log file (pin_multidb.log) to find any errors. The log file is either in the directory from which the script was started or in a directory specified in the configuration file.