Grid infrastructure (GI):HAIP on RDS is not supported (文檔 ID 2328941.1)
Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
集羣建議使用HAIP配置私網的冗餘,但是普通的以太網線需要配置本地地址鏈接,但是RDS不能配置本地地址鏈接.
在12.1.0.2之前,驗證私網的協議,去看ASM和instance的alert log
Cluster communication is configured to use the following interface(s) for this instance
172.xx.xx.xxx
cluster interconnect IPC version:Oracle RDS/IP (generic)
IPC Vendor 1 proto 3
Version 3.0
In the UDP case it would say "UDP/IP" instead of "RDS/IP".
在12.1.0.2之後,
In 12.2 and higher, to verify what protocol is used by RAC, look in the alert log of the ASM and Database instances during startup, refer to MOS Document 751343.1
To verify if the HAIP is used,
1) first check if the resource ora.cluster_interconnect.haip is online by issuing "crsctl stat res ora.cluster_interconnect.haip -init" and check the state
NAME=ora.cluster_interconnect.haip
TYPE=ora.haip.type
TARGET=ONLINE
STATE=ONLINE on cehaovmsp1153
2) Then check if the asm or the database is using haip.
Do this by one of following two methods to check IP address(es) that is getting used. Any 169.n.n.n is HAIP
1) Check the alert log of the ASM and the database instances during startup:
Cluster communication is configured to use the following interface(s) for this instance
169.xxx.xxx.xxx
cluster interconnect IPC version:Oracle RDS/IP (generic)
IPC Vendor 1 proto 3
Version 3.0
2) Query v$cluster_interconnects and check the IP address(es) by issuing "select name, ip_address,source from v$cluster_interconnects;"
NAME IP_ADDRESS SOURCE
--------------- ---------------- -------------------------------
eth1:1 169.xxx.xxx.xxx
To revert back RAC to use UDP instead of RDS, relink with UDP IPC library. Again, to do this relink the GI home and all related RDBMS homes by performing the following as OS home owner.
Relinking GI_HOME:
1) As root, unlock GI home: <GI_HOME>/crs/install/rootcrs.pl -unlock
2) As GI_HOME owner, go to GI_HOME/rdbms/lib
3) As GI_HOME owner, issue "make -f ins_rdbms.mk ipc_g ioracle"
4) As root, lock GI home: <GI_HOME>/crs/install/rootcrs.pl -patch
Relinking the database homes (repeat the following for all database homes):
1) As the ORACLE_HOME owner, stop all resources (database, listener, etc) that's running from the database home home. When stopping database, use NORMAL or IMMEDIATE option.
2) As the ORACLE_HOME owner, go to ORACLE_HOME/rdbms/lib
3) As the ORACLE_HOME, issue "make -f ins_rdbms.mk ipc_g ioracle"
4) As the ORACLE_HOME owner, start all resources that were stopped in the step 1