The following commands have been modified in this release.
Beginning with the Oracle Solaris Cluster 4.3.6 release, the geopg status command supports the following additional option:
Displays messages for any errors that put the configuration in the Error state, and messages for any errors that put the replication resource in the FAULTED or DEGRADED error states.
As of the Oracle Solaris Cluster 4.3.4 release, the replication_mode property of the Oracle Data Guard module to Geographic Edition is no longer used and has been removed from the geopg command. Ignore mentions of this data replication component property in Oracle Solaris Cluster 4.3 documentation.
After update to Oracle Solaris Cluster 4.3.4, no reconfiguration is necessary for protection groups that were created with the replication_mode property in previous versions. The property is ignored by Geographic Edition commands and is no longer listed in configuration output. This change has no effect on the protection group's behavior.
Oracle Solaris Cluster 4.3.4 software introduces version 6 of the SUNW.LogicalHostname resource type. The following changes apply to resources that are created with, or upgraded to, version 6 of the SUNW.LogicalHostname resource type:
The Global_zone property is set to False by default.
The Global_zone_override property is no longer supported. RGM methods will be executed in the zone where the resource group is configured.
Beginning with Oracle Solaris Cluster 4.3.4 software, the Active_data_guard extension property is added to the SUNW.oracle_server resource type. The extension property's characteristics are as follows:
Indicates whether a physical standby instance is additionally managed by Oracle Active Data Guard. Set this property to TRUE if the database instance being managed is in an Oracle Active Data Guard configuration. If a SUNW.oracle_server resource that is configured with the Active_data_guard extension property is restarted on the standby cluster, the Oracle database is started in read-only mode.
Tunable: When Disabled
The –G global-devices-file-system option to the clnode command is no longer used and has been removed from the clnode command. When adding a node to the cluster, a file system will automatically be created from a lofi device for the global device name space. Removing a node from the cluster removes the file system created from the lofi device on that node.