Database Reference
In-Depth Information
•
libXau-1.0.1
•
libXau-1.0.1 (32 bit)
•
libXi-1.0.1
•
libXi-1.0.1 (32 bit)
•
make-3.81
•
sysstat-7.0.2
Pre-Upgrade Checklist
Every successful deployment needs careful planning and must go through prerequisite verification before upgrading
an Oracle environment. You are therefore advised to work through some of the important pre-upgrade tasks
mentioned in the subsequent sections to ensure a smooth and successful upgrade.
Oracle Software Backups
Before any upgrade, it is essential to have an up-to-date backup copy of the existing Oracle software: GI and RDBMS,
and also the Cluster's critical components (OCR and OLR [Oracle Local Registry]) in order to secure yourself from
any sort of disaster situations that might arise before and after the upgrade. We recommend that you consider the
following backup actions:
Back up your current GI and RDBMS homes, preferably the entire Oracle software filesystem.
Perform a manual physical OCR/OLR backup.
Perform a full Oracle Database backup of the source databases.
Validating Node Readiness
Validating node (server) readiness prior to the upgrade procedure is one of the key steps of a successful upgrade. It is
mandatory to verify all the prerequisites, such as storage, OS kernel parameters, OS patches, etc., on the current nodes
to ensure that they meet the minimal requirements to proceed with the upgrade.
Prerequisite validations can be performed in two ways: with the Cluster verification utility (
runcluvfy.sh
) or
by letting the Oracle Universal Installer (OUI) perform the verification as part of the prerequisite checking during
the upgrade process. The following command demonstrates an example how to use the cluvfy utility to perform the
verification prior to installation of the Clusterware:
./runcluvfy.sh stage -pre crsinst -upgrade -n rac1,rac2 -rolling -fixup-src_crshome
/u01/app/11203/grid -dest_home /u01/app/12.1.0/grid -dest_version12.1.0 -verbose
■
Note
the
runcluvfy.sh
must be executed from the 12c software staging location.
In the event of any validation failures produced by the preceding command, you should fix the issues and
re-execute the command to ensure that all the prerequisite checks have been met.
