Observe the following requirements and software-support guidelines when you update to the Oracle Solaris Cluster 4.4 software:
Minimum Oracle Solaris OS – Oracle Solaris 11.4 is the minimum required to support Oracle Solaris Cluster 4.4 software.
Supported Oracle Solaris bundled applications – Confirm your application is supported in Oracle Solaris 11.4, see Chapter 2, Compatibility Notes in Oracle Solaris Cluster 4.4 Release Notes.
Update paths – Oracle Solaris Cluster 4.4 software supports the following direct update paths:
Update from at least version 4.3 – Use the standard, dual-partition method, or rolling method.
Supported hardware – The cluster hardware must be a supported configuration for Oracle Solaris Cluster 4.4 software. Contact your Oracle representative for information about current supported Oracle Solaris Cluster configurations.
Architecture changes during update – Oracle Solaris Cluster 4.4 software does not support update between architectures.
Software migration – Do not migrate from one type of software product to another product during Oracle Solaris Cluster update. Perform only software configuration changes that are specified by update procedures of an installed software product.
Updating to compatible versions – You must update all software on the cluster nodes to a version that is supported by Oracle Solaris Cluster 4.4 software. For example, if an application version is supported on Oracle Solaris Cluster 4.3 software but is not supported on Oracle Solaris Cluster 4.4 software, you must update to an application version that is supported on Oracle Solaris Cluster 4.4 software, if such a version of the application exists. See the Oracle Solaris Cluster 4 Compatibility Guide (http://www.oracle.com/technetwork/server-storage/solaris-cluster/overview/solariscluster4-compatibilityguide-1429037.pdf) for information about supported products.
Identical updates for all nodes – All cluster member nodes must have the same updates applied for proper cluster operation.
Migration from Oracle Solaris 10 – You can alternatively migrate Oracle Solaris Cluster 3.3 software running on the Oracle Solaris 10 OS to a solaris10 brand zone cluster. On a global cluster that already runs Oracle Solaris Cluster 4.4 software on Oracle Solaris 11 software, create a new solaris10 brand zone cluster. Then migrate to the zone cluster your Oracle Solaris Cluster 3.3 configuration and applications. See Chapter 6, Creating Zone Clusters in Installing and Configuring an Oracle Solaris Cluster 4.4 Environment and Creating the Image for Directly Migrating Oracle Solaris 10 Systems Into Zones in Creating and Using Oracle Solaris 10 Zones.
Zone cluster update – To update the Oracle Solaris OS or Oracle Solaris Cluster software that is running in a zone cluster, you must update the underlying global cluster. Do not attempt to update the OS or cluster software directly in the zone cluster. It is required that the cluster software version on the global cluster be the same as the cluster software version in the zone cluster.
If the upgrade is a rolling upgrade from Oracle Solaris Cluster 4.3 to Oracle Solaris Cluster 4.4 and the zone cluster has the resource of SUNW.rac_framework type, a special upgrade preparation procedure is required.
On one Oracle Solaris Cluster 4.3 cluster node, in the global zone run the following command for each zone cluster configured:
schost# /usr/cluster/lib/sc/ccradm addkey -Z <ZoneClusterName> \ -v 1 -k "cluster.properties.cmm_version" infrastructure
Without this preparation, the node rebooted into Oracle Solaris Cluster 4.4 will have its zone cluster node join the zone cluster but the zone cluster UCMM process then gets stuck in step10 state (instead of reaching the end state). This causes the RAC framework resource to reach its default (5 minute) start method timeout and go into the start_failed state. If the cluster is in this situation, just perform the step above in a node still running Oracle Solaris Cluster 4.3 and reboot the zone cluster node on the node running Oracle Solaris Cluster 4.4.
Failover zone update – You can update failover zones only when using the standard update or rolling update method. You cannot update failover zones if you are using the dual-partition update method.
Downgrade – Oracle Solaris Cluster 4.4 software does not support any downgrade of Oracle Solaris Cluster software.
Limitation of scinstall for data-service updates – The scinstall update utility only updates those data services that are provided with Oracle Solaris Cluster 4.4 software. You must manually update any custom or third-party data services, unless they also have IPS packages and later versions are available in their publisher.
Unique zpool names – zpool name must not be same as a cluster device group name. zpools managed by HAStoragePlus and an Oracle Solaris Cluster device group (e.g. device group of type SVM or type Disk) in the same cluster must not have the same name. Before you update, rename Oracle Solaris Cluster device group name or zpool name.
ORCL.ha-zone_sczbt, ORCL.ha-zone_sczsh, or ORCL.ha-zone_sczsmf resource updates –
When the cluster that you are updating is running resources of type ORCL.ha-zone_sczbt, ORCL.ha-zone_sczsh or ORCL.ha-zone_sczsmf, you must upgrade to Oracle Solaris Cluster 4.3 SRU 4 or later and specifically implement note 14 from the OSC 4.3 SRU4 README before you update to Oracle Solaris Cluster 4.4. See (https://support.oracle.com/rs?type=doc&id=2170110.1Doc ID 2170110.1), and Migration of Resources Registered as ORCL.ha-zone_sczbt, ORCL.ha-zone_sczsh or ORCL.ha-zone_sczsmf to the Latest Resource Type Version (21926061) in Oracle Solaris Cluster 4.4 Release Notes.
HA-LDOMS resource updates–
For resources registered as SUNW.ldom, before upgrading to Oracle Solaris Cluster 4.4, you must upgrade to Oracle Solaris Cluster 4.3 SRU 4 or later and specifically implement note 17 from the Oracle Solaris Cluster 4.3 SRU4 README (Doc ID 2170110.1) and HA-LDOMs Resources Must Update to 4.3 before Updating to 4.4 (23308155) in Oracle Solaris Cluster 4.4 Release Notes.
Caution - The /var/cluster.sav/ directory is created and used during current and future Oracle Solaris Cluster installation, update, and uninstallation operations. This directory and its contents are for Oracle Solaris Cluster internal use only, and must not be deleted by the user. User removal of this directory, or any of its contents, would pose a high risk of compromising the cluster during any future installation, update, or uninstallation of Oracle Solaris Cluster software.