[INS-40719] IP address configured for Single Client Access Name (SCAN): is already assigned to another system

Error Description:
Oracle grid/clusterware installation / reinstallation throws following error with SCAN configuration.
[INS-40719] IP address configured for Single Client Access Name (SCAN): is already assigned to another system


Solution Description
The scan is already being used by the previous installation which is not yet released for the we can do some checks to confirm the same.
1.      Do a ssh to the scan it will respond with login passwords which means it is already assigned to the system. In below example it is assigned to host 10.201.6.54. The IP should return value as Destination Host Unreachable instead of pinging. Here .54 scan ip is pinging with response time and .55 is host unreachable.
[root@Node1 /]# ssh test-scan
The authenticity of host 'test-scan (10.201.6.54)' can't be established.
ECDSA key fingerprint is ed:c4:6d:7f:fe:6e:63:3b:b0:08:49:fb:74:71:bb:b3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'test-scan,10.201.6.54' (ECDSA) to the list of known hosts.
Password:
Password:

[root@Node1 /]# ping 10.201.6.55
PING 10.201.6.55 (10.201.6.55) 56(84) bytes of data.
From 10.201.6.55icmp_seq=1 Destination Host Unreachable
From 10.201.6.55icmp_seq=2 Destination Host Unreachable
From 10.201.6.55icmp_seq=3 Destination Host Unreachable
From 10.201.6.55icmp_seq=4 Destination Host Unreachable
^C
--- 10.201.6.55 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4001ms
pipe 4
[root@Node1 /]# ping 10.201.6.54
PING 10.201.6.54 (10.201.6.54) 56(84) bytes of data.
64 bytes from 10.201.6.54: icmp_seq=1 ttl=64 time=0.691 ms
64 bytes from 10.201.6.54: icmp_seq=2 ttl=64 time=0.695 ms
64 bytes from 10.201.6.54: icmp_seq=3 ttl=64 time=0.601 ms
^C
--- 10.201.6.54 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.601/0.662/0.695/0.048 ms
[root@Node1 /]# ping 10.201.6.56
PING 10.201.6.56 (10.201.6.56) 56(84) bytes of data.
From 10.201.6.55icmp_seq=1 Destination Host Unreachable
From 10.201.6.55icmp_seq=2 Destination Host Unreachable
From 10.201.6.55icmp_seq=3 Destination Host Unreachable
From 10.201.6.55icmp_seq=4 Destination Host Unreachable
^C
--- 10.201.6.56 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2999ms
pipe 4
Solution
Make sure you are not using the scan any more with any of the cluster and do a network restart as root. Now all ping results are host unreachable results. It will release the IP and issue will be solved.
[root@Node1 /]# service network restart
Restarting network (via systemctl):                        [  OK  ]

[root@Node1 /]#   ssh test-scan

ssh: connect to host test-scan port 22: No route to host
DBA Tips Data Pump Reference

0 comments:

Post a Comment

 

dba topics. Copyright 2011-16 All Rights Reserved | Site Map | Contact | Disclaimer | Google