crs-1006 crs-0215 aix

aix 装 10.2.0.5 RAC，运行vipca，遇到crs-1006 crs-0215报错：

解决方法：

设置public和private的gateway，或者vipca中设置这个参数：FAIL_WHEN_DEFAULTGW_NOT_FOUND=0

具体参考metalink文档：CRS-0215: Could not start resource 'ora..vip' [ID 356535.1]

CRS-0215: Could not start resource 'ora..vip' [ID 356535.1]
	修改时间 25-MAR-2010类型 PROBLEM状态 MODERATED

In this Document
Symptoms
Changes
Cause
Solution

---

Platforms: 1-914CU;

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.4 to 11.1.0.7
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 10.1.0.4 to 11.1.0.7

Symptoms

The command : crs_stat -t output shows VIP is offline and trying to startitgives error :
CRS-0215: Could not start resource 'ora.dbtest2.vip'.

Example: crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora....st2.gsd application ONLINE ONLINE dbtest2
ora....st2.ons application ONLINE ONLINE dbtest2
ora....st2.vip application ONLINE OFFLINE

# ./srvctl start nodeapps -n dbtest2
dbtest2:ora.dbtest2.vip:Interface eri0 checked failed (host=dbtest2)
dbtest2:ora.dbtest2.vip:Failed to start VIP 10.11.11.198 (host=dbtest2)
dbtest2:ora.dbtest2.vip:Interface eri0 checked failed (host=dbtest2)
dbtest2:ora.dbtest2.vip:Failed to start VIP 10.11.11.198 (host=dbtest2)
CRS-1006: No more members to consider
CRS-0215: Could not start resource 'ora.dbtest2.vip'.
CRS-0210: Could not find resource ora.dbtest2.LISTENER_DBTEST2.lsnr.


To know what is the nodeapps configuration in particular for VIP,
issue the command: srvctl config nodeapps -n <nodename> -a -g -s -l
Example:
/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.


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"
You may turn off debugging with command : crsctl debug log res "ora.dbtest2.vip:0"
Start the VIP using srvctl start nodeapps again. This will create a log for VIP starting problem for 10.2 and aboveversion
in directory $ORA_CRS_HOME/log/<nodename>/racg/*vip.log

Example:lastlinesofthe*.vip.logshows-

2005-02-0920:38:06.711:[RACG][1][5602][1][ora.dbtest2.vip]:203800[5604]Checkinginterfaceexistance 203800[5604]Callinggetifbyip 203800[5604]getifbyip:startedfor10.11.11.198 203800[5604]getifbyip:returningIFeri0:1 203800[5604]Completedgetifbyiperi0:1 203801[5604]Completedwithin 2005-02-0920:38:06.711:[RACG][1][5602][1][ora.dbtest2.vip]:itialinterfacetest 203801[5604]checkIf:startforif=eri0 203801[5604]checkIf:-zdefaultgw 203801[5604]defaultgw:started 203801[5604]defaultgw:completedwith10.11.11.1 203801[5604]checkIf:-ndefaultgw 203804[5604]checkIf: 2005-02-0920:38:06.711:[RACG][1][5602][1][ora.dbtest2.vip]:inwhile,beforesleep 203805[5604]checkIf:inwhile,beforesleep 203806[5604]checkIf:checkedif=eri0failed Interfaceeri0checkedfailed(host=dbtest2) 203806[5604]checkIf:endforif=eri0 203806[5604]PerformingCRS_STATtesting 203806 2005-02-0920:38:06.711:[RACG][1][5602][1][ora.dbtest2.vip]:[5604]CompletedCRS_STATtesting 203806[5604]Completedsecondgatewaytest 203806[5604]Interfacetests FailedtostartVIP10.11.11.198(host=dbtest2)

From above we see the VIP:10.11.11.198 is correct however oracle function checkIf
is failing when trying to reach the default gateway IP:10.11.11.1

Changes

• Either the default gateway has got changed to someother IP -or-
• It is on a different network from the client (the network where the VIP is configured on) -or-
• It is not being used anymore.

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

You may proceed with netca and dbca to create a RAC database after this.

---

<<End_of_Article>> FOLDER:ST.Server.Scalability.RAC TOPIC:Administration and Configuration DOCUMENT-ID:356535.1 ALIAS: SOURCE:AWIZ 4830376.993 DOCUMENT-TYPE:PROBLEM ZCXTECH TITLE:CRS-0215: Could not start resource 'ora..vip' IMPACT:LOW SKILL-LEVEL:NOVICE STATUS:MODERATED DISTRIBUTION:EXTERNAL ZCXPUBLIC ZCXCURRENT AUTHOR:KMEHTA.IN ERROR:CRS-1006 ERROR:CRS-210 ERROR:CRS-215 PRODID-5 COMPONENT:RAC.ADMIN MINVER:10.1.0.4 MAXVER:11.1.0.7 PORTID-0 FDRSEG-824 FDRSEG-1221 FDRSEG-773 FDRSEG-465