關於 rac vip fail back
今天在測試rac 11g時發現vip不能自己飄過來,於是查了下些資料,做如下整理:
10.2.0.1 / 10.2.0.2: There is not permanent network monitoring, so it is not possible knowing when the public interface is back again, therefore we need to do a manual fail back
More in detail, it was the instance ( every 10 minutes ) the one who tries to move the VIP back to the preferred node (original node) doing this:
Stop the VIP
Start up the VIP on the original node
So in case the network wasn't fully available this operation will fail causing a new fail-over
During this time there's no service and one instance should exists at least in the node to perform the check
You may have noticed this new resource:
This resource monitors the network constantly, so its not the instance anymore
In case the network fails, there's a new feature called "offline resource monitoring", so it keeps pinging every 60 seconds ( default ) the network to check if its back again
10.2.0.1 / 10.2.0.2: There is not permanent network monitoring, so it is not possible knowing when the public interface is back again, therefore we need to do a manual fail back
crs_relocate10.2.0.3: The VIP automatically fails back when the network is up again, however the implementation wasn't totally fine and there are some side-effects introduced.
More in detail, it was the instance ( every 10 minutes ) the one who tries to move the VIP back to the preferred node (original node) doing this:
Stop the VIP
Start up the VIP on the original node
So in case the network wasn't fully available this operation will fail causing a new fail-over
During this time there's no service and one instance should exists at least in the node to perform the check
10.2.0.4: There's no VIP automatic fail back anymore, however it is possible to emulate the 10.2.0.3 behavior uncommenting the line
ORA_RACG_VIP_FAILBACK=1 && export ORA_RACG_VIP_FAILBACK Location: racgwrap script @ ORACLE_HOME11gR2 Starting with 11.2, the failover is made trough the monitoring of a newly introduced network resource.
You may have noticed this new resource:
crsctl status resource -t
ora.net1.network ONLINE ONLINE rac1 ONLINE ONLINE rac2
This resource monitors the network constantly, so its not the instance anymore
In case the network fails, there's a new feature called "offline resource monitoring", so it keeps pinging every 60 seconds ( default ) the network to check if its back again
crsctl stat type ora.network.type -p ATTRIBUTE=OFFLINE_CHECK_INTERVAL DEFAULT_VALUE=60Finally, it is also possible to disable this feature by setting the OFFLINE_CHECK_INTERVAL in the network resource to zero by doing this
crsctl modify type ora.network.type -attr "ATTRIBUTE=OFFLINE_CHECK_INTERVAL ,TYPE='int',DEFAULT_VALUE=0"Please note that is not supported to edit the ora.* resources
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/22969361/viewspace-1126726/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 關於 RAC VIP (Oracle10G RAC) 的探討(zt)Oracle
- oracle rac的vip與srvctl啟動關係Oracle
- rac vip failback issueAI
- RAC如何修改VIP
- 關於Cache的write-through & write-back
- 基於同網段的RAC架構VIP修改架構
- 基於不同網段的RAC架構VIP修改架構
- RAC更改叢集VIP
- RAC中修改IP, VIP
- 配置RAC中的VIP
- 【RAC】如何修改vip 或者vip 對應的hostname
- 關於前滾(roll forward)和回滾(roll back)Forward
- 基於RedHat的RAC環境下修改ip及vipRedhat
- 【RAC】Oracle rac 如何修改公網及vipOracle
- RAC改VIP和SCAN IP
- RAC 11.2.0.3 修改VIP地址
- oracle rac vip 漂移過程Oracle
- Oracle RAC Load Balance , Fail Over測試OracleAI
- RAC的VIP切換測試
- Oracle RAC修改public, VIP, SCAN IPOracle
- rac 手動漂移scan ip vip
- ORACLE10g修改RAC VIPOracle
- Oracle RAC修改IP和VIP地址Oracle
- 10.2.0.4以後vip不會自動relocate back回原節點
- oracle 11g rac 修改VIP、scan VIP、priv IP操作文件Oracle
- rac 新增第二public ip 和 vip
- RAC_網路_VIP漂移_SCAN IP
- Oracle RAC修改public,private,vip scan IPOracle
- 10g RAC中修改VIP地址
- rac的vip和監聽莫名故障
- 關於10g RAC監聽設定,tnsnames.ora設定,VIP及客戶端配置問題。客戶端
- 【VIP】調整RAC虛擬IP地址(VIP)及虛擬主機名
- 關於現代瀏覽器的 back-and-forward 快取機制瀏覽器Forward快取
- 關於RAC的remote_listenerREM
- 關於Oracle RAC後臺程式Oracle
- 關於RAC的私有網路
- Oracle 10g RAC vip 漂移問題Oracle 10g
- (轉)【VIP】調整RAC虛擬IP地址(VIP)及虛擬主機名