Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster 4.1 Release Notes Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Documentation Issues

This section discusses errors or omissions for documentation in the Oracle Solaris Cluster and Geographic Edition 4.1 release.

- Upgrade Guide

- HA for Oracle Guide

- HA for Oracle RAC Guide

- HA for Oracle Solaris Zones Guide

- Solaris Volume Manager

- Geographic Edition Data Replication Guide for Oracle Solaris Availability Suite

- Man Pages

### Upgrade Guide

In multiple chapters, the syntax for the `scinstall -u update` command is missing the option to specify license information, when needed. The full command syntax is the following:

    # scinstall -u update -b [-b bename] [-L accept,licenses]

For more information about the `-L` option, see the `scinstall`(1M) man page.

### HA for Oracle Guide

- In Setting HA for Oracle Extension Properties in Oracle Solaris Cluster Data Service for Oracle Guide, the list of required extension properties for the Oracle server resource is valid only if Oracle Grid Infrastructure is used. If you are not using Oracle Grid Infrastructure, the following extension properties are also required for the Oracle server resource:

  - `Connect_string`

  - `Alert_log_file`

  This information is also missing from Step 9 of How to Register and Configure HA for Oracle Without Oracle ASM (CLI) in Oracle Solaris Cluster Data Service for Oracle Guide.

  For information about the `Connect_string` and `Alert_log_file` extension properties, see the `SUNW.oracle_server`(5) man page.

- In How to Prepare the Nodes in Oracle Solaris Cluster Data Service for Oracle Guide, Step 7 is corrected and Step 8 is added as follows:

  - 7. If you are using a zone cluster, configure the `limitpriv` property by using the `clzonecluster` command.

        # clzonecluster configure zcname
        clzonecluster:zcname>set limitpriv="default,proc_priocntl,proc_clock_highres"
        clzonecluster:zcname>commit

  - 8. On each zone-cluster node, prevent Oracle Clusterware time synchronization from running in active mode.

    - Log in to the zone-cluster node as root.

    - Create an empty `/etc/inet/ntp.conf` file.

          # touch /etc/inet/ntp.conf

### HA for Oracle RAC Guide

The procedure How to Set the Necessary Privileges for Oracle RAC Software in a Zone Cluster in Chapter 1 contains incorrect information. The correct procedure is as follows:

1. Become superuser on the global cluster node that hosts the zone cluster.

2. Configure the `limitpriv` property by using the `clzonecluster` command.

       # clzonecluster configure zcname
       clzonecluster:zcname>set limitpriv ="default,proc_priocntl,proc_clock_highres"
       clzonecluster:zcname>commit

3. Beginning with Oracle RAC version 11g release 2, prevent Oracle Clusterware time synchronization from running in active mode.

   1. Log in to the zone-cluster node as root.

   2. Create an empty `/etc/inet/ntp.conf` file.

          # touch /etc/inet/ntp.conf

### HA for Oracle Solaris Zones Guide

The following instruction is missing from How to Install a Zone and Perform the Initial Internal Zone Configuration in Oracle Solaris Cluster Data Service for Oracle Solaris Zones Guide. Perform this step immediately after Step 6b:

- c. In the node where you updated the new UUID in the boot environment, if there are other non-global zones of brand type `solaris` configured, set the same UUID on the active boot environment for each non-global zone of brand type `solaris`.

      phys-schost-2# zfs set org.opensolaris.libbe:parentbe=uuid poolname/zonepath/rpool/ROOT/bename

For example:

    phys-schost-2# zoneadm list -cv
    …
       1 myzone1       running    /zones/myzone1   solaris  shared
    …

    phys-schost-2# zlogin myzone1 beadm list -H
    solaris;4391e8aa-b8d2-6da9-a5aa-d8b3e6ed6d9b;NR;/;606941184;static;1342165571

    phys-schost-2# zfs set org.opensolaris.libbe:parentbe=8fe53702-16c3-eb21-ed85-d19af92c6bbd \
    rpool/zones/myzone1/rpool/ROOT/solaris

### Solaris Volume Manager

Oracle Solaris Cluster 4.1 software supports Solaris Volume Manager software. The Oracle Solaris 11 documentation set does not include a manual for Solaris Volume Manager software. However, you can still use the Solaris Volume Manager Administration Guide from the Oracle Solaris 10 9/10 release, which is valid with the Oracle Solaris Cluster 4.1 release.

### Geographic Edition Data Replication Guide for Oracle Solaris Availability Suite

The following instruction is missing from the procedure How to Add an Application Resource Group to an Availability Suite Protection Group:

If the application resource group to add is configured with a raw-disk device group, that device group must be specified in the resource group configuration by its data volume, rather than by its device group name. This ensures that the resource will remain monitored after the application resource group is added to a protection group.

