7 Using Cloning to Add ASM and Oracle RAC to Nodes in a New Cluster

Deploying ASM Instance Homes

You must deploy the ASM home before you can deploy the new Oracle RAC database home. This section provides step-by-step instructions that describe how to:

1. Prepare the new cluster nodes

2. Deploy the ASM software

3. Run the clone.pl script on each node

4. Run the ASM_home/root.sh script on each node

5. Run NETCA to create the listeners

6. Run DBCA to create the ASM instances on each node

Step 1   Prepare the new cluster nodes

Perform the Oracle Database preinstallation steps, including such things as:

• Specify the kernel parameters.

• Use short, nondomain-qualified names for all names in the Hosts file.

• Test whether or not the interconnect interfaces are reachable using the ping command.

See your platform-specific Oracle RAC installation guide for a complete preinstallation checklist.

Step 2   Deploy the ASM software

To deploy the ASM software, you need to:

1. Restore the ASM home to all nodes in either the original home directory or to a different directory path. For example:

   [root@node1 root]# mkdir -p /opt/oracle/product/11g/asm
   [root@node1 root]# cd /opt/oracle/product/11g/asm
   [root@node1 asm]# tar –zxvf /pathname/asm11101.tgz
   

   Note that the ASM home location does not have to be in the same directory path as the original source home directory that you used to create the tar file.

2. Change the ownership of all files to the oracle and oinstall group. For example:

   [root@node1 asm]# chown –R oracle:oinstall /opt/oracle/product/11g/asm
   

Step 3   Run the clone.pl script on each node

To run the clone.pl script, which performs the main ASM cloning tasks, you must:

• Supply environment variables and cloning parameters in a start.sh script, as described in Table 7-1 and Table 7-2. Because the clone.pl script is sensitive to the parameters being passed to it, you must be accurate in your use of brackets, single quotes, and double quotes.

• Invoke the script as the oracle operating system user.

Example 7-1 shows an excerpt from the start.sh script that calls the clone.pl script.

ORACLE_BASE=/opt/oracle
ASM_home=/opt/oracle/product/11g/asm
cd ASM_home/clone
THISNODE=`hostname -s`
E01=ORACLE_HOME=${ASM_home}
E02=ORACLE_HOME_NAME=OraDBASM
E03=ORACLE_BASE=/opt/oracle
C01="-O'\"CLUSTER_NODES={node1, node2}\"'"
C02="'-O\"LOCAL_NODE=$THISNODE\"'"
perl ASM_home/clone/bin/clone.pl $E01 $E02 $E03 $C01 $C02

Table 7-1 describes the environment variables E01, E02, and E03 that are shown in bold typeface in Example 7-1.

Table 7-2 describes the cloning parameters C01 and C02, that are shown in bold typeface in Example 7-1.

Step 4   Run the ASM_home/root.sh script on each node

Run the ASM_home/root.sh as the root operating system user as soon as the clone.pl procedure completes on the node.

You should set the LD_LIBRARY_PATH environment variable before running the root.sh script. For example:

[root@node1 root]# export LD_LIBRARY_PATH=ASM_home/lib:$LD_LIBRARY_PATH
[root@node1 root]# /opt/oracle/product/11g/asm/root.sh -silent

Note that you can run the script on each node simultaneously:

[root@node2 root]# export LD_LIBRARY_PATH=ASM_home/lib:$LD_LIBRARY_PATH
[root@node2 root]# /opt/oracle/product/11g/asm/root.sh -silent

Ensure the script has completed on each node before proceeding to the next step.

Step 5   Run NETCA to create the listeners

At the end of the Oracle ASM home installation, the OUI creates a listener on each node, and registers the nodes as CRS resources with Oracle Clusterware.

The following example shows how to run NETCA in silent mode to create the listeners. In the response file, provide your node names in place of the variables: node1,node2. NETCA uses the response file to create the listener.ora entries on each node, start the listeners, and add the listeners to the Oracle Cluster Registry (OCR).

[oracle@node1 oracle]$ cd $ORACLE_HOME/bin/
[oracle@node1 bin]$ ./netca /silent \
            /responseFile $ORACLE_HOME/network/install/netca_typ.rsp \
            /inscomp server \
            /nodeinfo node1,node2

Step 6   Run DBCA to create the ASM instances on each node

This step shows how to invoke the DBCA in silent mode and provide response file input to create the ASM instances and the first ASM disk group.

The following example creates ASM instances on each node, registers them in the Oracle Cluster Registry, and creates an ASM disk group called +DATA that is made up of four disks: sde1, sdf1,sdg1 and sdh1. It also sets the SYS password to mypassword:

[oracle@node1 oracle]$ export ORACLE_HOME=/opt/oracle/product/11g/asm
[oracle@node1 oracle]$ cd $ORACLE_HOME/bin/
[oracle@node1 bin]$ ./dbca -silent -configureASM -gdbName NO -sid NO \
             -emConfiguration NONE \
             -diskList "/dev/sde1,/dev/sdf1,/dev/sdg1,/dev/sdh1" \
             -diskString "/dev/sd[e-h]1" \
             -diskGroupName "DATA" \
             -datafileJarLocation $ORACLE_HOME/assistants/dbca/templates \
             -nodeinfo node1,node2 \
             -obfuscatedPasswords false \
             -oratabLocation /etc/oratab \
             -asmSysPassword mypassword \
             -redundancy EXTERNAL

