| Red Hat Docs > Manuals > Cluster Suite/GFS Manuals > |
|
| Red Hat GFS: Installing and Configuring Oracle9i RAC with GFS 6.0 | ||
|---|---|---|
| Prev | Chapter 3. Installing and Configuring Oracle9i RAC | Next |
Installing and configuring Oracle components consists of the following tasks:
Installing Oracle Cluster Manager includes using the Red Hat GFS CDPN (Context Dependent Path Name) for the following directories:
$ORACLE_HOME/network
$ORACLE_HOME/oracm
Database's archive directory
To install the Cluster Manager, follow these steps:
At the Oracle management node, log in to the Oracle account.
 | Note |
|---|---|
This step is performed only from one node, the Oracle management node. |
Set up rsh on all nodes for user oracle and add private and public hostnames.
Run the Oracle Universal Installer from a CD-ROM or from stage directories.
From CD-ROM — Change directories and run the installation program. For example :
$ cd /home/oracle $ /cdrom/runInstaller |
From stage directories — Change directories and run the installation program. For example:
$ cd /stage/Disk1 $ ./runInstaller |
Running the Oracle Universal Installer causes a Welcome dialog box to be displayed. Click Next. Clicking Next causes the Inventory Location dialog box to be displayed.
At the What would you like as the base directory? dialog box, verify that the base directory is set to the $ORACLE_BASE directory from your environment variable. If so, click OK. Clicking OK causes the UNIX Group Name dialog box to be displayed.
At the UNIX Group Name dialog box, enter the group name, dba (created in Step 1 of Section 3.3 Preparing Oracle Nodes) and click Next. Clicking Next may cause an Oracle Universal Installer dialog box to be displayed that prompts you to run /tmp/orainstRoot.sh. In another terminal window, log in as root, and run the command as stated in the dialog box. After running the command, click Continue in the Oracle Universal Installer dialog box. Clicking Continue causes the File Locations dialog box to be displayed.
At the File Locations dialog box, under Destination..., verify that the ORACLE_HOME directory path is correct. At Name, type a name (for example, ora9i) and click Next. Clicking Next causes the Available Products dialog box to be displayed.
At the Available Products dialog box, select Oracle Cluster Manager 9.2.0.4.0 (for this manual) and click Next. Clicking Next causes the Public Node Information dialog box to be displayed.
At the Public Node Information dialog box, type the public hostnames for all nodes. Click Next. Clicking Next causes the Private Node Information dialog box to be displayed.
At the Private Node Information dialog box, type the private hostnames for all nodes.
Click Next. Clicking Next causes the Quorum Disk Information dialog box to be displayed.
At the Quorum Disk Information dialog box, type the full name of the raw device that has been mapped to the oraraw1 quorum disk (in the example configuration, /dev/raw/raw1). Click Next. Clicking Next causes a Summary dialog box to be displayed.
If the summary information is correct, click Install. If the summary information is incorrect, click Previous and perform the preceding step.
Upon completion of installation, the End of Installation dialog box is displayed. Click Exit and proceed to Section 3.4.2 Patching the Cluster Manager.
Acquire the 9.2.0.4 patch for the Cluster Manager. Use the Oracle Universal Installer to apply the patch. Proceed to Section 3.4.3 Modifying the $ORACLE_HOME/oracm/admin/cmcfg.ora File.
After you have installed and patched the Cluster Manager software, modify the $ORACLE_HOME/oracm/admin/cmcfg.ora file as follows:
Check to see that your system has a cmcfg.ora file. If there is no cmcfg.ora file, copy cmcfg.ora.tmp to cmcfg.ora.
If the hangcheck-timer module is not yet loaded, load it on each node:
rac1 # insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 |
rac2 # insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 |
rac3 # insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 |
rac4 # insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 |
In addition, at each node, add the following insmod command (same as in the preceding text) to etc/modules.conf to load the hangcheck-timer during reboot:
insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 |
Move to the $ORACLE_HOME/oracm/admin directory and make the following modifications to the cmcfg.ora file:
Add a HeartBeat variable set to 15000.
Add a PollInterval variable set to 1000.
Raise the MissCount variable to 215.
If the WatchDog timer is present, delete it.
Add a new variable, KernelModuleName=hangcheck-timer (a replacement for the WatchDog timer).
Add HostName, using public network name.
| Note |
|---|---|
The reason for replacing the WatchDog timer with hangcheck-timer is that the Cluster Manager software uses the much improved GPL hangcheck-timer. |
Refer to Example 3-2 for a sample modified cmcfg.ora file:
### CMCFG.ORA ### HeartBeat=15000 <--------- Added HeartBeat parameter ClusterName=Oracle Cluster Manager, version 9i PollInterval=1000 <--------- Added PollInterval parameter MissCount=215 <--------- Raised to 215 PrivateNodeNames=racpvt1 racpvt2 racpvt3 racpvt4 PublicNodeNames=rac1 rac2 rac3 rac4 ServicePort=9998 KernelModuleName=hangcheck-timer <-- Added, replacing Watchdog timer CmDiskFile=/dev/raw/raw1 HostName=rac1 <--------- Added HostName, using public network name |
Example 3-2. Sample cmcfg.ora File
Proceed to Section 3.4.4 Enabling oracm CDPN.
After modifying the cmcfg.ora file, create a Context Dependent Path Name (CDPN) as follows:
At any node in the network, change to the $ORACLE_HOME directory and make directories as follows:
# cd $ORACLE_HOME # mkdir rac1 rac2 rac3 rac4 |
Run the following script from $ORACLE_HOME:
$ for i in `ls -d rac*`; do cp -r oracm $i; done |
Move the oracm directory to oracm.orig using the following command:
$ mv oracm oracm.orig |
To create the CDPN, enter the following:
$ ln -s @hostname/oracm oracm |
Proceed to Section 3.4.5 Configuring Cluster Manager.
To configure the Cluster Manager, follow these steps for each node:
Change to the $ORACLE_HOME/oracm/admin directory.
Check the cmcfg.ora file to make sure that the HostName= parameter is included in the file. If the HostName= parameter is not present, add the parameter with its value equal to the private interface hostname of that node. For example, if the private interface hostname of the node was set to racpvt1 (during installation of the Oracle Cluster Manager, Section 3.4.1 Installing Oracle Cluster Manager), then the HostName= parameter should be set to racpvt1.
Example 3-3 shows the cmcfg.ora file of the node with the private interface hostname of racpvt1. The HostName= parameter has been set to racpvt1.
### CMCFG.ORA ### HeartBeat=15000 ClusterName=Oracle Cluster Manager, version 9i PollInterval=1000 MissCount=215 PrivateNodeNames=racpvt1 racpvt2 racpvt3 racpvt4 PublicNodeNames=rac1 rac2 rac3 rac4 ServicePort=9998 KernelModuleName=hangcheck-timer CmDiskFile=/dev/raw/raw1 HostName=racpvt1 <-- Hostname= set to racpvt1 |
Example 3-3. Hostname= Set to racpvt1
Proceed to Section 3.4.6 Starting Oracle Cluster Manager.
At each node, log in as the root user and run the following:
# . ~oracle/.bash_profile |
# cd $ORACLE_HOME/oracm/bin |
# ./ocmstart.sh |
Check for oracm processes.
Proceed to Section 3.4.7 Installing Oracle RDBMS.
To install Oracle RDBMS, follow these steps:
Start the Oracle Universal Installer from a CD-ROM or from stage directories.
From CD-ROM — Change directories and run the installation program. For example :
$ cd /home/oracle $ /cdrom/runInstaller |
From stage directories — Change directories and run the installation program. For example:
$ cd /stage/Disk1 $ ./runInstaller |
At the Cluster Node Selection dialog box, select the master node and click Next.
| Note |
|---|---|
Because you are using a shared ORACLE_HOME, you only need to select the master node. |
Navigate to the Available Products dialog box, select Oracle9i Database 9.2.0.4.0, and click Next. Clicking Next causes the Installation Types dialog box to be displayed.
At the Installation Types dialog box, click Custom and Next.
At the Available Product Components dialog box, ensure that Oracle9i Real Application Cluster 9.2.0.4.0 is selected. Check other components for which you are licensed and click Next. Clicking Next causes the Component Locations dialog box to be displayed. At that dialog box, click Next. (The Component Locations dialog box shows which components have been selected.)
At the Shared Configuration File Name dialog box, enter the second raw file pointing to the second quorum pool oraraw2 (in the example configuration, /dev/raw/raw2) and click Next.
At the Summary dialog box, ensure that it shows that the Real Application Cluster software installs. Click Install.
At the Setup Privileges dialog box (resulting from the previous step), you are asked to log in to each node as the root user and run $ORACLE_HOME/root.sh. Click OK after you have verified that the file /var/opt/oracle/srvConfig.loc exists, and that it points to the quorum pool oraraw2.
At the End of Installation dialog box, click Exit. You have completed the installation of software.
Proceed to Section 3.4.8 Patching the RDBMS Server.
Acquire the 9.2.0.4 patch for the RDBMS server. Use the Oracle Universal Installer to apply the patch. Proceed to Section 3.5 Creating an Oracle Database.