Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster 3.3 5/11 Release Notes Oracle Solaris Cluster |
Oracle Solaris Cluster 3.3 5/11 Release Notes
What's New in the Oracle Solaris Cluster 3.3 5/11 Software
Enhancements to the cluster check Command as a Cluster Validation Tool
Fencing Support for Sun ZFS Storage Appliance as a NAS Device
Support for Oracle ACFS as a Cluster File System
Zone Cluster Support for Loopback Mounts With HAStoragePlus Using ZFS
Configuration Wizard Support for Oracle 11g Release 2 with HA-Oracle and Oracle RAC
Support for Zone Clusters Without IP Addresses
Support for SWIFTAlliance Access 7.0 and SWIFTAlliance Gateway 7.0
Oracle ACFS as a Cluster File System
Veritas Volume Manager Cluster Feature No Longer Supported
Commands Modified in This Release
Node Fails To Start Oracle Clusterware After a Panic (uadmin 5 1) Fault Injection (11828322)
Need Support for Clusterized fcntl by Oracle ACFS (11814449)
Unable to Start Oracle ACFS in Presence of Oracle ASM in a Non-Global Zone (11707611)
SAP startsap Fails to Start the Application Instance if startsrv Is Not Running (7028069)
Problem Using Sun ZFS Storage Appliance as Quorum Device Through Fibre Channel or iSCSI (6966970)
Cluster Zone Won't Boot Up After Live Upgrade on ZFS Root (6955669)
Oracle Solaris Operating System
Sun StorageTek Availability Suite
Unable to Register Resource Type SUNW.scalable_acfs_proxy in a Zone Cluster (7023590)
Oracle's SPARC T3-4 Fails During Reboot (6993321)
Missing /dev/rmt Causes Incorrect Reservation Usage When Policy Is pathcount (6920996)
The global_fencing Property Code is Broken When the Value is Changed to prefer3 (6879360)
Autodiscovery Does Not Work on LDoms With Hybrid I/O (6870171)
Removing Nodes from the Cluster Configuration Can Result in Node Panics (6735924)
More Validation Checks Needed When Combining DIDs (6605101)
Solaris Cluster Manager Fails to Come Up in a 16-Node Cluster (6594485)
Apache Tomcat Does Not Start Due to Missing Script (7022690)
Gateway Probe Will Ping Pong if Database Listener Is Not Reachable (6927071)
Scalable Applications Are Not Isolated Between Zone Clusters (6911363)
clresourcegroup add-node Triggers an HAStoragePlus Resource to Become Faulted State (6547896)
GDS Returns Incorrect Exit Status in STOP Method for Non-PMF Services (6831988)
Result of System Requirements Checking Is Wrong (6495984)
ssm_start Fails Due to Unrelated IPMP Down (6938555)
Zones With ip-type=exclusive Cannot Host SUNW.LogicalHostname Resources After Upgrade (6702621)
Patches and Required Firmware Levels
Applying an Oracle Solaris Cluster 3.3 5/11 Core Patch
How to Apply the Oracle Solaris Cluster 3.3 5/11 Core Patch
Removing an Oracle Solaris Cluster 3.3 5/11 Core Patch
How to Remove an Oracle Solaris Cluster 3.3 5/11 Core Patch
This section provides information about patches for Oracle Solaris Cluster configurations, including the following subsections:
Note - If you are upgrading to Oracle Solaris Cluster 3.3 5/11 software, see Oracle Solaris Cluster Upgrade Guide. Applying a Oracle Solaris Cluster 3.3 5/11 Core patch does not provide the same result as upgrading the software to the Oracle Solaris Cluster 3.3 5/11 release.
Note - Read the patch README before applying or removing any patch.
You must be a registered My Oracle Support user to view and download the required patches for the Oracle Solaris Cluster product. If you do not have a My Oracle Support account, contact your Sun service representative or sales engineer, or register online at http://support.oracle.com.
Complete the following procedure to apply the Oracle Solaris Cluster 3.3 5/11 core patch. Ensure that all nodes of the cluster are maintained at the same patch level.
Caution - If an Oracle Solaris Cluster 3.3 5/11 core patch is removed, any resources that were upgraded in Step 3 must be downgraded to the earlier resource type versions. The procedure for downgrading requires planned downtime of these services. Therefore, do not perform Step 3 until you are ready to commit the Oracle Solaris Cluster 3.3 5/11 core patch permanently to your cluster. |
Run the clsetup command to obtain the list of new resource types. For more details, see Upgrading a Resource Type in Oracle Solaris Cluster Data Services Planning and Administration Guide.
For information about registering a resource type, see Registering a Resource Type in Oracle Solaris Cluster Data Services Planning and Administration Guide.
Complete the following procedure to remove the Oracle Solaris Cluster 3.3 5/11 core patch.
# clresourcetype list
# patchrm patch-id
Rebooting all of the nodes from which you removed the Oracle Solaris Cluster 3.3 5/11 core patch before rebooting any unaffected nodes ensures that the cluster is formed with the correct information in the CCR. If all nodes on the cluster were patched with the core patch, you can reboot the nodes into cluster mode in any order.
For instructions on rebooting nodes into cluster mode, see How to Reboot a Node in Oracle Solaris Cluster System Administration Guide.
Information about patch management options for the Oracle Solaris OS is available at the web site for Oracle Enterprise Manager Ops Center (formerly Sun Ops Center) at http://www.oracle.com/us/products/enterprise-manager/opscenter.
The following tools are part of the Oracle Solaris OS. Refer to the version of the manual that is published for the Oracle Solaris OS release that is installed on your system:
Information for using the Oracle Solaris patch management utility, patchadd, is provided in Chapter 23, Managing Patches, in System Administration Guide: Basic Administration.
Information for using Oracle Solaris Live Upgrade to apply patches is provided in the Solaris installation guide for Live Upgrade and upgrade planning at Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
If some patches must be applied when the node is in noncluster mode, you can apply them in a rolling fashion, one node at a time, unless a patch's instructions require that you shut down the entire cluster. Follow procedures in How to Apply a Rebooting Patch (Node) in Oracle Solaris Cluster System Administration Guide to prepare the node and boot it into noncluster mode. For ease of installation, consider applying all patches at once to a node that you place in noncluster mode.
The Sun StorageTek Common Array Manager (CAM) software, minimum required Version 6.0.1, provides SCSI3 or PGR support for the Sun StorageTek 2530 array for up to three nodes. The patch is not a required upgrade for the Sun StorEdge 6130, 2540, 6140, and 6540, and StorageTek FLX240, FLX280 and FLX380 platforms. The CAM patch is available from My Oracle Support.
The My Oracle Support Web site provides 24-hour access to the most up-to-date information regarding patches, software, and firmware for Oracle products. Access the My Oracle Support site at http://support.oracle.com for the most current matrixes of supported software, firmware, and patch revisions.
Before you install Oracle Solaris Cluster 3.3 5/11 software and apply patches to a cluster component (Oracle Solaris OS, Oracle Solaris Cluster software, volume manager software, data services software, or disk hardware), review each README file that accompanies the patches that you retrieved. All cluster nodes must have the same patch level for proper cluster operation.
For specific patch procedures and tips on administering patches, see Chapter 11, Patching Oracle Solaris Cluster Software and Firmware, in Oracle Solaris Cluster System Administration Guide.