In one of our RAC setups Listener (ora.LISTENER.lsnr) status was OFFLINE in the CRS. When I tried to start it as root user with the command "crs_start of ora.LISTENER.lsnr" it thrown below error and listener did not come up.
"CRS-2805: Unable to start 'ora.LISTENER.lsnr' because it has a 'hard' dependency on resource type 'ora.cluster_vip_net1.type' and no resource of that type can satisfy the dependency"
After doing some research I found that VIP of the node is not pinging even though CRS is up and running. Then learnt that VIP of the node is not registered with CRS which caused the listener to not to come up.
[root@rac1 bin]# ./srvctl config nodeapps -a
Network exists: 1/192.168.2.0/255.255.255.0/eth0, type static
VIP exists: /rac2-vip/192.168.2.112/192.168.2.0/255.255.255.0/eth0, hosting node rac2
The above output shows that only 2nd node rac2-vip is registered. 1st node VIP rac1-vip is not registered.
So, I registered the VIP of the node to CRS as root user with below command.
[root@rac1 bin]# ./srvctl add vip -n rac1 -A rac1-vip/255.255.255.0/eth0 -k 1
Now both the VIPs are registered.
[root@rac1 bin]# ./srvctl config nodeapps -a
Network exists: 1/192.168.2.0/255.255.255.0/eth0, type static
VIP exists: /rac1-vip/192.168.2.111/192.168.2.0/255.255.255.0/eth0, hosting node rac1
VIP exists: /rac2-vip/192.168.2.112/192.168.2.0/255.255.255.0/eth0, hosting node rac2
Start rac1-vip now
[root@rac1 bin]# ./crs_start -f ora.rac1.vip
Attempting to start `ora.rac1.vip` on member `rac1`
Start of `ora.rac1.vip` on member `rac1` succeeded.
Attempting to start `ora.LISTENER.lsnr` on member `rac1`
Start of `ora.LISTENER.lsnr` on member `rac1` succeeded.
Now the VIP is registered and it is reachable now. ora.LISTENER.lsnr status become ONLINE now.
"CRS-2805: Unable to start 'ora.LISTENER.lsnr' because it has a 'hard' dependency on resource type 'ora.cluster_vip_net1.type' and no resource of that type can satisfy the dependency"
After doing some research I found that VIP of the node is not pinging even though CRS is up and running. Then learnt that VIP of the node is not registered with CRS which caused the listener to not to come up.
[root@rac1 bin]# ./srvctl config nodeapps -a
Network exists: 1/192.168.2.0/255.255.255.0/eth0, type static
VIP exists: /rac2-vip/192.168.2.112/192.168.2.0/255.255.255.0/eth0, hosting node rac2
The above output shows that only 2nd node rac2-vip is registered. 1st node VIP rac1-vip is not registered.
So, I registered the VIP of the node to CRS as root user with below command.
[root@rac1 bin]# ./srvctl add vip -n rac1 -A rac1-vip/255.255.255.0/eth0 -k 1
Now both the VIPs are registered.
[root@rac1 bin]# ./srvctl config nodeapps -a
Network exists: 1/192.168.2.0/255.255.255.0/eth0, type static
VIP exists: /rac1-vip/192.168.2.111/192.168.2.0/255.255.255.0/eth0, hosting node rac1
VIP exists: /rac2-vip/192.168.2.112/192.168.2.0/255.255.255.0/eth0, hosting node rac2
Start rac1-vip now
[root@rac1 bin]# ./crs_start -f ora.rac1.vip
Attempting to start `ora.rac1.vip` on member `rac1`
Start of `ora.rac1.vip` on member `rac1` succeeded.
Attempting to start `ora.LISTENER.lsnr` on member `rac1`
Start of `ora.LISTENER.lsnr` on member `rac1` succeeded.
Now the VIP is registered and it is reachable now. ora.LISTENER.lsnr status become ONLINE now.
It resolves my issue thnx for the sharing.
ReplyDeleteGreat, Thank you.
ReplyDeleteReally appreciate this kind of informative blog. Thank you1
ReplyDeleteThank you David!
ReplyDelete