5 Cloning Oracle Clusterware

Step 1: Install Oracle Clusterware

Use the detailed instructions in the Oracle Grid Infrastructure Installation Guide to perform the following steps on the source node:

1. Install Oracle Clusterware 11g release 2 (11.2). This installation puts Oracle Cluster Registry (OCR) and the voting disk on Oracle Automatic Storage Management (Oracle ASM).

   Note:

   Either install and configure the Grid Infrastructure for a cluster or install just the Oracle Clusterware software, as described in your platform-specific Oracle Grid Infrastructure Installation Guide.

   If you installed and configured Grid Infrastructure for a cluster, then you must stop Oracle Clusterware before performing the cloning procedures. If you performed a software-only installation, then you do not have to stop Oracle Clusterware.

2. Install any patches that are required (for example, a Grid Infrastructure bundle patch), if necessary.

3. Apply one-off patches, if necessary.

   See Also:

   Oracle Grid Infrastructure Installation Guide for Oracle Clusterware installation instructions

Step 2: Shut Down Running Software

Before copying the source Oracle Grid Infrastructure home, shut down all of the services, databases, listeners, applications, Oracle Clusterware, and Oracle ASM instances that run on the node. Oracle recommends that you use the Server Control (SRVCTL) utility to first shut down the databases, and then the Oracle Clusterware Control (CRSCTL) utility to shut down the rest of the components.

Step 3: Create a Copy of the Oracle Grid Infrastructure Home

To keep the installed Oracle Grid Infrastructure home as a working home, make a full copy of the source Oracle Grid Infrastructure home for cloning.

Use one of the following methods to create a compressed copy of the Oracle Grid Infrastructure home.

Method 1: Create a copy of the Oracle Grid Infrastructure home and remove the unnecessary files from the copy:

1. On the source node, create a copy of the Oracle Grid Infrastructure home. To keep the installed Oracle Grid Infrastructure home as a working home, make a full copy of the source Oracle Grid Infrastructure home and remove the unnecessary files from the copy. For example, as root on Linux systems, run the cp command:

   # cp -prf Grid_home copy_path
   

   The preceding command copies the entire contents of Grid_home (for example, /u01/app/grid/11.2.0) to a new location (for example, /home/grid/gridcopy).

2. Delete unnecessary files from the copy.

   The Oracle Grid Infrastructure home contains files that are relevant only to the source node, so you can remove the unnecessary files from the copy of the Grid Infrastructure home in the log, crs/init, crf, and cdata directories. The following example for Linux and UNIX systems shows the commands to run to remove the unnecessary files from the copy of the Oracle Grid Infrastructure home:

   [root@node1 root]# cd copy_path
   [root@node1 grid]# rm -rf crs/install/crsconfig_addparams
   [root@node1 grid]# rm -rf host_name
   [root@node1 grid]# rm -rf log/host_name
   [root@node1 grid]# rm -rf gpnp/host_name
   [root@node1 grid]# find gpnp -type f -exec rm -f {} \;
   [root@node1 grid]# find cfgtoollogs -type f -exec rm -f {} \;
   [root@node1 grid]# rm -rf crs/init/*
   [root@node1 grid]# rm -rf cdata/*
   [root@node1 grid]# rm -rf crf/*
   [root@node1 grid]# rm -rf network/admin/*.ora
   [root@node1 grid]# find . -name '*.ouibak' -exec rm {} \;
   [root@node1 grid]# find . -name '*.ouibak.1' -exec rm {} \;
   [root@node1 grid]# rm -rf root.sh*
   

3. Create a compressed copy of the previously copied Oracle Grid Infrastructure home using tar or gzip on Linux and UNIX systems. Ensure that the tool you use preserves the permissions and file timestamps. For example:

   On Linux and UNIX systems:

   [root@node1 root]# cd copy_path
   [root@node1 grid]# tar -zcvpf /copy_path/gridHome.tgz .
   

   In the preceding example, the cd command changes the location to the copy of the Oracle Grid Infrastructure home with the unnecessary files removed that you created in the first two steps of this procedure, and the tar command creates a file named gridHome.tgz. In the tar command, copy_path represents the location of the copy of the Oracle Grid Infrastructure home.

   On AIX or HPUX systems:

   tar cpf - . | compress -fv > temp_dir/gridHome.tar.Z
   

   On Windows systems, use WinZip to create a zip file.

Method 2: Create a compressed copy of the Oracle Grid Infrastructure home using the -X option:

1. Create a file that lists the unnecessary files in the Oracle Grid Infrastructure home. For example, list the following file names, using the asterisk (*) wildcard, in a file called excludeFileList:

   Grid_home/host_name
   Grid_home/log/host_name
   Grid_home/gpnp/host_name
   Grid_home/crs/init/*
   Grid_home/cdata/*
   Grid_home/crf/*
   Grid_home/network/admin/*.ora
   Grid_home/root.sh*
   *.ouibak
   *.ouibak1
   

2. Use the tar command or Winzip to create a compressed copy of the Oracle Grid Infrastructure home. For example, on Linux and UNIX systems, run the following command to archive and compress the source Oracle Grid Infrastructure home:

   tar cpfX - excludeFileList Grid_home | compress -fv > temp_dir/gridHome.tar.Z
   

   Note:

   Do not use the jar utility to copy and compress the Oracle Grid Infrastructure home.

Step 1: Prepare the New Cluster Nodes

On each destination node, perform the following preinstallation steps:

• Specify the kernel parameters

• Configure block devices for Oracle Clusterware devices

• Ensure that you have set the block device permissions correctly

• Use short, nondomain-qualified names for all of the names in the /etc/hosts file

• Test whether the interconnect interfaces are reachable using the ping command

• Verify that the VIP addresses are not active at the start of the cloning process by using the ping command (the ping command of the VIP address must fail)

• Copy the following Oracle Automatic Storage Management Cluster File System tunable files from the source node to each destination node:

  On Linux and UNIX: /etc/sysconfig/advmtunables and /etc/sysconfig/acfstunables

  On AIX: /etc/advmtunables and /etc/acfstunables

  On Solaris: /etc/advmtunables and /etc/acfstunables

  On Windows: C:\windows\system32\drivers\advm\tunables and C:\windows\system32\drivers\acfs\tunables

• On AIX systems, and on Solaris x86-64-bit systems running vendor clusterware, if you add a node to the cluster, then you must run the rootpre.sh script (located at the mount point it you install Oracle Clusterware from a DVD or in the directory where you unzip the tar file if you download the software) on the node before you add the node to the cluster

• Run CVU to verify your hardware and operating system environment

Refer to your platform-specific Oracle Clusterware installation guide for the complete preinstallation checklist.

Step 2: Deploy the Oracle Grid Infrastructure Home on the Destination Nodes

Before you begin the cloning procedure that is described in this section, ensure that you have completed the prerequisite tasks to create a copy of the Oracle Grid Infrastructure home, as described in the section titled "Preparing the Oracle Grid Infrastructure Home for Cloning".

1. On each destination node, deploy the copy of the Oracle Grid Infrastructure home that you created in "Step 3: Create a Copy of the Oracle Grid Infrastructure Home", as follows:

   If you do not have a shared Oracle Grid Infrastructure home, then restore the copy of the Oracle Grid Infrastructure home on each node in the destination cluster. Use the equivalent directory structure as the directory structure that was used in the Oracle Grid Infrastructure home on the source node. Skip this step if you have a shared Oracle Grid Infrastructure home.

   For example, on Linux or UNIX systems, run commands similar to the following:

   [root@node1 root]# mkdir -p location_of_the_copy_of_the_Grid_home
   [root@node1 root]# cd location_of_the_copy_of_the_Grid_home
   [root@node1 crs]# tar -zxvf /path_name/gridHome.tgz
   

   In this example, path_name represents the directory structure in which you want to install the Oracle Grid Infrastructure home. Note that you can change the Grid home location as part of the clone process.

   On Windows systems, unzip the Oracle Grid Infrastructure home on the destination node in the equivalent directory structure as the directory structure in which the Oracle Grid Infrastructure home resided on the source node.

2. If you have not already deleted unnecessary files from the Oracle Grid Infrastructure home, then repeat step 2 in "Method 1: Create a copy of the Oracle Grid Infrastructure home and remove the unnecessary files from the copy:".

3. Create a directory for the Oracle Inventory on the destination node and, if necessary, change the ownership of all of the files in the Oracle Grid Infrastructure home to be owned by the Oracle Grid Infrastructure installation owner and by the Oracle Inventory (oinstall privilege) group. If the Oracle Grid Infrastructure installation owner is oracle, and the Oracle Inventory group is oinstall, then the following example shows the commands to do this on a Linux system:

   [root@node1 crs]# mkdir /u01
   [root@node1 crs]# chown oracle:oinstall /u01
   [root@node1 crs]# mkdir -p /u01/app/oraInventory
   [root@node1 crs]# mkdir -p /u01/app/11.2.0/grid
   

   When you run the last of the preceding commands on the Grid home, it clears setuid and setgid information from the Oracle binary. It also clears setuid from the following binaries:

   Grid_home/bin/extjob
   Grid_home/bin/jssu
   Grid_home/bin/oradism
   

   Run the following commands to restore the cleared information:

   chmod u+s Grid_home/bin/oracle
   chmod g+s Grid_home/bin/oracle
   chmod u+s Grid_home/bin/extjob
   chmod u+s Grid_home/bin/jssu
   chmod u+s Grid_home/bin/oradism
   

4. It is important to remove any Oracle network files from the Grid_home directory on both the source and destination nodes before continuing. For example, remove any tnsnames.ora, listener.ora, or sqlnet.ora files.

   See Also:

   "Locating and Viewing Log Files Generated During Cloning"

Step 3: Run the clone.pl Script on Each Destination Node

To set up the new Oracle Clusterware environment, the clone.pl script requires you to provide several setup values for the script. You can provide the variable values by either supplying input on the command line when you run the clone.pl script, or by creating a file in which you can assign values to the cloning variables. The following discussions describe these options.

-O'"CLUSTER_
NODES={node_
name,node_
name,...}"'

-O'"LOCAL_NODE=node_name"'

CRS=TRUE

$ perl clone.pl -silent ORACLE_BASE=/u01/app/oracle ORACLE_HOME=
/u01/app/11.2.0/grid ORACLE_HOME_NAME=OraHome1Grid
INVENTORY_LOCATION=/u01/app/oraInventory -O'"CLUSTER_NODES={node1, node2}"'
-O'"LOCAL_NODE=node1"' CRS=TRUE

C:\>perl clone.pl ORACLE_BASE=D:\u01\app\grid ORACLE_HOME=D:\u01\app\grid\11.2.0
ORACLE_HOME_NAME=OraHome1Grid "CLUSTER_NODES={node1, node2}"
"LOCAL_NODE=node1" CRS=TRUE

#!/bin/sh
ORACLE_BASE=/u01/app/oracle
GRID_HOME=/u01/app/11.2.0/grid
THIS_NODE=’hostname -s’

E01=ORACLE_BASE=${ORACLE_BASE}
E02=ORACLE_HOME=${GRID_HOME}
E03=ORACLE_HOME_NAME=OraGridHome1
E04=INVENTORY_LOCATION=${ORACLE_BASE}/oraInventory

#C00="-O'-debug'"
C01="-O'\"CLUSTER_NODES={node1,node2}\"'"
C02="-O'\"LOCAL_NODE=${THIS_NODE}\"'"

perl ${GRID_HOME}/clone/bin/clone.pl -silent $E01 $E02 $E03 $E04 $C01 $C02

Step 4: Launch the Configuration Wizard

The Configuration Wizard helps you to prepare the crsconfig_params file, prompts you to run the root.sh script (which calls the rootcrs.pl script), relinks Oracle binaries, and runs cluster verifications.

Start the Configuration Wizard, as follows:

$ Oracle_home/crs/config/config.sh

Optionally, you can run the Configuration Wizard silently, as follows, providing a response file:

$ Oracle_home/crs/config/config.sh -silent -responseFile file_name

To use GNS, Oracle recommends that you add GNS to the cluster after your cloned cluster is running. Add GNS using the srvctl add gns command.