CRS-1006 NO more members consider CRS-0215 could not start ora.rac1.vip

问题说明
    OS : AIX 6.1 TL9
    DB: Oracle 10.2.0.1
    安装双节点RAC，在安装CRS时候，第二个节点执行vipca时报错
    CRS-1006: no more members to consider CRS-0215: could not start resoure ora.rac1.vip

问题分析
     google到两种解决方法，经过实际的测试，两种方法均告失败，下面简单说明下这几种方法，第三种方法成功
     第一种 (失败）
    修改$ORA_CRS_HOME/bin/racgvip文件，将其中的221、231、371行的$5替换为$6 
    follow的文档没有找到
    第二种 （失败）    
    修改 $ORA_CRS_HOME/bin/racgvip文件，将其中的
    FAIL_WHEN_DEFAULTGW_NO_FOUND=1
    设置为     FAIL_WHEN_DEFAULTGW_NO_FOUND=0
    follow的文档  ID 356535.1

解决方法
    第三种 （成功）
    备份racgvip文件
    cd    racgvip racgvip.orig  
     修改 $ORA_CRS_HOME/bin/racgvip文件，将其中的行
    $ENTSTAT -d $_IF | $GREP -iEq ".*link.*status.*:.*up.*"
    替换为
    $ENTSTAT -d $_IF | $GREP -iEq '.*lan.*state.*:.*operational.*|.*link.*status.*:.*up.*|.*port.*operational.*state.*:.*up.*|.*driver.*flags.*:.*up.*'
    注意：确保没有多余的字符被写到该文件中。   这种方法follow的 ID 959746.1


补充 说明

    解决方法中参考【文档ID 959746.1】（AIX: 10.2/11.1 VIP Fails to Come Up with "Invalid Parameters, Or Failed To Bring Up VIP" ）
    实际上该文档描述的修改的racgvip内容与本文的racgvip内容有些出入，但是按照文档的操作，还是解决了本文遇到的这个问题。
    下面是【文档ID 959746.1】的描述

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.7 - Release: 10.2 to 11.1
IBM AIX on POWER Systems (64-bit)
IBM AIX Based Systems (64-bit)

Symptoms

On AIX 5.3 TL9+ , AIX 6 or AIX 6.1, the VIP fails to come up, with error "Invalid Parameters, Or Failed To Bring Up VIP".

srvctl start nodeapps -n racnode2
racnode2:ora.racnode2.vip:Interface eth0 checked failed (host=racnode2.us.oracle.com)
racnode2:ora.racnode2.vip:Invalid parameters, or failed to bring up VIP (host=racnode2.us.oracle.com)
CRS-1006: No more members to consider
CRS-0215: Could not start resource 'ora.racnode2.vip'

Tracing the racgvip command shows that it fails when checking to see if the public interface (NIC) is up.
However, the public interface is up.

An error message similar to the following may be seen in logs:

2009-07-23 17:40:05.812: [ RACG][1] [270490][1][ora.srvr0101.vip]: Thu Jul 23 17:40:05 BST 2009 [ 159774 ] IsIfAlive: /usr/bin/entstat -d en0 failed. Return = 1 (host=srvr0101)
Thu Jul 23 17:40:05 BST 2009 [ 159774 ] checkIf: end for if=en0
Invalid parameters, or failed to bring up VIP (host=srvr0101)

Changes

The adapter type for the public network is LHEA (IBM Logical Host Ethernet Adapter):

# /usr/bin/entstat -d en0
-------------------------------------------------------------
ETHERNET STATISTICS (en0) :
Device Type: Host Ethernet Adapter (l-hea)
...

Or, the adapter type is null in entstat -d output:

# /usr/bin/entstat -d en3
-------------------------------------------------------------
ETHERNET STATISTICS (en3) :
Device Type:
...


Cause

The entstat output for LHEA is different from a regular adapter.  

The racgvip script uses entstat output to determine if the specified interface is up or not; because the entstat output for LHEA is different, the check fails, therefore the VIP will not come up.

This is a known issue reported in the following bug:
Bug 8725020 - VIP WONT RUN (LHEA) ADAPTER 5.3 TL9

Same issue happens for devices whose device type is blank in entstat -d output.

Solution

The following workaround fixes the racgvip script so that it does not fail for LHEA adapters:

1. Backup the racgvip script
2. Edit this line in the script using vi:
$ENTSTAT -d $_IF | $GREP -iEq '.*lan.*state.*:.*operational.*|.*link.*status.*:.*up.*|.*port.*operational.*state.*:.*up.*'       

and replace it with this:
$ENTSTAT -d $_IF | $GREP -iEq '.*lan.*state.*:.*operational.*|.*link.*status.*:.*up.*|.*port.*operational.*state.*:.*up.*|.*driver.*flags.*:.*up.*'

(Notice that an extra regexp clause has been tacked on the end of the grep argument.)

3. Make sure that no stray characters have been introduced.
4. Save the racgvip file.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/28697282/viewspace-1626638/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/28697282/viewspace-1626638/