Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Services Reference Manual Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

### SUNW.scalable_asm_instance_proxy

### , scalable_asm_instance_proxy

- resource type implementation for the Oracle Clustered Automated Storage Management (ASM) instance proxy managed by Oracle Solaris Cluster

## Description

The `SUNW.scalable_asm_instance_proxy` resource type represents a proxy for the Oracle clustered ASM instance in an Oracle Solaris Cluster configuration.

Note - Use the `SUNW.scalable_asm_instance_proxy` resource type only if you are using Oracle Cluster Ready Services (CRS). If you are not using CRS, use the `SUNW.scalable_asm_instance`(5) resource type.

From Oracle 10g, Oracle Cluster Ready Services (CRS) manage the startup and shutdown of clustered ASM instances. To be managed by the CRS, these instances must be registered with the CRS. The Oracle CRS software also provides automatic fault monitoring and failure recovery for clustered ASM instances. These instances are represented as resources to Oracle CRS.

A resource of type `SUNW.scalable_asm_instance_proxy` is a proxy resource. The proxy resource acts as a substitute for a resource that is managed by Oracle CRS. The proxy resource enables Oracle Solaris Cluster utilities to manage Oracle RAC server instances through Oracle CRS. In this way, the `SUNW.scalable_asm_instance_proxy` resource type enables the clustering frameworks that are provided by Oracle Solaris Cluster and Oracle Cluster Ready Services (CRS) to interoperate.

The `SUNW.scalable_asm_instance_proxy` resource type enables you to use Oracle Solaris Cluster utilities as an alternative to Oracle utilities to start and stop Oracle RAC database instances.

Each resource of type `SUNW.scalable_asm_instance_proxy` has a monitor that obtains the following status information from the CRS resource for which the `SUNW.scalable_asm_instance_proxy` resource is acting as a proxy.

- The online or offline status of Oracle CRS

- The status of an Oracle clustered ASM instance:

  - Online and enabled

  - Online but disabled

  - Offline and enabled

  - Offline and disabled

- The success or failure of an attempt to start or stop a clustered ASM instance

- The ability of Oracle CRS to manage the Oracle clustered ASM instance

The timeout period that the monitor uses for obtaining status information is determined by the `proxy_probe_timeout` extension property. If the timeout period is too short, timeouts might cause the monitor to report the status of a valid RAC database instance as invalid. In this situation, consider increasing the value of the `proxy_probe_timeout` extension property.

This monitor only enables the status of Oracle clustered ASM instances to be monitored by Oracle Solaris Cluster utilities. This monitor does not provide fault monitoring and automatic fault recovery for Oracle clustered ASM instances. The Oracle CRS software provides this functionality.

Oracle clustered ASM server instances should be started only after the CRS framework and any storage resources are enabled on the cluster node. To ensure that this requirement is met, configure the Oracle clustered ASM instance proxy resource as follows:

- Create a strong positive affinity between the Oracle clustered ASM instance proxy resource group and the following resource groups:

  - The RAC framework resource group

  - Any resource group that contains storage resources for Oracle files

- Create a strong dependency between the Oracle clustered ASM instance proxy resource and the RAC framework resource.

- Create an offline-restart dependency between the Oracle clustered ASM instance proxy resource and the following resources:

  - The CRS framework resource

  - Any storage resources for Oracle files that you are using

Create these dependencies and affinities when you configure clustered ASM instance resources for the Oracle Solaris Cluster Support for Oracle data service or Oracle Solaris Cluster Support for Oracle RAC data service. For more information, see Oracle Solaris Cluster Data Service for Oracle Guide or Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide.

To register this resource type and create instances of this resource type, use one of the following options:

- The `clsetup`(1CL) utility, specifying the option for configuring Oracle Solaris Cluster Support for Oracle Real Application Clusters

- The following sequence of Oracle Solaris Cluster maintenance commands:

  1. To register this resource type, use the `clresourcetype`(1CL) command.

  2. To create instances of this resource type, use the `clresource`(1CL) command.

Note - A Solaris project might be specified for a `SUNW.scalable_asm_instance_proxy` resource or the resource group that contains a `SUNW.scalable_asm_instance_proxy` resource. In this situation, the project affects only the processes for the `SUNW.scalable_asm_instance_proxy` resource. The project does not affect the processes for any resources that Oracle CRS control, including processes for clustered ASM instances.

### Standard Properties

For a description of all standard resource properties, see the `r_properties`(5) man page.

