Upgrade

The Upgrade menu choice is only available on the NOAM. It includes server, Server Group (SG) and Entire Site (ES) options. in this context, site refers to this grouping (SO SG plus all replication children MP SGs). This additional automation prevents having to initiate a server group upgrade on the SO group followed by additional form submissions for each MP group.

Note:

In this context, site refers to the topological grouping of the SO SG and all its replication children MP SGs, regardless of geographic location of the servers. For example, the site upgrade includes a spare SOAM which is a member of SO SG, but is in another geographic location.

Use the Upgrade page to perform software upgrades and related functions on in-service servers in a network. In addition to initiating and accepting upgrades, this page provides to ability to perform backups, health checks (checkups), and reporting. Upgrade functionality is available on a server, SG, or site basis and supports pause, restart, and cancellation functionality.

There are several situations where the SG or site upgrade task automatically pauses or stops itself to allow you to perform recovery actions. You can then restart or cancel the overall upgrade. It is also possible to restart SG or site upgrade on a partially upgraded SG or site. When an SG or Site upgrade is paused or canceled, any currently running upgrades (from a TPD standpoint) continue until they complete or fail. Servers that are in the Pending state are not started.

SG upgrades automatically pause in the following situations:

• A server upgrade fails.
• A response of false from canServerUpgrade() function is received when the server requires an upgrade pre-check.
• A server upgrade is cancelled after being hung.

A SG upgrade can be ended by cancelling the SG upgrade from the Status & Manage > Tasks > Active Tasks page. The SG upgrade can then be restarted using the Administration > Software Management > Upgrade page. A site upgrade can be ended by cancelling the site upgrade from the Status & Manage > Tasks > Active Tasks page. The site upgrade can then be restarted using the Administration > Software Management > Upgrade page.

The server group upgrade provides the ability to upgrade all servers in a server group by filling out a form with options such as Mode and Availability, selecting an ISO, and clicking OK to initiate the upgrades. From that point, long running tasks on the NOAMP manage the upgrade of each server in the group, ensuring that enough servers in the group remain active to handle ongoing system management and subscriber traffic. While the servers are upgrading, you can view the progress of each server's upgrade. You can start an automated server group upgrade on multiple server groups with additional GUI actions.

Note:

The instructions in this section provide a generic framework for upgrades. You should always defer to the application specific upgrade instructions based on each release.

Caution:

We recommend you 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).