Skip Headers
Oracle® Communications Billing and Revenue Management System Administrator's Guide
Release 7.5

E16719-12
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

30 Multischema Utilities

This chapter provides reference information for Oracle Communications Billing and Revenue Management (BRM) multischema utilities.

load_config_dist

Use this utility to load the configuration/distribution table for database schema priorities into an Oracle Communications Billing and Revenue Management (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.

Location

BRM_Home/bin

Syntax

load_config_dist

Parameters

There are no input parameters for the load_config_dist utility.

Results

The progress of the program is displayed on the screen.

Important:

You must restart the Connection Manager (CM) to make new resources available.

load_pin_uniqueness

Use this utility to update the /uniqueness object in an Oracle Communications Billing and Revenue Management (BRM) multischema system when the object is not synchronized with the /service object in the schema.

Caution:

  • The "pin_multidb" utility calls this utility to create a /uniqueness object from a /service object in a multischema environment; therefore, stop the pin_multidb utility 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.

Location

BRM_Home/bin

Syntax

load_pin_uniqueness

Parameters

There are no input parameters for the load_pin_uniqueness utility.

Results

The progress of the program is displayed on the screen.

Important:

You must restart the CM to make new resources available.

pin_config_distribution

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.

Location

BRM_Home/bin

Syntax

pin_config_distribution

Parameters

There are no input parameters for the pin_config_distribution utility.

Results

The progress of the program is displayed on the screen.

pin_confirm_logins

Use this utility to update the /uniqueness object in the primary Oracle Communications Billing and Revenue Management (BRM) database schema with entries that have been confirmed and to delete logins that are not found.

Note:

If you use dblinks for managing the uniqueness table in a multischema environment, this utility is not required.

Define the frequency for running this utility in the BRM_Home/apps/multiDB/pin_multidb.conf file.

The pin_multidb script with the -f parameter starts pin_confirm_logins, but you can run the command directly if it is terminated or if you need to restart the CM after reconfiguration.

Location

BRM_Home/apps/multiDB

Syntax

pin_confirm_logins 

Parameters

There are no input parameters for the pin_confirm_logins utility.

Results

The progress of the program is displayed on the screen.

pin_mta_monitor

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.

Location

BRM_Home/bin

Syntax

pin_mta_monitor [mta_application]
(mon)> command

Parameters

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.

Commands

Table 30-1 lists the commands that you can enter at the monitor prompt.

Table 30-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.

  • t [+] number adds the specified number of threads to the thread pool of mta_application.

  • t [-] number removes the specified number of threads from the thread pool of mta_application.

?

Displays the pin_mta_monitor utility's commands.

q

Stops monitoring mta_application and exits the utility.


Results

This utility logs messages to stdout.

pin_multidb

Use this script to configure an Oracle Communications Billing and Revenue Management (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, edit the BRM_Home/apps/multiDB/pin_multidb.conf file.

  • Run pin_multidb 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.

Location

BRM_Home/setup/scripts

Syntax

pin_multidb [-i] [-f] [-R all | group] [-r group] [-h]

Parameters

Important:

To fully configure a multischema system, run the utility with -i, and then run it again with -f.
-i

Initializes the primary and secondary schemas.

-f

Finalizes the multischema installation.

-R all | group

-R all: Re-creates all refresh groups.

-R group: Re-creates the specified refresh group, where group can be any of the values listed in Table 30-2:

Table 30-2 -R Group Values

-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.

-r group

Forces a refresh of the specified group of objects, where group can be any of the values listed in Table 30-3:

Table 30-3 -r Group Values

-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.

-h

Displays the syntax and parameters for this utility.

Results

If the pin_multidb script does not notify you that it was successful, check that the data in both schemas are the same, or look in the utility log file (pin_multidb.log) to find any errors. The log file is either in the directory from which the utility was started or in a directory specified in the configuration file.