Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide |
1. Installing Support for Oracle RAC
Overview of the Installation Process for Support for Oracle RAC
Preinstallation Considerations
Hardware and Software Requirements
Oracle Solaris Cluster Framework Requirements
Supported Topology Requirements
Patch Installation Requirements
Storage Management Requirements for Oracle Files
Storage Management Schemes for Oracle Files
Storage Management Requirements for the Oracle Clusterware
Storage Management Requirements for the Oracle RAC Database
Storage Management Requirements for Oracle Binary Files and Oracle Configuration Files
Using Local Disks for Oracle Binary Files and Oracle Configuration Files
Using a Shared File System for Oracle Binary Files and Oracle Configuration Files
Storage Management Schemes Supported by Zone Clusters
SPARC: Processor Architecture Requirements for Oracle Components
Using Oracle Data Guard With Support for Oracle RAC
Using the Oracle Real Application Clusters Guard Option With Oracle Solaris Cluster 3.3 Software
Oracle Solaris Cluster Command Usage Restrictions
Preparing the Oracle Solaris Cluster Nodes
How to Bypass the NIS Name Service
How to Create the DBA Group and the DBA User Accounts
How to Configure Shared Memory for the Oracle RAC Software in the Global Cluster
How to Configure Shared Memory for the Oracle RAC Software in a Zone Cluster
How to Set the Necessary Privileges for Oracle RAC Software in a Zone Cluster
Installing the Support for Oracle RAC Packages
How to Install the Support for Oracle RAC Packages
SPARC: Installing the Oracle UDLM
SPARC: How to Install the Oracle UDLM
2. Configuring Storage for Oracle Files
3. Registering and Configuring the Resource Groups
4. Enabling Oracle RAC to Run in a 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
Preparing the Oracle Solaris Cluster nodes modifies the configuration of the operating system to enable Oracle RAC to run on Oracle Solaris Cluster nodes. Preparing the Oracle Solaris Cluster nodes and disks involves the following tasks:
Bypassing the NIS name service
Creating the database administrator (DBA) group and the DBA user accounts
Configuring shared memory for the Oracle RAC software
Caution - Perform these tasks on all nodes where Support for Oracle RAC can run. If you do not perform these tasks on all nodes, the Oracle installation is incomplete. An incomplete Oracle installation causes Support for Oracle RAC to fail during startup. |
To enable the Oracle RAC to run in a zone cluster, you need to perform the following additional tasks:
Configuring shared memory for Oracle RAC software in a zone cluster
Setting necessary privileges for Oracle RAC software in a zone cluster
Configuring logical hostname resources for Oracle RAC software in a zone cluster
This section contains the following information:
How to Configure Shared Memory for the Oracle RAC Software in the Global Cluster
How to Configure Shared Memory for the Oracle RAC Software in a Zone Cluster
How to Set the Necessary Privileges for Oracle RAC Software in a Zone Cluster
Before you prepare the Oracle Solaris Cluster nodes, ensure that all preinstallation tasks for Oracle RAC are completed. For more information, see your Oracle RAC documentation.
Bypassing the NIS name service protects the Support for Oracle RAC data service against a failure of a cluster node's public network. A failure of a cluster node's public network might cause the NIS name service to become unavailable. If Support for Oracle RAC refers to the NIS name service, unavailability of the name service might cause the Support for Oracle RAC data service to fail.
Bypassing the NIS name service ensures that the Support for Oracle RAC data service does not refer to the NIS name service when the data service sets the user identifier (ID). The Support for Oracle RAC data service sets the user ID when the data service starts or stops the database.
passwd: files [NOTFOUND=return] nis [TRYAGAIN=0] publickey: files [NOTFOUND=return] nis [TRYAGAIN=0] project: files [NOTFOUND=return] nis [TRYAGAIN=0] group: files [NOTFOUND=return] nis [TRYAGAIN=0]
For more information about the /etc/nsswitch.conf file, see the nsswitch.conf(4) man page.
Next Steps
Go to How to Create the DBA Group and the DBA User Accounts.
In installations of Oracle RAC with Oracle Solaris Cluster software, the DBA group is normally named dba. This group normally contains the root user and the oracle user.
Note - This configuration of users and groups differs from the configuration that is described in the Oracle documentation for a standalone installation of Oracle RAC. A standalone installation of Oracle RAC uses a primary DBA group that is named oinstall and a secondary group that is named dba. Some applications also require a secondary group that is named oper. For more information, see your Oracle documentation.
Perform this task on each cluster node.
# echo 'group-name:*:group-id:user-list' >> /etc/group
Specifies the name of the group for which you are adding an entry. This group is normally named dba.
Specifies the group's unique numerical ID (GID) within the system.
Specifies a comma-separated list of the user names that are allowed in the group. Ensure that the list contains the names of all DBA users that are required. This group normally contains the root user and the oracle user.
Ensure that the entry is identical on each node that can run Support for Oracle RAC.
You can create the name service entries in a network name service, such as the Network Information Service (NIS) or NIS+, so that the information is available to the data service clients. You can also create entries in the local /etc files to eliminate dependency on the network name service.
You are not required to create a home directory for the root user.
For each potential user whose home directory you are creating, type the following command:
# mkdir -p user-home
Specifies the full path of the home directory that you are creating.
You are not required to add the root user.
Use the useradd(1M) command to add each user. Adding a user to the system adds an entry for the user to the following files:
/etc/passwd
/etc/shadow
# useradd -u user-id -g group-name -d user-home \ [ -s user-shell] user-name
Specifies the user's unique numerical ID (UID) within the system.
Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.
Specifies the full path of the user's home directory. You must specify the home directory that you created for the user in Step 3.
Optionally specifies the full path name of the program that is to be used as the user's shell when the user logs in. If you omit the -s option, the system uses the /bin/sh program by default. If you specify the -s option, user-shell must specify a valid executable file.
Specifies the user name of the user that you are adding. You must specify the name of a potential user in the DBA group that you defined in Step 2.
Ensure that each user is identical on each node that can run Support for Oracle RAC.
Use the passwd(1) command to set the password of each user.
# password user-name
Specifies the user name of the user whose password you are setting. You must specify the name of a user in the DBA group that you added in Step 4.
The passwd command prompts you for the password.
The passwd command prompts you to retype the password.
Owner: the user for which you created the home directory
Group: the DBA group that you defined in Step 2
For each home directory for which you are changing ownership, type the following command:
# chown user-name:group-name user-home
Specifies the user name of the user for whose home directory you are changing ownership. You must specify the name of a user in the DBA group that you added in Step 4.
Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.
Specifies the full path of the user's home directory. You must specify the home directory that you created for the user in Step 3.
For each subdirectory that you are creating, type the following command:
# mkdir /var/opt/user-name
Specifies the user name of the user whose subdirectory of the /var/opt directory you are creating. You must specify the name of a user in the DBA group that you added in Step 4.
Owner: the user for which you created the directory
Group: the DBA group that you defined in Step 2
For each directory for which you are changing ownership, type the following command:
# chown user-name:group-name /var/opt/user-name
Specifies the user name of the user for whose home directory you are changing ownership. You must specify the name of a user in the DBA group that you added in Step 4.
Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.
Example 1-1 Creating the DBA Group and the DBA User Accounts
This example shows the sequence of commands for creating the DBA group dba, which is to contain the users root and oracle.
The dba group and the oracle user are created as follows:
The GID of the dba group is 520.
The home directory of the oracle user is /Oracle-home.
The UID of the oracle user is 120.
The oracle user's login shell is the Korn shell.
# echo 'dba:*:520:root,oracle' >> /etc/group # mkdir /Oracle-home # useradd -u 120 -g dba -d /Oracle-home -s /bin/ksh oracle # passwd oracle New Password:oracle Re-enter new Password:oracle passwd: password successfully changed for oracle # chown oracle:dba /Oracle-home # mkdir /var/opt/oracle # chown oracle:dba /var/opt/oracle
See Also
The following man pages:
Next Steps
Go to How to Configure Shared Memory for the Oracle RAC Software in the Global Cluster.
To enable the Oracle RAC software to run correctly, you must ensure that sufficient shared memory is available on all the cluster nodes. Perform this task on each cluster node.
You must configure these parameters on the basis of the resources that are available in the cluster. However, the value of each parameter must be sufficient to enable the Oracle RAC software to create a shared memory segment that conforms to its configuration requirements. For the minimum required value of each parameter, see your Oracle documentation.
The following example shows entries to configure in the /etc/system file.
*SHARED MEMORY/ORACLE set shmsys:shminfo_shmmax=4294967295
Caution - Before you reboot, you must ensure that any volume manager software that is already installed is completely installed. An incomplete installation of volume manager software causes a panic. If you use VxVM, also ensure that you have installed the software and that the license for the VxVM cluster feature is valid. Otherwise, a panic occurs when you reboot. For information about how to recover from a node panic during installation, see Node Panic During Initialization of Support for Oracle RAC. |
For detailed instructions, see Shutting Down and Booting a Single Node in a Cluster in Oracle Solaris Cluster System Administration Guide.
Next Steps
Go to Installing the Support for Oracle RAC Packages.
To configure shared memory for the Oracle RAC software in a zone cluster, perform the following steps:
For detailed instructions on configuring the shared memory in a global cluster, see How to Configure Shared Memory for the Oracle RAC Software in the Global Cluster.
Note - These steps do not affect the actual shared memory control for the zone cluster. You perform these steps to help Oracle dbca utility enables you to set the database memory allocation. If the Oracle dbca utility is not used for RAC database creation, you can skip these steps in the zone cluster.
#clzonecluster configure zcname clzonecluster:zcname> add capped-memory clzonecluster:cz1-2n:capped-memory> set physical=memsize clzonecluster:cz1-2n:capped-memory> set swap=memsize clzonecluster:cz1-2n:capped-memory> set locked=memsize clzonecluster:cz1-2n:capped-memory> end clzonecluster:cz1-2n>commit
Specifies the physical memory size.
Specifies the swap memory size.
Specifies the limit of the shared memory segment size that the Oracle RAC database processes can request to lock in memory.
Note - In addition to the locked attribute of the capped-memory property, you can use the max-shm-memory property to directly configure the limit of the shared memory segment in a zone cluster. See also the Solaris man page zonecfg(1M).
#clzonecluster reboot zcname
Note - You can perform the step to configure the capped-memory property attributes as part of the zone cluster creation. If you configure the capped-memory property attributes as part of the zone cluster creation, the memory-related properties immediately take effect after the first zone cluster boot. See How to Create a Zone Cluster in Oracle Solaris Cluster Software Installation Guide.
You should set the necessary privileges to enable Oracle RAC to run in a zone cluster configuration. You can use the clzonecluster command to include the necessary privileges in a zone cluster configuration by setting the limitpriv property. Perform the following steps to set the necessary privileges in a zone cluster to run Oracle RAC.
# clzonecluster configure zcname clzonecluster:zcname>set limitpriv ="default,proc_priocntl,proc_clock_highres" clzonecluster:zcname>commit
# clzonecluster reboot zcname
Note - You can perform the step to configure the limitpriv property as part of the zone cluster creation. For information on creating a zone cluster, see How to Create a Zone Cluster in Oracle Solaris Cluster Software Installation Guide.
To support logical hostname resources for an Oracle RAC 9i configuration and Oracle Clusterware virtual IP resources in Oracle RAC 10g and 11g configurations in zone clusters, you should configure the failover-capable hostnames or IP addresses used by those resources in a given zone cluster using the clzonecluster command.
Perform the following steps to configure the virtual IP addresses in a zone cluster configuration for Oracle RAC 10g or 11g.
# clzonecluster configure zcname clzonecluster:zcname>add net clzonecluster:zcname:net>set address=racnode1-vip clzonecluster:zcname:net>end clzonecluster:zcname>add net clzonecluster:zcname:net>set address=racnode2-vip clzonecluster:zcname:net>end clzonecluster:zcname>commit
# clzonecluster reboot zcname