Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster 3.3 3/13 Release Notes Oracle Solaris Cluster 3.3 3/13 |
Oracle Solaris Cluster 3.3 3/13 Release Notes
What's New in the Oracle Solaris Cluster 3.3 3/13 Software
Qualification of VxVM and VxFS
New clsetup Wizards to Create a Zone Cluster
Resource Dependencies Can Be Defined on a Per-Node Basis
Support for Kernel Cage Dynamic Reconfiguration (DR)
Cluster Security Framework Is Enhanced
Faster Failure Detection and Response by Storage Monitors
New clsetup Wizard to Configure the Oracle PeopleSoft Application Server Data Service
New clsetup Wizard to Configure the Oracle WebLogic Server Data Service
New Data Service for Oracle External Proxy
New Data Service for SAP NetWeaver
New Data Service for Oracle PeopleSoft Enterprise Process Scheduler
New Data Service for Oracle Web Tier
Support for Sun ZFS Storage Appliance Data Replication With Geographic Edition
Oracle ACFS as a Cluster File System
Topology Pages in Oracle Solaris Cluster Manager
Commands Modified in This Release
Oracle ASM With Solaris Volume Manager Mirrored Logical Volumes
ACFS Proxy Resource Goes Offline During Installation of Oracle Binaries (16581850)
Tavor InfiniBand (IB) Transport Cluster Nodes Panic: mutex_enter: bad mutex, lp (16372022)
Solaris Upgrade to Oracle Solaris 10 8/11 Overwrites the hostname.adp Contents (15882549)
Oracle Solaris Operating System
Features Not Supported in This Release
Cannot Set the Jumbo Frame MTU Size for the clprivnet Interface (16618736)
Cluster Check Utility S6708502 Reports RT Process ora_dism as Unsupported (16365116)
Public Net Failure Does Not Fail Over DB Server Resource with SCAN Listener (16231523)
Cluster File System Does Not Support Extended Attributes (15790565)
Unable to Register Resource Type SUNW.scalable_acfs_proxy in a Zone Cluster (15700050)
Cannot Create a Resource From a Configuration File With Non-Tunable Extension Properties (15658184)
Disabling Device Fencing While Cluster Is Under Load Results in Reservation Conflict (15608862)
Autodiscovery Does Not Work on LDoms With Hybrid I/O (15581535)
Removing Nodes from the Cluster Configuration Can Result in Node Panics (15500647)
More Validation Checks Needed When Combining DIDs (15423531)
sun.storage_proxy.type Resource in Offline State After uadmin 5 1 (16910145)
Active-Standby Configuration Not Supported for HA for TimesTen (16861602)
Disabled LDom Resource Keeps the LDom in a Bound State (16323723)
Manual Umount of ZFS File System Does Not Get Remounted Automatically (16319552)
Errors Occur When Deleting an HA LDom Resource (16229698)
Oracle Solaris 10 Samba Patch 119757-20 or 119758-20 Impacts the HA-Samba Data Service (15757158)
When set Debug_level=1, pas-rg Fails Over to Node 2 And Cannot Start on Node 1 Anymore (15803844)
Scalable Applications Are Not Isolated Between Zone Clusters (15611122)
Geographic Edition Disables ASM Resources in Incorrect Order, Resulting in Error Messages (16004984)
Cluster Node Does Not Have Access to ZFS Storage Appliance Projects or iSCSI LUNs (15924240)
Multiple Notification Emails Sent from Global Cluster When Zone Clusters Are in Use (15746425)
DR State Stays Reporting unknown on One Partner (15808054)
Running the scinstall -u Command Leaves 'installed' Zones in 'mounted' State (15817301)
Result of System Requirements Checking Is Wrong (12185261)
The clzonecluster cancel Command Can Cause an Error (15950187)
sc_delegated_restarter Does Not Take Into Account Environment Variable Set in Manifest (15795184)
Unable to Re-enable Transport Interface After Disabling With ifconfig unplumb interface (15770198)
Failure of Logical Hostname to Fail Over Caused by getnetmaskbyaddr() (15733435)
Patches and Required Firmware Levels
Applying an Oracle Solaris Cluster 3.3 3/13 Core Patch
How to Apply the Oracle Solaris Cluster 3.3 3/13 Core Patch
Removing an Oracle Solaris Cluster 3.3 3/13 Core Patch
How to Remove an Oracle Solaris Cluster 3.3 3/13 Core Patch
This section discusses errors or omissions for documentation, online help, or man pages in the Oracle Solaris Cluster 3.3 3/13 release.
The Oracle Solaris Cluster Software Installation Guide contains the following errors:
“Global Fencing” in Chapter 1 – The value prefer3 is mistakenly described as the default global-fencing setting. The correct default value is pathcount.
“How to Configure an HAStoragePlus Resource for a Cluster File System that is Used by Non-Global Zones” – In Step 6, an incorrect property is used. Instead of the Network_resources_used property, use the Resource_dependencies_offline_restart property to specify the HAStoragePlus resource. This property dependency makes the application restart when the HAStoragePlus resource with monitoring enabled is restarted.
The Oracle Solaris Cluster Data Service for Oracle Guide contains the following omission:
Using Oracle ASM in both the global cluster and a zone cluster – If you use Oracle ASM in a global cluster as well as in a zone cluster configured in that global cluster, you must ensure that, in each particular cluster, Oracle ASM can see only those devices that are intended for its use, whether in the global zone or in a zone cluster. If Oracle ASM can see devices that are used by Oracle ASM in a different cluster, this can cause start problems for Oracle Clusterware or Grid Infrastructure, because Oracle ASM sees the devices as already mounted elsewhere.
The Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide contains the following errors and omissions:
Using Oracle ASM in both the global cluster and a zone cluster – If you use Oracle ASM in a global cluster as well as in a zone cluster configured in that global cluster, you must ensure that, in each particular cluster, Oracle ASM can see only those devices that are intended for its use, whether in the global zone or in a zone cluster. If Oracle ASM can see devices that are used by Oracle ASM in a different cluster, this can cause start problems for Oracle Clusterware or Grid Infrastructure, because Oracle ASM sees the devices as already mounted elsewhere.
“Storage Management Schemes for Oracle Files” – In Table 1-2 , the cell for Oracle Clusterware binary files with an Oracle ACFS file system should show a minus (-) symbol instead of a plus (+) symbol. An ACFS file system cannot store Oracle Clusterware binary files.
“Types of Oracle Files That You Can Store on an Oracle ACFS File System” – Oracle Clusterware binary files is incorrectly included in the list of file types.
“How to Create Oracle Solaris Cluster Resources in the Global Cluster for Interoperation With Oracle 10g or 11g“ – In Step 4, the rg_affinities property is incorrect. The optional db-storage-rg resource group should be specified as a strong positive affinity, as follows:
-p rg_affinities=++rac-fmwk-rg[,++db-storage-rg]
“How to Create an Oracle ASM Resource for Oracle Clusterware Interoperation With Oracle Solaris Cluster Software” – The command in Step 8b is incorrect. The correct command is as follows:
# Grid_home/bin/crs_register sun.node.asm-dg-rs -update -r crs-asm-instance
“How to Create an Oracle Grid Infrastructure Resource for Interoperation With Oracle Solaris Cluster” – In Step 3, the description of the HOSTING_MEMBERS property should be, “The list of nodes in the cluster membership, separated by spaces”.
For Steps 4 through 8, the correct instructions are as follows:
4. Determine the DBA group of the Oracle Grid Infrastructure installation.
# Grid_home/bin/osdbagrp
5. Set the primary group of the Oracle Grid Infrastructure storage_proxy resource to the group determined in Step 4.
# Grid_home/bin/crsctl setperm resource sun.sc-resource -g "griddba"
6. Determine the DBA group of the Oracle Database Software installation.
# oracle_home/bin/osdbagrp
7. Set the group permissions of the Oracle Grid Infrastructure storage_proxy resource to the group determined in Step 6.
Omit this step if the Oracle Grid Infrastructure installation DBA group griddba-group, determined in Step 4, and the Oracle Database Software installation DBA group dba-group, determined in Step 6, are the same DBA group.
# Grid_home/bin/crsctl setperm resource sun.sc-resource -u "group:dba-group:r-x"
8. Bring online the Oracle Grid Infrastructure storage_proxy resource.
# Grid_home/bin/crsctl start resource sun.sc-resource
Upgrading Oracle Grid Infrastructure or Oracle Database software – If you need to upgrade Oracle Grid Infrastructure or Oracle Database software but are not also upgrading Oracle Solaris or Oracle Solaris Cluster software, you must first remove the grid or database software from Oracle Solaris Cluster control. This includes any zone cluster resources that depend on the resources in the global cluster.
The following instructions describe the steps to perform before and after you upgrade the grid or database software.
From one node, identify the Oracle Grid Infrastructure and Oracle Database resources that you need to disable.
# clresource -t resource-type list
The following are the resource types that might be used:
SUNW.asm_diskgroup
SUNW.oracle_listener
SUNW.oracle_rac_server
SUNW.oracle_server
SUNW.scalable_acfs_proxy
SUNW.scalable_asm_diskgroup_proxy
SUNW.scalable_asm_instance
SUNW.scalable_asm_instance_proxy
SUNW.scalable_rac_listener
SUNW.scalable_rac_server
SUNW.scalable_rac_server_proxy
From one node, use the clresource command to remove any dependencies by other resources on grid or database resources or both.
# clresource set -p Resource_dependencies-=dependent-resource application-resource
Specifies a resource on which this resource has a dependency.
Deletes the specified value.
Specifies the grid or database resource.
Specifies the application resource that depends on the grid or database resource.
On one node at a time, remove Oracle Solaris Cluster control of resources associated with the Grid Infrastructure or Oracle Database software you intend to upgrade.
Perform these steps on each node that runs Oracle Grid Infrastructure or Oracle Database software, or both.
Disable the resources.
# clresource disable -n node resource
Specifies the node where the resource is to be disabled.
Specifies the grid or database resource to disable.
Note - Do not disable the RAC framework resource, which uses the SUNW.rac_framework resource type. This resource is necessary for the operation of Oracle RAC.
After all associated resources on the node are disabled, manually restart the Grid Infrastructure or Oracle Database software, or both, on the nodes where the software was disabled.
Use the standard Oracle grid or database commands. This action ensures that the components remain outside Oracle Solaris Cluster control when you upgrade the grid or database software.
From one node, upgrade the Oracle Grid Infrastructure or Oracle Database software, or both.
Follow procedures provided in the Oracle Grid Infrastructure or Oracle Database documentation.
If the upgraded software requires an addition or change of any extension properties, from one node update the affected grid or database resources, or both.
# clresource set -p property=property-value {-p property=property-value …} \ resource
Specifies the setting of a given property.
Specifies the resource that contains the affected property.
From one node, enable the Oracle Solaris Cluster resources that are associated with Oracle Grid Infrastructure or Oracle Database software, or both.
# clresource enable resource
Oracle Solaris Cluster control of grid or database resources is restored.
From one node, restore the resource dependencies on the grid or database resources.
# clresource set -p Resource_dependencies+=dependent-resource application-resource
Specifies a resource on which the application resource has a dependency.
Adds the specified value.
Specifies the grid or database resource.
Specifies the application resource that depends on the grid or database resource.
The Oracle Solaris Cluster Data Service for Oracle Web Tier Guide contains the following errors:
The following note is incorrect and should be ignored:
Note - You need to install the HA for Oracle Web Tier packages in the global cluster and not in the zone cluster.
It is supported to install HA for Oracle Web Tier packages directly in a zone cluster.
Because this data service is introduced in the Oracle Solaris Cluster 3.3 3/13 release, there is no previous resource type version to upgrade from. Therefore, information in the section Information for Registering the New Resource Type Version is extraneous and can be ignored.
This section discusses errors, omissions, and additions in the Oracle Solaris Cluster man pages.
Some man pages, such as clquorum(1CL), contain information about Network Appliance NAS devices. This information is extraneous and should be ignored.