Registering and Configuring HA for Oracle

Tools for Registering and Configuring HA for Oracle

Oracle Solaris Cluster provides the following tools for registering and configuring HA for Oracle:

• The clsetup utility. For more information, see How to Register and Configure HA for Oracle (clsetup).

• Oracle Solaris Cluster maintenance commands. For more information, see How to Register and Configure HA for Oracle Without Oracle ASM (CLI).

The clsetup utility provides a wizard for configuring HA for Oracle. The wizard reduces the possibility for configuration errors that might result from command syntax errors or omissions. This wizard also ensures that all required resources are created and that all required dependencies between resources are set.

Setting HA for Oracle Extension Properties

Use the extension properties in Appendix A, HA for Oracle Extension Properties to create your resources. To set an extension property of a resource, include the option -p property=value in the clresource command that creates or modifies the resource. Use the procedure in Chapter 2, Administering Data Service Resources, in Oracle Solaris Cluster Data Services Planning and Administration Guide to configure the extension properties if you have already created your resources.

You can update some extension properties dynamically. You can update others, however, only when you create or disable a resource. The Tunable entries indicate when you can update each property. See the r_properties(5) man page for details about all Oracle Solaris Cluster resource properties.

SUNW.oracle_server Extension Properties describes the extension properties that you can set for the Oracle server. For the Oracle server, you are required to set only the following extension properties:

• Oracle_home

• Oracle_sid

• Db_unique_name

How to Register and Configure HA for Oracle (clsetup)

This procedure provides the long forms of the Oracle Solaris Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.

Before You Begin

Ensure that the following prerequisites are met:

• The volume manager of the cluster is configured to provide volumes on shared storage that are accessible from any node where Oracle could potentially run.

• Raw devices and file systems on the storage volumes that Oracle will use for its database are created.

• The Oracle software is installed to be accessible from all nodes where Oracle could potentially run.

• Kernel variables for the UNIX operating system are configured for Oracle.

• The Oracle software is configured for all nodes that could potentially run Oracle.

• The data service packages are installed.

Ensure that you have the following information:

• The names of the cluster nodes that master the data service.

• The path to the Oracle application binaries for the resources that you plan to configure.

• The database type.

1. Become superuser on any cluster node.
2. Start the clsetup utility.

   # clsetup

   The clsetup main menu is displayed.

3. Type the number that corresponds to the option for data services and press Return.

   The Data Services menu is displayed.

4. Type the number that corresponds to the option for configuring HA for Oracle and press Return.

   The clsetup utility displays the list of prerequisites for performing this task.

5. Verify that the prerequisites are met, and press Return.

   The clsetup utility displays a list of the cluster nodes.

6. Select the nodes where you require Oracle to run.
   • To accept the default selection of all listed nodes in an arbitrary order, press Return.
   • To select a subset of the listed nodes, type a comma-separated or space-separated list of the numbers that correspond to the nodes. Then press Return.

     Ensure that the nodes are listed in the order in which the nodes are to appear in the node list of the resource group in which the Oracle resource is to be placed.

   • To select all nodes in a particular order, type a comma-separated or space-separated ordered list of the numbers that correspond to the nodes and press Return.

     Ensure that the nodes are listed in the order in which the nodes are to appear in the node list of the resource group in which the Oracle resource is to be placed.

7. To confirm your selection of nodes, type d and press Return.

   The clsetup utility displays the types of Oracle components that are to be configured.

8. Type the numbers of the Oracle components you want to configure and press Return.

   The clsetup utility lists the Oracle home directory.

9. Specify the Oracle home directory for your installation of the Oracle software.
   • If the directory is listed, select the directory as follows:
     1. Type the number that corresponds the directory that you are selecting.

        The clsetup utility displays a list of Oracle system identifiers that are configured on the cluster. The utility also prompts you to specify the system identifier for your installation of Oracle.

   • If the directory is not listed, specify the directory explicitly.
     1. Type e and press Return.

        The clsetup utility prompts you for the Oracle home directory.

     2. Type the full path to the Oracle home directory and press Return.

        The clsetup utility displays a list of Oracle system identifiers that are configured on the cluster. The utility also prompts you to specify the system identifier for your installation of Oracle.

