Oracle 10g RAC installation: 07 Add the second node

Tweet

With your first node turned off, you have simply to copy physically your rac1 files into another directory. This will be useful first of all because it is a faster way to create another Linux environments, but above all because we will use the same Oracle users with the same passwords to estabilish later the user equivalence. The user equivalence is necessary for the OUI when begin to copy the Oracle software from the first node to the others n (in our installation just to the second node) and it should be able to connect to the remote node(s) without being prompted for the oracle user password.

We created our first node on the directory F:\UnbreakableRac1, so create another directory (F:\UnbreakableRac2) and copy and paste all the files from F:\UnbreakableRac1 directory into F:\UnbreakableRac2 directory

Now from your vmWare GSX server select File->Open Virtual Machine and then click on Browse button to add your second node (I selected the file F:\UnbreakableRac2\rhel4.vmx). Then click on Edit virtual machine settings and change the name of this second node in rac2

At this point you will see two tabs on your vmWare GSX server, rac1 and rac2: now this time start the second node (rac2). The first time you will be asked if create a new identifier for this machine... You have to create a new identifier.


You will see while your second node is starting that a MAC address misconfiguration is detected: this because you have to probe for new MAC address using system-config-network tool from a root terminal.
So as root user type on your terminal system-config-network and for each network device check for a new MAC address.


Change also your hostname from rac1.vmware.com to rac2.vmware.com.


Save your network configuration and type

/etc/init.d/network restart

Type

hostname

to see if you have written the right hostname for your second node (you should see rac2.vmware.com)

Login as oracle user (su - oracle) and edit your .profile file, changing the ORACLE_SID variable in racdb2.


In the next step we will estabilish the user equivalence between the two nodes (rac1 and rac2) using ssh and ssh-keygen tools.