{"id":2847,"date":"2013-07-09T01:00:24","date_gmt":"2013-07-09T01:00:24","guid":{"rendered":"http:\/\/www.oratraining.com\/blog\/?p=2847"},"modified":"2013-07-17T06:22:52","modified_gmt":"2013-07-17T06:22:52","slug":"installing-12c-rac-on-linux-vm-setup-shared-file-system-and-other-pre-requisites","status":"publish","type":"post","link":"https:\/\/www.oratraining.com\/blog\/2013\/07\/installing-12c-rac-on-linux-vm-setup-shared-file-system-and-other-pre-requisites\/","title":{"rendered":"Installing 12c RAC on Linux VM: Setup shared file system and other pre-requisites"},"content":{"rendered":"

Previous:\u00a0<\/strong>Copy\/clone this virtual machine to create second node and modify host details<\/a><\/p>\n

Now we need to setup shared file system for these nodes since having shared storage is a must for Oracle RAC<\/p>\n

Since we are not using any external storage, NAS or SAN, we will host the shared file system on node 1 and share the same with node 2 using NFS. This is not recommended for production but since we are not using external storage for VMs this is the best way to achieve shared file system.<\/p>\n

Note:<\/strong>\u00a0Please do not use VMWare’s shared folders option since it is not cluster-aware and cannot make sure that read\/writes from multiple hosts are handled properly. This can cause cluster panic so use NFS only for this VM purpose. Also we are not using VirtualBox shared disk option since we want to keep it generic in nature.<\/p>\n

Since we are not using shared storage for Virtual Machines, we are sharing disks via NFS from one node to another.\u00a0Here is how the VMs can be represented.<\/p>\n

\"11gR2-VM-visio\"<\/a><\/p>\n

Login to\u00a0Node 1<\/strong>\u00a0using root user. Please note that these steps are\u00a0ONLY to be done on Node 1<\/strong>, not on node 2.<\/p>\n

Let us first create the directories which will host the shared data.<\/p>\n

[root@dbhost1 ~]#\u00a0mkdir \/shared_1<\/strong><\/p>\n

[root@dbhost1 ~]#\u00a0mkdir \/shared_2<\/strong><\/p>\n

[root@dbhost1 ~]#\u00a0mkdir \/shared_3<\/strong><\/p>\n

[root@dbhost1 ~]#\u00a0chown grid:dba \/shared_1<\/strong><\/p>\n

[root@dbhost1 ~]#\u00a0chown grid:dba \/shared_2<\/strong><\/p>\n

[root@dbhost1 ~]#\u00a0chown grid:dba \/shared_3<\/strong><\/p>\n

[root@dbhost1 ~]#\u00a0chmod g+w \/shared_1<\/strong><\/p>\n

[root@dbhost1 ~]#\u00a0chmod g+w \/shared_2<\/strong><\/p>\n

[root@dbhost1 ~]#\u00a0chmod g+w \/shared_3<\/strong><\/p>\n

Now we need to enable these directories to be shared over NFS. Enter following details in\u00a0\/etc\/exports <\/strong>file<\/p>\n

You will need uid and guid for user grid. You can find it by executing “id” command while logged in as “grid” user.<\/p>\n

[grid@dbhost1 ~]# id
\nuid=54322<\/strong>(grid) gid=54322<\/strong>(dba) groups=54322<\/strong>(dba),54323<\/strong>(oinstall)<\/p>\n

\n

[root@dbhost1 ~]#\u00a0more \/etc\/exports<\/strong><\/p>\n

\/shared_1 *(rw,sync,no_root_squash,insecure,anonuid=54322,anongid=54322)
\n<\/strong><\/p>\n

\/shared_2 *(rw,sync,no_root_squash,insecure,anonuid=54322,anongid=54322)
\n<\/strong><\/p>\n

\/shared_3 *(rw,sync,no_root_squash,insecure,anonuid=54322,anongid=54322)
\n<\/strong><\/p><\/blockquote>\n

Check if NFS service is running. If not we need to start it.<\/p>\n

[root@ dbhost1~]#\u00a0service nfs status<\/strong><\/p>\n

rpc.mountd is stopped<\/p>\n

nfsd is stopped<\/p>\n

rpc.rquotad is stopped<\/p>\n

[root@ dbhost1~]#\u00a0chkconfig nfs on<\/strong><\/p>\n

[root@ dbhost1~]#\u00a0service nfs start<\/strong><\/p>\n

Starting NFS services:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [\u00a0 OK\u00a0 ]<\/p>\n

Starting NFS quotas:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [ \u00a0OK\u00a0 ]<\/p>\n

Starting NFS daemon:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [\u00a0 OK\u00a0 ]<\/p>\n

Starting NFS mountd:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [\u00a0 OK\u00a0 ]<\/p>\n

Stopping RPC idmapd:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [\u00a0 OK\u00a0 ]<\/p>\n

Starting RPC idmapd:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0[\u00a0 OK\u00a0 ]<\/p>\n

These above steps have enabled the newly created shared directories for NFS mount.<\/p>\n

Now following steps need to be done on both\u00a0Node 1 and Node 2<\/strong><\/p>\n

“Append”<\/strong>\u00a0following entries in \/etc\/fstab file<\/p>\n

[root@dbhost1 ~]#\u00a0tail -3 \/etc\/fstab<\/strong><\/p>\n

nfshost:\/shared_1 \/u01 nfs rw,bg,hard,nolock,noac,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0<\/strong><\/span><\/pre>\n
nfshost:\/shared_2 \/u02 nfs rw,bg,hard,nolock,noac,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0<\/pre>\n
nfshost:\/shared_3 \/u03 nfs rw,bg,hard,nolock,noac,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0<\/pre>\n
 <\/p>\n
[root@dbhost2 ~]# tail -3 \/etc\/fstab<\/strong><\/p>\n
nfshost:\/shared_1 \/u01 nfs rw,bg,hard,nolock,noac,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0<\/p>\n
nfshost:\/shared_2 \/u02 nfs rw,bg,hard,nolock,noac,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0<\/p>\n
nfshost:\/shared_3 \/u03 nfs rw,bg,hard,nolock,noac,nointr,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 0 0<\/p>\n
 <\/p>\n
Let us mount each of these shared directories to the mount points created earlier. This is not required to be done from next restart since system will automatically mount them based on\u00a0<\/span>\/etc\/fstab<\/strong>\u00a0entries.<\/span><\/p>\n
[root@dbhost1 ~]#\u00a0mount \/u01<\/strong><\/p>\n
[root@dbhost1 ~]#\u00a0mount \/u02<\/strong><\/p>\n
[root@dbhost1 ~]#\u00a0mount \/u03<\/strong><\/p>\n
Same on node 2<\/strong>
\n[root@dbhost2 ~]# mount \/u01<\/strong>
\n[root@dbhost2 ~]# mount \/u02<\/strong>
\n[root@dbhost2 ~]# mount \/u03<\/strong><\/p>\n
Confirm if these directories are mounted correctly.<\/p>\n
[root@dbhost1 ~]# df -h<\/strong><\/p>\n
Filesystem Size Used Avail Use% Mounted on<\/p>\n
\/dev\/mapper\/VolGroup00-LogVol00<\/p>\n
283G 4.6G 264G 2% \/<\/p>\n
\/dev\/sda1 99M 41M 53M 44% \/boot<\/p>\n
tmpfs 1002M 0 1002M 0% \/dev\/shm<\/p>\n
nfshost:\/shared_1 283G 4.6G 264G 2% \/u01<\/strong><\/p>\n
nfshost:\/shared_2 283G 4.6G 264G 2% \/u02<\/strong><\/p>\n
nfshost:\/shared_3 283G 4.6G 264G 2% \/u03<\/strong><\/p>\n
Same on node 2<\/strong>
\n[root@dbhost2 ~]# df -h<\/strong><\/p>\n
Filesystem Size Used Avail Use% Mounted on<\/p>\n
\/dev\/mapper\/VolGroup00-LogVol00<\/p>\n
283G 4.6G 264G 2% \/<\/p>\n
\/dev\/sda1 99M 41M 53M 44% \/boot<\/p>\n
tmpfs 1002M 0 1002M 0% \/dev\/shm<\/p>\n
nfshost:\/shared_1 283G 4.6G 264G 2% \/u01<\/strong><\/p>\n
nfshost:\/shared_2 283G 4.6G 264G 2% \/u02<\/strong><\/p>\n
nfshost:\/shared_3 283G 4.6G 264G 2% \/u03<\/strong><\/p>\n
As I said, next time when you restart, automatically these directories will be mounted,<\/p>\n
IMPORTANT NOTE:<\/strong><\/span>\u00a0Whenever you are restarting both servers,\u00a0make sure that you let Node 1 start properly before starting Node 2.\u00a0<\/strong>The reason being, the\u00a0shared file system is hosted on Node 1<\/strong>\u00a0so if node 2 starts before node 1 has enabled NFS share during startup, the mount points will not come up on Node 2. This will especially be a problem once our clusterware and RAC database are installed.<\/p>\n
Setting up user-equivalence on both nodes (Passwordless SSH setup)<\/strong><\/p>\n
Having passwordless ssh connectivity is a must for RAC installation. This is required for both nodes to communicate with each other and passing commands to each node during runtime and maintenance.<\/p>\n
We will setup user-equivalence for both\u00a0oracle\u00a0<\/strong>and\u00a0grid<\/strong>\u00a0users. Let us start with\u00a0grid owner user\u00a0grid <\/strong>first.<\/p>\n
Perform following on Node1<\/strong><\/p>\n
We will use all\u00a04 combinations\u00a0every time. i.e. dbhost1, dbhost1.paramlabs.com (fully qualified domain name), dbhost2, dbhost2.paramlabs.com
\n<\/strong><\/span><\/p>\n
[grid@dbhost1 ~]$ ssh grid@dbhost2<\/strong><\/p>\n
The authenticity of host ‘dbhost2 (192.168.1.122)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost2,192.168.1.122’ (RSA) to the list of known hosts.<\/p>\n
grid@dbhost2’s password:<\/p>\n
[grid@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2 closed.<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ssh grid@dbhost1<\/strong><\/p>\n
The authenticity of host ‘dbhost1 (192.168.1.121)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost1,192.168.1.121’ (RSA) to the list of known hosts.<\/p>\n
grid@dbhost1’s password:<\/p>\n
[grid@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1 closed.<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ssh grid@dbhost1.paramlabs.com<\/strong><\/p>\n
The authenticity of host ‘dbhost1.paramlabs.com (192.168.1.121)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost1.paramlabs.com’ (RSA) to the list of known hosts.<\/p>\n
grid@dbhost1.paramlabs.com’s password:<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ssh grid@dbhost2.paramlabs.com<\/strong><\/p>\n
The authenticity of host ‘dbhost2.paramlabs.com (192.168.1.122)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost2.paramlabs.com’ (RSA) to the list of known hosts.<\/p>\n
grid@dbhost2.paramlabs.com’s password:<\/p>\n
Last login: Mon Jul 8 13:24:19 2013 from dbhost1.paramlabs.com<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ssh-keygen -t dsa<\/strong><\/p>\n
Generating public\/private dsa key pair.<\/p>\n
Enter file in which to save the key (\/home\/grid\/.ssh\/id_dsa):<\/p>\n
Enter passphrase (empty for no passphrase):<\/p>\n
Enter same passphrase again:<\/p>\n
Your identification has been saved in \/home\/grid\/.ssh\/id_dsa.<\/p>\n
Your public key has been saved in \/home\/grid\/.ssh\/id_dsa.pub.<\/p>\n
The key fingerprint is:<\/p>\n
xxxxxx grid@dbhost1.paramlabs.com<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ls -ltr \/home\/grid\/.ssh\/<\/strong><\/p>\n
total 12<\/p>\n
-rw-r–r– 1 grid dba 1612 Jul 8 13:25 known_hosts<\/p>\n
-rw-r–r– 1 grid dba 616 Jul 8 13:26 id_dsa.pub<\/strong><\/p>\n
-rw——- 1 grid dba 668 Jul 8 13:26 id_dsa<\/strong><\/p>\n
 <\/p>\n
[grid@dbhost2 ~]$ ssh-keygen -t dsa<\/strong><\/p>\n
Generating public\/private dsa key pair.<\/p>\n
Enter file in which to save the key (\/home\/grid\/.ssh\/id_dsa):<\/p>\n
Created directory ‘\/home\/grid\/.ssh’.<\/p>\n
Enter passphrase (empty for no passphrase):<\/p>\n
Enter same passphrase again:<\/p>\n
Your identification has been saved in \/home\/grid\/.ssh\/id_dsa.<\/p>\n
Your public key has been saved in \/home\/grid\/.ssh\/id_dsa.pub.<\/p>\n
The key fingerprint is:<\/p>\n
xxxx grid@dbhost2.paramlabs.com<\/p>\n
 <\/p>\n
[grid@dbhost2 ~]$ ls -ltr \/home\/grid\/.ssh<\/strong><\/p>\n
total 8<\/p>\n
-rw-r–r– 1 grid dba 616 Jul 8 13:28 id_dsa.pub<\/strong><\/p>\n
-rw——- 1 grid dba 668 Jul 8 13:28 id_dsa
\n<\/strong><\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ scp \/home\/grid\/.ssh\/id_dsa.pub grid@dbhost2:\/home\/grid\/.ssh\/authorized_keys<\/strong><\/p>\n
grid@dbhost2’s password:<\/p>\n
id_dsa.pub 100% 616 0.6KB\/s 00:00<\/p>\n
 <\/p>\n
[grid@dbhost2 ~]$ scp \/home\/grid\/.ssh\/id_dsa.pub grid@dbhost1:\/home\/grid\/.ssh\/authorized_keys
\n<\/strong><\/p>\n
The authenticity of host ‘dbhost1 (192.168.1.121)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/p>\n
Warning: Permanently added ‘dbhost1,192.168.1.121’ (RSA) to the list of known hosts.<\/p>\n
grid@dbhost1’s password:<\/p>\n
id_dsa.pub 100% 616 0.6KB\/s 00:00<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ cat \/home\/grid\/.ssh\/id_dsa.pub >> \/home\/grid\/.ssh\/authorized_keys<\/strong><\/p>\n
[grid@dbhost2 ~]$ cat \/home\/grid\/.ssh\/id_dsa.pub >> \/home\/grid\/.ssh\/authorized_keys<\/strong><\/p>\n
 <\/p>\n
Now let us test the passwordless connectivity between these 2 nodes using grid user.\u00a0 It should not prompt for password. In that case the test will be successful.
\n<\/strong><\/span><\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ssh grid@dbhost1<\/strong><\/p>\n
Last login: Mon Jul 8 13:30:02 2013 from dbhost2.paramlabs.com<\/p>\n
[grid@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1 closed.<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ssh grid@dbhost2<\/strong><\/p>\n
Last login: Mon Jul 8 13:30:10 2013 from dbhost2.paramlabs.com<\/p>\n
[grid@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2 closed.<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ssh grid@dbhost1.paramlabs.com<\/strong><\/p>\n
Last login: Mon Jul 8 13:31:38 2013 from dbhost1.paramlabs.com<\/p>\n
[grid@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1.paramlabs.com closed.<\/p>\n
 <\/p>\n
[grid@dbhost1 ~]$ ssh grid@dbhost2.paramlabs.com<\/strong><\/p>\n
Last login: Mon Jul 8 13:31:41 2013 from dbhost1.paramlabs.com<\/p>\n
[grid@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2.paramlabs.com closed.<\/p>\n
 <\/p>\n
Let’s do the same on dbhost2
\n<\/strong><\/span><\/p>\n
 <\/p>\n
[grid@dbhost2 ~]$ ssh grid@dbhost1<\/strong><\/p>\n
Last login: Mon Jul 8 13:31:46 2013 from dbhost1.paramlabs.com<\/p>\n
[grid@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1 closed.<\/p>\n
 <\/p>\n
[grid@dbhost2 ~]$ ssh grid@dbhost2<\/strong><\/p>\n
Last login: Mon Jul 8 13:31:50 2013 from dbhost1.paramlabs.com<\/p>\n
[grid@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2 closed.<\/p>\n
 <\/p>\n
[grid@dbhost2 ~]$ ssh grid@dbhost1.paramlabs.com<\/strong><\/p>\n
The authenticity of host ‘dbhost1.paramlabs.com (192.168.1.121)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost1.paramlabs.com’ (RSA) to the list of known hosts.<\/p>\n
Last login: Mon Jul 8 13:32:09 2013 from dbhost2.paramlabs.com<\/p>\n
[grid@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1.paramlabs.com closed.<\/p>\n
 <\/p>\n
[grid@dbhost2 ~]$ ssh grid@dbhost2.paramlabs.com<\/strong><\/p>\n
The authenticity of host ‘dbhost2.paramlabs.com (192.168.1.122)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost2.paramlabs.com’ (RSA) to the list of known hosts.<\/p>\n
Last login: Mon Jul 8 13:32:11 2013 from dbhost2.paramlabs.com<\/p>\n
[grid@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2.paramlabs.com closed.<\/p>\n
 <\/p>\n
This concludes passwordless ssh setup for grid user. Let us do the same exercise for oracle user.
\n<\/strong><\/span><\/p>\n
 <\/p>\n
Let us generate public key for\u00a0dbhost1.\u00a0Accept defaults and press enter whenever prompted.
\n<\/strong><\/span><\/p>\n
 <\/p>\n
[oracle@dbhost1 ~]$ ssh-keygen -t dsa<\/strong><\/p>\n
Generating public\/private dsa key pair.<\/p>\n
Enter file in which to save the key (\/home\/oracle\/.ssh\/id_dsa):<\/p>\n
Enter passphrase (empty for no passphrase):<\/p>\n
Enter same passphrase again:<\/p>\n
Your identification has been saved in \/home\/oracle\/.ssh\/id_dsa.<\/p>\n
Your public key has been saved in \/home\/oracle\/.ssh\/id_dsa.pub.<\/p>\n
The key fingerprint is:<\/p>\n
xxxxx oracle@dbhost1.paramlabs.com<\/p>\n
 <\/p>\n
Now let us generate public key for\u00a0dbhost2.\u00a0Accept defaults and press enter whenever prompted.
\n<\/strong><\/span><\/p>\n
 <\/p>\n
[oracle@dbhost2 ~]$ ssh-keygen -t dsa<\/strong><\/p>\n
Generating public\/private dsa key pair.<\/p>\n
Enter file in which to save the key (\/home\/oracle\/.ssh\/id_dsa):<\/p>\n
Created directory ‘\/home\/oracle\/.ssh’.<\/p>\n
Enter passphrase (empty for no passphrase):<\/p>\n
Enter same passphrase again:<\/p>\n
Your identification has been saved in \/home\/oracle\/.ssh\/id_dsa.<\/p>\n
Your public key has been saved in \/home\/oracle\/.ssh\/id_dsa.pub.<\/p>\n
The key fingerprint is:<\/p>\n
xxxxx oracle@dbhost2.paramlabs.com<\/p>\n
 <\/p>\n
[oracle@dbhost1 ~]$ ls -ltr \/home\/oracle\/.ssh\/<\/strong><\/p>\n
total 8<\/p>\n
-rw-r–r– 1 oracle oinstall 618 Jul 8 19:55 id_dsa.pub<\/strong><\/p>\n
-rw——- 1 oracle oinstall 672 Jul 8 19:55 id_dsa
\n<\/strong><\/p>\n
 <\/p>\n
[oracle@dbhost2 ~]$ ls -ltr \/home\/oracle\/.ssh\/<\/strong><\/p>\n
total 8<\/p>\n
-rw-r–r– 1 oracle oinstall 618 Jul 8 19:55 id_dsa.pub<\/strong><\/p>\n
-rw——- 1 oracle oinstall 668 Jul 8 19:55 id_dsa<\/strong><\/p>\n
 <\/p>\n
Now we need to copy this public key to second host in order to authorize it to connect to this host using this (oracle) user without password. We will save this public key in a file named\u00a0authorized_keys\u00a0on node 2.
\n<\/strong><\/span><\/p>\n
 <\/p>\n
[oracle@dbhost1~]$ cd \/home\/oracle\/.ssh\/<\/strong><\/p>\n
[oracle@dbhost1 .ssh]$ scp id_dsa.pub oracle@dbhost2:\/home\/oracle\/.ssh\/authorized_keys<\/strong><\/p>\n
The authenticity of host ‘dbhost2 (192.168.1.122)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost2,192.168.1.122’ (RSA) to the list of known hosts.<\/p>\n
oracle@dbhost2’s password:<\/p>\n
id_dsa.pub<\/p>\n
 <\/p>\n
[oracle@dbhost2 ~]$ cd \/home\/oracle\/.ssh\/<\/strong><\/p>\n
[oracle@dbhost2 ~]$ scp id_dsa.pub oracle@dbhost1:\/home\/oracle\/.ssh\/authorized_keys<\/strong><\/p>\n
The authenticity of host ‘dbhost1 (192.168.1.121)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost1,192.168.1.121’ (RSA) to the list of known hosts.<\/p>\n
oracle@dbhost1’s password:<\/p>\n
id_dsa.pub 100% 618 0.6KB\/s 00:00<\/p>\n
 <\/p>\n
Also we will append the public key for dbhost1 to itself as well so that it can do ssh to samebox without password (2 of the 4 combinations)
\n<\/strong><\/span><\/p>\n
 <\/p>\n
[oracle@dbhost1 .ssh]$ cat id_dsa.pub >> authorized_keys<\/strong><\/p>\n
[oracle@dbhost2 .ssh]$ cat id_dsa.pub >> authorized_keys<\/strong><\/p>\n
 <\/p>\n
Now let us test the passwordless connectivity between these 2 nodes using oracle user.
\n<\/strong><\/span><\/p>\n
 <\/p>\n
[oracle@dbhost1 .ssh]$ ssh oracle@dbhost1<\/strong><\/p>\n
The authenticity of host ‘dbhost1 (192.168.1.121)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost1,192.168.1.121’ (RSA) to the list of known hosts.<\/p>\n
Last login: Mon Jul 8 19:54:43 2013 from 192.168.1.181<\/p>\n
[oracle@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1 closed.<\/p>\n
 <\/p>\n
[oracle@dbhost1 .ssh]$ ssh oracle@dbhost2<\/strong><\/p>\n
Last login: Mon Jul 8 19:54:49 2013 from 192.168.1.181<\/p>\n
[oracle@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2 closed.<\/p>\n
 <\/p>\n
[oracle@dbhost1 .ssh]$ ssh oracle@dbhost1.paramlabs.com<\/strong><\/p>\n
The authenticity of host ‘dbhost1.paramlabs.com (192.168.1.121)’ can’t be established.<\/p>\n
RSA key fingerprint is a<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost1.paramlabs.com’ (RSA) to the list of known hosts.<\/p>\n
Last login: Mon Jul 8 19:58:48 2013 from dbhost1.paramlabs.com<\/p>\n
[oracle@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1.paramlabs.com closed.<\/p>\n
 <\/p>\n
[oracle@dbhost1 .ssh]$ ssh oracle@dbhost2.paramlabs.com<\/strong><\/p>\n
The authenticity of host ‘dbhost2.paramlabs.com (192.168.1.122)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost2.paramlabs.com’ (RSA) to the list of known hosts.<\/p>\n
Last login: Mon Jul 8 19:58:51 2013 from dbhost1.paramlabs.com<\/p>\n
[oracle@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2.paramlabs.com closed.<\/p>\n
 <\/p>\n
Now do the similar steps on Node 2 (dbhost2)<\/strong>
\n<\/span><\/p>\n
 <\/p>\n
[oracle@dbhost2 .ssh]$ ssh oracle@dbhost1<\/strong><\/p>\n
Last login: Mon Jul 8 19:58:57 2013 from dbhost1.paramlabs.com<\/p>\n
[oracle@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1 closed.<\/p>\n
 <\/p>\n
[oracle@dbhost2 .ssh]$ ssh oracle@dbhost2<\/strong><\/p>\n
The authenticity of host ‘dbhost2 (192.168.1.122)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost2,192.168.1.122’ (RSA) to the list of known hosts.<\/p>\n
Last login: Mon Jul 8 19:59:02 2013 from dbhost1.paramlabs.com<\/p>\n
[oracle@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2 closed.<\/p>\n
 <\/p>\n
[oracle@dbhost2 .ssh]$ ssh oracle@dbhost1.paramlabs.com<\/strong><\/p>\n
The authenticity of host ‘dbhost1.paramlabs.com (192.168.1.121)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost1.paramlabs.com’ (RSA) to the list of known hosts.<\/p>\n
Last login: Mon Jul 8 19:59:17 2013 from dbhost2.paramlabs.com<\/p>\n
[oracle@dbhost1 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost1.paramlabs.com closed.<\/p>\n
 <\/p>\n
[oracle@dbhost2 .ssh]$ ssh oracle@dbhost2.paramlabs.com<\/strong><\/p>\n
The authenticity of host ‘dbhost2.paramlabs.com (192.168.1.122)’ can’t be established.<\/p>\n
RSA key fingerprint is<\/p>\n
Are you sure you want to continue connecting (yes\/no)? yes<\/strong><\/p>\n
Warning: Permanently added ‘dbhost2.paramlabs.com’ (RSA) to the list of known hosts.<\/p>\n
Last login: Mon Jul 8 19:59:20 2013 from dbhost2.paramlabs.com<\/p>\n
[oracle@dbhost2 ~]$ exit<\/p>\n
logout<\/p>\n
Connection to dbhost2.paramlabs.com closed.<\/p>\n
Next:\u00a0<\/strong>Install Oracle Grid Infrastructure<\/a><\/p>\n
Oracle 12c (12.1) RAC (Real Applications Cluster) installation on Linux Virtual Machines \u2013 Step by step guide<\/strong><\/span><\/a><\/p>\n
1.\u00a0Create Virtual Machine and install 64 bit Linux<\/a>
\n2.\u00a0Add additional virtual Ethernet card and perform prerequisites in Linux<\/a>
\n3.\u00a0Copy\/clone this virtual machine to create second node and modify host details<\/a>
\n4.\u00a0Setup shared file system and other pre-requisites<\/a>
\n5.\u00a0Install Oracle Grid Infrastructure<\/a>
\n6.\u00a0Install Oracle Database software and create RAC database<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Previous:\u00a0Copy\/clone this virtual machine to create second node and modify host details Now we need to setup shared file system for these nodes since having shared storage is a must for Oracle RAC Since we are not using any external storage, NAS or SAN, we will host the shared file system on node 1 and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[3,4,8,10,14,38,20],"tags":[180,179,169,176,172,178,96,186,170,171,173,105,177,174,175,147,148,182,181],"class_list":["post-2847","post","type-post","status-publish","format-standard","hentry","category-linuxunixsolaris","category-oracle","category-database","category-oracle-dba","category-oracle-rac","category-virtualbox-virtualization","category-virtualization","tag-12-1-0-installation","tag-12-1-0-rac","tag-12c","tag-12c-installation","tag-12c-rac","tag-12c-rac-installation","tag-linux","tag-nfs","tag-oracle-12","tag-oracle-12c","tag-oracle-12c-rac","tag-oracle-linux","tag-rac-installation","tag-real-application-clusters","tag-real-applications-cluster","tag-virtual-machine","tag-virtualbox","tag-vm","tag-vmware"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/posts\/2847","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/comments?post=2847"}],"version-history":[{"count":0,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/posts\/2847\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/media?parent=2847"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/categories?post=2847"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/tags?post=2847"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}