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
Patch for Cluster Support for Sun StorageTek 2530 Array
Oracle Solaris Cluster 3.3 5/11 Documentation Set
This section discusses errors or omissions for documentation, online help, or man pages in the Oracle Solaris Cluster 3.3 5/11 release.
This section discusses errors, omissions, and additions in the Oracle Solaris Cluster man pages.
The clnasdevice(1CL) man page contains the incorrect name for the sun_uss NAS device type. The man page uses Oracle's Sun Storage 7000 Unified Storage Systems as the NAS device name, but the correct name is Oracle's Sun ZFS Storage Appliance. The man page is also missing some information. See clnasdevice(1CL) Man Page for the correct contents of this man page.
If the name_service property is not specified when you create a zone cluster, a value for the property is pulled from the /etc/sysidcfg file in the global zone. However, because this information might be stale, always specify the name_service property when creating a zone cluster. To reflect this behavior, the description of the name_service property is changed to the following:
This property specifies the naming service to be used in the zone cluster. It is an optional property, and the setting in the global zone is used by default. However, the settings in the global zone's /etc/sysidcfg file might be stale. To ensure that this property has the correct setting, enter the value manually by using the clzonecluster command.
The description of the timezone property is also revised as follows:
This property specifies the time zone to be used in the zone cluster. The value is obtained from the environment of the clzonecluster command by default.
The following new value for the Standby_mode extension property is missing from the man page:
Beginning with Oracle 11g, specifies a snapshot standby database.
Support for Oracle ACFS with Oracle Solaris Cluster 3.3 5/11 introduces a new resource type, SUNW.scalable_acfs_proxy. The man page for this resource type is not included in this release. See SUNW.scalable_acfs_proxy(5) Man Page for the contents of this man page.