My Oracle Support Banner

Error when Installing BRM 7.5 Ps3 on the To-be Secondary Schema of a Multi-schema BRM Instance (Doc ID 1545493.1)

Last updated on MAY 02, 2013

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

When installing BRM 7.5 patch Set 3 (PS3) on multi-schema, what will be the secondary schema of a multi-schema BRM instance. Database number "0.0.0.2" is being used for the DM Oracle. This was asked during PortalBase installation and written in the pin_setup.values.

There is issue when installing PatchSet 3 and during the executing of pin_75ps3_upgrade.pl script. The following .source files in "$PIN_HOME/sys/dd/data have POID DB "0.0.0.1" instead of "$PIN_CONF_DB_NO", like the other ones:

dd_objects_audit_coll_gdtls.source
dd_objects_collections_action.source
dd_objects_config_coll_actions.source
dd_objects_group_coll_targets_mem.source
dd_objects_pipeline_startup.source
update_schema_slm.source

For this reason, when processing those source files listed above, the DM Oracle complains because expects the DB number to be 0.0.0.2 instead of 0.0.0.1 and the execution of "pin_75ps3_upgrade.pl" fails.

Changes

 Installing BRM 7.5 PS3/

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.