Working with Health Checks
System-level health checks are provided to help ensure that no pathologies interfere with the
software update. If a problem is encountered, it is noted in the Alert Log and the update process
is aborted. System software updates do not proceed until all problems have been corrected.
You can manually run the same health checks in advance of any planned update. This allows
you to check the state of the system prior to scheduling an update maintenance window so you
can correct any problems that could interfere with the update process. Any problem report that
is issued by a manual health check is identical to that issued by the health checks integrated
in the update process. As with the integrated health checks, you are presented with a link to
the Alert Log, as described in “Alert Log Entries” on page 38, when problems are found. If
no problems are found, the System Ready state transitions to Yes to indicate that the system is
ready for software updates.
Note - Running an update health check does not replace meeting required preconditions.
Precondition checks, described in “Preparing to Upgrade the Software” on page 321, must also
be executed and problems resolved prior to upgrading the system software.
Checking System Health (BUI)
Use the following procedure to check system health using the BUI.
1.
After you select and start an update, update health checks may be issued from
the Apply Software Update dialog box in the BUI by clicking Check. The system
remains in the Unchecked state until the Check button is clicked.
Working with Health Checks 337
To Next Page
Loading...
Need help?
General