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

### , scalable_asm_instance

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

## Description

The `SUNW.scalable_asm_instance` resource type represents the single instance ASM in an Oracle Solaris Cluster configuration.

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

The `SUNW.scalable_asm_instance` resource type is a multiple-master resource type. A single resource of this type can run on multiple nodes concurrently, but does not use network load balancing.

Each `SUNW.scalable_asm_instance` resource represents all Oracle single instance ASM instances. Each instance of the single instance ASM is uniquely identified by the value of the `oracle_sid` extension property on the node where the instance is running.

The `oracle_sid` extension property is a per-node property. A single resource of this type can take a different value of this property for each node.

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

- 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.

### 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:

`Failover_mode`
  Default

    SOFT

  Tunable

    Any time

`Load_balancing_policy`
  Default

    LB_WEIGHTED

  Tunable

    At creation

`Load_balancing_weights`
  Default

    ””

  Tunable

    Any time

`Monitor_check_timeout`
  Minimum

    60

  Default

    300

`Monitor_start_timeout`
  Minimum

    60

  Default

    300

`Monitor_stop_timeout`
  Minimum

    60

  Default

    300

`Network_resources_used`
  Default

    ””

  Default

    Any time

`Port_list`
  Default

    ””

  Tunable

    Anytime

`Retry_count`
  Maximum

    10

  Default

    2

  Tunable

    Anytime

`Retry_Interval`
  Maximum

    3600

  Default

    370

  Tunable

    Anytime

`Scalable`
  Default

    FALSE

  Tunable

    At creation

`Start_timeout`
  Minimum

    60

  Default

    300

`Stop_timeout`
  Minimum

    60

  Default

    300

`Through_probe_interval`
  Minimum

    3600

  Default

    60

  Tunable

    ANYTIME

`Update_timeout`
  Minimum

    60

  Default

    300

`Validate_timeout`
  Minimum

    60

  Default

    300

### Extension Properties

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

`Child_mon_level`(integer)

  Provides control over the processes that are monitored through the Process Monitor Facility (PMF). This property denotes the level to which the forked child processes are monitored. Omitting this property or setting this property to the default value is the same as omitting the `-C`option for `pmfadm`(1M). All child processes and their descendents are monitored.

  Category

    Optional

  Default

    -1

  Tunable

    When disabled

`debug_level`

  Note - All SQL*Plus and srvmgr messages that the single instance ASM 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 for the Oracle single instance ASM resources 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

`Failover_Enabled`(boolean)

  Allows the resources to fail over. If this property is set to `False`, failover of the resource is disabled. You can use this property to prevent the application resource from initiating a failover of the resource group.

  Note - Use the `Failover_mode` property instead of the `Failover_enabled` extension property because `Failover_mode` better controls failover behavior. For more information, see the descriptions of the `LOG_ONLY` and `RESTART_ONLY` values for `Failover_mode` in `r_properties`(5).

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

  Category

    Optional

  Default

    True

  Tunable

    When disabled

`Log_level`

  Specifies the level, or type, of diagnostic messages that are logged by GDS. You can specify `None`, `Info`, or `Err` for this property. When you specify `None`, diagnostic messages are not logged by GDS. When you specify `Info`, both information and error messages are logged. When you specify `Err`, only error messages are logged.

  Category

    Optional

  Default

    Info

  Tunable

    Any time

`Network_aware`(boolean)

  This property specifies whether an application uses the network.

  Category

    Optional

  Default

    `False`

  Tunable

    At creation

`Monitor_retry_count`

  This property specifies the number of PMF restart allowed for the fault monitor.

  Default

    4

  Tunable

    Any time

`Monitor_retry_interval`

  This property specifies the number of PMF restart allowed for the fault monitor.

  Default

    2

  Tunable

    Any time

`probe_command`(string)

  Specifies the command that periodically checks the health of the single instance ASM.

  Category

    Required

  Default

    `"/opt/SUNWscor/oracle_asm/bin/asm_control probe -R %RS_NAME -G %RG_NAME -T %RT_NAME"`

  Tunable

    None

`Probe_timeout`(integer)

  This property specifies the timeout value, in seconds, for the probe command.

  Category

    Optional

  Default

    30 seconds

  Tunable

    Any time

`Start_command`(string)

  Specifies the command that starts the single instance ASM.

  Category

    Required

  Default

    `"/opt/SUNWscor/oracle_asm/bin/asm_control start -R %RS_NAME -G %RG_NAME -T %RT_NAME"`

  Tunable

    None

`Stop_command`(string)

  Specifies the command that stops the single instance ASM.

  Category

    Required

  Default

    `"/opt/SUNWscor/oracle_asm/bin/asm_control stop -R %RS_NAME -G %RG_NAME -T %RT_NAME"`

  Tunable

    None

`Stop_signal`(integer)

  Specifies the command that stops the single instance ASM.

  Category

    Optional

  Default

    `15`

  Tunable

    When disabled

`Validate_command`(string)

  Specifies the absolute path to the command that validates the application, although currently not used.

  Category

    Optional

  Default

    `Null`

  Tunable

    When disabled

`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 single instance ASM on the node where the instance is running.

  Data Type

    String

  Range

    `Not applicable`

  Default

    +ASM

  Tunable

    When disabled

## Examples

Example 1 Creating a `scalable_asm_instance` Resource

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

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

2. Registering the `SUNW.scalable_asm_instance` resource type

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

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

The example makes the assumption that the bash shell is used.

    phys-schost-1# clresourcetype register SUNW.scalable_asm_instance
    phys-schost-1# clresourcegroup create -S asm-inst-rg
    phys-schost-1# clresource create -g asm-inst-rg \
    -t SUNW.scalable_asm_instance \
    -p Oracle_home=/export/home/oraasm/oracle/product/10.2.0/db_1 \\
    -d asm-inst-rs
    phys-schost-1# clresourcegroup online -M asm-inst-rg
    phys-schost-1# clresource enable asm-inst-rs

In the above example, the default value of `+ASM` is used for `oracle_sid`. If different values are required for `oracle_sid`, you should use the `per_node` property attribute as follows:

    phys-schost-1# clresource create -g asm-inst-rg \
    -t SUNW.scalable_asm_instance \
    -p Oracle_home=/export/home/oraasm/oracle/product/10.2.0/db_1 \\
    -p "Oracle_sid{pmutt1}"=+ASM_node1 \\
    -p "Oracle_sid{pmutt2}"=+ASM_node2 \\
    -d asm-inst-rs

## 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 |