Cause

By default, the server's default gateway is used as a ping target during the Oracle RAC 10g VIP status check action. 
Upon a ping failure, Oracle will decide that the current interface where the VIP is running has failed, and will initiate 
an interface / internode VIP failover. 

In above case, we used just one node for CRS installation, so the VIP coudn't failover to other nodes and thus reported additional error like : 
CRS-1006: No more members to consider 
CRS-0215: Could not start resource 'ora.dbtest2.vip'.

Solution

10.1.0.4 and above introduced a parameter FAIL_WHEN_DEFAULTGW_NOT_FOUND in the file 
$ORA_CRS_HOME/bin/racvip to address this problem. 

The following steps will fix the VIP starting problem for above mentioned scenario. 

1- stop nodeapps 
2- As root, 
vi the script. $ORA_CRS_HOME/bin/racgvip and change the value of 
variable FAIL_WHEN_DEFAULTGW_NOT_FOUND=0 . 
3- start nodeapps and you should see the resources ONLINE
 

修改$ORA_CRS_HOME/bin/racgvip：

[root@rac2 bin]# cd /oracle/app/crs/bin/

[root@rac2 bin]# vi racgvip

修改：FAIL_WHEN_DEFAULTGW_NOT_FOUND=0

运行：

[root@rac1 ~]# cd /oracle/app/crs/bin/

[root@rac1 bin]# ./crs_stat -t

Name           Type           Target    State     Host

------------------------------------------------------------

ora.rac1.gsd   application    ONLINE    ONLINE    rac1

ora.rac1.ons   application    ONLINE    ONLINE    rac1

ora.rac1.vip   application    ONLINE    ONLINE    rac2

ora.rac2.gsd   application    ONLINE    ONLINE    rac2

ora.rac2.ons   application    ONLINE    ONLINE    rac2

ora.rac2.vip   application    ONLINE    ONLINE    rac2

问题解决