Customer feedback, 11.2.0.4, Linux7 GI cluster software, Oracle software is installed properly completed.
DBCA building a database, there
VIP do not all share the same subnetwork,or the vip subnetwok does not match that of any public network interface in the cluster
First, observe problems
Querying the cluster resource status
Cluster Resources
--------------------------------------------------------------------------------
ora.rac1.vip
1 ONLINE ONLINE Rac1
ora.rac2.vip
1 ONLINE ONLINE Rac2
ora.LISTENER_SCAN1.lsnr
1 ONLINE ONLINE Rac1
ora.cvu
1 ONLINE ONLINE Rac1
ora.oc4j
1 ONLINE ONLINE Rac1
ora.scan1.vip
1 ONLINE ONLINE Rac1
[grid@rac1 ~]$
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.10.6.8)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
The command completed successfully
[grid@rac1 ~]$ srvctl config vip -n rac2
VIP exist: /rac2-vip/10.10.6.9/10.10.6.0/255.255.255.0/, managed nodes rac2
[grid@rac1 ~]$ srvctl config vip -n rac1
VIP exist: /rac1-vip/10.10.6.8/10.10.6.0/255.255.255.0/, managed nodes rac1
$cat /etc/hosts
127.0.0.1 localhost
:: 1 rac1
10.10.6.6 rac1
10.10.6.7 rac2
10.10.6.8 shrt1-vip
10.10.6.9 rac2-vip
10.10.6.10 rac-scan
can see from the above, Grid can not register properly monitor information resources Public ip
IP address ping rac1 can get is 127.XXX
suggestion, comment out the subsequent information :: 1
recommended Baidu get is interpreted :: 1 using Ipv6 address resolution.
Restart crs OK
Second, questions
11.2.0.4 RAC supports the use of ipv6 ???
Query 2.1 12.1 Official documents
Query 12. 1 official documents
Network Address Configuration in a Cluster You can configure a network interface for either IPv4, IPv6, or both types of addresses on a given network.
If you configure redundant network interfaces using a third-party technology, then Oracle does not support configuring one
interface to support IPv4 addresses and the other to support IPv6 addresses. You must configure network interfaces
of a redundant interface pair with the same IP address type. If you use the Oracle Clusterware Redundant Interconnect feature,
then you must use IPv4 addresses for the interfaces. All the nodes in the cluster must use the same IP protocol configuration. Either all the nodes use only IPv4,
or all the nodes use only IPv6, or all the nodes use both IPv4 and IPv6. You cannot have some nodes in the cluster configured
to support only IPv6 addresses, and other nodes in the cluster configured to support only IPv4 addresses. The local listener listens on endpoints based on the address types of the subnets configured for the network resource.
Possible types are IPV4, IPV6, or both. Cluster public network card, which can be ipv4, ipv6 may be, but does not allow a ipv4, ipv6 another
query 12.1 enhancements! ! ! Description does not support 11.2.0.4 before!
2.7.5 Oracle RAC Enhancements
The following sections describe new features for Oracle RAC.
2.7.5.1 Support for IPv6 Based IP Addresses for Oracle RAC Client Connectivity
Cluster nodes can be configured to use either IPv4 or IPv6 based IP addresses for the Virtual IPs (VIP) on the public network, while more than one public network can be defined for the cluster. Database clients and applications can connect to either IPv4 or IPv6 VIP addresses. The Single Client Access Name (SCAN) listener automatically redirects client connects to the appropriate database listener within a given subnet considering the IP protocol requested by the client. SCAN listeners can be defined for each subnet in the cluster.
IPv6 based IP addresses have become the latest standard for the information technology infrastructure in today's data centers. With this release, Oracle RAC and Oracle Grid Infrastructure support this standard for client connectivity.
See Also:
Oracle Clusterware Administration and Deployment Guide for details
Support for IPv6 IP address to enable Oracle RAC client connections
Cluster nodes can be configured to use based on the IP address of the IPv4 or IPv6, and can be defined as a cluster of a plurality of public networks of virtual IP (VIP) on the public network.
Database and client applications can connect to IPv4 or IPv6 VIP address. Single Client Access Name (SCAN) the listener based on the IP protocol client request,
automatically redirected to the client database connection listeners within a given subnet. The cluster can be defined for each subnet SCAN listener.
Note: This is useless to say private networks, support IPV6 !!!
or 12.1 further illustrate the private network only allows IPV4! ! !
https://docs.oracle.com/database/121/CWLIN/networks.htm#CIHCEIJH
5.4 IPv4 and IPv6 Protocol Requirements
Oracle Grid Infrastructure and Oracle RAC support the standard IPv6 address notations specified by RFC 2732 and global and site-local IPv6 addresses as defined by RFC 4193.
Cluster member node interfaces can be configured to use IPv4, IPv6, or both types of Internet protocol addresses. However, be aware of the following:
Configuring public VIPs: During installation, you can configure VIPs for a given public network as IPv4 or IPv6 types of addresses. You can configure an IPv6 cluster by selecting VIP and SCAN names that resolve to addresses in an IPv6 subnet for the cluster, and selecting that subnet as public during installation. After installation, you can also configure cluster member nodes with a mixture of IPv4 and IPv6 addresses.
If you install using static virtual IP (VIP) addresses in an IPv4 cluster, then the VIP names you supply during installation should resolve only to IPv4 addresses. If you install using static IPv6 addresses, then the VIP names you supply during installation should resolve only to IPv6 addresses.
During installation, you cannot configure the cluster with VIP and SCAN names that resolve to both IPv4 and IPv6 addresses. For example, you cannot configure VIPs and SCANS on some cluster member nodes to resolve to IPv4 addresses, and VIPs and SCANs on other cluster member nodes to resolve to IPv6 addresses. Oracle does not support this configuration.
Configuring private IP interfaces (interconnects): you must configure the private network as an IPv4 network. IPv6 addresses are not supported for the interconnect.
Redundant network interfaces: If you configure redundant network interfaces for a public or VIP node name, then configure both interfaces of a redundant pair to the same address protocol. Also ensure that private IP interfaces use the same IP protocol. Oracle does not support names using redundant interface configurations with mixed IP protocols. You must configure both network interfaces of a redundant pair with the same IP protocol.
GNS or Multi-cluster addresses: Oracle Grid Infrastructure supports IPv4 DHCP addresses, and IPv6 addresses configured with the Stateless Address Autoconfiguration protocol, as described in RFC 2462.
2.2 12.2 Official documents
doubt? 12.1 RAC is not supported private network IPV6?
12.2 RAC private network began to support IPV6.
IPv4 and IPv6 Protocol Requirements Oracle Grid Infrastructure and Oracle RAC support the standard IPv6 address notations specified by RFC 2732 and global and
site-local IPv6 addresses as defined by RFC 4193. Configuring Public VIPs Cluster member node interfaces can be configured to use IPv4, IPv6, or both types of Internet protocol addresses. During installation,
you can configure VIPs for a given public network as IPv4 or IPv6 types of addresses. You can configure an IPv6 cluster by selecting
VIP and SCAN names that resolve to addresses in an IPv6 subnet for the cluster, and selecting that subnet as public during installation.
After installation, you can also configure cluster member nodes with a mixture of IPv4 and IPv6 addresses. If you install using static virtual IP (VIP) addresses in an IPv4 cluster, then the VIP names you supply during installation
should resolve only to IPv4 addresses. If you install using static IPv6 addresses, then the VIP names you supply during installation
should resolve only to IPv6 addresses. During installation, you cannot configure the cluster with VIP and SCAN names that resolve to both IPv4 and IPv6 addresses.
You cannot configure VIPs and SCANS on some cluster member nodes to resolve to IPv4 addresses, and VIPs and SCANs on other cluster
member nodes to resolve to IPv6 addresses. Oracle does not support this configuration. Configuring Private IP Interfaces (Interconnects) You can configure the private network either as an IPv4 network or IPv6 network. Redundant Network Interfaces If you configure redundant network interfaces for a public or VIP node name, then configure both interfaces of a redundant pair
to the same address protocol. Also ensure that private IP interfaces use the same IP protocol. Oracle does not support names using
redundant interface configurations with mixed IP protocols. You must configure both network interfaces of a redundant pair with
the same IP protocol. GNS or Multi-Cluster Addresses Oracle Grid Infrastructure supports IPv4 DHCP addresses, and IPv6 addresses configured with the Stateless Address Autoconfiguration
protocol, as described in RFC 2462. Note:Link-local and site-local IPv6 addresses as defined in RFC 1884 are not supported. Parent topic: Configuring Networks for Oracle Grid Infrastructure and Oracle RAC
2.3 MOS 11.2.0.4 do not support IPV6 ???
doubt? Why 11g does not support ipv6, but Oracle Grid can properly install it? I guess the IP address is a network, so you can create success vip normal. But listen resource that which is normal, but for DBCA when the need to register the instance RAC cluster, you need to be registered to use vip, due to the card using ipv6, so some level configuration parsing from incompatible card does not support Oracle Public .
Observation MOS single instance can be modified to meet the conditions, RAC did not find instructions.
Note that, just as MOS further illustrate Oracle 11g listener default rule is Ipv4
and Oracle 11g release 2 ipv6 support for client landed resolution, 12.1 really support the RAC level. Server Fails to Start the when WebLogic Specifying IPV6 Address in JDBC the URL of for RAC Datasource ( Doc ID 2402429.1 ) SYMPTOMS WLS Server failing to start with invalid IP address when configuring the IPV6 address for the database in ONS section
of datasource. Issue not seen with IPV4 address. CAUSE Oracle Database 11g Release 2 supports IPv6 addressing for all features and components in single-instance mode,
and Oracle Database 12c Release 1 extends that to allow client connectivity over public networks to Oracle Real Application
Clusters (Oracle RAC). You are trying to use an 11g driver/ons jar file with RAC and the statement makes it clear that it isn’t supported until 12.1. The 11.x ons jar file isn’t parsing the ONS string to handle IPV6 addresses (looking for the last colon to separate out
the port from the address string). REFER: HTTP: // www.oracle.com/technetwork/database/enterprise-edition/oracledatabaseipv6sod-4007245.pdf
follows after the DB 11.2.0.4 single instance is created, you can refer to the following, the transformation of use of IPV6! But non-RAC, the transformation is not the focus of this document, not described in detail.
ON the Oracle Database Enterprise IPv6 Enabling Edition (Doc ID 783,570.1)
the Oracle Database - Standard Edition - Version 11.2.0.1 to 11.2.0.2.0 [Release 11.2]
PURPOSE
Introduction
IPv6 is designed with migration in mind. It is possible to run an Operating System with both IPv4 and IPv6 running at the same time. It is possible to configure the Oracle Database and Listener to use both IPv4 and IPv6, but this note covers how to setup the Oracle 11g Release 2 (11.2.0.0) software to use only IPv6 on a Linux system that has both IPv4 and IPv6 configured. The 11.2 release is the only one that supports the IPv6 protocol.