10. Specify the Oracle SID of the Oracle database that you are configuring.
    • If the SID is listed, select the SID as follows:
      1. Type the number that corresponds the SID that you are selecting.

         The clsetup utility displays the properties of the Oracle Solaris Cluster resources that the utility will create.

    • If the SID is not listed, specify the SID explicitly.
      1. Type e and press Return.

         The clsetup utility prompts you for the SID.

      2. Type the SID and press Return.

         The clsetup utility displays the properties of the Oracle Solaris Cluster resources that the utility will create.

    The clsetup utility displays the properties of the Oracle Solaris Cluster resources that the utility will create.

11. If you require a different name for any Oracle Solaris Cluster resources properties, change each value as follows.
    1. Type the number that corresponds to the name that you are changing and press Return.

       The clsetup utility displays a screen where you can specify the new name.

    2. At the New Value prompt, type the new name and press Return.

    The clsetup utility returns you to the list of the properties of the Oracle Solaris Cluster resource that the utility will create.

12. To confirm your selection of Oracle Solaris Cluster resource properties, type d and press Return.

    The clsetup utility displays a list of existing storage resources. If no storage resources are available, the clsetup utility displays a list of shared storage types where data is to be stored.

13. Type the numbers that correspond to type of shared storage that you are using for storing the data and press Return.

    The clsetup utility displays the file-system mount points that are configured in the cluster.

14. Select the file system mount points as follows.
    • To accept the default selection of all listed file-system mount points in an arbitrary order, type a. Then press Return.
    • To select a subset of the listed filea system mount points, type a comma-separated or space-separated list of the numbers that correspond to the file-system mount points. Then press Return.

    The clsetup utility displays the global disk sets and device groups that are configured in the cluster.

15. Select the device groups as follows.
    • To accept the default selection of all listed device groups in an arbitrary order, type a and press Return.
    • To select a subset of the listed device groups, type a comma-separated or space-separated list of the numbers that correspond to the device groups and press Return.

    The clsetup utility returns to you the list of highly available storage resources.

16. Type a comma-separated or space-separated list of the numbers that correspond to the storage resources that your data service requires, and press Return.
17. To confirm your selection of Oracle Solaris Cluster storage resources, type d and press Return.

    The clsetup utility displays all the existing logical hostname resources in the cluster. If there are no logical hostname resources available, the clsetup utility prompts for the logical hostname that the resource will make highly available.

18. Specify the logical hostname and press Return.

    The clsetup utility returns to you the list of available logical hostname resources.

19. Type a comma-separated or space-separated list of the numbers that correspond to the logical hostname resources that your data service requires, and press Return.
20. To confirm your selection of Oracle Solaris Cluster logical hostname resources, type d and press Return.

    The clsetup utility displays the names of the Oracle Solaris Cluster objects that the utility will create.

21. If you require a different name for any Oracle Solaris Cluster objects, change each name as follows.
    • Type the number that corresponds to the name that you are changing and press Return.

      The clsetup utility displays a screen where you can specify the new name.

    • At the New Value prompt, type the new name and press Return.

      The clsetup utility returns you to the list of the names of the Oracle Solaris Cluster objects that the utility will create.

22. To confirm your selection of Oracle Solaris Cluster object names, type d and press Return.
23. To create the configuration, type c and Press Return.

    The clsetup utility displays a progress message to indicate that the utility is running commands to create the configuration. When configuration is complete, the clsetup utility displays the commands that the utility ran to create the configuration.

24. Press Return to continue.
25. (Optional) Type q and press Return repeatedly until you quit the clsetup utility.

    If you prefer, you can leave the clsetup utility running while you perform other required tasks before using the utility again.

How to Register and Configure HA for Oracle Without Oracle ASM (CLI)

This procedure provides the long forms of the Oracle Solaris Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.

Before You Begin

Ensure that the following prerequisites are met:

• The volume manager of the cluster is configured to provide volumes on shared storage that are accessible from any node where Oracle could potentially run.

• Raw devices and file systems on the storage volumes that Oracle will use for its database are created.

• The Oracle software is installed to be accessible from all nodes where Oracle could potentially run.

• Kernel variables for the UNIX operating system are configured for Oracle.

• The Oracle software is configured for all nodes that could potentially run Oracle.

