Home > clusterware > CRS-0215: Could not start resource ‘ora.tvmdb02.LISTENER_TVMDB02.lsnr’.

CRS-0215: Could not start resource ‘ora.tvmdb02.LISTENER_TVMDB02.lsnr’.

Symptoms

When starting nodeapps of cluster nodes, it returned the messages below

$ srvctl start nodeapps -n tvmdb02
tvmdb02:ora.tvmdb02.vip:checkIf: Default gateway is not defined (host=tvmdb02)
tvmdb02:ora.tvmdb02.vip:Interface vnet100001 checked failed (host=tvmdb02)
tvmdb02:ora.tvmdb02.vip:Failed to start VIP 172.31.10.103 (host=tvmdb02)
tvmdb02:ora.tvmdb02.vip:checkIf: Default gateway is not defined (host=tvmdb02)
tvmdb02:ora.tvmdb02.vip:Interface vnet100001 checked failed (host=tvmdb02)
tvmdb02:ora.tvmdb02.vip:Failed to start VIP 172.31.10.103 (host=tvmdb02)
CRS-0215: Could not start resource ‘ora.tvmdb02.LISTENER_TVMDB02.lsnr’.

Checking system default gateway, the default gateway was missing

$ netstat -nr
Routing Table: IPv4
Destination           Gateway           Flags  Ref     Use     Interface
——————– ——————– —– —– ———- ———
10.0.0.0             10.1.2.201           U         1        130 vnet2
172.31.10.0          172.31.10.101        U         1         17 vnet100001
192.168.77.0         192.168.77.221       U         1          2 vnet0
127.0.0.1            127.0.0.1            UH       28    3831355 lo0

Fix

Adding the default gateway to the system by root

#  route add default 172.31.10.254

Restart the nodeapps successfully

$  srvctl start nodeapps -n tvmdb02

Advertisements
Categories: clusterware
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: