VIP Problem on Richmond1 (01)

Friday 09 May, 2008 - 23:39

Found the correct log at /u00/crs/oracle/product/10/log/richmond1/racg/ora.richmond1.vip.log with repeated error messages like:

2008-05-09 18:00:18.506: [ RACG][3076428992] [9596][3076428992][ora.richmond1.vip]: clsrcexecut: env ORACLE_CONFIG_HOME=/u00/crs/oracle/product/10/app
2008-05-09 18:00:18.506: [ RACG][3076428992] [9596][3076428992][ora.richmond1.vip]: clsrcexecut: cmd = /u00/crs/oracle/product/10/app/bin/racgeut -e _USR_ORA_DEBUG=0 54 /u00/crs/oracle/product/10/app/bin/racgvip check richmond1
2008-05-09 18:00:18.506: [ RACG][3076428992] [9596][3076428992][ora.richmond1.vip]: clsrcexecut: rc = 1, time = 10.080s
2008-05-09 18:00:18.506: [ RACG][3076428992] [9596][3076428992][ora.richmond1.vip]: end for resource = ora.richmond1.vip, action = start, status = 1, time = 20.230s
2008-05-09 21:07:50.047: [ RACG][3076416704] [29420][3076416704][ora.richmond1.vip]: Interface eth0 checked failed (host=richmond1.yaocm.id.au)
Invalid parameters, or failed to bring up VIP (host=richmond1.yaocm.id.au)

Google on RACG VIP failed eth0 picked up Error while installing Oracle10g RAC on Ent.Linix using VMWA. The solution proposed is to set a real default gateway on eth0.

# vi /etc/sysconfig/network-scripts/ifcfg-eth0 (to change gateway to 192.168.100.65)
# service network restart
# /u00/crs/oracle/product/10/app/bin/crs_start ora.richmond1.vip
Attempting to start `ora.richmond1.vip` on member `richmond1`
Start of `ora.richmond1.vip` on member `richmond1` failed.
CRS-1006: No more members to consider
CRS-0215: Could not start resource 'ora.richmond1.vip'.

Same errors in the log.

Reran vipca - same errors.

Rebooted richmond1.

Still the same problem. The underlying symptom is that there is no eth0:1 defined.

Oracle RAC - Errors and Issues says:

starting VIP application resource on (2) nodes1:CRS-1006: No more members to consider

CRS-0215: Could not start resours 'ora.vm01rhel.vip' : Check the log file /u01/app/oracle/product/10.2.0/crs/log/vm01rhel/racg/ora.vm01rhel.vip.log

- I got this issue resolved by specifying the default gateway to some dummy ip address (same subnet) in both of my virtual machines. Earlier i didnt specify any default gateway both in my virtual machines and got this error