JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster 3.3 5/11 Release Notes     Oracle Solaris Cluster
search filter icon
search icon

Document Information

Preface

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

Restrictions

Oracle ACFS as a Cluster File System

Veritas Volume Manager Cluster Feature No Longer Supported

Commands Modified in This Release

Product Name Changes

Compatibility Issues

Node Panic When Calling rename(2) to Rename an Oracle ACFS Directory to its Parent Directory (11828617)

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)

Oracle Solaris Cluster Project Shares Workflow Should Return All Shares Underneath r/w Projects (7041969)

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)

Solaris Volume Manager GUI

Accessibility Information

Supported Products

Data Services

File Systems

Oracle Solaris 10 on SPARC

Oracle Solaris 10 on x86

Memory Requirements

Oracle Solaris Operating System

Oracle VM Server for SPARC

Sun Management Center

Sun StorageTek Availability Suite

Volume Managers

Oracle Solaris 10 on SPARC

Oracle Solaris 10 on x86

Product Localization

Known Issues and Bugs

Administration

Resource Group Does Not Fail Over When Failover_mode Is Set to SOFT During a Public Interface Failure (7038727)

Unable to Register Resource Type SUNW.scalable_acfs_proxy in a Zone Cluster (7023590)

Oracle's SPARC T3-4 Fails During Reboot (6993321)

Removing the Last Node That Hosts a Zone Cluster Does Not Remove the Zone Cluster From the Cluster Configuration (6969605)

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)

EMC SRDF and Hitachi TrueCopy Reject Switchover When Replicated Device-Group Status Will Cause Switchover and Switchback to Fail (6798901)

Configuring a Scalable Resource With the LB_STICKY_WILD Load Balancing Policy Fails With clsetup (6773401)

Removing Nodes from the Cluster Configuration Can Result in Node Panics (6735924)

If the Solaris Security Toolkit Is Configured on Cluster Nodes, scstat -i Gives an RPC Bind Failure Error(6727594)

More Validation Checks Needed When Combining DIDs (6605101)

Solaris Cluster Manager Fails to Come Up in a 16-Node Cluster (6594485)

Data Services

Resource Group Creation After Zone Cluster Reboot but Before RGM Reconfiguration Leads to Inconsistent State Within RGM (7041222)

Apache Tomcat Does Not Start Due to Missing Script (7022690)

SAP Web Application Server Primary Instance Not Able to Come Online on the Same Node After Killing the Dispatcher (7018400)

HAStoragePlus Resource Configured in Scalable Resource Group with Cluster File System Stays at "Starting" State Indefinitely (6960386)

Gateway Probe Will Ping Pong if Database Listener Is Not Reachable (6927071)

Scalable Applications Are Not Isolated Between Zone Clusters (6911363)

Running clnas add or clnas remove Command on Multiple Nodes at the Same Time Could Cause Problem (6791618)

clresourcegroup add-node Triggers an HAStoragePlus Resource to Become Faulted State (6547896)

Developer Environment

GDS Returns Incorrect Exit Status in STOP Method for Non-PMF Services (6831988)

Installation

The installer Deletes the Existing Package Corresponding to Ops Center Agent JavaDB Database. (6956479)

Localization

Result of System Requirements Checking Is Wrong (6495984)

Runtime

cldevicegroup Status Always Shows Multi-Owner Solaris Volume Manager Disk Sets Configured on vucmm Framework as "offline" (6962196)

ssm_start Fails Due to Unrelated IPMP Down (6938555)

Upgrade

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

Patch Management Tools

Patch for Cluster Support for Sun StorageTek 2530 Array

My Oracle Support

Oracle Solaris Cluster 3.3 5/11 Documentation Set

Documentation Addendum

Man Pages

clnasdevice(1CL)

clzonecluster(1CL)

SUNW.oracle_server(5)

SUNW.scalable_acfs_proxy(5)

A.  Documentation Appendix

Patches and Required Firmware Levels

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.

Applying an Oracle Solaris Cluster 3.3 5/11 Core Patch

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

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.


How to Apply the Oracle Solaris Cluster 3.3 5/11 Core Patch

  1. Install the patch using the usual rebooting patch procedure for a core patch.
  2. Verify that the patch has been installed correctly on all nodes and is functioning properly.
  3. Perform Resource Type upgrades to any new versions of the resource type available.

    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.

Removing an Oracle Solaris Cluster 3.3 5/11 Core Patch

Complete the following procedure to remove the Oracle Solaris Cluster 3.3 5/11 core patch.

How to Remove an Oracle Solaris Cluster 3.3 5/11 Core Patch

  1. List the resource types on the cluster.
    # clresourcetype list
  2. If you have upgraded to any new resource types after applying the core patch, follow the directions in How to Remove a Resource Type in Oracle Solaris Cluster Data Services Planning and Administration Guide.
  3. Remove the Oracle Solaris Cluster 3.3 5/11 core patch from each node on which you installed the patch.
    # patchrm patch-id
  4. Reboot into cluster mode all of the nodes from which you removed the Oracle Solaris Cluster 3.3 5/11 core patch.

    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.

  5. Reboot any remaining nodes into cluster mode.

    For instructions on rebooting nodes into cluster mode, see How to Reboot a Node in Oracle Solaris Cluster System Administration Guide.

Patch Management Tools

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:

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.

Patch for Cluster Support for Sun StorageTek 2530 Array

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.

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.