Standard resource properties are overridden for this resource type as follows:

`Prenet_start_timeout`
  Minimum

    60

  Default

    300

`Prenet_stop_timeout`
  Minimum

    60

  Default

    300

### Extension Properties

The extension properties of the `SUNW.scalable_asm_instance_proxy` resource type are as follows.

`crs_home`

  This property specifies the full path to the Oracle CRS home directory. The Oracle CRS home directory contains the binary files, log files and parameter files for the Oracle CRS software.

  Data Type

    String

  Range

    Not applicable

  Default

    No default defined

  Tunable

    When disabled

`debug_level`

  Note - All SQL*Plus and srvmgr messages that the clustered ASM instance proxy resource issues are written to the log file `/var/opt/SUNWscor/oracle_asm/message_log.${RESOURCE}`.

  This property indicates the level to which debug messages from the monitor for the Oracle clustered ASM instance proxy are logged. When the debug level is increased, more debug messages are written to the system log `/var/adm/messages` as follows:

  0

    No debug messages

  1

    Function Begin and End messages

  2

    All debug messages and function Begin/End messages

  You can specify a different value of the `debug_level` extension property for each node that can master the resource.

  Data Type

    Integer

  Range

    0–2

  Default

    0

  Tunable

    Any time

`oracle_home`

  This property specifies the full path to the Oracle home directory. The Oracle home directory contains the binary files, log files, and parameter files for the Oracle software.

  Data Type

    String

  Range

    Not applicable

  Default

    No default defined

  Tunable

    When disabled

`oracle_sid`

  This property specifies the Oracle System Identifier (SID). The Oracle SID uniquely identifies the Oracle clustered ASM database instance on the node where the instance is running.

  You must specify a different value of the `oracle_sid` extension property for each node that can master the resource. The value for each node must correctly identify the instance that is running on the node.

  Data Type

    String

  Range

    Not applicable

  Default

    `NULL`

  Tunable

    When disabled

`proxy_probe_timeout`

  This property specifies the timeout value, in seconds, that the proxy monitor uses when checking the status of the CRS resource for which this resource is acting as a proxy.

  Data Type

    Integer

  Range

    5–120

  Default

    60

  Tunable

    Any time

`proxy_probe_interval`

  This property specifies the interval , in seconds, between probes of the CRS resource for which this resource is acting as a proxy.

  Data Type

    Integer

  Range

    5–120

  Default

    60

  Tunable

    Any time

## Examples

Example 1 Creating a `scalable_asm_instance_proxy` Resource

This example shows the commands for performing the following operations to create a `scalable_asm_instance_proxy` resource on a two-node cluster:

1. Creating the `asm-inst-rg` resource group

2. Registering the `SUNW.scalable_asm_instance_proxy` resource type

3. Adding the `asm-inst-rs` resource to the `asm-inst-rg` resource group

A different value of the `oracle_sid` extension property is set for each node that can master the resource.

The example makes the following assumptions:

- The bash shell is used.

- A resource group that is named `scal-mp-rg` exists and contains a resource of type `SUNW.ScalMountPoint` that is named `scal-mp-rs`.

- A RAC framework resource group that is named `rac-fmwk-rg` exists and contains resources that are shown in the following table:

  Resource Type | Resource Name
  --- | ---
  `SUNW.crs_framework` | `crs_framework-rs`
  `SUNW.rac_framework` | `rac_framework-rs`

    phys-schost-1# clresourcetype register SUNW.scalable_asm_instance_proxy
    phys-schost-1# clresourcegroup create -g asm-inst-rg
    phys-schost-1# clresourcgroup set -p rg_affinities=++rac-fmwk-rg asm-inst-rg
    phys-schost-1# clresource create -g asm-inst-rg \
    -t SUNW.scalable_asm_instance_proxy \
    -p oracle_home=/global/11g/asm/product/11.1.0/db_1 \
    -p crs_home=/global/11g/crs \
    -p "oracle_sid {pmutt1}"=+ASM1 \
    -p "oracle_sid {pmutt2}"=+ASM2 \\
    -p resource_dependencies_offline_restart=crs-fmwk-rs qfs-mp-rs -d asm-inst-rs
    phys-schost-1# clresourcegroup online -eM asm-inst-rg

## See Also

Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide, Oracle Solaris Cluster Data Service for Oracle Guide, Oracle Solaris Cluster Data Services Planning and Administration Guide

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