• The data service packages are installed.

Ensure that you have the following information:

• The names of the cluster nodes that master the data service.

• The logical hostname that clients use to access the data service. Normally, you set up this IP address when you install the cluster. See the Oracle Solaris Cluster Concepts Guide for details about network resources.

• The path to the Oracle application binaries for the resources that you plan to configure.

• The database type.

1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify and solaris.cluster.admin RBAC authorizations.
2. Register the resource types for the data service.

   For HA for Oracle, you register two resource types, SUNW.oracle_server and SUNW.oracle_listener, as follows.

   ---

   Note - If you are using an Oracle Grid Infrastructure for Clusters Single Client Access Name (SCAN) listener, omit registration of the SUNW.oracle_listener resource type.

   ---

   # clresourcetype register SUNW.oracle_server
   # clresourcetype register SUNW.oracle_listener

3. Create a failover resource group to hold the network and application resources.

   This step is not required if you use the Oracle Solaris ZFS file system, because the resource group was created when the highly available local ZFS file system was configured in How to Prepare the Nodes. The resources that are created in other steps in this procedure are to be added to this resource group.

   You can optionally select the set of nodes on which the data service can run with the -n option, as follows.

   # clresourcegroup create [-n node-zone-list] resource-group

   resource-group

   Specifies the name of the resource group. This name can be your choice but must be unique for resource groups within the cluster.

4. Verify that all of the network resources that you use have been added to your name service database.

   You should have performed this verification during the Oracle Solaris Cluster installation.

   ---

   Note - Ensure that all of the network resources are present in the server's and client's /etc/inet/hosts file to avoid any failures because of name service lookup.

   ---

5. Add a logical hostname resource to the failover resource group.

   # clreslogicalhostname create -g resource-group [-h logicalhostname] logicalhostname-rs

   logicalhostname

   Specifies a logical hostname. This logical hostname must present in your name service database. If logicalhostname and logicalhostname-rs are identical, logicalhostname is optional.

   logicalhostname-rs

   Specifies the name that you are assigning to the logical hostname resource that you are creating.

6. Register the HAStoragePlus resource type with the cluster.

   # clresourcetype register SUNW.HAStoragePlus

7. Add a resource of type HAStoragePlus to the failover resource group.

   ---

   Note - If you use the Oracle Solaris ZFS file system for Oracle files, omit this step. The HAStoragePlus resource was created when the highly available local ZFS file system was configured. For more information, see How to Prepare the Nodes.

   ---

   ---

   Caution - Raw devices from Oracle Solaris Cluster device groups are not supported in non-global zones.

   ---

   # clresource create -g resource-group -t SUNW.HAStoragePlus \
   -p GlobalDevicePaths=device-path \
   -p FilesystemMountPoints=mount-point-list \
   -p AffinityOn=TRUE hastp-rs

   You must set either the GlobalDevicePaths extension property or the FilesystemMountPoints extension property:

   • If your database is on a raw device, set the GlobalDevicePaths extension property to the global device path.

   • If your database is on the cluster file system, specify mount points of the cluster file system and the local file system.

   ---

   Note - AffinityOn must be set to TRUE and the local file system must reside on global disk groups to be failover.

   ---

   The resource is created in the enabled state.

8. Bring online the failover resource group in a managed state on a cluster node.

   # clresourcegroup online -M resource-group

   -M

   Places the resource group that is brought online in a managed state.

