Although the Oracle Communications Billing and Revenue Management (BRM) system is designed for trouble-free installation, you might encounter a problem. This chapter lists some problems other customers have encountered and describes their solutions.
For more information, see "Reference Guide to BRM Error Codes" and "Resolving Problems in Your BRM System" in BRM System Administrator's Guide.
For more information on errors that can occur when installing your database, see your database documentation.
When you try to start the Oracle Listener, you get a ”permission denied” error.
If you have a problem installing the BRM software or its optional components, first check the pin_setup.log file, and then the Data Manager (DM) and Connection Manager (CM) log files for possible reasons for the failure.
The pin_setup script fails when it tries to start the Connection Manager (CM) or Data Manager (DM).
The manager cannot find the dld.so (HP-UX IA64) file, because the CM or DM host computer is missing the necessary C++ libraries.
Install C++ runtime libraries on the computer that will run the System Manager, and reinstall BRM. See "Overview of Hardware and Software Requirements".
BRM installation fails, and you receive the following error:
ORA-07279: spcre: semget error, unable to get first semaphore set. HP-UX Error: 28: No space left on device Additional information: 1
The database host server doesn't have sufficient shared memory to perform the installation.
Set the kernel SEMMNI, SEMMNS, and SEMMAP parameters to the following values:
SEMMNI = 1000 SEMMNS = 1000 SEMMAP = 1002
Note:
If multiple applications are running on the host computer, increase the values in these parameters to handle the most demanding application's semaphore requirements.You receive the error ”An error occurred during the move data process -132.”
After you install BRM and while running the pin_setup script of BRM, when the Oracle DM starts, errors are recorded in the dm_oracle.pinlog file.
Conflicting settings in the pin_setup.values configuration file often cause database connection failures.
The pin_setup script cannot connect to the database, and the error message in the DM log file shows that the DM is trying to connect to the incorrect database.
The pin_setup script cannot log in to the BRM database. The error message indicates an invalid user name or password.
The $MAIN_DB{'user'} and $MAIN_DB{'password'} entries in the pin_setup.values file do not specify the correct user name and password for the BRM database. The default BRM user name and password is pin.
First, verify that you can connect to the BRM database by using the user name and password you want. If you cannot connect:
Use SQL statements to set up the user and password for the BRM database.
Enter the correct user name and password for the BRM database in the $MAIN_DB{'user'} and $MAIN_DB{'password'} entries in the pin_setup.values file.
Re-run the pin_setup script.
The pin_setup script cannot start the DM, and the DM's error log file refers to ”bad shmget”, ”bad shmat”, or another error related to memory.
Use the HP-UX SAM utility to increase the SEMMNI, SEMMNS, or SEMMAP values. For example:
SEMMNI = 1000 SEMMNS = 1000 SEMMAP = 1002
Note:
If multiple applications are running on the host computer, increase these values based on each application's shared memory requirements.Increase the shared memory value in the /etc/system file. For example, type the following in a text editor, such as vi:
set shmsys:shminfo_shmmax=4294967295
Increase the shared memory value in the /etc/sysctl.conf file. Type the following in a text editor:
Log on as root.
Open the /etc/sysctl.conf file.
Add the following lines to the end of the file, or modify the values if these lines are already present:
kernel.shmmax = 536870912 kernel.shmall = 536870912
Run sysctl -p from the unix prompt.