SUNW.scalable_rac_server(5) (Sun Cluster Data Services Reference Manual for Solaris OS)

Sun Cluster Data Services Reference Manual for Solaris OS

SUNW.scalable_rac_server(5)

NAME | Description | Examples | Attributes | See Also

NAME

SUNW.scalable_rac_server, scalable_rac_server – resource type implementation for the Oracle 9i Real Application Clusters (RAC) server managed by Sun Cluster

Description

The SUNW.scalable_rac_server resource type represents the Oracle 9i RAC server in a Sun Cluster configuration.

Note –

Use the SUNW.scalable_rac_server resource type only if you are using Oracle 9i RAC. If you are using Oracle 10g R2, use the SUNW.scalable_rac_server_proxy(5) resource type.

The SUNW.scalable_rac_server 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_rac_server resource represents all Oracle RAC server instances for a database. Each instance of the RAC server 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.

Oracle RAC server instances should be started only after the RAC framework is enabled on the cluster node. To ensure that this requirement is met, configure the Oracle RAC server resource and the RAC framework as follows:

Create a strong positive affinity between the Oracle RAC server resource group and the RAC framework resource group.
Create a strong dependency between the Oracle RAC server resource and the RAC framework resource.

Create these dependencies and affinities when you configure database resources for the Sun Cluster Support for Oracle RAC data service. For more information, see Configuring Resources for Oracle RAC Database Instances in Sun Cluster Data Service for Oracle RAC Guide for Solaris OS in Sun Cluster Data Service for Oracle RAC Guide for Solaris OS.

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

Sun Cluster Manager
The clsetup(1CL) utility, specifying the option for configuring Sun Cluster Support for Oracle Real Application Clusters
The following sequence of Sun 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:

Boot_timeout

Minimum: 5
Default: 30

Failover_mode

Default: SOFT
Tunable: Any time

Fini_timeout

Minimum: 5
Default: 30

Init_timeout

Minimum: 5
Default: 30

Monitor_start_timeout

Minimum: 5
Default: 120

Monitor_stop_timeout

Minimum: 5
Default: 120

Retry_count

Minimum: -1
Maximum: 9999
Default: 2
Tunable: Any time

Retry_interval

Minimum: 0
Maximum: 2592000
Default: 900
Tunable: Any time

Start_timeout

Minimum: 5
Default: 600

Stop_timeout

Minimum: 5
Default: 600

Thorough_probe_interval

Minimum: 1
Maximum: 2592000
Default: 30
Tunable: Any time

Update_timeout

Minimum: 5
Default: 240

Validate_timeout

Minimum: 5
Default: 120

Extension Properties

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

alert_log_file

This property is set to the absolute path of the Oracle alert log file. The Oracle software logs alerts in this file. The Oracle RAC server fault monitor scans the alert log file for new alerts at the following times:

When the RAC server fault monitor is started
Each time that the RAC server fault monitor queries the health of the server

If an action is defined for a logged alert that the RAC server fault monitor detects, the RAC server fault monitor performs the action in response to the alert.

Preset actions for logged alerts are listed in Appendix B, Preset Actions for DBMS Errors and Logged Alerts, in Sun Cluster Data Service for Oracle RAC Guide for Solaris OS in Sun Cluster Data Service for Oracle RAC Guide for Solaris OS. To change the action that the RAC server fault monitor performs, customize the server fault monitor as explained in Customizing the Oracle 9i RAC Server Fault Monitor in Sun Cluster Data Service for Oracle RAC Guide for Solaris OS in Sun Cluster Data Service for Oracle RAC Guide for Solaris OS.

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

Data Type: String
Range: Not applicable
Default: NULL
Tunable: Any time

connect_cycle

This property specifies the number of fault monitor probe cycles that are performed before the fault monitor disconnects from the database.

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

Data Type: Integer
Range: 0–99999
Default: 5
Tunable: Any time

connect_string

This property specifies the Oracle database user ID and password that the fault monitor uses to connect to the Oracle database. This property is specified as follows:

userid/password

userid: Specifies the Oracle database user ID that the fault monitor uses to connect to the Oracle database.
password: Specifies the password that is set for the Oracle database user userid.

The system administrator must define the database user ID and password for the fault monitor during the setup of Oracle RAC. To use Solaris authentication, type a slash (/) instead of a user ID and password.

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

Data Type: String
Range: Not applicable
Default: NULL
Tunable: Any time

