Installing Rated Event Loader

2 Installing Rated Event Loader

Learn how to install the Oracle Communications Billing and Revenue Management (BRM) Rated Event Loader (RE Loader) software, which includes the Rated Event Manager (RE Manager) software.

Topics in this chapter:

Installing RE Loader

To install RE Loader and RE Manager, perform the procedures in these sections:

Granting Execute Permission for dbms_lock

Before you install RE Loader, you must grant execute permission to pin_user for dbms_lock:

% sqlplus sys@databaseAlias
Enter password: password

Grant execute privileges to pin_user:

SQL> grant execute on dbms_lock to pin_user

Granting Write Permission to the Data Manager

When you install RE Loader on a system where BRM is not installed, you must grant the Data Manager (DM) write permission before installing RE Loader.

Perform the following on all machines containing a DM:

In a text editor, open your DM configuration file:

BRM_home/sys/dm_oracle/pin.conf

BRM_home is the directory in which you installed BRM components.
Write down the values of your dd_write_enable_fields, dd_write_enable_objects, dd_write_enable_portal_objects, and dd_mark_as_portal entries.
Set the values of the following entries to 1:
```
- dm dd_write_enable_fields 1
- dm dd_write_enable_objects 1
- dm dd_write_enable_portal_objects 1
- dm dd_mark_as_portal 1
```
Note:

If any entry is not in the file, add it.

For more information, see the information in the DM pin.conf file.
Save and close the file.
Stop and restart the DM.

You can now install RE Loader.

Installing the RE Loader Package

To install RE Loader, see "Installing Individual BRM Components" in BRM Installation Guide.

Creating RE Loader Database Partitions

Note:

You must perform this step to ensure that the new event tables have the same partitioning layout as your existing event tables. If you install several optional components, perform this step only after installing the last component.

To create partitions for RE Loader events:

On the system where BRM is installed, go to the BRM_home/apps/partition_utils directory.
Run the partition_utils utility to enable delayed-event partitions:
```
perl partition_utils.pl -o enable -t delayed -c storable_class
```
where storable_class specifies the event classes for which you want partitioning.

Note:

You must create partitions for all subclasses of a specific event that you want to load.

For example, this command creates partitions for /event/delayed/session/telco/gsm delayed events:
```
perl partition_utils.pl -o enable -t delayed -c /event/session/telco/gsm
```

For more information, see:

"Enabling Delayed-Event Partitioning" in BRM System Administrator's Guide
"partition_utils" in BRM System Administrator's Guide.

Your RE Loader installation is now complete.

Returning Data Manager Permissions to their Original Values

To return your DM permissions to their original values:

In a text editor, open your DM configuration file:

BRM_home/sys/dm_oracle/pin.conf
Restore the following entries to their original values (the values they had before you modified them). The default value for each entry is 0:
```
- dm dd_write_enable_fields 
- dm dd_write_enable_objects 
- dm dd_write_enable_portal_objects 
- dm dd_mark_as_portal
```
Save and close the file.
Stop and restart the DM.

Preventing POID Errors in Multischema Systems

BRM multischema systems ensure that all POIDs are unique across all database schemas by using a POID-generation algorithm. This BRM algorithm sets each schema's starting sequence number to a unique value and then increments each sequence number by a set value. By default, BRM sets the increment value equal to the number of schemas in your system.

For example, if your system contains three schemas:

Schema 1 uses a starting sequence number of 10000
Schema 2 uses a starting sequence number of 10001
Schema 3 uses a starting sequence number of 10002

The incremental value is 3.

This example results in the following POID numbers shown in Table 2-1:

Table 2-1 Example Schema POID Numbers

Time	POID for Schema 1	POID for Schema 2	POID for Schema 3
1	10000	10001	10002
2	10003	10004	10005
3	10006	10007	10008

When RE Loader loads a batch of objects into the BRM database, it reserves a group of POIDs as follows:

Changes the increment value by using the following equation:
```
(Number of objects to load) x (Current increment value)
```
For example, if RE Loader must load 2,000 objects into the database and the current increment value is 3, it changes the increment value to 2,000 x 3 = 6,000.
Allocates POIDs to objects.
Returns the increment value to its original value.

However, if a major error occurs during the allocation process, the increment value can remain at the incorrect high value. To catch these situations, you can configure RE Loader to check the database increment value against a specified maximum before it reserves a group of POIDs. When the increment value exceeds the specified maximum, RE Loader exits and logs an error message, notifying your database administrator to manually reset the increment value.

To configure RE Loader to compare the increment value against a specified maximum:

Open the BRM_home/apps/pin_rel/Infranet.properties file in a text editor.
Set the infranet.rel.max_increment_by entry to the number of database schemas in your system:
```
infranet.rel.max_increment_by = 20
```
The default is 20.
Save and close the file.

Uninstalling RE Loader

To uninstall RE Loader, see "Uninstalling Optional Components" in BRM Installation Guide.