This chapter explains how to enable Oracle RAC to run on your Sun Cluster nodes.
Overview of Tasks for Enabling Oracle RAC to Run in a Cluster
Creating Node-Specific Files and Directories for a Shared File System
Verifying the Installation and Configuration of Sun Cluster Support for Oracle RAC
Table 3–1 summarizes the tasks for enabling Oracle RAC to run in a cluster.
Perform these tasks in the order in which they are listed in the table.
Table 3–1 Tasks for Enabling Oracle RAC to Run in a Cluster
Task |
Instructions |
---|---|
Install the Oracle RAC software | |
Create node-specific files and directories that the Sun Cluster Support for Oracle RAC software requires |
Creating Node-Specific Files and Directories for a Shared File System |
Verify the installation of the Oracle RAC software | |
Create your Oracle database | |
(Not required for Oracle 10g R1) Configure resources for Oracle RAC database instances | |
Verify the Sun Cluster Support for Oracle RAC installation and configuration |
Verifying the Installation and Configuration of Sun Cluster Support for Oracle RAC |
For detailed instructions for installing Oracle RAC, see your Oracle documentation.
To simplify the maintenance of your Oracle installation, you can install the Oracle binary files and Oracle configuration files on a shared file system. The following shared file systems are supported:
The Sun StorEdge QFS shared file system
The cluster file system
A file system on a Network Appliance NAS device
If you are installing the Oracle binary files and Oracle configuration files on a shared file system, specify the absolute paths to the file system when the Oracle installation tool requests this information. Do not use a symbolic link whose target is the shared file system.
By default, the network interfaces panel of the Oracle 10g Universal Installer shows all interfaces as private. If you are installing Oracle 10g RAC for use with Sun Cluster, override these defaults as follows:
Ensure that clprivnet0 is the only private interface.
Set the public network interfaces to public.
Ensure that all other interfaces are not used. These interfaces represent the underlying network interfaces for the cluster interconnects.
By default, the Oracle installer installs CRS on all nodes in a cluster. Instructions for installing CRS on a subset of Sun Cluster nodes are available at the Oracle MetaLink web site. See Oracle MetaLink note 280589.1 How to install Oracle 10g CRS on a cluster where one or more nodes are not to be configured to run CRS.
The next steps depend on the location of your Oracle binary files and Oracle configuration files. See the following table.
File Location |
Next Step |
---|---|
Shared file system |
Creating Node-Specific Files and Directories for a Shared File System |
Local disks of each node |
When Oracle software is installed on a shared file system, all the files in the directory that the ORACLE_HOME environment variable specifies are accessible by all cluster nodes. However, some Oracle files and directories must maintain node-specific information.
If you install Oracle software on a shared file system, you must create local copies of files and directories that must maintain node-specific information. To ensure that these files and directories are accessible by all cluster nodes, use a symbolic link whose target is a file or a directory on a file system that is local to a node. Such a file system is not part of the shared file system.
To use a symbolic link for this purpose, you must allocate an area on a local file system. To enable Oracle applications to create symbolic links to files in this area, the applications must be able to access files in this area. Because the symbolic links reside on the shared file system, all references to the links from all nodes are the same. Therefore, all nodes must have the same namespace for the area on the local file system.
Perform this procedure for each directory that is to maintain node-specific information. The following directories are typically required to maintain node-specific information:
For information about other directories that might be required to maintain node-specific information, see your Oracle documentation.
On each cluster node, create the local directory that is to maintain node-specific information.
Ensure that the local directory structure that you create matches the global directory structure that contains the node-specific information. For example, the global directory /global/oracle/network/agent might contain node-specific information that you require to be stored locally under the /local directory. In this situation, you would create a directory that is named /local/oracle/network/agent.
# mkdir -p local-dir |
Specifies that all nonexistent parent directories are created first.
Specifies the full path name of the directory that you are creating.
On each cluster node, make a local copy of the global directory that is to maintain node-specific information.
Ensure that the local copy of the node-specific information is contained in the local directory that you created in Step 1.
# cp -pr global-dir local-dir-parent |
Specifies that the owner, group, permissions modes, modification time, access time, and access control lists are preserved.
Specifies that the directory and all its files, including any subdirectories and their files, are copied.
Specifies the full path of the global directory that you are copying. This directory resides on the shared file system under the directory that the ORACLE_HOME environment variable specifies.
Specifies the directory on the local node that is to contain the local copy. This directory is the parent directory of the directory that you created in Step 1.
Replace the global directory that you copied in Step 2 with a symbolic link to the local copy of the global directory.
From any cluster node, remove the global directory that you copied in Step 2.
# rm -r global-dir |
Specifies that the directory and all its files, including any subdirectories and their files, are removed.
Specifies the file name and full path of the global directory that you are removing. This directory is the global directory that you copied in Step 2.
From any cluster node, create a symbolic link from the local copy of the directory to the global directory that you removed in Step a.
# ln -s local-dir global-dir |
This example shows the sequence of operations that is required to create node-specific directories on a two-node cluster. This cluster is configured as follows:
The ORACLE_HOME environment variable specifies the /global/oracle directory.
The local file system on each node is located under the /local directory.
The following operations are performed on each node:
To create the required directories on the local file system, the following commands are run:
# mkdir -p /local/oracle/network/agent |
# mkdir -p /local/oracle/network/log |
# mkdir -p /local/oracle/network/trace |
# mkdir -p /local/oracle/srvm/log |
# mkdir -p /local/oracle/apache |
To make local copies of the global directories that are to maintain node-specific information, the following commands are run:
# cp -pr $ORACLE_HOME/network/agent /local/oracle/network/. |
# cp -pr $ORACLE_HOME/network/log /local/oracle/network/. |
# cp -pr $ORACLE_HOME/network/trace /local/oracle/network/. |
# cp -pr $ORACLE_HOME/srvm/log /local/oracle/srvm/. |
# cp -pr $ORACLE_HOME/apache /local/oracle/. |
The following operations are performed on only one node:
To remove the global directories, the following commands are run:
# rm -r $ORACLE_HOME/network/agent |
# rm -r $ORACLE_HOME/network/log |
# rm -r $ORACLE_HOME/network/trace |
# rm -r $ORACLE_HOME/srvm/log |
# rm -r $ORACLE_HOME/apache |
To create symbolic links from the local directories to their corresponding global directories, the following commands are run:
# ln -s /local/oracle/network/agent $ORACLE_HOME/network/agent |
# ln -s /local/oracle/network/log $ORACLE_HOME/network/log |
# ln -s /local/oracle/network/trace $ORACLE_HOME/network/trace |
# ln -s /local/oracle/srvm/log $ORACLE_HOME/srvm/log |
# ln -s /local/oracle/apache $ORACLE_HOME/apache |
Perform this procedure for each file that is to maintain node-specific information. The following files are typically required to maintain node-specific information:
For information about other files that might be required to maintain node-specific information, see your Oracle documentation.
On each cluster node, create the local directory that will contain the file that is to maintain node-specific information.
# mkdir -p local-dir |
Specifies that all nonexistent parent directories are created first.
Specifies the full path name of the directory that you are creating.
On each cluster node, make a local copy of the global file that is to maintain node-specific information.
# cp -p global-file local-dir |
Specifies that the owner, group, permissions modes, modification time, access time, and access control lists are preserved.
Specifies the file name and full path of the global file that you are copying. This file was installed on the shared file system under the directory that the ORACLE_HOME environment variable specifies.
Specifies the directory that is to contain the local copy of the file. This directory is the directory that you created in Step 1.
Replace the global file that you copied in Step 2 with a symbolic link to the local copy of the file.
From any cluster node, remove the global file that you copied in Step 2.
# rm global-file |
Specifies the file name and full path of the global file that you are removing. This file is the global file that you copied in Step 2.
From any cluster node, create a symbolic link from the local copy of the file to the global file that you removed in Step a.
# ln -s local-file global-file |
This example shows the sequence of operations that is required to create node-specific files on a two-node cluster. This cluster is configured as follows:
The ORACLE_HOME environment variable specifies the /global/oracle directory.
The local file system on each node is located under the /local directory.
The following operations are performed on each node:
To create the local directory that will contain the files that are to maintain node-specific information, the following command is run:
# mkdir -p /local/oracle/network/admin |
To make a local copy of the global files that are to maintain node-specific information, the following commands are run:
# cp -p $ORACLE_HOME/network/admin/snmp_ro.ora \ /local/oracle/network/admin/. |
# cp -p $ORACLE_HOME/network/admin/snmp_rw.ora \ /local/oracle/network/admin/. |
The following operations are performed on only one node:
To remove the global files, the following commands are run:
# rm $ORACLE_HOME/network/admin/snmp_ro.ora |
# rm $ORACLE_HOME/network/admin/snmp_rw.ora |
To create symbolic links from the local copies of the files to their corresponding global files, the following commands are run:
# ln -s /local/oracle/network/admin/snmp_ro.ora \ $ORACLE_HOME/network/admin/snmp_rw.ora |
# ln -s /local/oracle/network/admin/snmp_rw.ora \ $ORACLE_HOME/network/admin/snmp_rw.ora |
Go to Verifying the Installation of Oracle RAC.
After you have installed Oracle RAC, verify that the installation is correct. Perform this verification before you attempt to create your Oracle database. This verification does not verify that RAC database instances can be started and stopped automatically.
Confirm that the tests that the Oracle installer runs to verify the cluster were passed.
If the results of these tests are no longer available for review, run the Oracle utility cluvfy to repeat the tests.
For more information, see your Oracle documentation.
Confirm that the owner, group, and mode of the $ORACLE_HOME/bin/oracle file are as follows:
Owner: oracle
Group: dba
Mode: -rwsr-s--x
# ls -l $ORACLE_HOME/bin/oracle |
Confirm that the binary files for the Oracle listener exist in the $ORACLE_HOME/bin directory.
Go to Creating an Oracle Database.
Perform this task to configure and create the initial Oracle database in a Sun Cluster environment. If you create and configure additional databases, you do not need to repeat this task.
To create the database, use one command from the following list:
The Oracle dbca command
The Oracle sqlplus command
For detailed instructions for creating an Oracle database, see your Oracle documentation.
How to specify to the dbca command the location of data files on a shared file system depends on your release of Oracle.
When dbca prompts you for a storage option, select Cluster File System.
When dbca prompts you for the location, select the option for common location.
After selecting the option for a common location, type the name of the directory on the shared file system and press Return.
Specify the -datafileDestination path option of the dbca command.
path specifies the path to a directory on a shared file system where the data files are to be stored.
After you have created the Oracle database, go to Configuring Resources for Oracle RAC Database Instances.
Resources for Oracle RAC database instances enable the database instances to be administered from Sun Cluster.
If you are using Oracle 10g R2 RAC, these resources also enable Sun Cluster and Oracle Cluster Ready Services (CRS) to interoperate.
The software architectures of Oracle 9i, Oracle 10g R1, and Oracle 10g R2 are different. As a result of these differences, the resources for Oracle RAC database instances that Sun Cluster requires depend on the version of Oracle that you are using.
If you are using Oracle 10g R1, omit this task. In Oracle 10g R1, Oracle CRS and Sun Cluster cannot interoperate. Instead, Oracle CRS start and shut down Oracle RAC database instances.
You can also use the Oracle 10g R2 RAC Plug-in for Sun N1 Service Provisioning System to deploy Oracle 10g R2 RAC software in a Sun Cluster configuration. Follow instructions in the documentation at http://wikis.sun.com/display/SunCluster/Oracle+RAC+10g+R2+Plug-in.
Sun Cluster provides the following tools for registering and configuring resources for Oracle RAC database instances:
The clsetup(1CL) utility. For more information, see the following sections:
Sun Cluster Manager. For more information, see the Sun Cluster Manager online help.
Sun Cluster maintenance commands. For more information, see the following sections:
The clsetup utility and Sun Cluster Manager each provide a wizard for configuring resources for Oracle RAC database instances. The wizards reduce the possibility of 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.
When you perform this task, the clsetup utility creates the following resources for interoperation with Oracle 10g R2:
A Sun Cluster resource to act as a proxy for the Oracle RAC database
A Sun Cluster resource to represent the Oracle CRS framework
Oracle CRS resources to represent scalable device groups
Oracle CRS resources to represent scalable file-system mount points
Ensure that the following prerequisites are met:
The RAC framework resource group is created and is online.
Storage resources for Oracle files are configured.
Node-specific files and directories for a shared file system are created.
The Oracle database is running.
To determine whether the Oracle database is running, use the Oracle srvctl command as follows:
$ srvctl status database -d db-name |
db-name specifies the name of the Oracle database.
Ensure that you have the following information:
The full path to the Oracle CRS home directory
The name of the Oracle RAC database for which you are configuring resources
The full path to the Oracle home directory
The Oracle system identifier (SID) for each instance of the database for which you are configuring resources
The names of all Sun Cluster storage resources for Oracle files that you are using
On one node of the cluster, become superuser.
Start the clsetup utility.
# clsetup |
The clsetup main menu is displayed.
Type the number that corresponds to the option for data services and press Return.
The Data Services menu is displayed.
Type the number that corresponds to the option for configuring Sun Cluster Support for Oracle RAC and press Return.
The clsetup utility displays information about Sun Cluster Support for Oracle RAC.
Press Return to continue.
The clsetup utility prompts you to select whether you are performing the initial configuration of Sun Cluster Support for Oracle RAC or administering an existing configuration.
Type the number that corresponds to the option for performing the initial configuration of Sun Cluster Support for Oracle RAC and press Return.
The clsetup utility displays a list of components of Oracle RAC to configure.
Type the number that corresponds to the option for resources for Oracle RAC database instances and press Return.
The clsetup utility displays the list of prerequisites for performing this task.
Verify that the prerequisites are met, and press Return.
The clsetup utility displays a list of versions of Oracle that you can configure by using this utility.
Type the number that corresponds to the option for Oracle 10g R2 and press Return.
The clsetup utility displays a list of Oracle CRS home directories that exist on the cluster.
Specify the Oracle CRS home directory for your installation of the Oracle CRS software.
Specify the name of the Oracle RAC database that you are configuring.
Specify the Oracle home directory for your installation of the Oracle RAC software.
If the directory is listed, type the number that corresponds to the directory that you are selecting 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 the first node in the list of nodes where Oracle RAC is to run.
If the directory is not listed, specify the directory explicitly:
Type e and press Return.
The clsetup utility prompts you for the Oracle home directory.
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 the first node in the list of nodes where Oracle RAC is to run.
Specify the Oracle SID of the Oracle RAC database instance for the node that you are configuring.
Perform this step for each node in the list of nodes where Oracle RAC is to run.
You must specify a unique Oracle SID for each node. If you specify a duplicate SID, the clsetup utility warns you that the SID is a duplicate and prompts you to specify the SID again.
If the SID is listed, type the number that corresponds to the SID that you are selecting and press Return.
The response of the clsetup utility depends on whether you have specified the Oracle SID for all nodes where Oracle RAC is to run.
If you have not specified the Oracle SID for all nodes, the clsetup utility prompts you for the SID of the next node in the node list.
If you have specified the Oracle SID for all nodes, the clsetup utility displays a list of Sun Cluster storage resources for Oracle files that are configured. For information about these resources, see Registering and Configuring Storage Resources for Oracle Files.
If the SID is not listed, specify the SID explicitly.
Type e and press Return.
The clsetup utility prompts you for the SID.
Type the SID and press Return.
The response of the clsetup utility depends on whether you have specified the Oracle SID for all nodes where Oracle RAC is to run.
If you have not specified the Oracle SID for all nodes, the clsetup utility prompts you for the SID of the next node in the node list.
If you have specified the Oracle SID for all nodes, the clsetup utility displays a list of Sun Cluster storage resources for Oracle files that are configured. For information about these resources, see Registering and Configuring Storage Resources for Oracle Files.
Type a comma-separated or space-separated list of the numbers that correspond to the storage resources that you are using, and press Return.
The clsetup utility displays the names of the Sun Cluster objects that the utility will create.
If you require a different name for any Sun 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 Sun Cluster objects that the utility will create.
To confirm your selection of Sun Cluster object names, press Return.
The clsetup utility displays information about the Sun Cluster configuration that the utility will create.
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.
Press Return to continue.
The clsetup utility returns you to the list of options for configuring Sun Cluster Support for Oracle RAC.
(Optional) Type q and press Return repeatedly until you quit the clsetup utility.
The following table lists the default configuration of Sun Cluster resources that the clsetup utility creates when you complete this task.
The clsetup utility also creates an Oracle CRS resource for each Sun Cluster resource for scalable device groups and scalable file-system mount points on which Oracle components depend.
The name of each Oracle CRS resource that the clsetup utility creates is as follows:
sun.node.sc-rs
The replaceable items in this name are as follows:
node specifies the name of the node where the Oracle CRS resource is to run.
sc-rs specifies the name of the Sun Cluster resource that the Oracle CRS resource represents. This resource is created when the task in Registering and Configuring Storage Resources for Oracle Files is performed.
The Oracle CRS resource for the database instance on node depends on the Oracle CRS resource that the clsetup utility creates for that node. Oracle CRS resources for database instances are created during the installation and configuration of the Oracle RAC
The name of the Oracle CRS resource for the database instance on a node is as follows:
ora.dbname.sid.inst
The replaceable items in this name are as follows:
dbname specifies the database name of the database instance that the Oracle CRS resource represents.
sid specifies the Oracle SID of the database instance that the Oracle CRS resource represents.
Go to Verifying the Installation and Configuration of Sun Cluster Support for Oracle RAC.
Ensure that the following prerequisites are met:
The RAC framework resource group is created and is online.
Storage resources for Oracle files are configured.
Node-specific files and directories for a shared file system are created.
Ensure that you have the following information:
The full path to the Oracle home directory
The Oracle system identifier (SID) for each instance of the database for which you are configuring resources
The names of all Sun Cluster storage resources for Oracle files that you are using
The logical hostnames, or the names of the logical hostname resources, that you are using for Oracle listeners
On one node of the cluster, become superuser.
Start the clsetup utility.
# clsetup |
The clsetup main menu is displayed.
Type the number that corresponds to the option for data services and press Return.
The Data Services menu is displayed.
Type the number that corresponds to the option for configuring Sun Cluster Support for Oracle RAC and press Return.
The clsetup utility displays information about Sun Cluster Support for Oracle RAC.
Press Return to continue.
The clsetup utility prompts you to select whether you are performing the initial configuration of Sun Cluster Support for Oracle RAC or administering an existing configuration.
Type the number that corresponds to the option for performing the initial configuration of Sun Cluster Support for Oracle RAC and press Return.
The clsetup utility displays a list of components of Oracle RAC to configure.
Type the number that corresponds to the option for resources for Oracle RAC database instances and press Return.
The clsetup utility displays the list of prerequisites for performing this task.
Verify that the prerequisites are met, and press Return.
The clsetup utility displays a list of versions of Oracle that you can configure by using this utility.
Type the number that corresponds to the option for Oracle 9i and press Return.
Type the number that corresponds to the option to configure both the listener and the server.
The clsetup utility displays a list of Oracle home directories that exist on the cluster.
Specify the Oracle home directory for your installation of the Oracle RAC software.
If the directory is listed, type the number that corresponds to the directory that you are selecting 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 the first node in the list of nodes where Oracle RAC is to run.
If the directory is not listed, specify the directory explicitly:
Type e and press Return.
The clsetup utility prompts you for the Oracle home directory.
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 the first node in the list of nodes where Oracle RAC is to run.
Specify the Oracle SID of the Oracle RAC database instance for the node that you are configuring.
The wizard prompts you to perform this step for each node in the list of nodes where Oracle RAC is to run.
You must specify a unique Oracle SID for each node. If you specify a duplicate SID, the clsetup utility warns you that the SID is a duplicate and prompts you to specify the SID again.
If you require a different value for any Sun Cluster resource properties, change each property as follows.
The wizard prompts you to perform this step for each node in the list of nodes where Oracle RAC is to run.
Type the number that corresponds to the property that you are changing and press Return.
The clsetup utility displays a screen where you can specify the new value.
At the New Value prompt, type the new value and press Return.
The clsetup utility returns you to the values of properties for the node.
To confirm your selection of Sun Cluster resource properties, press Return.
The response of the clsetup utility depends on whether you have specified the Sun Cluster resource properties for all nodes where Oracle RAC is to run.
If you have not specified Sun Cluster resource properties for all nodes, the clsetup utility prompts you to specify the system identifier for the next node in the list of nodes.
If you have specified the Sun Cluster resource properties for all nodes, the clsetup utility displays a list of logical hostname resources that are configured.
Configure a logical hostname resource for each node where Oracle RAC is to run.
The Oracle listener uses the logical hostname resource for a node to connect to the Oracle RAC database instance on the node.
The wizard prompts you to perform this step for each node in the list of nodes where Oracle RAC is to run.
If the logical hostname resource is listed, type the number that corresponds to the resource that you are selecting and press Return.
The response of the clsetup utility depends on whether you have configured a logical hostname resource for all nodes where Oracle RAC is to run.
If you have not configured a resource for all nodes, the clsetup utility prompts you to configure a resource for the next node.
If you have configured a resource for all nodes, the clsetup utility displays a list of Sun Cluster storage resources for Oracle files that are configured. For information about these resources, see Registering and Configuring Storage Resources for Oracle Files.
If the logical hostname resource is not listed, create the resource as follows:
Type the logical hostname and press Return.
The clsetup utility returns you to the list of logical hostname resources. An entry for the logical hostname resource that the wizard will create is added to the list.
Type the number that corresponds to the resource that you are creating and press Return.
The response of the clsetup utility depends on whether you have configured a logical hostname resource for all nodes where Oracle RAC is to run.
If you have not configured a resource for all nodes, the clsetup utility prompts you to configure a resource for the next node.
If you have configured a resource for all nodes, the clsetup utility displays a list of Sun Cluster storage resources for Oracle files that are configured. For information about these resources, see Registering and Configuring Storage Resources for Oracle Files.
Type a comma-separated or space-separated list of the numbers that correspond to the storage resources that you are using, and press Return.
The clsetup utility displays the names of the Sun Cluster objects that the utility will create.
If you require a different name for any Sun 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 Sun Cluster objects that the utility will create.
To confirm your selection of Sun Cluster object names, press Return.
The clsetup utility displays information about the Sun Cluster configuration that the utility will create.
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.
Press Return to continue.
The clsetup utility returns you to the list of options for configuring Sun Cluster Support for Oracle RAC.
(Optional) Type q and press Return repeatedly until you quit the clsetup utility.
The following table lists the default resource configuration that the clsetup utility creates when you complete this task.
Go to Verifying the Installation and Configuration of Sun Cluster Support for Oracle RAC.
After you install, register, and configure Sun Cluster Support for Oracle RAC, verify the installation and configuration. Verifying the Sun Cluster Support for Oracle RAC installation and configuration determines if resources and resource groups for Oracle RAC behave as required.
Offline-restart dependencies between resources ensure that if the independent resource is about to be taken offline, the dependent resource is taken offline first. The dependent resource remains offline until the independent resource is restarted. The procedures in this section explain how to verify that these dependencies are correctly set. For detailed information about offline-restart dependencies, see the description of the resource_dependencies_offline_restart resource property in Resource Properties in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Verifying the installation and configuration of Sun Cluster Support for Oracle RAC involves the following tasks:
Verifying the configuration of the RAC Framework resource group
Verifying the configuration of storage resources for Oracle files
(Oracle 10g R2 and Oracle 9i only) Verifying the configuration of resources for Oracle RAC database instances
If you are using Oracle 10g R1, no resources for Oracle RAC database instances are configured.
The task to perform depends on the version of Oracle RAC that you are using:
Oracle 10g R2. Perform the task in How to Verify the Configuration of Resources for Oracle 10g R2 RAC Database Instances.
Oracle 9i. Perform the task in How to Verify the Configuration of Resources for Oracle 9i RAC Database Instances.
Verifying the correct behavior for shutdown and booting of the cluster
The RAC framework resource group is created when the task in Registering and Configuring the RAC Framework Resource Group is performed.
This procedure provides the long forms of the Sun Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Become superuser on a cluster node or assume a role that provides solaris.cluster.read and solaris.cluster.admin RBAC authorizations.
Verify that the RAC framework resource group is correctly configured.
# clresourcegroup show rac-fmk-rg |
Specifies the name of the RAC framework resource group.
If the RAC framework resource group is not already online, bring online the RAC framework resource group.
# clresourcegroup online rac-fmwk-rg |
Specifies the name of the RAC framework resource group.
Verify that all resource groups for Oracle RAC are online.
# clresourcegroup status |
Storage resources for Oracle files are created when the task in Registering and Configuring Storage Resources for Oracle Files is performed.
Perform this task only if your configuration of storage management schemes requires storage resources for Oracle files.
This procedure provides the long forms of the Sun Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Become superuser on a cluster node.
Verify that all resource groups that contain storage resources for Oracle files are correctly configured.
# clresourcegroup show rac-storage-rg-list |
Specifies a comma-separated list of resource groups that contain storage resources for Oracle files.
Take offline the resource group that contains the resources on which the RAC database resource depends.
# clresourcegroup offline rac-storage-rg |
Specifies the name of the resource group that contains the resources on which the RAC database resource depends. The resource group to take offline depends on your choice of storage management schemes for Oracle files.
If you are using a shared file system for Oracle files, take offline the resource group that contains scalable file-system mount-point resources.
If you are using a volume manager without a file system for Oracle files, take offline the resource group that contains scalable device-group resources.
This step might require several minutes to complete.
Verify that the resource groups for Oracle RAC behave as follows:
The status of the resource group that you took offline in Step 3 is offline.
The status of the RAC database resource group is offline.
The status of the RAC framework resource group depends on the version of Oracle that you are using:
If you are using Oracle 10g R2, the status of the RAC framework resource group is pending online blocked.
If you are using Oracle 10g R1 or Oracle 9i, the status of the RAC framework resource group remains online.
# clresourcegroup status |
(Oracle 10g R2 only) Verify that the Oracle CRS are offline.
To verify that the Oracle CRS are offline, consult the system messages file to find messages to indicate that CRS are being shut down.
Bring online the resource group that you took offline in Step 3.
# clresourcegroup online rac-storage-rg |
Specifies the name of the resource group that you took offline in Step 3.
This step might require several minutes to complete.
(Oracle 10g R2 only) On each node, restart the Oracle CRS.
# /etc/init.d/init.crs start Startup will be queued to init within 30 seconds. |
This step might require several minutes to complete.
(Oracle 10g R2 only) On each node, verify that the Oracle CRS are online.
Use the Oracle command crstat for this purpose.
# crs-home/bin/crs_stat |
Specifies the Oracle CRS home directory. This directory contains the Oracle CRS binary files and Oracle CRS configuration files.
The startup of Oracle CRS on all nodes might require several minutes to complete. If you perform this step before the Oracle CRS are online on all nodes, the status on some nodes might be offline. In this situation, repeat this step until the status of the Oracle CRS is online on all nodes.
Verify that all resource groups for Oracle RAC are online.
# clresourcegroup status |
Bringing online the resource group that contains the resources on which the RAC database resource depends also brings online the RAC database resource group. If you perform this step before the RAC database resource group is online on all nodes, the status on some nodes might be online faulted. In this situation, repeat this step until the status of the RAC database resource group is online on all nodes.
Resources for Oracle 10g R2 RAC database instances are created when the tasks in one of the following sections are performed:
How to Enable Sun Cluster and Oracle 10g R2 CRS to Interoperate
Creating Resources for Interoperation With Oracle 10g by Using Sun Cluster Maintenance Commands
This procedure provides the long forms of the Sun Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Become superuser on a cluster node.
Verify that the RAC database resource group is correctly configured.
# clresourcegroup show rac-db-rg |
Specifies the name of the RAC database resource group.
If required, verify that the Oracle CRS resources to represent Sun Cluster storage resources are correctly configured.
Perform this step only if your configuration of storage management schemes requires storage resources for Oracle files.
Confirm that the Oracle CRS resources to represent Sun Cluster storage resources exist.
Use the Oracle command crstat for this purpose.
# crs-home/bin/crs_stat | grep NAME=sun. |
Specifies the Oracle CRS home directory. This directory contains the Oracle CRS binary files and Oracle CRS configuration files.
For each Oracle CRS resource that represents an Oracle RAC database instance, confirm that the required dependencies are set.
Each Oracle CRS resource that represents an Oracle RAC database instance requires a dependency on a resource that is listed in Step a.
# crs-home/bin/crs_stat crs-resource| grep REQUIRED_RESOURCE |
Specifies the Oracle CRS home directory. This directory contains the Oracle CRS binary files and Oracle CRS configuration files.
Specifies the name of an Oracle CRS resource that represents an Oracle RAC database instance. The format of this name is ora.dbname.sid.inst. The replaceable items in this format are as follows:
Specifies the database name of the instance.
Specifies the Oracle SID of the instance.
Disable the CRS framework resource.
# clresource disable -t SUNW.crs_framework + |
This step might require several minutes to complete.
Verify that the Oracle CRS are offline.
Attempt to obtain the status of Oracle CRS resources.
Use the Oracle command crstat for this purpose.
# crs-home/bin/crs_stat -t CRS-0184: Cannot communicate with the CRS daemon. |
Specifies the Oracle CRS home directory. This directory contains the Oracle CRS binary files and Oracle CRS configuration files.
Consult the system messages file to find messages to indicate that CRS are being shut down.
Verify that the following resources are offline on all nodes:
The CRS framework resource
The RAC database resource
# clresource status -t SUNW.crs_framework,SUNW.scalable_rac_server_proxy + |
On each node, restart the Oracle CRS.
# /etc/init.d/init.crs start Startup will be queued to init within 30 seconds. |
This step might require several minutes to complete.
On each node, verify that the Oracle CRS are online.
Use the Oracle command crstat for this purpose.
# crs-home/bin/crs_stat |
Specifies the Oracle CRS home directory. This directory contains the Oracle CRS binary files and Oracle CRS configuration files.
The startup of Oracle CRS on all nodes might require several minutes to complete. If you perform this step before the Oracle CRS are online on all nodes, the status on some nodes might be offline. In this situation, repeat this step until the status of the Oracle CRS is online on all nodes.
Enable the CRS framework resource.
# clresource enable -t SUNW.crs_framework + |
This step might require several minutes to complete.
Verify that the following resources are online on all nodes:
The CRS framework resource
The RAC database resource
# clresource status -t SUNW.crs_framework,SUNW.scalable_rac_server_proxy + |
Enabling the CRS framework resource also enable the RAC database resource. If you perform this step before the RAC database resource is enabled on all nodes, the status on some nodes might be offline. In this situation, repeat this step until the status of the RAC database resource is online on all nodes.
Resources for Oracle 9i RAC database instances are created when the tasks in one of the following sections are performed:
This procedure provides the long forms of the Sun Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Become superuser on a cluster node, or assume a role that provides solaris.cluster.read and solaris.cluster.admin RBAC authorizations.
Verify that the RAC database resource group and the resource groups for logical hostname resources are correctly configured.
# clresourcegroup show rac-db-rg,lhrg-list |
Specifies the name of the RAC database resource group.
Specifies a comma-separated list of resource groups for logical hostname resources.
Take offline the RAC database resource group.
# clresourcegroup offline rac-db-rg |
Specifies the name of the RAC database resource group.
Verify that the RAC database resource group is offline.
# clresourcegroup status rac-db-rg |
Specifies the name of the RAC database resource group.
Verify that the resources in the RAC database resource group are offline on all nodes.
The RAC database resource group contains the following resources:
The scalable RAC server resource
The scalable RAC listener resource
# clresource status -t SUNW.scalable_rac_server,SUNW.scalable_rac_listener + |
Bring online again the RAC database resource group.
# clresourcegroup online rac-db-rg |
Specifies the name of the RAC database resource group.
Verify that the RAC database resource group is online.
# clresourcegroup status rac-db-rg |
Specifies the name of the RAC database resource group.
Verify that the resources in the RAC database resource group are online on all nodes.
The RAC database resource group contains the following resources:
The scalable RAC server resource
The scalable RAC listener resource
# clresource status -t SUNW.scalable_rac_server,SUNW.scalable_rac_listener + |
If your configuration of Sun Cluster Support for Oracle RAC is correct, Sun Cluster ensures that Oracle RAC is stopped and started correctly when you shut down and boot the cluster.
This task requires downtime. If you are verifying the installation and configuration of Sun Cluster Support for Oracle RAC on a production cluster where other data services are running, omit this task.
This procedure provides the long forms of the Sun Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Shut down the cluster.
For instructions for performing this task, see How to Shut Down a Cluster in Sun Cluster System Administration Guide for Solaris OS.
Confirm that the cluster shuts down correctly.
Boot the cluster.
For instructions for performing this task, see How to Boot a Cluster in Sun Cluster System Administration Guide for Solaris OS.
Confirm that the cluster starts correctly.
Verify that all Oracle RAC resource groups and their resources are online.
# clresourcegroup status |
The bringing online of all Oracle RAC resource groups might require several minutes to complete. If you perform this step before the resource groups are enabled on all nodes, the status on some nodes might be offline. In this situation, repeat this step until the status of all Oracle RAC resource groups is online on all nodes.