In this Document
Goal
Background: Adding new nodes to a cluster
Background: Using cloning for CRS home
Purpose of this note
Solution
Usage
Example - Specifying information about the voting disk(s)
Scalability RAC Community
References
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.3 and later [Release: 10.2 and later ]
Information in this document applies to any platform.
Goal
When using the "cloning" method to add a new node to a cluster, how to specify options such as the OCR and Voting disk location?
Background: Adding new nodes to a cluster
Starting
with 10gR2, there are two methods available to add new nodes to a
cluster. The first method is to use the 'addNode.bat' script. The
second method is to use the "cloning" procedure.
Both methods are documented:
UNIX:
Chapter 10 - Adding and Deleting Nodes and Instances on UNIX-Based Systems
http://download-west.oracle.com/docs/cd/B19306_01/rac.102/b14197/adddelunix.htm
WINDOWS:
addNode.sh -
Chapter 11 - Adding and Deleting Nodes and Instances on Windows-Based Systems
http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/adddelwin.htm
cloning -
Note 407086.1 - USING CLONING IN CRS/RAC WINDOWS ENVIRONMENTS TO ADD A NODE
(Note:
The cloning procedure in Windows is also documented in chapter 11,
however, for CRS home cloning, please use the instructions in Note 407086.1 instead.)
Background: Using cloning for CRS home
This
is a brief overview of the cloning procedure, used to clone a CRS home
from an existing node to a new one. (It assumes that you have already
successfully installed an Oracle Clusterware home on at least one node.)
1. Tar (Unix) or zip (windows) the CRS home on the existing node.
2. Copy the file to the new node's CRS home
3.
Make sure that the new node meets all of the hardware, software,
network, etc. requirements in the installation guide and has settings
that match up with the existing node(s) in the cluster. For example:
* Make sure that the shared disks are accessible for the new nodes
* cluster interconnect NIC must have the same name as the other nodes
(Unix) or binding order is correct for network cards (Windows)
* Correct user and group(s) exist on the new node (Unix)
* the user that performs the cloning is the same as the user that performed the installation (Windows)
4. Untar/unzip the archived CRS home on the new node
5. Unix: Run the "clone.pl" perl script from the new node
Windows: run "setup.exe -clone" command from the new node
6. Unix:
* Run orainstRoot.sh root.sh on the new node.
* Set up ONS and interfaces on the new node.
Windows:
* Run cfgToolAllCommands.
There
may be additional steps or some differences depending on the situation
(eg. whether using cloning to create a new cluster or to add a node to
an existing cluster, etc.) For full instructions, please see the
documentation & note referenced above.
Purpose of this note
The goal of
this note is to show how to specify options to "clone.pl" or "setup.exe
-clone", when cloning an Oracle Clusterware home. This applies to step 5
in the above steps and doesn't affect any of the other steps. All
other steps must still be followed.
Oracle© Clusterware Administration and Deployment Guide
11g Release 1 (11.1)
Part Number B28255-06
Chapter 3: Cloning Oracle Clusterware
This supersedes this note and should be used as the reference for 11g. The cloning procedure has not changed significantly from 10gR2 to 11g, so it can also be referred to for 10gR2.
Solution
There are command line options to clone.pl with which you can specify options such as the OCR and Voting disk location.
You can see more information on the command line options that are available to you by checking the
OUI sample CRS response file. The clone.pl process is a way to shortcut the OUI process without
having to re-extract the files, and so it takes some of the same options.
To see the OUI sample CRS response file: On the CRS installation media, navigate to the directory
Disk1/response and open the file crs.rsp in a text editor. See Note 336912.1 for more information
on this file. These are the variables from the response file that you can use:
1. n_storageTypeVDSK (2=externally redundant, 1=not externally redundant)
2. n_storageTypeOCR (2=externally redundant, 1=not externally redundant)
3. s_clustername
4. ret_PrivIntrList (Required only if you want to change default values.)
5. sl_tableList
6. s_votingdisklocation
7. s_OcrVdskMirror1RetVal (Optional. Please see the explanation in rsp file)
8. s_ocrpartitionlocation
9. s_ocrMirrorLocation (Optional. Please see the explanation in rsp file)
10. s_VdskMirror2RetVal (Optional. Please see the explanation in rsp file)
The meaning of these variables is explained in the crs.rsp sample response file.
Fill out these variables exactly as mentioned in the example in the response file.
Usage
For clone.pl, pass these values after the -O option. Anything following the -O is passed to the OUI clone command line as is.
The OUI documentation gives the following command to run clone.pl (Unix):
perl clone.pl ORACLE_HOME=<$CRS_HOME> ORACLE_HOME_NAME=Oracle_home_name
'-On_storageTypeVDSK=2' '-On_storageTypeOCR=2'
'-O"sl_tableList={new_node:new_node-priv:new_node-vip}"'
'-O-noConfig''-O"INVENTORY_LOCATION=central_inventory_location"'
Here is an example of how to modify that command to specify more information about the voting disks.
Example - Specifying information about the voting disk(s)
First, understanding the recommended parameter '-On_storageTypeVDSK=2'
In crs.rsp we find the following :
###############################################################################
# The following entries can be used to specify inforamtion about your voting #
# disks(s).
###############################################################################
#------------------------------------------------------------------------------
#Name : n_storageTypeVDSK
#Datatype : Integer
#Description: Represents the redundancy characteristics of the disk used for
# storing the voting disk(s).
#
# This entry is a number that can take on the values of 1 or 2.
# These values have the following meaning:
# a. 1 = Not Redundant. In this case, you should specify three
# voting disks to eliminate the possibility of a single point
# of failure.
# b. 2 = Externally Redundant. This disk you are placing the
# voting disk on already has some form of external redundancy
# solution. In this case, you need only use one voting disk.
#Example : n_storageTypeVDSK = 1
#------------------------------------------------------------------------------
n_storageTypeVDSK=<Value Unspecified>
Therefore the value of "2" is appropriate if the voting disk is appropriate, if not, change it to "1".
Now, for specifying the actual location of the voting disk. In crs.rsp we find the following :
#Name : s_votingdisklocation
#Datatype : String
#Description: The location of your first voting disk.
#Example : s_votingdisklocation = "/oradbshare/oradata/vdisk"
#------------------------------------------------------------------------------
s_votingdisklocation=<Value Unspecified>
Therefore the argument to add to the clone.pl command to specify a voting disk location of /dev/crsdisk/vote1 is :
'-O"s_votingdisklocation=/dev/crsdisk/vote1"'
If the voting disk is not externally redundant then you would also specify a 2nd and 3rd location
'-O"s_OcrVdskMirror1RetVal=/dev/crsdisk/vote2"'
'-O"s_VdskMirror2RetVal=/dev/crsdisk/vote3"'
With
these changes, the full command to clone a CRS home, with 3
non-redundant voting disks at /dev/crsdisk/vote1, /dev/crsdisk/vote2,
/dev/crsdisk/vote3, would be:
perl clone.pl ORACLE_HOME=<$CRS_HOME> ORACLE_HOME_NAME=Oracle_home_name
'-On_storageTypeVDSK=1' '-On_storageTypeOCR=2'
'-O"sl_tableList={new_node:new_node-priv:new_node-vip}"'
'-O-noConfig''-O"INVENTORY_LOCATION=central_inventory_location"'
'-O"s_votingdisklocation=/dev/crsdisk/vote1"'
'-O"s_OcrVdskMirror1RetVal=/dev/crsdisk/vote2"'
'-O"s_VdskMirror2RetVal=/dev/crsdisk/vote3"'
NB: Adding parameters to the clone.pl command doesn't remove any of the
other steps in the cloning procedure. All other steps must still be
followed.
If using "setup.exe -clone", following the steps in Note 407086.1, you do not need to use the -O option in order to use these parameters. For example, the command given in Note 407086.1 is :
setup.exe -clone -silent ORACLE_HOME=E:\oracle\product\10.2.0\crs ORACLE_HOME_NAME=
OraCr10g_home
n_storageTypeVDSK=1 n_storageTypeOCR=1
"sl_tableList={rmntops2:rmntops2-priv:rmntops2-vip}"
PERFORM_PARTITION_TASKS=false -noconfig -debug
To modify this to use external redundancy for the voting disk, just use
"n_storageTypeVDSK=2"
instead of
"n_storageTypeVDSK=1" .
Oracle� Clusterware Administration and Deployment Guide
11g Release 1 (11.1)
Part Number B28255-06
Chapter 3: Cloning Oracle Clusterware
Section 3.3: Cloning Script Variables Reference
This supersedes this note and should be used as the reference for 11g. The cloning procedure has not changed significantly from 10gR2 to 11g, so it can also be referred to for 10gR2.
Scalability RAC Community
To
discuss this topic further with Oracle experts and industry peers, we
encourage you to review, join or start a discussion in the My Oracle Support Scalability RAC Community.
References
NOTE:336912.1 - Installing Oracle Clusterware Using a Cluster Configuration File
NOTE:407086.1 - USING CLONING IN CRS/RAC WINDOWS ENVIRONMENTS TO ADD A NODE
NOTE:565009.1 - FAQs on RDBMS Oracle Home Cloning Using OUI
OracleÃÂî Universal Installer and OPatch User's Guide, 10g Release 2 (10.2) for Windows and UNIX, Chapter 7
浙公网安备 33010602011771号