The information in this section provides a general overview of the automated site upgrade process. Always refer to the application specific upgrade instructions based on each release.
Follow these general steps when performing an automated site upgrade:
- Upgrade the NO server group serially (one at a time) to ensure at least one NO is always active to provide OAM&P.
- Upgrade the DRNO server group. Note that some products upgrade these first.
- Select an SO network element and upgrade it as follows:
- The SO servers can either be serial or bulk (non-active at once, then active) as specified in General Options.
- Upgrade the MP servers using desired availability settings. The code uses the following rules (some of which can be specified by the user):
- Servers are upgraded in parallel as long as the number of active, non-upgrading servers exceeds the user specified minimum availability.
- Servers can be upgraded serially instead.
- Servers are upgraded in HA order meaning Spare servers followed by Observer, Stby, and Active. An additional application-level customization allows certain servers to be upgraded last, once the rest of their group has upgraded.
- Repeat step 3 until all SO network sites are upgraded (thereby completing upgrade of the entire network).
- Accept the upgrade.
Caution:
Contact
My Oracle Support and inform them of your upgrade plans before beginning this or any upgrade procedure. Before upgrading, go to the
My Oracle Support website to acquire the correct upgrade procedure for your
product and review any relevant Technical Service Bulletins (TSBs).