For example, if the device group `rawdg` has a corresponding data volume of `/dev/global/rdsk/d1s0`, you must set the `GlobalDevicePaths` property of the application resource group with the data volume, as follows:

    # clresourcegroup set -p GlobalDevicePaths=/dev/global/rdsk/d1s0 rawdg

### Man Pages

This section discusses errors, omissions, and additions in the following Oracle Solaris Cluster man pages:

- clzonecluster(1CL)

- ORCL.sapcenter(5)

- ORCL.saprepenq(5)

- ORCL.saprepenq_preempt(5)

- ORCL.sapstartsrv(5)

- scdpmd.conf(4)

- scha_check_app_user(1HA)

- SUNW.HAStoragePlus(5)

- SUNW.ScalDeviceGroup(5)

- SUNW.ScalMountPoint(5)

#### clzonecluster(1CL)

- The (cluster) `ip-type` property incorrectly states that the only supported value is supported is `shared`. Both `shared` and `exclusive` `ip-types` are supported.

- The `privnet` resource name incorrectly contains a hyphen (`priv-net`). The correct resource name is `privnet`.

#### ORCL.sapcenter(5)

- In the Description section, the seventh bullet point must read as follows:

  The resource group weak positive affinities must ensure that the SAP central service resource group fails over to the node where the SAP replicated enqueue resource group is online. If an `ORCL.saprepenq_preempt` resource is not configured, it must be implemented by strong negative affinities such that the replicated enqueue server resource group is off-loaded from the failover target node before the SAP central service resource group is started.

- In Example 1, make the following change:

      Change: -p resource_dependencies=bono-1,db-rs,scs-strt-rs
      To: -p resource_dependencies=db-rs,scs-strt-rs

#### ORCL.saprepenq(5)

In the Description section, the seventh bullet point must read as follows:

The resource group weak positive affinities must ensure that the SAP central service resource group fails over to the node where the SAP replicated enqueue resource group is online. If an `ORCL.saprepenq_preempt` resource is not configured, it must be implemented strong negative by affinities such that the replicated enqueue server resource group is off-loaded from the failover target node before the SAP central service resource group is started.

#### ORCL.saprepenq_preempt(5)

In the Description section, the eighth bullet point must read as follows:

The resource group weak positive affinities must ensure that the SAP central service resource group fails over to the node where the SAP replicated enqueue resource group is online. If an `ORCL.saprepenq_preempt` resource is not configured, it must be implemented by strong negative affinities such that the replicated enqueue server resource group is off-loaded from the failover target node before the SAP central service resource group is started. If the replicated enqueue preempter resource is configured, it is the task of this resource to off-load the replicated enqueue server resource group to a spare node after the enqueue tables are copied.

#### ORCL.sapstartsrv(5)

- In the Name section, the sentence describing the resource type must read as follows:

  resource type implementation for processing `sapstartsrv` of Oracle Solaris Cluster HA for SAP NetWeaver

- In Example 1, make the following change:

      Change: /usr/cluster/bin/clrs create -d -g pas-rg -t sapstartsrv
      To: /usr/cluster/bin/clrs create -d -g scs-rg -t sapstartsrv

#### scdpmd.conf(4)

The minimum value for the `Ping_interval` property is incorrect. The value should be 20, not 60.

#### scha_check_app_user(1HA)

The use of “effective user ID” in this man page is incorrect. The correct term in all places is “real user ID”. For information about the distinction between a real user ID and an effective user ID, see the `setuid`(2) man page.

#### SUNW.HAStoragePlus(5)

In the description for the `RebootOnFailure` property, the second paragraph is incorrect. The correct paragraph is the following:

If `RebootOnFailure` is set to `TRUE` and at least one device is found available for each entity specified in the `GlobalDevicePaths`, `FileSystemMountPoints`, or `Zpools` property, the local system is rebooted. The local system refers to the global-cluster node or the zone-cluster node where the resource is online.

#### SUNW.ScalDeviceGroup(5)

In the description for the `RebootOnFailure` property, the second paragraph is incorrect. The correct paragraph is the following:

If `RebootOnFailure` is set to `TRUE` and at least one device is found available for each entity specified in the `GlobalDevicePaths`, `FileSystemMountPoints`, or `Zpools` property, the local system is rebooted. The local system refers to the global-cluster node or the zone-cluster node where the resource is online.

#### SUNW.ScalMountPoint(5)

In the description for the `RebootOnFailure` property, the second paragraph is incorrect. The correct paragraph is the following:

If `RebootOnFailure` is set to `TRUE` and at least one device is found available for each entity specified in the `GlobalDevicePaths`, `FileSystemMountPoints`, or `Zpools` property, the local system is rebooted. The local system refers to the global-cluster node or the zone-cluster node where the resource is online.

Copyright © 2000, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |