Preparing the Replacement Compute Server for the Cluster

The initial installation of Recovery Appliance modified various files.

To modify the files on the replacement compute server:

Replicate the contents of the following files from a working compute server in the cluster:
1. Copy the /etc/security/limits.conf file.
2. Merge the contents of the /etc/hosts files.
3. Copy the /etc/oracle/cell/network-config/cellinit.ora file.
4. Update the IP address with the IP address of the BONDIB0 interface on the replacement compute server.
5. Copy the /etc/oracle/cell/network-config/cellip.ora file.
6. Configure additional network requirements, such as 10 GbE.
7. Copy the /etc/modprobe.conf file.
8. Copy the /etc/sysctl.conf file.
9. Restart the compute server, so the network changes take effect.
Set up the Oracle software owner on the replacement compute server by adding the user name to one or more groups. The owner is usually the oracle user.
1. Obtain the current group information from a working compute server:
```
# id oracle
uid=1000(oracle) gid=1001(oinstall) groups=1001(oinstall),1002(dba),1003(oper),1004(asmdba)
```
2. Use the groupadd command to add the group information to the replacement compute server. This example adds the groups identified in the previous step:
```
# groupadd –g 1001 oinstall
# groupadd –g 1002 dba
# groupadd –g 1003 oper
# groupadd –g 1004 asmdba
```
3. Obtain the current user information from a working compute server:
```
# id oracle uid=1000(oracle) gid=1001(oinstall) \
  groups=1001(oinstall),1002(dba),1003(oper),1004(asmdba)
```
4. Add the user information to the replacement compute server. This example adds the group IDs from the previous step to the oracle user ID:
```
# useradd -u 1000 -g 1001 -G 1001,1002,1003,1004 -m -d /home/oracle -s \
  /bin/bash oracle
```
5. Create the ORACLE_BASE and Grid Infrastructure directories. This example creates /u01/app/oracle and /u01/app/12.1.0/grid:
```
# mkdir -p /u01/app/oracle
# mkdir -p /u01/app/12.1.0/grid
# chown -R oracle:oinstall /u01/app
```
6. Change the ownership of the cellip.ora and cellinit.ora files. The owner is typically oracle:dba.
```
# chown -R oracle:dba /etc/oracle/cell/network-config
```
7. Secure the restored compute server:
```
$ chmod u+x /opt/oracle.SupportTools/harden_passwords_reset_root_ssh
$ /opt/oracle.SupportTools/harden_passwords_reset_root_ssh
```
  The compute server restarts.
8. Log in as the root user. When you are prompted for a new password, set it to match the root password of the other compute servers.
9. Set the password for the Oracle software owner. The owner is typically oracle.
```
# passwd oracle
```
Set up SSH for the oracle account:
1. Change to the oracle account on the replacement compute server:
```
# su - oracle
```
2. Create the dcli group file on the replacement compute server, listing the servers in the Oracle cluster.
3. Run the setssh-Linux.sh script on the replacement compute server. This example runs the script interactively:
```
$ /opt/oracle.SupportTools/onecommand/setssh-Linux.sh -s
```
  The script prompts for the oracle password on the servers. The -s option causes the script to run in silent mode.
4. Change to the oracle user on the replacement compute server:
```
# su - oracle
```
5. Verify SSH equivalency:
```
$ dcli -g dbs_group -l oracle date
```
Set up or copy any custom login scripts from the working compute server to the replacement compute server:
```
$ scp .bash* oracle@replacement_server:. 
```
In the preceding command, replacement_server is the name of the new server, such as ra01db01.