Gprs Pin_setup Is Getting Errors Saying Tables Already Exist

(Doc ID 758971.1)

Last updated on JULY 27, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.0]
Information in this document applies to any platform.
This problem can occur on any platform.


On Oracle Communications Billing and Revenue Management(BRM), version, while running the GPRS pin_setup, it throws errors saying 'Tables already exist'.

This error occurs during pin_setup for GPRS when GSM is installed first and GPRS is installed afterwards. This occurs after a migration to V7.3

Steps To Reproduce:

(a) Install 7.3_GPRS_Mgr_30_hpux_32_opt.bin.
(b) Install 7.3_GPRS_20_30_OraUpg_hpux_32_opt.bin.
(c) Run upgrade scripts.
(d) Run pin_setup.
(e) Install 7.3_GSM_Mgr_hpux_32_opt.bin.
(f) Install 7.3_GSM_10_20_OraUpg_hpux_32_opt.bin.
(g) Run upgrade scripts.
(h) Run pin_setup.

Here the 'pin_setup' fails saying that tables already exist. The tables are added by upgrade scripts. The "$CREATE_DATABASE_TABLES" option is set to "No" in pin_setup.values. The loading of config files is also failing as the config files don't have absolute path in the scripts. This happens for both GPRS as well as GSM pin_setup.

For example:

GSM: $PIN_HOME/bin/load_pin_telco_tags -dv $PIN_HOME/sys/data/config/pin_telco_tags
GPRS: $PIN_HOME/bin/load_pin_telco_tags -d -v $PIN_HOME/sys/data/config/pin_telco_tags_gprs


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms