First Part of installation will be setting up password-less connectivity and running cluvfy to make sure everything is allright
I have mounted by Desktop mount using VMWare shared folders (at time of instllation)
I have my binaries here
I have my binaries here
RAC12c 234074108 113347900 120726208 49% /media/sf_RAC12c
Unzip the software
Unzip the software
[grid@rac1 Desktop]$ su -
Password:
Last login: Fri Mar 3 20:39:20 IST 2017 on pts/0
[root@rac1 ~]# mkdir /stage
[root@rac1 ~]# cd /stage/
[root@rac1 stage]# unzip -qq /media/sf_RAC12c/
Database/ Grid/ Linux 7/ New folder/ rpm/
[root@rac1 stage]# unzip -qq /media/sf_RAC12c/Grid/linuxamd64_12102_grid_1of2.zip
[root@rac1 stage]# unzip -qq /media/sf_RAC12c/Grid/linuxamd64_12102_grid_2of2.zip
[root@rac1 stage]# chown -R grid:oinstall /stage
[root@rac1 stage]# ls -ld /stage
now go to /stage/grid/sshsetup directory
[grid@rac1 sshsetup]$ ./sshUserSetup.sh -user grid -hosts "rac1 rac2" -noPromptPassphrase -confirm -advanced
(output shown only for oracle user)
[grid@rac1 sshsetup]$ ./sshUserSetup.sh -user oracle -hosts "rac1 rac2" -noPromptPassphrase -confirm -advanced
The output of this script is also logged into /tmp/sshUserSetup_2017-03-03-21-21-45.log
Hosts are rac1 rac2
user is oracle
Platform:- Linux
Checking if the remote hosts are reachable
PING rac1.localdomain (10.10.10.1) 56(84) bytes of data.
64 bytes from rac1.localdomain (10.10.10.1): icmp_seq=1 ttl=64 time=0.060 ms
64 bytes from rac1.localdomain (10.10.10.1): icmp_seq=2 ttl=64 time=0.077 ms
64 bytes from rac1.localdomain (10.10.10.1): icmp_seq=3 ttl=64 time=0.100 ms
64 bytes from rac1.localdomain (10.10.10.1): icmp_seq=4 ttl=64 time=0.180 ms
64 bytes from rac1.localdomain (10.10.10.1): icmp_seq=5 ttl=64 time=0.078 ms
--- rac1.localdomain ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 0.060/0.099/0.180/0.042 ms
PING rac2.localdomain (10.10.10.2) 56(84) bytes of data.
64 bytes from rac2.localdomain (10.10.10.2): icmp_seq=1 ttl=64 time=0.831 ms
64 bytes from rac2.localdomain (10.10.10.2): icmp_seq=2 ttl=64 time=0.717 ms
64 bytes from rac2.localdomain (10.10.10.2): icmp_seq=3 ttl=64 time=0.650 ms
64 bytes from rac2.localdomain (10.10.10.2): icmp_seq=4 ttl=64 time=0.809 ms
64 bytes from rac2.localdomain (10.10.10.2): icmp_seq=5 ttl=64 time=0.711 ms
--- rac2.localdomain ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 0.650/0.743/0.831/0.073 ms
Remote host reachability check succeeded.
The following hosts are reachable: rac1 rac2.
The following hosts are not reachable: .
All hosts are reachable. Proceeding further...
firsthost rac1
numhosts 2
The script will setup SSH connectivity from the host rac1.localdomain to all
the remote hosts. After the script is executed, the user can use SSH to run
commands on the remote hosts or copy files between this host rac1.localdomain
and the remote hosts without being prompted for passwords or confirmations.
NOTE 1:
As part of the setup procedure, this script will use ssh and scp to copy
files between the local host and the remote hosts. Since the script does not
store passwords, you may be prompted for the passwords during the execution of
the script whenever ssh or scp is invoked.
NOTE 2:
AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME DIRECTORY
AND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEDGES TO THESE
directories.
Do you want to continue and let the script make the above mentioned changes (yes/no)?
Confirmation provided on the command line
The user chose yes
User chose to skip passphrase related questions.
Creating .ssh directory on local host, if not present already
Creating authorized_keys file on local host
Changing permissions on authorized_keys to 644 on local host
Creating known_hosts file on local host
Changing permissions on known_hosts to 644 on local host
Creating config file on local host
If a config file exists already at /home/grid/.ssh/config, it would be backed up to /home/grid/.ssh/config.backup.
Creating .ssh directory and setting permissions on remote host rac1
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR oracle. THIS IS AN SSH REQUIREMENT.
The script would create ~oracle/.ssh/config file on remote host rac1. If a config file exists already at ~oracle/.ssh/config, it would be backed up to ~oracle/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rac1.
Warning: Permanently added 'rac1,10.10.10.1' (ECDSA) to the list of known hosts.
oracle@rac1's password:
Done with creating .ssh directory and setting permissions on remote host rac1.
Creating .ssh directory and setting permissions on remote host rac2
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR oracle. THIS IS AN SSH REQUIREMENT.
The script would create ~oracle/.ssh/config file on remote host rac2. If a config file exists already at ~oracle/.ssh/config, it would be backed up to ~oracle/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rac2.
Warning: Permanently added 'rac2,10.10.10.2' (ECDSA) to the list of known hosts.
oracle@rac2's password:
Done with creating .ssh directory and setting permissions on remote host rac2.
Copying local host public key to the remote host rac1
The user may be prompted for a password or passphrase here since the script would be using SCP for host rac1.
oracle@rac1's password:
Done copying local host public key to the remote host rac1
Copying local host public key to the remote host rac2
The user may be prompted for a password or passphrase here since the script would be using SCP for host rac2.
oracle@rac2's password:
Done copying local host public key to the remote host rac2
Creating keys on remote host rac1 if they do not exist already. This is required to setup SSH on host rac1.
Creating keys on remote host rac2 if they do not exist already. This is required to setup SSH on host rac2.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
53:9f:08:b9:d1:e0:b1:bf:c4:41:23:98:37:cb:31:85 oracle@rac2.localdomain
The key's randomart image is:
+--[ RSA 1024]----+
| o+o+ |
| o.EO . |
| o*=+ |
| oB + . |
| S = o |
| o . |
| . |
| |
| |
+-----------------+
Updating authorized_keys file on remote host rac1
Updating known_hosts file on remote host rac1
Updating authorized_keys file on remote host rac2
Updating known_hosts file on remote host rac2
SSH setup is complete.
------------------------------------------------------------------------
Verifying SSH setup
===================
The script will now run the date command on the remote nodes using ssh
to verify if ssh is setup correctly. IF THE SETUP IS CORRECTLY SETUP,
THERE SHOULD BE NO OUTPUT OTHER THAN THE DATE AND SSH SHOULD NOT ASK FOR
PASSWORDS. If you see any output other than date or are prompted for the
password, ssh is not setup correctly and you will need to resolve the
issue and set up ssh again.
The possible causes for failure could be:
1. The server settings in /etc/ssh/sshd_config file do not allow ssh
for user oracle.
2. The server may have disabled public key based authentication.
3. The client public key on the server may be outdated.
4. ~oracle or ~oracle/.ssh on the remote host may not be owned by oracle.
5. User may not have passed -shared option for shared remote users or
may be passing the -shared option for non-shared remote users.
6. If there is output in addition to the date, but no password is asked,
it may be a security alert shown as part of company policy. Append the
additional text to the <OMS HOME>/sysman/prov/resources/ignoreMessages.txt file.
------------------------------------------------------------------------
--rac1:--
Running /usr/bin/ssh -x -l oracle rac1 date to verify SSH connectivity has been setup from local host to rac1.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Fri Mar 3 21:22:09 IST 2017
------------------------------------------------------------------------
--rac2:--
Running /usr/bin/ssh -x -l oracle rac2 date to verify SSH connectivity has been setup from local host to rac2.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Fri Mar 3 21:22:09 IST 2017
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rac1 to rac1
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Fri Mar 3 21:22:10 IST 2017
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rac1 to rac2
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Fri Mar 3 21:22:10 IST 2017
------------------------------------------------------------------------
-Verification from complete-
SSH verification complete.
Run Cluster Verification utility
./runcluvfy.sh stage -pre crsinst -n rac1,rac2 -verbose | tee /tmp/cluvfy.out
Find for errors and resolve if any
Find for errors and resolve if any
grep -e fail -e ^PRVE /tmp/cluvfy.out
rac2 2.9387GB (3081432.0KB) 4GB (4194304.0KB) failed
rac1 2.9387GB (3081432.0KB) 4GB (4194304.0KB) failed
Result: Total memory check failed
PRVE-0426 : The size of in-memory file system mounted as /dev/shm is "5120000k" megabytes which is less than the required size of "2048" megabytes on node ""
PRVE-0426 : The size of in-memory file system mounted as /dev/shm is "5120000k" megabytes which is less than the required size of "2048" megabytes on node ""
Check for /dev/shm mounted as temporary file system failed
Explanation of /dev/shm
The size of in-memory file system mounted at /dev/shm is "24576" megabytes which does not match the size in /etc/fstab as "0" megabytes (Doc ID 1918620.1)
In my case I am going to ignore all of these errors and continue the installation in next blog.
rac2 2.9387GB (3081432.0KB) 4GB (4194304.0KB) failed
rac1 2.9387GB (3081432.0KB) 4GB (4194304.0KB) failed
Result: Total memory check failed
PRVE-0426 : The size of in-memory file system mounted as /dev/shm is "5120000k" megabytes which is less than the required size of "2048" megabytes on node ""
PRVE-0426 : The size of in-memory file system mounted as /dev/shm is "5120000k" megabytes which is less than the required size of "2048" megabytes on node ""
Check for /dev/shm mounted as temporary file system failed
Explanation of /dev/shm
The size of in-memory file system mounted at /dev/shm is "24576" megabytes which does not match the size in /etc/fstab as "0" megabytes (Doc ID 1918620.1)
In my case I am going to ignore all of these errors and continue the installation in next blog.
No comments:
Write comments