9. Create Oracle application resources in the failover resource group.

   ---

   Note - If you are using an Oracle Grid Infrastructure for Clusters Single Client Access Name (SCAN) listener, omit configuration of the SUNW.oracle_listener resource.

   ---

   • Oracle server resource:

     # clresource create -g resourcegroup \
     -t SUNW.oracle_server \ 
     -p Oracle_sid=instance \
     -p Oracle_home=Oracle_home \
     -p Db_unique_name=db-unique-name \
     -p Restart_type=entity-to-restart \
     [-p Dataguard_role=role] \
     [-p Standby_mode=mode] \
     -p Resource_dependencies_offline_restart=storageplus-resource \
      resource

   • Oracle listener resource:

     # clresource create -g resource-group \
     -t SUNW.oracle_listener \ 
     -p Listener_name=listener \
     -p Oracle_home=Oracle_home \
     -p Resource_dependencies_offline_restart=storageplus-resource \
     resource

   -g resource-group

   Specifies the name of the resource group into which the resources are to be placed.

   -t

   Specifies the type of the resource to add.

   -p Oracle_sid=instance

   Sets the Oracle system identifier.

   -p Listener_name=listener

   Sets the name of the Oracle listener instance. This name must match the corresponding entry in listener.ora.

   -p Oracle_home=Oracle_home

   Sets the path to the Oracle home directory.

   -p Db_unique_name=db-unique-name

   Sets the unique name of the database.

   -p Restart_type=entity-to-restart

   Specifies the entity that the server fault monitor restarts when the response to a fault is restart. Set entity-to-restart as follows:

   • To specify that only this resource is restarted, set entity-to-restart to RESOURCE_RESTART. By default, only this resource is restarted.

   • To specify that all resources in the resource group that contains this resource are restarted, set entity-to-restart to RESOURCE_GROUP_RESTART.

     If you set entity-to-restart to RESOURCE_GROUP_RESTART, all other resources (such as Apache or DNS) in the resource group are restarted, even if they are not faulty. Therefore, include in the resource group only the resources that you require to be restarted when the Oracle server resource is restarted.

   -p Dataguard_role=role

   Specifies the role of the database instance. Change role as follows:

   • To create a resource for a primary database instance that does not have standby instances configured, change role to NONE. This value is the default value.

   • To create a resource for a primary database instance that has standby database instances configured, change role to PRIMARY.

   • To create a resource for a standby database instance, change role to STANDBY.

   -p Standby_mode=mode

   Specifies the mode for the standby database instance. If you change Dataguard_role to NONE or PRIMARY, the value of the Standby_mode is ignored.

   • To specify a logical standby database, change mode to LOGICAL. This value is the default value.

   • To specify a physical standby database, change mode to PHYSICAL.

   • To specify a snapshot standby database, change mode to SNAPSHOT.

   resource

   Specifies the name of the resource that you are creating.

   ---

   Note - Optionally, you can set additional extension properties that belong to the Oracle data service to override their default values. See Setting HA for Oracle Extension Properties for a list of extension properties.

   ---

   The resources are created in the enabled state.

Example 1-1 Registering HA for Oracle to Run in the Global Zone

This example shows how to register HA for Oracle on a two-node cluster. The following are the sample names used in the commands:

Node names

phys-schost-1, phys-schost-2

Logical hostname

schost-1

Resource group

resource-group-1 (failover resource group)

HAStoragePlus resource

hastp-rs

Oracle resources

oracle-server-1, oracle-listener-1

Oracle instances

ora-lsnr (listener), ora-srvr (server)

Oracle database unique name

dbcloud

Create the failover resource group to contain all of the resources.
# clresourcegroup create resource-group-1
 
Add the logical hostname resource to the resource group.
# clreslogicalhostname create -g resource-group-1 schost-1 
 
Register the SUNW.HAStoragePlus resource type.
# clresourcetype register SUNW.HAStoragePlus

Add a resource of type SUNW.HAStoragePlus to the resource group.
# clresource create -g resource-group-1 \
-t SUNW.HAStoragePlus \
-p FileSystemMountPoints=/global/oracle,/global/ora-data/logs,/local/ora-data \
-p AffinityOn=TRUE \
hastp-rs
Bring the resource group online in a managed state
# clresourcegroup online -M resource-group-1

Register the Oracle resource types.
# clresourcetype register SUNW.oracle_server
# clresourcetype register SUNW.oracle_listener
 
Add the Oracle application resources to the resource group.
# clresource create -g resource-group-1 \
-t SUNW.oracle_server \
-p Oracle_home=/global/oracle \
-p Oracle_sid=ora-srvr \
-p Db_unique_name=dbcloud \
-p Dataguard_role=STANDBY \
-p Standby_mode=PHYSICAL \
-p Resource_dependencies_offline_restart=hastp-rs \
oracle-server-1
 
# clresource create -g resource-group-1 \
-t SUNW.oracle_listener \
-p Oracle_home=/global/oracle \
-p Listener_name=ora-lsnr \
oracle-listener-1