Deploying Oracle RAC Database Homes

Deployment to a new cluster of the Oracle RAC Database home is a multiple-step process. The steps are almost identical to the steps you performed to for creating the ASM home described in "Deploying ASM Instance Homes". The differences are that when deploying an Oracle RAC database, you do not create listeners inside the database home and you provide different DBCA parameters to deploy an Oracle RAC database home.

This section provides step-by-step instructions that describe how to:

1. Prepare the new cluster nodes

2. Deploy the Oracle RAC database software

3. Run the clone.pl script on each node

4. Run the $ORACLE_HOME/root.sh script on each node

5. Run DBCA to create the Oracle RAC instances on each node

Step 1   Prepare the new cluster nodes

Perform the Oracle Database preinstallation steps, including such things as:

• Specify the kernel parameters.

• Use short, nondomain-qualified names for all names in the Hosts file.

• Verify that you can ping the public and interconnect names.

• Ensure Oracle Clusterware is active.

• Ensure ASM is active and there is at least one ASM disk group configured.

See your platform-specific Oracle RAC installation guide for a complete preinstallation checklist.

Step 2   Deploy the Oracle RAC database software

To deploy the Oracle RAC database software, you need to:

1. Restore the Oracle Database home to all nodes. For example:

   [root@node1 root]# mkdir -p /opt/oracle/product/11g/db
   [root@node1 root]# cd /opt/oracle/product/11g/db
   [root@node1 db]# tar –zxvf /pathname/db11101.tgz
   

   When providing the home location and pathname:

   • If you are cloning Oracle RAC to a new cluster, then the home location can be in the same directory path or in a different directory path from the source home that you used to create the tar.

   • If you are cloning Oracle RAC to an existing cluster, then the home location and directory paths must be the same.

2. Change the ownership of all files to the oracle and oinstall group. For example:

   [root@node1 db]# chown –R oracle:oinstall /opt/oracle/product/11g/db
   

Step 3   Run the clone.pl script on each node

To run the clone.pl script, which performs the main Oracle RAC cloning tasks, you must:

• Supply the environment variables and cloning parameters in the start.sh script, as described in Table 7-3 and Table 7-4. Because the clone.pl script is sensitive to the parameters being passed to it, you must be accurate in your use of brackets, single quotes, and double quotes.

• Invoke the script as the oracle operating system user.

Example 7-2 shows an excerpt from the start.sh script that calls the clone.pl script.

ORACLE_BASE=/opt/oracle
ORACLE_HOME=/opt/oracle/product/11g/db
cd $ORACLE_HOME/clone
THISNODE=`hostname -s`

E01=ORACLE_HOME=${ORACLE_HOME}
E02=ORACLE_HOME_NAME=OraDBRAC
E03=ORACLE_BASE=/opt/oracle
C01="-O'\"CLUSTER_NODES={node1, node2}\"'"
C02="'-O\"LOCAL_NODE=$THISNODE\"'"

perl $ORACLE_HOME/clone/bin/clone.pl $E01 $E02 $E03 $C01 $C02

Table 7-3 describes the environment variables E01, E02, and E03 that are shown in bold typeface in Example 7-2.

Table 7-4 describes the cloning parameters C01 and C02, that are shown in bold typeface in Example 7-2.

Step 4   Run the $ORACLE_HOME/root.sh script on each node

Run the $ORACLE_HOME/root.sh as the root operating system user as soon as the clone.pl procedure completes on the node.

You should set the LD_LIBRARY_PATH environment variable before running the root.sh script. For example:

[root@node1 root]# export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
[root@node1 root]# /opt/oracle/product/11g/db/root.sh -silent

Note that you can run the script on each node simultaneously:

[root@node2 root]# export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
[root@node2 root]# /opt/oracle/product/11g/db/root.sh -silent

Ensure the script has completed on each node before proceeding to the next step.

Step 5   Run DBCA to create the Oracle RAC instances on each node

This step shows how to invoke the DBCA in silent mode and provide response file input to create the Oracle RAC instances.

The following example creates Oracle RAC instances on each node, registers the instances in the OCR, creates the database files in the ASM disk group called DATA, and creates sample schemas. It also sets the sys, system, sysman and dbsnmp passwords to mypassword:

[oracle@node1 oracle]$ export ORACLE_HOME=/opt/oracle/product/11g/db
[oracle@node1 oracle]$ cd $ORACLE_HOME/bin/
[oracle@node1 bin]$./dbca -silent -createDatabase -templateName General_Purpose.dbc\
           -gdbName ERI -sid ERI \
           -sysPassword mypassword -systemPassword mypassword \
           -sysmanPassword mypassword -dbsnmpPassword mypassword \
           -emConfiguration LOCAL \
           -storageType ASM -diskGroupName DATA \
           -datafileJarLocation $ORACLE_HOME/assistants/dbca/templates \
           -nodeinfo node1,node2 -characterset WE8ISO8859P1 \
           -obfuscatedPasswords false -sampleSchema true \
           -oratabLocation /etc/oratab