How to troubleshoot debug VIP problems:
-----View statistics for node application resources:
/u01/crs/bin/srvctl config nodeapps-n dbtest2-a-g-s-L
VIP exists.:/dbtest2-vip/10.11.11.198/255.255.255.0/eri0
GSD exists.
ONS Daemon exists.
Listener does not exist.
------Debug VIP
Further debug it by uncommenting the environment variable _usr_ora_debug=1 in the script $ORA _CRS_HOME/BIN/RACGVIP
OR simply as root user, issue the command:
Crsctl Debug Log res "Ora.dbtest2.vip:5"
Turn off debugging with command:
Crsctl Debug Log res "ora.dbtest2.vip:0"
Start the VIP using Srvctl start Nodeapps again. This would create a log for VIPs starting problem for 10.2 and above version
In Directory $ORA _crs_home/log/<nodename>/racg/*vip.log
----------the role of Gateway gateways in Oracle RAC 10g:
By default, the server's default gateway is used as a ping target during the Oracle RAC 10g VIP status check action.
See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/storage/
Upon a ping failure, Oracle would decide that this current interface where the VIP is running has, and would failed 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 ad Ditional error like:
Crs-1006:no 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 would fix the VIP starting problem for above mentioned.
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 to the resources ONLINE
You could proceed with NETCA and DBCA to create a RAC database after this.
Add default gateway
#route Add default GW 192.168.8.1