Call for Oracle support & training (800) 766-1884
Free Oracle Tips

Home
Corporate Oracle Training
Custom Oracle Training
Oracle New Features Training
Advanced Oracle DBA Classes
Oracle Tuning Courses
Oracle Tips & Tricks
Oracle Training Links
Oracle Training Links
Oracle Training Links

We are top for USA Oracle Training Clients

 

Free Oracle Tips


 
HTML Text AOL

Free Oracle App Server Tips


 
HTML Text

Oracle support

Oracle training

Oracle tuning

Rednecks!

Remote Oracle

Custom Oracle Training

Donald K. Burleson

Oracle RAC Tips

Configure HP ServiceGuard Cluster

After all the LAN cards are installed and configured, and all the RAC volume groups and the cluster lock volume groups are configured, the cluster configuration can be started. The following sequence is very important. However, if the RAC volume groups are unknown at this time, the cluster should be configured minimally with a lock volume group.

By now, the cluster lock volume group should have been created. Since only one volume group was configured for the entire RAC cluster vg_ops is used for the lock volume as well.

  1. Create a cluster configuration template:

$ cmquerycl -n nodeA -n nodeB -v -C /etc/cmcluster/rac.asc

  1. Edit the cluster configuration file (rac.asc).

The cluster configuration file should be set with both DLM and GMS enabled clauses to NO, since neither need be configured with Oracle9i RAC. The Oracle kernel now handles global cache management transparently. For compatibility with older versions of Oracle, the cluster configuration file still contains a section for DLM and GMS. The necessary changes have to be made with this file for the cluster. For example, change the ClusterName and adjust the heartbeat interval and node timeout to prevent unexpected failovers due to GCM traffic.

  1. Check the cluster configuration:

$ cmcheckconf -v -C rac.asc

  1. The lock disk should be activated on the configuration node only. Lock volume can only be activated on the node where the cmapplyconf command is issued so that the lock disk can be initialized accordingly.

$ vgchange -a y /dev/vg_rac

  1. Create the binary configuration file and distribute the cluster configuration to all the nodes in the cluster:

$ cmapplyconf -v -C rac.asc

Note: The cluster is not started until cmrunnode is run on each node or cmruncl.

  1. De-activate the lock disk on the configuration node after cmapplyconf:

$ vgchange -a n /dev/vg_rac

  1. Start the cluster and make sure it is up and running. After testing the cluster, shut it down in order to make changes later to the HP-UX kernel parameters.

Start the cluster from any node in the cluster:

$ cmruncl -v

Or, on each node:

$ cmrunnode -v

  1. Make all RAC volume groups and Cluster Lock volume groups sharable and cluster aware (not packages) from the cluster configuration node:

$ vgchange -S y -c y /dev/vg_rac

  1. On all the nodes, activate the volume group in shared mode in the cluster:

$ vgchange -a s /dev/vg_rac

  1. Check the cluster status:

$ cmviewcl -v

  1. On all the nodes, deactivate the volume group in shared mode in the cluster:

$ vgchange -a n vg_rac

  1. Halt the cluster from any node in the cluster:

$ cmhaltcl -v

  1. Check the cluster status:

$ cmviewcl -v

For more details refer to the white paper: “Oracle9i Real Application Clusters (RAC) on HP-UX” by Rebecca Kühn, Rainer Marekwia, HP/Oracle Cooperative Technology Center.


For more information, see the book Oracle 11g Grid and Real Application Clusters 30% off if you buy it directly from Rampant TechPress . 

Written by top Oracle experts, this RAC book has a complete online code depot with ready to use RAC scripts.

 

 

 
 
 

Oracle performance tuning book

 

 

Oracle performance tuning software

 
Oracle performance tuning software
 
Oracle performance Tuning 10g reference poster
 
Oracle training in Linux commands
 
Oracle training Excel
 
 
 
 
 
email BC:


Copyright © 1996 -  2014 by Burleson Inc. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.