Applying Patches to a Geographic Edition System

Observe the following guidelines and requirements to patch Geographic Edition 3.3 software:

• You must run the same patch levels for Oracle Solaris Cluster software and the common agent container software on all nodes of the same cluster.

• Within a cluster, the patch level for each node on which you have installed Geographic Edition software must meet the Oracle Solaris Cluster 3.3 patch-level requirements.

• All nodes in the same cluster must have the same version of Geographic Edition software and the same patch level. However, primary and secondary clusters can run different versions of Geographic Edition software, provided that each version of Geographic Edition is correctly patched and the versions are no more than one release different.

• To ensure that the patches have been installed properly, install the patches on your secondary cluster before you install the patches on the primary cluster.

• For additional information about Geographic Edition patches, see the patch README file.

• See Oracle Solaris Cluster Geographic Edition 3.3 Release Notes for a list of required patches.

How to Prepare an Geographic Edition System for Patches

1. Ensure that the cluster is functioning properly.

   To view the current status of the cluster, run the following command from any node:

   % cluster status

   See the cluster(1CL) man page for more information.

   Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.

2. Become superuser on a node of the global cluster.
3. Remove all application resource groups from protection groups.

   This step ensures that resource groups are not stopped when you later stop the protection groups.

   # geopg remove-resource-group resourcegroup protectiongroup

   See the geopg(1M) man page for more information.

4. Perform the preceding steps on all clusters that have a partnership with this cluster.
5. Stop all protection groups that are active on the cluster.

   # geopg stop -e local protectiongroup

   See the geopg(1M) man page for more information.

6. Stop the Geographic Edition infrastructure.

   # geoadm stop

   Shutting down the infrastructure ensures that a patch installation on one cluster does not affect the other cluster in the partnership.

   See the geoadm(1M) man page for more information.

7. On each node, stop the common agent container.

   # /usr/sbin/cacaoadm stop

Next Steps

Install the required patches for the Geographic Edition software. Go to How to Install Patches on an Geographic Edition System.

How to Install Patches on an Geographic Edition System

Perform this procedure on all nodes of the cluster.

Patch the secondary cluster before you patch the primary cluster, to permit testing.

Before You Begin

Perform the following tasks:

• Ensure that the Solaris OS is installed to support Geographic Edition software.

  If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Geographic Edition software and any other software that you intend to install on the cluster.

• Ensure that Geographic Edition software packages are installed on the node.

• Ensure that you completed all steps in How to Prepare an Geographic Edition System for Patches.

1. Ensure that all the nodes are online and part of the cluster.

   To view the current status of the cluster, run the following command from any node:

   % cluster status

   See the cluster(1CL) man page for more information.

   Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.

2. Become superuser in the global zone of a node.
3. Install any necessary patches to support Geographic Edition software by using the patchadd command.

   If you are applying Oracle Solaris Cluster patches, use the Oracle Solaris Cluster methods on both clusters.

4. Repeat Step 2 and Step 3 on each remaining node.
5. After you have installed all required patches on all nodes of the cluster, on each node of the global cluster or zone cluster that you are configuring with Geographic Edition, start the common agent container.

   # /usr/sbin/cacaoadm start

6. On one node, enable Geographic Edition software.

   # geoadm start

7. Add all application resource groups that you removed while you were preparing the cluster for a patch installation back to the protection group.

   # geopg add-resource-group resourcegroup protectiongroup

   See the geopg(1M) man page for more information.

8. Start all the protection groups that you have added.

   # geopg start -e local [-n] protectiongroup

   See the geopg(1M) man page for more information.

Next Steps

After you patch the secondary cluster, perform a sanity test on the Geographic Edition software, and then repeat this procedure on the primary cluster.