Installing and Configuring HA for Oracle
Overview of the Installation and Configuration Process for HA for Oracle
Planning the HA for Oracle Installation and Configuration
Configuration Planning Questions
How to Configure the Oracle Database Access Using Solaris Volume Manager
How to Configure the Oracle Database Access Using Veritas Volume Manager
How to Configure the Oracle Database Access Using Oracle ASM
How to Install the Oracle ASM Software
How to Verify the Oracle ASM Software Installation
Installing the Oracle Software
How to Install the Oracle Software
How to Set the Oracle Kernel Parameters
Verifying the Oracle Installation and Configuration
How to Verify the Oracle Installation
How to Create a Primary Oracle Database
Setting Up Oracle Database Permissions
How to Set Up Oracle Database Permissions
Installing the HA for Oracle Packages
How to Install the HA for Oracle Packages
Registering and Configuring HA for Oracle
Tools for Registering and Configuring HA for Oracle
Setting HA for Oracle Extension Properties
How to Register and Configure HA for Oracle by Using the clsetup Utility
Verifying the HA for Oracle Installation
How to Verify the HA for Oracle Installation
Location of HA for Oracle Log Files
Tuning the HA for Oracle Fault Monitors
Operation of the Oracle Server Fault Monitor
Operation of the Main Fault Monitor
Operation of the Database Client Fault Probe
Operations to Monitor the Partition for Archived Redo Logs
Operations to Determine Whether the Database is Operational
Actions by the Server Fault Monitor in Response to a Database Transaction Failure
Scanning of Logged Alerts by the Server Fault Monitor
Operation of the Oracle Listener Fault Monitor
Obtaining Core Files for Troubleshooting DBMS Timeouts
Customizing the HA for Oracle Server Fault Monitor
Defining Custom Behavior for Errors
Changing the Response to a DBMS Error
Responding to an Error Whose Effects Are Major
Ignoring an Error Whose Effects Are Minor
Changing the Response to Logged Alerts
Changing the Maximum Number of Consecutive Timed-Out Probes
Propagating a Custom Action File to All Nodes in a Cluster
Specifying the Custom Action File That a Server Fault Monitor Should Use
How to Specify the Custom Action File That a Server Fault Monitor Should Use
Upgrading HA for Oracle Resource Types
Upgrading the SUNW.oracle_listener Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
Upgrading the SUNW.oracle_server Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
Changing the Role of an Oracle Data Guard Instance
How to Change the Role of an Oracle Data Guard Instance
A. HA for Oracle Extension Properties
B. Preset Actions for DBMS Errors and Logged Alerts
Oracle Solaris Cluster provides the following tools for registering and configuring HA for Oracle:
The clsetup(1CL) utility. For more information, see How to Register and Configure HA for Oracle by Using the clsetup Utility.
Oracle Solaris Cluster Manager. For more information, see the Oracle Solaris Cluster Manager online help.
Oracle Solaris Cluster maintenance commands. For more information, see How to Register and Configure HA for Oracle Without Oracle ASM Using Oracle Solaris Cluster Maintenance Commands.
The clsetup utility and Oracle Solaris Cluster Manager each provide a wizard for configuring HA for Oracle. The wizards reduce the possibility for configuration errors that might result from command syntax errors or omissions. These wizards also ensure that all required resources are created and that all required dependencies between resources are set.
Use the extension properties in 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(1CL) 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 Appendix A, Standard Properties, in Oracle Solaris Cluster Data Services Planning and Administration Guide for details about all Solaris Cluster 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
Alert_log_file
Connect_string
This procedure provides the long forms of the Solaris Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.
Note - The clsetup utility does not support configuration of HA for Oracle with ZFS.
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 or zones where Oracle could potentially run.
Kernel variables for the UNIX operating system are configured for Oracle.
The Oracle software is configured for all nodes or zones that could potentially run Oracle.
The data service packages are installed.
Ensure that you have the following information:
The names of the cluster nodes or zones 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.
# clsetup
The clsetup main menu is displayed.
The Data Services menu is displayed.
The clsetup utility displays the list of prerequisites for performing this task.
The clsetup utility displays a list of the cluster nodes.
Ensure that the nodes or zones are listed in the order in which the nodes or zones are to appear in the node list of the resource group in which the Oracle resource is to be placed. The first node or zone in the list is the primary node or zone of this resource group.
Ensure that the nodes or zones are listed in the order in which the nodes or zones are to appear in the node list of the resource group in which the Oracle resource is to be placed. The first node or zone in the list is the primary node or zone of this resource group.
The clsetup utility displays the types of Oracle components that are to be configured.
The clsetup utility lists the Oracle home directory.
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.
The clsetup utility prompts you for the Oracle home directory.
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.
The clsetup utility displays the properties of the Solaris Cluster resources that the utility will create.
The clsetup utility prompts you for the SID.
The clsetup utility displays the properties of the Solaris Cluster resources that the utility will create.
The clsetup utility displays the properties of the Solaris Cluster resources that the utility will create.
The clsetup utility displays a screen where you can specify the new name.
The clsetup utility returns you to the list of the properties of the Oracle Solaris Cluster resource that the utility will create.
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.
The clsetup utility displays the file-system mount points that are configured in the cluster.
The clsetup utility displays the global disk sets and device groups that are configured in the cluster.
The clsetup utility returns to you the list of highly available storage resources.
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 is to make highly available.
The clsetup utility returns to you the list of available logical hostname resources.
The clsetup utility displays the names of the Solaris Cluster objects that the utility will create.
The clsetup utility displays a screen where you can specify the new name.
The clsetup utility returns you to the list of the names of the Oracle Solaris Cluster objects that the utility will create.
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.
If you prefer, you can leave the clsetup utility running while you perform other required tasks before using the utility again.
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 or zones where Oracle could potentially run.
Kernel variables for the UNIX operating system are configured for Oracle.
The Oracle software is configured for all nodes or zones that could potentially run Oracle.
The data service packages are installed.
Ensure that you have the following information:
The names of the cluster nodes or zones 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.
For HA for Oracle, you register two resource types, SUNW.oracle_server and SUNW.oracle_listener, as follows.
# clresourcetype register SUNW.oracle_server # clresourcetype register SUNW.oracle_listener
This step is not required if you use the Solaris ZFS, because the resource group was created when the highly available local ZFS was configured. 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 or zones on which the data service can run with the -n option, as follows.
# clresourcegroup create [-n node-zone-list] resource-group
Specifies a comma-separated, ordered list of zones that can master this resource group. The format of each entry in the list is node:zone. In this format, node specifies the name or ID of a node and zone specifies the name of a non-global Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node.
The order in this list determines the order in which the nodes or zones are considered primary during failover. This list is optional. If you omit this list, the global zone of each cluster node can master the 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.
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.
# clreslogicalhostname create -g resource-group [-h logicalhostname] \ logicalhotname-rs
Specifies a logical hostname. This logical hostname must present in your name service database. If logicalhostname and logicalhostname-rs are identical, logicalhostname is optional.
Specifies the name that you are assigning to the logical hostname resource that you are creating.
# clresourcetype register SUNW.HAStoragePlus
Caution - Raw devices from Oracle Solaris Cluster device groups are not supported in non-global zones. |
Note - The SUNW.HAStoragePlus resource type must be version 4 if it is to be supported in non-global zones.
Note - If you use the Solaris ZFS for Oracle files, omit this step. The SUNW.HAStoragePlus resource was created when the highly available local ZFS was configured. For more information, see How to Prepare the Nodes.
# 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.
# clresourcegroup online -M resource-group
Places the resource group that is brought online in a managed state.
Oracle server resource:
# clresource create -g resourcegroup \ -t SUNW.oracle_server \ -p Connect_string=user/passwd \ -p ORACLE_SID=instance \ -p ORACLE_HOME=Oracle-home \ -p Alert_log_file=path-to-log \ -p Restart_type=entity-to-restart \ [-p Dataguard_role=role] \ [-p Standby_mode=mode] \-p resource_dependencies=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=storageplus-resource resource
Specifies the name of the resource group into which the resources are to be placed.
Specifies the type of the resource to add.
Sets the path under $ORACLE_HOME for the server message log.
Specifies the user and password that the fault monitor uses to connect to the database. These settings must agree with the permissions that you set up in How to Set Up Oracle Database Permissions. If you use Solaris authorization, type a slash (/) instead of the user name and password.
Sets the Oracle system identifier.
Sets the name of the Oracle listener instance. This name must match the corresponding entry in listener.ora.
Sets the path to the Oracle home directory.
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.
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.
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.
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 Registering HA for Oracle to Run in the Global Zone
The following example shows how to register HA for Oracle on a two-node cluster.
Cluster Information 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) (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 Alert_log_file=/global/oracle/message-log \ -p ORACLE_SID=ora-srvr -p Connect_string=scott/tiger \ -p Dataguard_role=STANDBY -p Standby_mode=PHYSICAL 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 2 Registering HA for Oracle to Run in the Non-Global Zone
The following example shows how to register HA for Oracle on a two-node cluster.
Cluster Information Node names: phys-schost-1, phys-schost-2 Non-global zone names: sc1zone1, sc2zone1 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) (Create the failover resource group to contain all of the resources.) # clresourcegroup create phys-schost-1:sc1zone1,phys-schost-2:sc2zone1 \ 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 Alert_log_file=/global/oracle/message-log \ -p ORACLE_SID=ora-srvr -p Connect_string=scott/tiger \ -p Dataguard_role=STANDBY -p Standby_mode=PHYSICAL 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 3 Registering HA for Oracle to Run in a Zone Cluster
The following example shows how to register HA for Oracle in a zone cluster.
Cluster Information 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) (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 Alert_log_file=/global/oracle/message-log \ -p ORACLE_SID=ora-srvr -p Connect_string=scott/tiger \ -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
Note - Single instance Oracle ASM is not supported with Oracle 11g release 2.
This procedure explains the steps to register and configure single instance Oracle ASM using Oracle Solaris Cluster maintenance commands. The Oracle_Home for Oracle ASM is on a local file system only.
Note - Oracle ASM disk group and Oracle database can be configured in different resource groups. If the Oracle ASM disk group and Oracle database are configured in different resource groups, you should set a strong positive affinity (+++) between the Oracle ASM disk group resource group and Oracle database resource group.
# clresourcetype register SUNW.scalable_asm_instance_proxy
# clresourcetype register SUNW.asm_diskgroup
# clresourcetype register SUNW.scalable_asm_diskgroup_proxy
# clresourcegroup create -S asm-inst-rg
Specifies the name of the scalable resource group for the Oracle ASM instance.
# clreslogicalhostname create -g asm-dg-rg [-h logicalhostname] \ logicalhostname-rs
Specifies a logical hostname. This logical hostname must present in your name service database. If logicalhostname and logicalhostname-rs are identical, logicalhostname is optional.
Specifies the name that you are assigning to the logical hostname resource that you are creating.
# clresource create -g asm-inst-rg \ -t SUNW.scalable_asm_instance \ -p ORACLE_HOME=oracle-home \ -d asm-inst-rs
Specifies the name of the resource group for the Oracle ASM instance.
Sets the path to the Oracle ASM home directory.
Note - You must use only a local file system for the Oracle ASM home directory.
Specifies the name of the Oracle ASM instance resource that you are creating.
# clresourcegroup online -eM asm-inst-rg
# clresourcegroup create asm-dg-rg
# clresourcegroup set -p rg_affinities=++asm-inst-rg asm-dg-rg
# clresource create -g asm-dg-rg -t SUNW.asm_diskgroup \ -p asm_diskgroups=dg[,dg…] \ -p resource_dependencies_offline_restart=asm-inst-rs,asm-stor-rs \ -d asm-dg-rs
Specifies the type of the resource to add.
Specifies the ASM disk group.
Specifies the name of the Oracle ASM storage resource.
Specifies the name of the resource that you are creating.
# 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
# clresource online -eM asm-dg-rg
# clresource status +
For HA for Oracle, you register the resource types SUNW.oracle_server and SUNW.oracle_listener as follows.
# clresourcetype register SUNW.oracle_server # clresourcetype register SUNW.oracle_listener
Oracle server resource:
# clresource create -g asm-dg-rg \ -t SUNW.oracle_server \ -p Connect_string=user/passwd \ -p ORACLE_SID=instance \ -p ORACLE_HOME=Oracle-home \ -p Alert_log_file=path-to-log \ -p Restart_type=entity-to-restart \ -p Resource_dependencies_offline_restart=asm-dg-rs \ -d ora-db-rs
Oracle listener resource:
# clresource create -g asm-dg-rg \ -t SUNW.oracle_listener \ -p LISTENER_NAME=listener \ -p ORACLE_HOME=Oracle-home \ -p resource_dependencies_offline_restart=asm-dg-rs logicalhostname-rs \ -d ora-lsr-rs
Specifies the name of the Oracle ASM disk resource group into which the resources are to be placed.
Specifies the type of the resource to add.
Sets the path under $ORACLE_HOME for the server message log.
Specifies the user and password that the fault monitor uses to connect to the database. These settings must agree with the permissions that you set up in How to Set Up Oracle Database Permissions. If you use Solaris authorization, type a slash (/) instead of the user name and password.
Sets the Oracle system identifier.
Sets the name of the Oracle listener instance. This name must match the corresponding entry in listener.ora.
Sets the path to the Oracle home directory.
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.
# clresource enable ora-db-rs
# clresource enable ora-lsr-rs
This procedure explains the steps to register and configure HA for Oracle with clustered Oracle ASM instance using Oracle Solaris Cluster maintenance commands.
Note - You should install the Oracle Clusterware software before performing the steps in this procedure.
Note - You can also use the clsetup utility to perform the steps 1 to 6 in the procedure.
# clresourcetype register SUNW.rac_framework # clresourcetype register SUNW.crs_framework
# clresourcegroup create -S rac-fmwk-rg
# clresource create -g rac-fmwk-rg -t SUNW.rac_framework rac-fmwk-rs
# clresource create -g rac-fmwk-rg -t SUNW.crs_framework \ -p resource_dependencies=rac-fmwk-rs \ -d crs-fmwk-rs
# clresourcegroup create ora-db-rg
Note - You can perform this step only if you have installed the ORCLudlm package before performing the Oracle ASM software installation.
# clresourcetype register SUNW.rac_udlm
# clresource create -g rac-fmwk-rg -t SUNW.rac_udlm \ -p resource_dependencies=rac-fmwk-rs rac-udlm-rs
Note - You should decide the file system you are going to use for Oracle_Home and set up the file system before performing this step. For information on how to setup a file system, see Preparing the Nodes and Disks.
If you are using a QFS shared file system, perform the following steps to register the QFS shared file system resource type and create the resource groups. Otherwise, you should use the SUNW.HAStoragePlus resource type.
# clresourcetype register SUNW.qfs
# clresourcegroup create qfs-rg
# clresource create -g qfs-rg -t SUNW.qfs -p QFSFileSystem=qfs-mp qfs-rs
Specifies the name of the resource group.
Specifies the type of the resource to add.
Specifies the QFS shared file system mount point.
Specifies the name of the QFS shared file system resource that you are creating.
# clresourcegroup online -eM qfs-rg
# clresourcetype register SUNW.ScalMountPoint
# clresourcegroup create -S scal-mp-rg
# clresource create -g scal-mp-rg -t SUNW.ScalMountPoint \ -p mountpointdir=mount-point \ -p filesystemtype=s-qfs \ -p targetfilesystem=qfs-name \ -p resource_dependencies=qfs-rs \ -d scal-mp-rs
Specifies the name of the scalable resource group.
Specifies the type of the resource to add.
Specifies the directory to which the file system is mounted.
Specifies the file system type you are using.
Specifies the file system name that is mounted on this mount point.
Specifies the name of the scalable mount point resource that you are creating.
# clresourcegroup online -eM scal-mp-rg
# clresourcetype register SUNW.HAStoragePlus
# clresource create -g ora-db-rg -t SUNW.HAStoragePlus \ -p filesystemmountpoints=mount-point-list -d hastp-rs
# clresourcegroup online -eM ora-db-rg
# clresourcetype register SUNW.scalable_asm_instance_proxy
# clresourcetype register SUNW.asm_diskgroup
# clresourcetype register SUNW.scalable_asm_diskgroup_proxy
# clresourcegroup create -S asm-inst-rg asm-dg-rg
# clresourcegroup set -p rg_affinities=++rac-fmwk-rg asm-inst-rg
# clresourcegroup set -p rg_affinities=++asm-inst-rg asm-dg-rg
# clresource create -g rac-fmwk-rg -t SUNW.crs_framework \ -p resource_dependencies=rac-fmwk-rs \ -d crs-fmwk-rs
# clresource create -g asm-inst-rg -t SUNW.asm_instance_proxy \ -p ORACLE_HOME=oracle-home \ -p crs_home=crs-home \ -p "oracle_sid{node1}"=instance \ -p "oracle_sid{node2}"=instance \ -p resource_dependencies_offline_restart=crs-fmwk-rs,qfs-mp-rs \ -d asm-inst-rs
Specifies the name of the resource group into which the resources are to be placed.
Specifies the type of the resource to add.
Sets the Oracle system identifier.
Sets the path to the Oracle home directory.
Specifies the name of the resource that you are creating.
# clresource create -g asm-dg-rg -t SUNW.asm_diskgroup \ -p asm_diskgroups=dg[,dg…] \ -p resource_dependencies_offline_restart=asm-inst-rs,asm-stor-rs \ -d asm-dg-rs
Specifies the type of the resource to add.
Specifies the ASM disk group.
Specifies the name of the Oracle ASM storage resource.
Specifies the name of the resource that you are creating.
# 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
# clresourcegroup online -eM asm-inst-rg
# clresourcegroup online -eM asm-dg-rg
# clresource status +
For HA for Oracle, you register two resource types, SUNW.oracle_server and SUNW.oracle_listener, as follows.
# clresourcetype register SUNW.oracle_server # clresourcetype register SUNW.oracle_listener
# clreslogicalhostname create -g ora-db-rg [-h logicalhostname] \ logicalhostname-rs
Specifies a logical hostname. This logical hostname must present in your name service database. If logicalhostname and logicalhostname-rs are identical, logicalhostname is optional.
Specifies the name that you are assigning to the logical hostname resource that you are creating.
# clresourcegroup online -eM ora-db-rg
Oracle server resource:
# clresource create -g ora-db-rg \ -t SUNW.oracle_server \ -p Connect_string=user/passwd \ -p ORACLE_SID=instance \ -p ORACLE_HOME=Oracle-home \ -p Alert_log_file=path-to-log \ -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,logicalhostname-rs \ -d ora-ls-rs
Specifies the name of the resource group into which the resources are to be placed.
Specifies the type of the resource to add.
Sets the path under $ORACLE_HOME for the server message log.
Specifies the user and password that the fault monitor uses to connect to the database. These settings must agree with the permissions that you set up in How to Set Up Oracle Database Permissions. If you use Solaris authorization, type a slash (/) instead of the user name and password.
Sets the Oracle system identifier.
Sets the path to the Oracle home directory.
Sets the name of the Oracle listener instance. This name must match the corresponding entry in listener.ora.
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.
# clresource enable ora-db-rs
# clresource enable ora-ls-rs
Note - You can also install Oracle_Home for Oracle ASM on a cluster file system. If you are using a cluster file system, you should create the resources SUNW.HAStoragePlus and SUNW.scalable_asm_instance and set the appropriate dependencies between these two resources.
Sample commands to create the SUNW.HAStoragePlus resource and SUNW.scalable_asm_instance resource is given as follows:
# clresource create -g asm-inst-rg -t SUNW.HAStoragePlus \ -p FilesystemMountPoints=cluster-file-system \ hastp-rs
# clresource create -g asm-inst-rg -t SUNW.scalable_asm_instance \ -p ORACLE_HOME=oracle-home \ -p "oracle_sid{node1}"=instance \ -p "oracle_sid{node2}"=instance \ -p resource_dependencies_restart=hastp-rs \ -p resource_dependencies_offline_restart=crs-fmwk-rs \ asm-inst-rs
Go to Verifying the HA for Oracle Installation after you register and configure Solaris Cluster HA for Oracle.