Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster 3.3 3/13 |
1. Preparing to Upgrade Oracle Solaris Cluster Software
2. Performing a Standard Upgrade to Oracle Solaris Cluster 3.3 3/13 Software
3. Performing a Dual-Partition Upgrade to Oracle Solaris Cluster 3.3 3/13 Software
4. Performing a Live Upgrade to Oracle Solaris Cluster 3.3 3/13 Software
5. Performing a Rolling Upgrade
How to Commit the Upgraded Cluster to Oracle Solaris Cluster 3.3 3/13 Software
How to Verify Upgrade of Oracle Solaris Cluster 3.3 3/13 Software
How to Finish Upgrade to Oracle Solaris Cluster 3.3 3/13 Software
Before You Begin
Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.
phys-schost# scversions
|
phys-schost# scversions -c
Committing the upgrade enables the cluster to utilize all features in the newer software. New features are available only after you perform the upgrade commitment.
phys-schost# scversions Upgrade commit is NOT needed. All versions match.
Next Steps
Go to How to Verify Upgrade of Oracle Solaris Cluster 3.3 3/13 Software.
Perform this procedure to verify that the cluster is successfully upgraded to Oracle Solaris Cluster 3.3 3/13 software. Perform all steps from the global zone only.
Before You Begin
Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.
Ensure that all steps in How to Commit the Upgraded Cluster to Oracle Solaris Cluster 3.3 3/13 Software are completed successfully.
phys-schost# clnode show-rev -v
The first line of output states which version of Oracle Solaris Cluster software the node is running. This version should match the version that you just upgraded to.
phys-schost# clnode status
See the clnode(1CL) man page for more information about displaying cluster status.
Example 6-1 Verifying Upgrade to Oracle Solaris Cluster 3.3 3/13 Software
The following example shows the commands used to verify upgrade of a two-node cluster to Oracle Solaris Cluster 3.3 3/13 software. The cluster node names are phys-schost-1 and phys-schost-2.
phys-schost# clnode show-rev -v 3.3 … phys-schost# clnode status === Cluster Nodes === --- Node Status --- Node Name Status --------- ------ phys-schost-1 Online phys-schost-2 Online
Next Steps
Go to How to Finish Upgrade to Oracle Solaris Cluster 3.3 3/13 Software.
Perform this procedure to finish Oracle Solaris Cluster upgrade. Perform all steps from the global zone only.
Before You Begin
Ensure that all steps in How to Verify Upgrade of Oracle Solaris Cluster 3.3 3/13 Software are completed.
phys-schost-1# cluster set -p resource_security=SECURE
For more information about this property, see Using the resource_security Property in Oracle Solaris Cluster Data Services Developer’s Guide and the cluster(1CL) man page.
Follow the documentation that accompanies the data services.
You must migrate all resources to the Oracle Solaris Cluster 3.3 3/13 resource-type version to use the new features and bug fixes that are provided in this release.
Note - For HA for SAP Web Application Server, if you are using a J2EE engine resource or a web application server component resource or both, you must delete the resource and recreate it with the new web application server component resource. Changes in the new web application server component resource includes integration of the J2EE functionality. For more information, see Oracle Solaris Cluster Data Service for SAP Web Application Server Guide.
See Upgrading a Resource Type in Oracle Solaris Cluster Data Services Planning and Administration Guide, which contains procedures which use the command line. Alternatively, you can perform the same tasks by using the Resource Group menu of the clsetup utility. The process involves performing the following tasks:
Registering the new resource type.
Migrating the eligible resource to the new version of its resource type.
Modifying the extension properties of the resource type.
Note - The Oracle Solaris Cluster 3.3 3/13 release might introduce new default values for some extension properties. These changes affect the behavior of any existing resource that uses the default values of such properties. If you require the previous default value for a resource, modify the migrated resource to set the property to the previous default value.
phys-schost# clsetup
The clsetup Main Menu is displayed.
The Resource Group Menu is displayed.
Type q to back out of each submenu, or press Ctrl-C.
# clresourcegroup online -eM resourcegroup
# clresourcegroup status # clresource status
# clresourcegroup online -Z zonecluster resource-group # clresource enable -Z zonecluster resource # clresourcegroup online -eM -Z zonecluster resource-group
phys-schost# clresource enable hadb-resource phys-schost# hadbm start database-name
For more information, see the hadbm(1m) man page.
The following example shows the httpd.conf file located on the /global cluster file system.
phys-schost# cat /usr/apache/bin/apchectl | grep HTTPD=/usr HTTPD="/usr/apache/bin/httpd -f /global/web/conf/httpd.conf"
phys-schost# vi /usr/apache/bin/apchectl #HTTPD=/usr/apache/bin/httpd HTTPD="/usr/apache/bin/httpd -f /global/web/conf/httpd.conf"
Specify the number of zone clusters that you expect to configure in the cluster.
phys-schost# cluster set net-props -p num_zoneclusters=N
The command calculates the number of additional private-network IP addresses that are needed and automatically modifies the IP address range.
phys-schost# clsetup
The clsetup Main Menu is displayed.
The Resource Group Menu is displayed.
This step includes the bringing online of resource groups in non-global zones.
Type q to back out of each submenu, or press Ctrl-C.
Also perform this task if you want to configure automatic reboot for the first time.
phys-schost# clnode show
phys-schost# clnode set -p reboot_on_path_failure=enabled node
Specifies the property to set
Specifies that the node will reboot if all monitored disk paths fail, provided that at least one of the disks is accessible from a different node in the cluster.
phys-schost# clnode show === Cluster Nodes === Node Name: node … reboot_on_path_failure: enabled …
See How to Validate the Cluster in Oracle Solaris Cluster Software Installation Guide.
phys-schost# prtvtoc /dev/rdsk/cNtXdYsZ > filename
Store the file in a location outside the cluster. If you make any disk configuration changes, run this command again to capture the changed configuration. If a disk fails and needs replacement, you can use this information to restore the disk partition configuration. For more information, see the prtvtoc(1M) man page.
An archived backup of your cluster configuration facilitates easier recovery of the your cluster configuration,
For more information, see How to Back Up the Cluster Configuration in Oracle Solaris Cluster System Administration Guide.
Troubleshooting
Resource-type migration failure - Normally, you migrate resources to a new resource type while the resource is offline. However, some resources need to be online for a resource-type migration to succeed. If resource-type migration fails for this reason, error messages similar to the following are displayed:
phys-schost - Resource depends on a SUNW.HAStoragePlus type resource that is not online anywhere. (C189917) VALIDATE on resource nfsrs, resource group rg, exited with non-zero exit status. (C720144) Validation of resource nfsrs in resource group rg on node phys-schost failed.
If resource-type migration fails because the resource is offline, use the clsetup utility to re-enable the resource and then bring its related resource group online. Then repeat migration procedures for the resource.
Java binaries location change - If the location of the Java binaries changed during the upgrade of Oracle Solaris software, you might see error messages similar to the following when you attempt to run the cacaoadm start or smcwebserver start commands:
phys-schost# /usr/sbin/cacaoadm startNo suitable Java runtime found. Java 1.5.0_06 or higher is required.Jan 3 17:10:26 ppups3 cacao: No suitable Java runtime found. Java 1.5.0_06 or higher is required.Cannot locate all the dependencies
phys-schost# smcwebserver start/usr/sbin/smcwebserver: /usr/jdk/jdk1.5.0_06/bin/java: not found
These errors are generated because the start commands cannot locate the current location of the Java binaries. The JAVA_HOME property still points to the directory where the previous version of Java was located, but that previous version was removed during upgrade.
To correct this problem, change the setting of JAVA_HOME in the following configuration files to use the current Java directory:
/etc/webconsole/console/config.properties/etc/opt/SUNWcacao/cacao.properties