Example 1-2 Registering HA for Oracle to Run in a Zone Cluster

This example shows how to register HA for Oracle in a zone cluster. The following are the sample names used in the commands, which are issued from the global cluster:

Node names

phys-schost-1, phys-schost-2

Zone cluster names

zonecluster1, zonecluster2

Logical hostname

zchost-1

Resource group

resource-group-1 (failover resource group)

HAStoragePlus resource

hastp-rs

Oracle resources

oracle-server-1, oracle-listener-1

Oracle instances

ora-lsnr (listener), ora-srvr (server)

Oracle database unique name

dbcloud

Create the failover resource group to contain all of the resources.)
# clresourcegroup create -Z zonecluster1 resource-group-1
 
Add the logical hostname resource to the resource group.)
# clreslogicalhostname create -Z zonecluster1 -g resource-group-1 zchost-1 
 
Register the SUNW.HAStoragePlus resource type.)
# clresourcetype register -Z zonecluster1 SUNW.HAStoragePlus

Add a resource of type SUNW.HAStoragePlus to the resource group.)
# clresource create -Z zonecluster1 \
-g resource-group-1 \
-t SUNW.HAStoragePlus \
-p FileSystemMountPoints=/global/oracle,/global/ora-data/logs,/local/ora-data \
-p AffinityOn=TRUE \
hastp-rs

Bring the resource group online in a managed state
# clresourcegroup online -Z zonecluster1 -M resource-group-1

Register the Oracle resource types.)
# clresourcetype register -Z zonecluster1 SUNW.oracle_server
# clresourcetype register -Z zonecluster1 SUNW.oracle_listener
 
Add the Oracle application resources to the resource group.)
# clresource create -Z zonecluster1 \
-g resource-group-1 \
-t SUNW.oracle_server \
-p Oracle_home=/global/oracle \
-p Oracle_sid=ora-srvr \
-p Db_unique_name=dbcloud \
-p Dataguard_role=STANDBY \
-p Standby_mode=PHYSICAL \
oracle-server-1
 
# clresource create -Z zonecluster1 -g resource-group-1 \
-t SUNW.oracle_listener \
-p Oracle_home=/global/oracle \
-p Listener_name=ora-lsnr \
oracle-listener-1

How to Create an Oracle Grid Infrastructure Resource With Clustered Oracle ASM Disk Groups and a Third-Party Volume Manager (CLI)

Perform this procedure to include a third-party volume manager with clustered Oracle ASM disk groups in your configuration that uses clustered Oracle ASM. This procedure uses Oracle Grid Infrastructure (Grid Infrastructure) commands and Oracle Solaris Cluster maintenance commands.

Use this procedure to manually create an Oracle Grid Infrastructure resource that proxies the Oracle Solaris Cluster SUNW.ScalDeviceGroup resource. In this procedure, the Grid Infrastructure resource is named sun.resource. You configure sun.resource to ensure that the corresponding Oracle ASM disk group is not mounted until sun.resource is online. The sun.resource resource comes online only if the corresponding SUNW.ScalDeviceGroup resource is online. And the SUNW.ScalDeviceGroup resource only comes online if the actual volume-manager disk set or disk group is online.

To ensure that the Oracle ASM disk group benefits from this dependency chain, after you define sun.resource, you modify the appropriate Grid Infrastructure Oracle ASM disk-group resource so that the hard-start dependency includes sun.resource. Modifying the hard-start dependency of the Grid Infrastructure Oracle ASM disk-group resource can only be performed by the SUNW.scalable_asm_diskgroup_proxy resource by using the VALIDATE method. Therefore, you must set an offline-restart dependency between the SUNW.scalable_asm_diskgroup_proxy and SUNW.ScalDeviceGroup resources.

Before You Begin

Configure the disk set or disk group for clustered Oracle ASM to use.

• If you are using Solaris Volume Manager for Sun Cluster, create a multi-owner disk set. Follow procedures in How to Create a Multi-Owner Disk Set in Solaris Volume Manager for Sun Cluster for the Oracle RAC Database in Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide.

1. Become superuser.
2. Create the Grid Infrastructure sun.storage_proxy.type resource type.

   # /Grid_home/bin/crsctl add type sun.storage_proxy.type -basetype cluster_resource

3. Create a Grid Infrastructure sun.resource resource of type sun.storage_proxy.type.

   ---

   Note - Ensure that all attribute values are enclosed in single quotes ('). Otherwise, the VALIDATE method of the SUNW.scalable_asm_diskgroup_proxy resource will fail the validation.

   ---

   # /Grid_home/bin/crsctl add res sun.scal-asmdg1-rs -type sun.storage_proxy.type \
   -attr "ACTION_SCRIPT='/opt/SUNWscor/dsconfig/bin/scproxy_crs_action' \
   HOSTING_MEMBERS='node1 node2' \
   CARDINALITY='2' \
   PLACEMENT='restricted' \
   ACL='owner:root:rwx,pgrp:oinstall:rwx,other::r--' \
   SCRIPT_TIMEOUT='20' \
   RESTART_ATTEMPTS='60'"

   sun.scal-asmdg1-rs

   The SUNW.ScalDeviceGroup resource name.

   -type sun.storage_proxy.type

   Specifies the sun.storage_proxy.type resource type.

   ACTION_SCRIPT

   Specifies the /opt/SUNWscor/dsconfig/bin/scproxy_crs_action action script.

   HOSTING_MEMBERS

   Specifies the Oracle Solaris Cluster resource group's node list entries that contain the SUNW.ScalDeviceGroup resource.

   CARDINALITY

   Sets the number of hosts that are defined in HOSTING_MEMBERS.

   PLACEMENT

   Set to restricted.

   ACL

   Sets the owner equal to root and the group equal to the ACL group entry for the Oracle ASM disk group. The following example command displays the ACL group entry, oinstall:

   # /Grid_home/bin/crsctl stat res ora.DATA1.dg -p | grep ACL=
   ACL=owner:oragrid:rwx,pgrp:oinstall:rwx,other::r--

   SCRIPT_TIMEOUT

   Set to 20.

   RESTART_ATTEMPTS

   Set to 60.

4. Verify that sun.resource is correctly defined.

   Output is similar to the following:

   # /Grid_home/bin/crsctl stat res sun.scal-asmdg1-rs -p
         NAME=sun.scal-asmdg1-rs
         TYPE=sun.storage_proxy.type
         ACL=owner:root:rwx,pgrp:oinstall:rwx,other::r--
         ACTION_FAILURE_TEMPLATE=
         ACTION_SCRIPT=/opt/SUNWscor/dsconfig/bin/scproxy_crs_action
         ACTIVE_PLACEMENT=0
         AGENT_FILENAME=%CRS_HOME%/bin/scriptagent
         AUTO_START=restore
         CARDINALITY=2
         CHECK_INTERVAL=60
         DEFAULT_TEMPLATE=
         DEGREE=1
         DESCRIPTION=
         ENABLED=1
         FAILOVER_DELAY=0
         FAILURE_INTERVAL=0
         FAILURE_THRESHOLD=0
         HOSTING_MEMBERS=node1 node2
         LOAD=1
         LOGGING_LEVEL=1
         NOT_RESTARTING_TEMPLATE=
         OFFLINE_CHECK_INTERVAL=0
         PLACEMENT=restricted
         PROFILE_CHANGE_TEMPLATE=
         RESTART_ATTEMPTS=60
         SCRIPT_TIMEOUT=20
         SERVER_POOLS=
         START_DEPENDENCIES=
         START_TIMEOUT=0
         STATE_CHANGE_TEMPLATE=
         STOP_DEPENDENCIES=
         STOP_TIMEOUT=0
         UPTIME_THRESHOLD=1h
   #

5. Set the offline-restart dependency to add a dependency.
   1. Display the current dependency.

      # /Grid_home/bin/crsctl stat res ora.DATA1.dg -p | grep START_DEPENDENCIES
                  START_DEPENDENCIES=hard(ora.asm) pullup(ora.asm)
      
      # clresource show -p Resource_dependencies_offline_restart asm-data1-rs
      
                  === Resources ===
      
                  Resource: asm-data1-rs
                  Resource_dependencies_offline_restart: asm-inst-rs
      
                  -- Standard and extension properties --

   2. Set the new dependency.
      • If asm-data1-rs already exists, use the following command to set the dependency.

        Note that the command includes the plus (+) symbol:

        # clresource set -p Resource_dependencies_offline_restart+=scal-asmdg1-rs asm-data1-rs

      • If asm-data1-rs does not yet exist, use the following command to create the resource with the offline-restart dependency:

        # clresource create -g asm-dg-rg \ -t SUNW.scalable_asm_diskgroup_proxy \ -p asm_diskgroups=data1 \ -p Resource_dependencies_offline_restart=asm-inst-rs,scal-asmdg1-rs \ -d asm-data1-rs

   3. Verify the configured dependency.

      # /Grid_home/bin/crsctl stat res ora.DATA1.dg -p | grep START_DEPENDENCIES
                  START_DEPENDENCIES=hard(ora.asm,sun.scal-asmdg1-rs) pullup(ora.asm)
      # clresource show -p Resource_dependencies_offline_restart asm-data1-rs
                  === Resources ===
                   
                  Resource: asm-data1-rs
                  Resource_dependencies_offline_restart: asm-inst-rs scal-asmdg1-rs
                   
                  -- Standard and extension properties --

Next Steps

Go to How to Register and Configure HA for Oracle With Clustered Oracle ASM Instance (CLI).

How to Register and Configure HA for Oracle With Clustered Oracle ASM Instance (CLI)

This procedure explains the steps to register and configure HA for Oracle with clustered Oracle ASM instance using Oracle Solaris Cluster maintenance commands.

1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify and solaris.cluster.admin RBAC authorizations.

   ---

   Note - You can also use the clsetup utility to perform the steps 1 to 6 in the procedure.

   ---

2. Register the resource types for Oracle RAC framework and Oracle Clusterware framework.

   # clresourcetype register SUNW.rac_framework
   # clresourcetype register SUNW.crs_framework

3. Create a scalable resource group rac-fmwk-rg.

   # clresourcegroup create -S rac-fmwk-rg

4. Add a resource of type SUNW.rac_framework to the rac-fmwk-rg resource group.

   # clresource create -g rac-fmwk-rg -t SUNW.rac_framework rac-fmwk-rs

5. Add a resource of type SUNW.crs_framework to the rac-fmwk-rg resource group.

   # clresource create -g rac-fmwk-rg -t SUNW.crs_framework \
   -p Resource_dependencies_offline_restart=rac-fmwk-rs \
   -d crs-fmwk-rs

6. Create a failover resource group ora-db-rg for the Oracle database.

   # clresourcegroup create ora-db-rg

7. Register the SUNW.HAStoragePlus resource type and create a resource group.

   ---

   Note - For information on how to set up a file system, see Preparing the Nodes and Disks.

   ---

8. Register the Oracle ASM resource types for the data service.
   1. Register the scalable ASM instance proxy resource type.

      # clresourcetype register SUNW.scalable_asm_instance_proxy

   2. Register the appropriate ASM disk-group resource type.

      # clresourcetype register SUNW.scalable_asm_diskgroup_proxy

9. Create resource groups asm-inst-rg and asm-dg-rg.

   # clresourcegroup create -S asm-inst-rg asm-dg-rg

10. Set a strong positive affinity on rac-fmwk-rg by asm-inst-rg.

    # clresourcegroup set -p Rg_affinities=++rac-fmwk-rg asm-inst-rg

11. Set a strong positive affinity on asm-inst-rg by asm-dg-rg.

    # clresourcegroup set -p Rg_affinities=++asm-inst-rg asm-dg-rg

12. Add a resource of type SUNW.crs_framework to the rac-fmwk-rg resource group.

    # clresource create -g rac-fmwk-rg \
    -t SUNW.crs_framework \
    -p Resource_dependencies_offline_restart=rac-fmwk-rs \
    -d crs-fmwk-rs

13. Add a resource of type SUNW.scalable_asm_instance_proxy to the asm-inst-rg resource group.

    # clresource create -g asm-inst-rg \
    -t SUNW.asm_instance_proxy \
    -p Oracle_home=Oracle_home \
    -p "oracle_sid{node1}"=instance \
    -p "oracle_sid{node2}"=instance \
    -p Resource_dependencies_offline_restart=crs-fmwk-rs \
    -d asm-inst-rs

    -g asm-inst-rg

    Specifies the name of the resource group into which the resources are to be placed.

    -t SUNW.asm_inst_proxy

    Specifies the type of the resource to add.

    -p oracle_sid{node}=instance

    Sets the Oracle system identifier.

    -p Oracle_home=Oracle_home

    Sets the path to the Oracle home directory.

    -p Resource_dependencies_offline_restart=crs-fmwk-rs

    Specifies the offline restart dependency.

    -d asm-inst-rs

    Specifies the name of the resource that you are creating.

14. Add an ASM disk-group resource to the asm-dg-rg resource group.

    Use the SUNW.scalable_asm_diskgroup_proxy resource type.

    # clresource create -g asm-dg-rg -t SUNW.scalable_asm_diskgroup_proxy \
    -p Asm_diskgroups=dg[,dg…] \
    -p Resource_dependencies_offline_restart=asm-inst-rs,asm-stor-rs \
    -d asm-dg-rs

15. Bring online the asm-inst-rg resource group in a managed state on a cluster node.

    # clresourcegroup online -eM asm-inst-rg

16. Bring online the asm-dg-rg resource group in a managed state on a cluster node.

    # clresourcegroup online -eM asm-dg-rg

17. Verify the Oracle ASM installation by issuing the status command.

    # clresource status +

18. Register the resource types for the HA for Oracle data service.

    For HA for Oracle, you register two resource types, SUNW.oracle_server and SUNW.oracle_listener, as follows.

    ---

    Note - If you are using an Oracle Grid Infrastructure for Clusters Single Client Access Name (SCAN) listener, omit registration of the SUNW.oracle_listener resource type.

    ---

    # clresourcetype register SUNW.oracle_server
    # clresourcetype register SUNW.oracle_listener

19. Add a logical hostname resource to the failover resource group for Oracle database.

    # clreslogicalhostname create -g ora-db-rg [-h logicalhostname] \
    logicalhostname-rs

    logicalhostname

    Specifies a logical hostname. This logical hostname must present in your name service database. If logicalhostname and logicalhostname-rs are identical, logicalhostname is optional.

    logicalhostname-rs

    Specifies the name that you are assigning to the logical hostname resource that you are creating.

20. Bring online the failover resource group in a managed state on a cluster node.

    # clresourcegroup online -eM ora-db-rg

21. Create Oracle application resources in the failover resource group.

    ---

    Note - If you are using an Oracle Grid Infrastructure for Clusters Single Client Access Name (SCAN) listener, omit configuration of the SUNW.oracle_listener resource.

    ---

    • Oracle server resource:

      # clresource create -g ora-db-rg \
      -t SUNW.oracle_server \
      -p Oracle_sid=instance \
      -p Oracle_home=Oracle_home \
      -p Db_unique_home=db-unique-home \
      -p Resource_dependencies_offline_restart=asm-dg-rs \
      -d ora-db-rs

    • Oracle listener resource:

      # clresource create -g ora-db-rg \
      -t SUNW.oracle_listener \
      -p Oracle_home=Oracle_home \
      -p Listener_name=listener \
      -p Resource_dependencies_offline_restart=asm-dg-rs \
      -d ora-ls-rs

    -g ora-db-rg

    Specifies the name of the resource group into which the resources are to be placed.

    -t SUNW.oracle_server/listener

    Specifies the type of the resource to add.

    -p Oracle_sid=instance

    Sets the Oracle system identifier.

    -p Oracle_home=Oracle_home

    Sets the path to the Oracle home directory.

    -p Db_unique_name=db-unique-name

    Sets the Oracle database unique name.

    -p listener_name=listener

    Sets the name of the Oracle listener instance. This name must match the corresponding entry in listener.ora.

    -d ora-ls-rs

    Specifies the name of the resource that you are creating.

    ---

    Note - Optionally, you can set additional extension properties that belong to the Oracle data service to override their default values. See Setting HA for Oracle Extension Properties for a list of extension properties.

    ---

22. Bring online the Oracle server resource.

    # clresource enable ora-db-rs

23. If configured, bring online the Oracle listener resource.

    # clresource enable ora-ls-rs

Where to Go From Here

Go to Verifying the HA for Oracle Installation after you register and configure HA for Oracle.