custom_action_file

This property specifies the absolute path of the file that defines the custom behavior of the Oracle RAC server fault monitor. The format of this file is defined in the custom_action_file(4) man page.

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

Data Type: String
Range: Not applicable
Default: Empty string
Tunable: Any time

debug_level

This property indicates the level to which debug messages from the Oracle RAC server component are logged. When the debug level is increased, more debug messages are written to the log files. These messages are logged to the file /var/opt/SUNWscor/scalable_rac_server/message_log.rs, where rs is the name of the resource that represents the Oracle RAC server component.

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–100
Default: 1, which logs syslog messages
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 RAC 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.

Data Type: String
Range: Not applicable
Default: NULL
Tunable: When disabled

parameter_file

This property specifies the full path to the Oracle parameter file. This file contains parameters that are to be set when the Oracle database is started. This property is optional. If you do not set this property, the default parameter file that is specified by Oracle is used, namely: oracle-home/dbs/initoracle-sid.ora.

oracle-home: Specifies the Oracle home directory
oracle-sid: Specifies the Oracle system identifier of the database instance for which the file is to be used.

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

Data Type: String
Range: Not applicable
Default: No default defined
Tunable: Any time

probe_timeout

This property specifies the timeout value, in seconds, that the fault monitor uses when checking the status of an Oracle RAC server.

Data Type: Integer
Range: 1–99999
Default: 300
Tunable: Any time

user_env

This property specifies the name of the file that contains the environment variables that are to be set before the database starts up or shuts down. You must define all environment variables whose values differ from Oracle defaults in this file.

For example, a user's listener.ora file might not be located under the /var/opt/oracle directory or the oracle-home/network/admin directory. In this situation, the TNS_ADMIN environment variable must be defined.

The definition of each environment variable that is defined must follow the format variable-name=value. Each definition must start on a new line in the environment file.

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

Data Type: String
Range: Not applicable
Default: No default defined
Tunable: Any time

wait_for_online

This property specifies whether the START method of the Oracle RAC server resource waits for the database to be online before the START method exits. The permitted values for this property are as follows:

True: Specifies that the START method of the Oracle RAC server resource waits for the database to be online before the START method exits.
False: Specifies that the START method runs the commands to start the database but does not wait for the database to come online before the START method exits.

Data Type: Boolean
Range: Not applicable
Default: True
Tunable: Any time

Examples

Example 1 Creating a `scalable_rac_server` Resource

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

Creating the rac-db-rg resource group
Registering the SUNW.scalable_rac_server resource type
Adding the scalable_rac_server-rs resource to the rac-db-rg resource group

A different value of the following extension properties is set for each node that can master the resource:

alert_log_file
oracle_sid

The example makes the following assumptions:

The C shell is used.
A RAC framework resource group that is named rac-framework-rg exists and contains resources of types as shown in the following table:

Resource Type

Resource Name

SUNW.rac_framework

rac_framework-rs

SUNW.rac_udlm

rac_udlm-rs

SUNW.rac_svm

rac_svm-rs
Creation of a resource of type SUNW.scalable_rac_listener that is named scalable_rac_listener-rs is outside the scope of this example.

Resource Type	Resource Name
`SUNW.rac_framework`	`rac_framework-rs`
`SUNW.rac_udlm`	`rac_udlm-rs`
`SUNW.rac_svm`	`rac_svm-rs`

phys-schost-1# clresourcegroup create \
-p rg_affinities=++rac-framework-rg \
-p desired_primaries=2 \
-p maximum_primaries=2  \
rac-db-rg
...Creation of RAC listener resource
phys-schost-1# clresourcetype register SUNW.scalable_rac_server
phys-schost-1# clresource create -g rac-db-rg -t SUNW.scalable_rac_server \
-p resource_dependencies=rac_framework-rs \
-p resource_dependencies_weak=scalable_rac_listener-rs \
-p oracle_home=/home/oracle/product/9.2.0 \
-p connect_string=scooter/t!g3r \
-p oracle_sid\{1\}=V920RAC1 \
-p oracle_sid\{2\}=V920RAC2 \
-p alert_log_file\{1\}=/home/oracle/9.2.0/rdbms/log/alert_V920RAC1.log \
-p alert_log_file\{2\}=/home/oracle/9.2.0/rdbms/log/alert_V920RAC2.log \
scalable_rac_server-rs

Attributes

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWscor