Installing Cluster Manager Oracle Database Tips by Donald Burleson

Step-by-step instructions for installing Oracle Cluster ManagerSoftware are detailed below.

1.      Launch the Installer by inserting Disk One for Oracle 9i into the CDRom of the Oracle1node. The operating system will mount the CD automatically and an icon for the CD will appear on the desktop. From a command line, launch the installer by typing the command /mnt/cdrom/runInstaller.

2.      When the welcome screen appears, click next. If the environmental variable for $ORACLE_BASE is correct, the path for the base directory will appear as shown.

3.      In the next step you will choose the UNIX group that will own the Oracle software files. Members of the oinstallgroup will have the ability to manipulate the files related to the database installation.

4.      To run the orainstRoot.sh script, open a new terminal window. Use the sucommand to switch to the root user, and then type the path and name of the script.

5.      If the environmental variable $ORACLE_HOME is set, the destination path will be correct as shown above.

6.      Choose the Oracle Cluster Managersoftware.

7.      Indicate the Public Node Names

8.      Indicate the Private Node Names

9.      Indicate the Quorum Disk Information (case sensitive!).

10.  The summary screen will list the software that is about to be installed. As you watch the progression of the install, you will see that the files are copied from oracle1 to oracle2.

11.  The installation of Cluster Manager will finish quickly.

Configuring and Starting Cluster Manager

Now that Cluster Manager has been installed, it must be configured and started. Begin by using geditto edit the file $ORACLE_HOME/oracm/admin/cmcfg.ora so that it includes the additions and changes shown in Figure 6.3. This file should be edited on each node. The only difference between the two nodes is on line nine, where the name of the node on the private network is indicated. 

To start the Cluster Manager, use the sucommand to switch to root user and issue the commands shown in Figure 6.4. Cluster Manager software relies on the hangcheck-timer kernel module which is preloaded with the parameters shown. The ocmstart.sh script starts the Oracle Cluster Manager software.

Use the command ps ?ef to list all running processes. This command can be piped into grep which limits the output to lines which contain oracmbut do not contain grep as shown in Figure 6.4. It is normal for oracm to spawn several processes of itself.

In order for the process oracmto run, the node it runs on must have read and write access to the shared configuration file CMquorum.dbf. If a problem is encountered, oracm will not be found by the ps -ef command. To find the problem, view the contents of the $ORACLE_HOME/oracm/log/cm.log file.

If it is necessary to stop the oracmprocess, use the pkill oracm command as root. In order to restart oracm, the file $ORACLE_HOME/oracm/log/ocmstart.ts must be deleted if its timestamp is too recent. It can be deleted with the rm command.

If you want to learn RAC at home, get the bestselling book "Personal Oracle Real Application Clusters" by Edward Stoever. You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.