Oracle Database Oracle Clusterware Installation Guide for HP-UX
Oracle Database Oracle Clusterware Installation Guide for HP-UX
Oracle Database Oracle Clusterware Installation Guide for HP-UX
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Installing an Upgrade On a Subset of Nodes<br />
B-4 <strong>Oracle</strong> <strong>Clusterware</strong> <strong>Installation</strong> <strong>Guide</strong><br />
You can patch the entire cluster, and then run the root.sh patch script in a rolling<br />
fashion to make the patch update active.<br />
4. After you select the nodes you want to upgrade, the Installer installs the patch<br />
software in the existing <strong>Oracle</strong> <strong>Clusterware</strong> home on the local and the remote<br />
subset of nodes you have selected.<br />
OUI prompts you to run the appropriate root script <strong>for</strong> the patchset. The script<br />
starts the <strong>Oracle</strong> <strong>Clusterware</strong> stack on the upgraded subset of nodes. However, it<br />
lists it as an inactive version.<br />
5. After you upgrade the initial node or subset of nodes, repeat steps 1 through 4 <strong>for</strong><br />
each remaining node or subset of nodes until all nodes in the cluster have been<br />
patched, and the new version is the active version.<br />
When all member nodes of the cluster are running the new <strong>Oracle</strong> <strong>Clusterware</strong><br />
release, then the new clusterware becomes the active version. Otherwise, the older<br />
<strong>Oracle</strong> <strong>Clusterware</strong> release is still used.<br />
To list the version of <strong>Oracle</strong> <strong>Clusterware</strong> that is installed on a node, enter the<br />
following command, where CRShome is the <strong>Oracle</strong> <strong>Clusterware</strong> home, and<br />
nodename is the name of the node:<br />
# CRShome/bin/crsctl query crs softwareversion [nodename]<br />
To list the <strong>Oracle</strong> <strong>Clusterware</strong> software version that is running on a node, enter the<br />
following command, where CRShome is the <strong>Oracle</strong> <strong>Clusterware</strong> home:<br />
# CRShome/bin/crsctl query crs activeversion<br />
If you intend to install or upgrade <strong>Oracle</strong> RAC, then you must first complete the<br />
upgrade to <strong>Oracle</strong> <strong>Clusterware</strong> 11g release 1 (11.1) on all cluster member nodes<br />
be<strong>for</strong>e you install the <strong>Oracle</strong> <strong>Database</strong> 11g release 1 (11.1) version of <strong>Oracle</strong> RAC.<br />
6. Check with <strong>Oracle</strong> Support to confirm you have installed any recommended patch<br />
sets, bundle patches or critical patches.<br />
To check <strong>for</strong> the latest recommended patches <strong>for</strong> <strong>Oracle</strong> <strong>Clusterware</strong> and <strong>Oracle</strong><br />
Real Application Clusters, log on to the following site:<br />
https://metalink2.oracle.com<br />
Click Patches & Updates, and click <strong>Oracle</strong> <strong>Database</strong> from the Recommended<br />
Patches list. Provide in<strong>for</strong>mation as prompted.<br />
B.5 Installing an Upgrade On a Subset of Nodes<br />
To upgrade an <strong>Oracle</strong> <strong>Clusterware</strong> release, you must shut down all <strong>Oracle</strong> <strong>Database</strong><br />
instances on the subset of nodes you want to upgrade be<strong>for</strong>e modifying the <strong>Oracle</strong><br />
software. Review the instructions in the release upgrade README document <strong>for</strong><br />
additional instructions specific to the upgrade.<br />
Be<strong>for</strong>e you shut down any processes that are monitored by Enterprise Manager Grid<br />
Control, set a blackout in Grid Control <strong>for</strong> the processes that you intend to shut down.<br />
This is necessary so that the availability records <strong>for</strong> these processes indicate that the<br />
shutdown was planned downtime, rather than an unplanned system outage.<br />
To shut down <strong>Oracle</strong> processes and upgrade a subset of nodes, complete the following<br />
steps: