Can Upgrade Script Be Run from Different Sever which Points to Same DB
(Doc ID 2186461.1)
Last updated on AUGUST 28, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM) 7.5.0 patchset 15 where BRM is installed on 2 nodes (Server-A and Server-B) with both pointing to the same database, what is the recommended approach to patching this deployment?
When PS15 was installed/upgraded on Server-A, it went fine and the system is up and running. The pin.conf changes were made after executing the $PIN_HOME/setup/scripts/pin_75_75ps15_upgrade.pl script.
On Server-B, unless the the same perl script is executed, the new pin.conf changes are not made.
Should the $PIN_HOME/setup/scripts/pin_75_75ps15_upgrade.pl perl script also be run on the second node (Server-B)?
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