Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide Oracle Solaris Cluster |
1. Installing Support for Oracle RAC
2. Configuring Storage for Oracle Files
3. Registering and Configuring the Resource Groups
4. Enabling Oracle RAC to Run in a Cluster
Overview of Tasks for Enabling Oracle RAC to Run in a Cluster
Installing Oracle RAC Software
Installing Binary Files and Configuration Files on a Shared File System
Overriding Networking Defaults for Oracle 10g, 11g, or 12c Oracle Clusterware
Installing Oracle Clusterware on a Subset of Oracle Solaris Cluster Nodes
Creating Node-Specific Files and Directories for a Shared File System
How to Create a Node-Specific Directory for a Shared File System
Verifying the Installation of Oracle RAC
How to Verify the Installation of Oracle 10g, 11g, or 12c RAC
How to Verify the Installation of Oracle 9i RAC
Creating an Oracle ASM Instance and Disk Groups
How to Create an Oracle ASM Instance and Disk Groups
Creating an Oracle Clusterware Framework Resource
How to Create an Oracle Clusterware Framework Resource
How to Specify the Location of Data Files on a Shared File System for Oracle 10g, 11g, or 12c
How to Specify the Location of Data Files on a Shared File System for Oracle 9i
Configuring Resources for Oracle RAC Database Instances
Tools for Registering and Configuring Resources for Oracle RAC Database Instances
How to Automate the Startup and Shutdown of Oracle 9i RAC Database Instances
Verifying the Installation and Configuration of Support for Oracle RAC
How to Verify the Configuration of the Oracle RAC Framework Resource Group
How to Verify the Configuration of the Multiple-Owner Volume-Manager Framework Resource Group
How to Verify the Configuration of Storage Resources for Oracle Files
How to Verify the Configuration of Resources for Oracle 9i RAC Database Instances
How to Verify the Correct Behavior for Shutdown and Booting of the Cluster
5. Administering Support for Oracle RAC
6. Troubleshooting Support for Oracle RAC
7. Modifying an Existing Configuration of Support for Oracle RAC
8. Upgrading Support for Oracle RAC
A. Sample Configurations of This Data Service
B. Preset Actions for DBMS Errors and Logged Alerts
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.
The administrator creates the file system on a global-cluster voting node, even when a zone cluster uses the file system. The administrator configures the node-specific file system into the zone cluster node using the zonecfg command.
This section contains the following procedures:
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.
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.
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.
# 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.
# ln -s local-dir global-dir
Example 4-1 Creating Node-Specific Directories
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.
# 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.
# 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.
# 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.
# ln -s local-file global-file
Example 4-2 Creating Node-Specific Files
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
Next Steps