Oracle 12c R2 Error Codes and Solution Suggestions from INS-40100 to INS-41200
- INS-40102: Specified Grid home is invalid
Cause: The Oracle Grid Infrastructure for a cluster home (Grid home) was placed in the installation owners home directory.
Action: Oracle recommends that you do not place the Grid home in a user home directory, because ownership of the path to that directory is changed to root.
- INS-40103: The installer has detected that the software location specified is on an OCFS2 partition.
Cause: Configuration of an Oracle Grid Infrastructure for a cluster Grid home is not supported on OCFS2 partitions.
Action: Specify a Grid home location that is not an OCFS2 partition.
- INS-40104: The installer has detected that the software location specified is on an OCFS2 partition.
Cause: Configuration of an Oracle Grid Infrastructure for a cluster Grid home is not supported on OCFS2 partitions.
Action: Specify a Grid home location that is not an OCFS2 partition.
Cause: The installer detects that you have configured Oracle Grid Infrastructure software on this server, and that the Oracle base you provided for this install is not the same as the existing Oracle Grid Infrastructure software Oracle base.
Action: Provide the same Oracle base location for this Oracle Grid Infrastructure installation that is used for the existing Oracle Grid Infrastructure.
Cause: The installer detects that the Oracle home location you provided is on an Oracle ASM Cluster File System (ACFS) mountpoint. You cannot place Oracle Grid Infrastructure binaries on an ACFS mount point.
Action: Specify a Grid home location that is on a location other than an ACFS mount point.
- INS-40107: It is recommended that you choose a location with sufficient disk space to accommodate installation of future patches.
Cause: The selected Oracle home was on a volume without enough disk space for future patching.
Action: Choose a location for Oracle home that has enough space (minimum of stringMB) or free up space on the existing volume.
- INS-40108: The installer has detected that the software location specified is on an temporary file system.
Cause: Configuration of an Oracle Grid Infrastructure for a cluster Grid home should not be done on temporary file system .
Action: Specify a Grid home location that is not an temporary file system.
Cause: The Installer has detected the presence of Oracle Clusterware software configured on the node.
Action: You can have only one instance of Oracle Clusterware software configured on a node that is part of an existing cluster.
- INS-40404: The installer has detected a configured instance of Oracle grid infrastructure software on the server.
Cause: You selected to install and configure a new Oracle grid infrastructure installation (Oracle Clusterware and Oracle ASM). However, only one installation of Oracle Clusterware and Oracle ASM can be configured on a server at the same time.
Action: Deconfigure the existing Oracle Grid Infrastructure software before installing and configuring a new instance of Oracle Grid Infrastructure software.
- INS-40405: The installer has detected a configured instance of Oracle Grid Infrastructure software on the system.
Cause: You selected to install and configure a new Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle ASM). However, only one installation of Oracle Clusterware and Oracle ASM can be configured on a server at the same time.
Action: Deconfigure the existing Oracle Grid Infrastructure software before installing and configuring a new instance of Oracle Grid Infrastructure software.
- INS-40406: The Installer has not detected an existing Oracle Grid Infrastructure software on the system.
Cause: The installer is unable to detect any existing Oracle Clusterware or Oracle ASM installation to upgrade.
Action: You can choose either to install a new Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle ASM) on this node and add the node to an existing cluster, or you can install a new Oracle Grid Infrastructure installation and make the node part of a new cluster. If you want to add the node to an existing cluster, then review Oracle Clusterware Administration and Deployment Guide and follow the addnode procedure. If you want to create a new cluster, then select the option for a new installation.
Cause: You can have only one Oracle ASM instance configured on the node.
Action: Select the Software Only installation of Oracle Grid Infrastructure into a new home, and configure Oracle ASM in the new home after installation.
- INS-40409: The installer has detected local Cluster Synchronization Services (CSS) configured on this host. Local CSS is running from: string.
Cause: You selected to install and configure an Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle ASM). However, Oracle Clusterware cannot be installed on a server with a configured CSS daemon.
Action: Deconfigure and delete the existing local CSS daemon, and then restart the installer.
- INS-40410: The installer has detected a configured instance of Oracle Grid Infrastructure software on the system.
Cause: You selected to install and configure a new Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle ASM). However, only one installation of Oracle Clusterware and Oracle ASM can be configured on a server at the same time.
Action: Deconfigure the existing Oracle Grid Infrastructure software before installing and configuring a new instance of Oracle Grid Infrastructure software.
Cause: None of the network interfaces detected on this system supports IPv4 protocol.
Action: Configure at least one of the public interfaces available on this system to support IPv4.
Cause: The installer has detected that an earlier version of Oracle ASM is configured on the server.
Action: If you intend to upgrade Oracle ASM as part of this installation, then you must shut down the Oracle ASM instance before proceeding. Shut down any database instances using Oracle ASM before shutting down the Oracle ASM instance.
- INS-40414: The installer has detected an unused Oracle Cluster Registry (OCR) location pointer file (string) on the system.
Cause: OCR location pointer file (string) is left behind from a previous installation.
Action: Delete the OCR location pointer file (string) and restart the installer.
Cause: The installer has detected the presence of Oracle Database release string instances.
Action: If you intend to upgrade Oracle ASM as part of this upgrade, then you must upgrade Oracle Database instances using Oracle ASM to release string or later before proceeding with upgrading Oracle ASM.
- INS-40416: The installer has detected that the version of the configured instance of Grid Infrastructure is not compatible for upgrading to this release of Grid Infrastructure.
Cause: Oracle Clusterware or Oracle ASM release string or above is needed to upgrade to Oracle Grid Infrastructure.
Action: Install the patchset to upgrade the configured instance of Grid Infrastructure to version string or higher.
- INS-40417: The installer has detected an unused Oracle Cluster Registry (OCR) location registry key (string) on the system.
Cause: OCR location registry key (string) is left behind from a previous installation.
Action: Delete the OCR location registry key (string) and restart the installer.
Cause: The installer has detected that the Oracle Clusterware stack on the local node is not running.
Action: Either run the Installer on the node where Oracle Clusterware stack is running or open a terminal, log in as root or Administrator, change directory to the Oracle Clusterware home (Grid home), and start Oracle Clusterware by entering this command: crsctl start crs
- INS-40419: The installer detects that the configured Oracle Automatic Storage Management (Oracle ASM) release is earlier than the Oracle Grid Infrastructure release.
Cause: Installer has detected that configured version of Automatic Storage Management software is lower than the Grid Infrastructure software version.
Action: Open a terminal, log in as the Grid Infrastructure installation owner, change directory to the Grid home, and run ASMCA to upgrade Oracle ASM.
- INS-40420: The current installation user is not the same as the installation owner of the existing Oracle Grid Infrastructure software.
Cause: The installer detects that the current installation user (string) is not the same as the existing Oracle Grid Infrastructure software user (string). To upgrade the existing software, run the installer as the user owning the Oracle Grid Infrastructure home.
Action: Restart the installation as the user that owns the existing Grid home.
- INS-40421: The installer cannot detect the owner of the existing Oracle Grid Infrastructure home (Grid home).
Cause: The installer is unable to detect the owner of the existing Grid home. To upgrade the software, you must run the installer as the user owning the Grid home.
Action: Run the installer as the user owning the existing Grid home.
- INS-40422: The installer has detected that the configured instance of Grid Infrastructure is not compatible for upgrading to this release of Grid Infrastructure.
Cause: Patchset for the bug string is not installed on the configured instance of the Grid Infrastructure home.
Action: Install the patchset for the bug string on all the nodes to upgrade the configured instance of Grid Infrastructure to current version.
- INS-40423: The Oracle Cluster Registry and the Voting disk are located on a Oracle Cluster File System.
Cause: n/a
Action: n/a
- INS-40424: Installer has detected that the Oracle Cluster Registry (OCR) locations of existing clusterware configuration are on a block or character storage device.The OCR locations cannot be on a block or character storage device during upgrade.
Cause: n/a
Action: n/a
- INS-40425: Installer has detected that the Oracle Cluster Registry (OCR) is not managed through Automatic Storage management (ASM).
Cause: n/a
Action: n/a
Cause: n/a
Action: n/a
- INS-40427: The installer has detected that you are trying to upgrade from a leaf node of a Flex cluster.
Cause: The upgrade action of a Flex cluster is not allowed from a leaf node.
Action: Please upgrade from a hub node of this Flex cluster.
- INS-40601: The Intelligent Platform Management Interface (IPMI) driver is not installed on one or more of the following nodes: string.
Cause: The installer detected that Intelligent Platform Management Interface (IPMI) drivers were not installed on all the nodes that you indicated should be part of the cluster. Cluster Synchronization Service (CSS) requires this driver, as it interacts with the IPMI driver to ensure cluster integrity.
Action: Download the IPMI driver from the hardware vendor website, and ensure that the driver is installed and configured on all the nodes, so that installation can continue.
Cause: The BMC user name text field was blank.
Action: You have selected Intelligent Platform Management Interface (IPMI) to use for failure isolation support. The installer requires the Baseboard Management Controller (BMC) user name to proceed with configuration. Enter the BMC user name that has privileges to interact with the IPMI-compliant hardware.
Cause: Invalid characters were specified in the user name.
Action: Enter a valid BMC user name. The Baseboard Management Controller (BMC) user name can only contain lower or uppercase alphanumeric characters (a – z, A – Z, 0 – 9), hyphen(-), period(.) and underscore(_).
Cause: n/a
Action: n/a
Cause: The specified value for the GNS subdomain contained one or more invalid characters.
Action: Enter a valid GNS subdomain name. Valid characters for the GNS subdomain can be any combination of lower or uppercase alphanumeric characters (a – z, A – Z, 0 – 9), hyphen(-), and period(.).
Cause: n/a
Action: n/a
Cause: The GNS subdomain could not be resolved using TCP/IP host name lookup.
Action: Specify a subdomain that can be resolved.
Cause: The specified value for the GNS virtual IP address contained one or more invalid characters.
Action: Enter a valid value for the GNS virtual IP Address. Valid characters for GNS virtual IP addresses can be any combination of lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), hyphen(-), and period(.).
Cause: n/a
Action: n/a
Cause: The GNS virtual IP address could not be resolved using TCP/IP host name lookup.
Action: Specify a valid GNS virtual IP address.
Cause: The specified GNS virtual host name could not be resolved to an IP address. This may occur if the IP address is in use on another cluster, or the IP address has not been registered to this name in the Domain Name System (DNS).
Action: Ensure that you have entered a virtual host name that is not in use. If you continue to receive an error, then contact your network administrator for assistance.
Cause: The specified value for the cluster name contained one or more invalid characters.
Action: Provide a valid value for the cluster name. Valid characters can be any combination of lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), and hyphen(-).
Cause: The cluster name did not start with a letter.
Action: Provide a value for the cluster name that starts with a letter
Cause: The Cluster name text field was blank.
Action: Provide a valid value for the cluster name.
Cause: The specified cluster name was too long.
Action: Provide a cluster name that is 15 or fewer characters in length.
Cause: The cluster name cannot be longer than string characters. With the Typical install type, the host portion of the SCAN is used as the cluster name. If that portion is longer than string characters, then the installer truncates the cluster name to string characters.
Action: If you want to use a specific name for the cluster, then provide a name no greater than string characters, or select the Advanced installation type.
Cause: The name you provided as the SCAN contained one or more invalid characters.
Action: Enter a valid name for the SCAN. Valid characters can be any combination of lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), hyphen(-), and period(.).
Cause: The name you provided as the SCAN contained one or more invalid characters. For the Typical installation type, invalid characters include those that are invalid for a cluster name, because the cluster name is derived from SCAN.
Action: Enter a valid name for the SCAN and for the cluster name. Valid characters can be any combination of lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), hyphen(-), and period(.).
Cause: The SCAN did not start with an alphabetic character.
Action: Provide a value for the SCAN that starts with an alphabetic character.
Cause: No name was provided as the SCAN.
Action: Provide a valid name to use for the SCAN.
Cause: The name you provided as the SCAN could not be resolved using TCP/IP host name lookup.
Action: Provide name to use for the SCAN for which the domain can be resolved.
- INS-40719: IP address configured for Single Client Access Name (SCAN): string is already assigned to another system.
Cause: The installer could not find the IP addresses you selected as SCAN addresses. This may be because they are assigned to another system, or because the IP addresses are not listed in the DNS or hosts files as assigned to this domain name.
Action: Enter resolvable IP addresses to use as SCAN addresses.
Cause: The name configured as the SCAN was not associated with an IP address.
Action: Ensure the names you provide as SCANs are associated with IP addresses.
Cause: The SCAN port text field was empty.
Action: Provide a valid value for the SCAN port.
Cause: The value entered for the SCAN port contained one or more invalid characters. A valid SCAN port is a number.
Action: Enter a valid numeric value for the SCAN port.
Cause: The value entered for the SCAN Port was out of the valid range.
Action: Enter a SCAN port number between 1024 and 65535.
Cause: None of the locally defined network interfaces has a subnet matching the SCAN subnet.
Action: Define a public interface with a subnet matching the one you want to use for the SCAN.
- INS-40725: Unable to determine the existence of an interface with a subnet matching the SCAN subnet.
Cause: No interface was found with a subnet matching the subnet designated as the SCAN subnet.
Action: Define a public interface with a subnet matching the one you want to use for the SCAN.
Cause: The name you provided as the SCAN is not in the GNS subdomain.
Action: Ensure the name you provide as the SCAN is in the same domain as the GNS subdomain.
Cause: The name for the configured SCAN is already associated with an IP address.
Action: If you intend to use GNS resolution for your cluster, then ensure the names you provide for SCANs are not associated with IP addresses that are already in use.
Cause: The installer detects that the SCAN port number you provided is already in use. This can occur if Oracle9i RAC is installed on the server, and it is using the port.
Action: Provide a different SCAN port number in the range 1024 and 65535.
Cause: Single Client Access Name (SCAN) cannot have a domain name suffix when configuring cluster to use shared GNS
Action: Remove the period(\”.\”) and any following text from the specified Single Client Access Name (SCAN)
Cause: To configure Shared GNS, a GNS Client data file has to be specified.
Action: Specify a valid GNS Client data file to configure shared GNS.
- INS-40730: Hostname portion of the specified Single Client Access Name (SCAN) Name: string is longer than 63 characters.
Cause: n/a
Action: n/a
Cause: Installer has detected that the specified GNS Client data file is not a valid file, or does not exist, or is not a readable file.
Action: Specify a valid GNS Client data file to configure shared GNS.
Cause: Configuring Grid Naming Service(GNS) is mandatory to configure Flex Cluster.
Action: Choose to configure GNS to have configure Flex Cluster.
Cause: n/a
Action: n/a
Cause: n/a
Action: n/a
Cause: The specified value for the GNS virtual IP address is IPV6, for which DHCP is not supported.
Action: Ensure that the option to Configure DHCP assigned Virtual IPs to the nodes is deselected.
- INS-40735: Specified Grid Naming Service (GNS) subdomain is not valid. It does not follow the standard domain name format.
Cause: n/a
Action: n/a
Cause: The GNS Client data file location should not be a UNC path.
Action: Provide the GNS Client data file location which is not on a UNC path.
Cause: n/a
Action: n/a
Cause: Values in the cluster node information table are unfilled.
Action: Provide valid data in the cluster node information table.
Cause: Some fields were left blank in the cluster node information table.
Action: Ensure that all information in the table is filled in.
Cause: The name you provided as the host name contains one or more invalid characters.
Action: Ensure that the host name contains valid characters. Valid characters for host names can be any combination of lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), and hyphen (-).
Cause: The value provided for ORACLE_HOSTNAME does not resolve to a valid host name.
Action: Provide a valid host name for ORACLE_HOSTNAME, and restart the installer.
Cause: One or more IP addresses do not resolve to valid host names.
Action: You must enter valid IP addresses that resolve to hostnames before installation can continue.
- INS-40906: Duplicate host name string found in the node information table for Oracle Clusterware install.
Cause: Duplicate entries have been made in the node information table for Oracle Clusterware installation.
Action: Remove duplicate entries in the Oracle Clusterware node information table.
Cause: The local node (the node where you are running the installer) was missing from the list of host names you provided.
Action: Include the local node in the list of host names for grid installation.
Cause: One or more host names you provided are invalid, as they do not resolve to a valid IP address.
Action: Enter valid host names.
Cause: Node information was entered for two or more nodes that belonged to different domains.
Action: Enter host names belonging to the same domain.
Cause: The Virtual IP did not resolve to an IP address.
Action: Enter a valid name for the virtual IP that resolves to an IP address.
Cause: Some public nodes either were unreachable, or they belonged to a different subnet.
Action: Ensure that nodes in the list are up and reachable, and ensure that the node addresses are all in the same subnet.
Cause: One or more virtual host names appeared to be assigned to another system on the network.
Action: Ensure that the virtual host names assigned to each of the nodes in the cluster are not currently in use, and the IP addresses are registered to the domain name you want to use as the virtual host name.
Cause: The user performing this installation is not configured identically on all nodes. This may be due to differences in the user or group IDs, or to SSH configuration issues.
Action: If necessary, refer to the installation guide for information about how to set up user equivalence manually on cluster nodes.
Cause: An Oracle9i RAC installation was present on remote node string, but not on the local node.
Action: To install on a set of nodes on which the Oracle9i release of Oracle RAC has been configured, start the installer on the node where Oracle9i RAC is installed so that the installer can upgrade the existing installation.
- INS-40915: The installer has detected the presence of Oracle Clusterware on the following nodes: string.
Cause: Either Oracle Clusterware is running on the listed nodes, or previous installations of Oracle Clusterware are not completely deinstalled.
Action: For each node listed, ensure that existing Oracle Clusterware is completely deinstalled. You can also choose not to include these nodes in this installation.
Cause: The installer detected single-instance versions of Cluster Synchronization Services (CSS) on the following nodes in the cluster:string
Action: Before proceeding with the installation, you must deconfigure CSS, shut down any Oracle Automatic Storage Management (Oracle ASM) instances, and shut down all databases that use Oracle ASM for storage on all of the listed nodes. Oracle Clusterware installation starts a cluster-wide version of CSS. After Oracle Clusterware installation is complete, you may start up any databases and Oracle ASM instances that previously used CSS. When they are brought back up, Oracle Clusterware provides CSS.
Cause: n/a
Action: n/a
Cause: Virtual IP name cannot be in IP address format.
Action: Provide a valid virtual IP name.
Cause: You did not provide a hostname for the node.
Action: Enter a valid hostname.
Cause: You did not enter a name for the virtual IP address.
Action: Enter a valid virtual IP name.
Cause: The name you provided for the virtual IP name contains one or more invalid characters.
Action: Provide a name to use for the virtual IP name that contains valid characters. Valid characters for virtual IP name can be any combination of lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), and hyphen(-).
Cause: SCAN provided does not resolve to an IP address.
Action: Ensure that the SCAN is valid, and that it is resolvable to an IP address.
Cause: No local network interface was found with an address matching the subnet for the SCAN.
Action: Ensure that the SCAN subnet matches the subnet configured on an existing local network interface.
Cause: Unable to locate common interfaces or subnets on all cluster member nodes.
Action: Ensure that the local node has valid network interfaces, with valid subnets that are the same on all cluster member nodes.
- INS-40925: One or more nodes have interfaces not configured with a subnet that is common across all cluster nodes.
Cause: One or more nodes have network interfaces configured with a subnet that is not common to all nodes in the cluster.
Action: Ensure all cluster nodes have a public interface that is defined with the same subnet, and accessible by all nodes in the cluster.
Cause: One or more nodes have interfaces configured with subnets that are different than the SCAN subnet.
Action: Ensure all nodes have a public interface configured with a subnet that matches the SCAN subnet.
Cause: The following nodes have interfaces in common subnets that have different interface names: string
Action: Ensure that the names of interfaces defined on common subnets are the same on all cluster member nodes.
Cause: An unknown error occurred during validation of addresses or subnets on cluster member nodes.
Action: Ensure network interfaces are configured correctly, and that subnets are available on all nodes of the cluster. Ensure all nodes have at least one public interface on a subnet available on all nodes, and ensure all nodes have one public interface on the same subnet.
- INS-40929: Installer has detected that the Oracle 9i Global Services Daemon (GSD) is running on the following nodes: string
Cause: Oracle 9i Global Services Daemon (GSD) processes are detected on some or all of the nodes specified.
Action: To allow Oracle Clusterware to serve Oracle9i RAC databases, on each cluster member node you must shut down the Oracle9i Database GSD, and shut down any Oracle RAC databases. The installer will configure a GSD to run in the new grid Oracle home. After installation, you may restart all Oracle9i databases.
Cause: One or more node VIPs could not be resolved to a valid IP address.
Action: Be sure all node VIPs are resolvable to a valid IP address.
- INS-40931: The following nodes have interfaces that are configured on a subnet that is different from the SCAN subnet: string.
Cause: Some node VIPs are on subnets that are different from the SCAN subnet.
Action: For each cluster member node, ensure that the VIP is configured with the SCAN subnet.
Cause: Unknown errors were encountered while validating Node VIPS.
Action: Ensure all node VIPs resolve to a valid IP address.
Cause: Interface information collection failed.
Action: Be sure all nodes are accessible and have valid network interfaces defined.
Cause: n/a
Action: n/a
- INS-40935: A cluster operation (For example, copy file, file exists, or other operation) failed on node string: Message: string
Cause: n/a
Action: n/a
Cause: A cluster operation (for example, list interfaces) failed.
Action: Ensure that all cluster member nodes are accessible on the network.
Cause: The hostname or names listed are invalid.
Action: Ensure that you are not providing aliases, and that the hostnames you provide are valid.
- INS-40938: The installer has detected that some or all cluster member nodes of the Oracle 9i RAC database are not included in the selected list of nodes.
Cause: Some of the nodes that are cluster members of the Oracle9i RAC database are not among the nodes you selected.
Action: In the list of nodes, specify all the cluster member nodes of the Oracle9i RAC database.
- INS-40939: Some of the nodes you selected are not members of the vendor cluster that is on the local server.
Cause: The installer detects that this node is a member of a vendor cluster, and that some of the nodes you selected to make members of the Oracle Clusterware cluster are not members of the vendor cluster.
Action: If you install Oracle Clusterware on a node that is a member of a vendor cluster, then all nodes that you select to be Oracle Clusterware nodes must also be members of the vendor cluster.
Cause: Nodes are not configured on the same domain.
Action: Ensure that all nodes are configured on the same domain
Cause: The installer cannot collect domain information from one or more nodes you selected.
Action: Before proceeding with the installation, ensure that all selected nodes are configured on the same domain.
Cause: Target Hub node size for a cluster should be an integer value between string and string.
Action: Specify a valid value for Target Hub node size.
Cause: A Flex Cluster type Oracle Clusterware can be configured only if there is at least one Hub node or Auto Node.
Action: Add a Hub node or Auto node to the configuration.
Cause: n/a
Action: n/a
Cause: n/a
Action: n/a
Cause: The value provided for vip suffix has one or more invalid characters.
Action: Provide a value for the virtual IP suffix that contains valid characters. Valid characters for virtual IP suffix can be any combination of lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), and hyphen(-).
Cause: You did not enter a value for virtual IP suffix.
Action: Enter a valid virtual IP suffix for the node range.
Cause: You did not provide a host prefix for the node range.
Action: Enter a valid host prefix.
Cause: Host prefix provided contains one or more invalid characters.
Action: Ensure that the host prefix contains valid characters. Valid characters for host prefix can be any combination of lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), and hyphen (-).
Cause: Either the lower or the upper bound of the node range is blank.
Action: Provide valid lower and upper bound of the node range you wish to configure.
Cause: The lower or the upper bound of the node range contain one or more invalid characters.
Action: Ensure that the lower and upper bound of the node range contain valid numbers.
Cause: n/a
Action: n/a
- INS-40954: Local node string did not resolve to an IP address. Provide alternative name that resolves to an IP address.
Cause: n/a
Action: n/a
- INS-40955: Local node string could not be resolved using TCP/IP host name lookup. It is recommended that the local node is resolvable using TCP/IP lookup. This may avoid configuration failures at a later stage.
Cause: n/a
Action: n/a
- INS-40956: The specified public host string did not resolve to an IP address. Provide alternative name that resolves to an IP address.
Cause: n/a
Action: n/a
- INS-40957: The specified public host string could not be resolved using TCP/IP host name lookup. It is recommended that the public host name is resolvable using TCP/IP lookup. This may avoid configuration failures at a later stage.
Cause: n/a
Action: n/a
- INS-40958: Installer has detected that specified string (string) is configured with the dual stack addresses.
Cause: The specified string is configured with both ipv4 and ipv6 addresses.
Action: Be sure to specify a string which is configured with sigle IP address family.
Cause: Either the format of the information entered was incorrect, or the interface name or subnet information was incorrect.
Action: Enter the correct interface information before proceeding
Cause: None of the network interfaces were designated as public.
Action: Designate at least one interface as a public interface.
Cause: Interface string has been marked as both Public and Private.
Action: Designate interface string either as Public or Private, but not both Public and Private.
Cause: There is no interface marked as Private.
Action: Ensure that at least one interface is designated as Private.
Cause: The chosen public interface is not on the same subnet as the SCAN VIP.
Action: Ensure the chosen public interface is on the same subnet as the SCAN VIP subnet, and that the same subnet is configured for SCAN VIPs on all cluster nodes.
Cause: The chosen public or private interface subnet is not identical on all nodes.
Action: Ensure that the subnets configured for public and private interfaces are identical on all cluster nodes.
- INS-41107: The interface (string) chosen as Public or Private is not on a shared subnet. Nodes not defining are: string
Cause: The Public or Private interface on the nodes indicated are on a different subnet than the ones used on other nodes.
Action: Ensure that the specified Public or Private interface share the same subnet across the nodes.
- INS-41108: string on subnet string chosen as public does not match subnet of Grid Naming Service (GNS) VIP.
Cause: The chosen public interface is not on the same subnet as the GNS VIP.
Action: Be sure that the chosen public interface is on a subnet which matches the GNS VIP subnet and is common across all cluster nodes.
- INS-41109: Configured network mask string for the interface string is not same across all cluster nodes.
Cause: Installer has detected that interface string does not have the same netmask string configured on all cluster nodes.
Action: Ensure that the chosen interface has been configured with same netmask across all cluster nodes.
- INS-41110: Installer has transferred the provided interface list to following format: string. This might be because either the Installer has detected hybrid interface configuration (both IPv4 and IPv6 configuration present) on the cluster nodes, or different interface names are configured for particular subnet on the cluster nodes. In the latter case, Installer will not consider interface names during Grid Infrastructure configuration.
Cause: n/a
Action: n/a
Cause: You have specified generic name for the interface configured on the subnet (string). But installer detected that multiple interfaces configured on this subnet.
Action: Ensure that you have specified interface name appropriately.
Cause: Installer has detected that network interface string does not maintain connectivity on all cluster nodes.
Action: Ensure that the chosen interface has been configured across all cluster nodes.
Cause: Installer has detected that both public and private interfaces are configured on the same subnet.
Action: Ensure that the public and private interfaces are configured on different subnets.
- INS-41114: Interface selected as Private (cluster interconnect) (string) is not configured with Internet Protocol version 4 (IPv4).
Cause: Installer has detected that the interface (string) is not configured with Internet Protocol version 4 (IPv4). Only those interfaces which are configured with Internet Protocol version 4 (IPv4) can be specified as Private(cluster interconnect) interface.
Action: Ensure that the interface selected for Private(cluster interconnect) is configured with IPv4.
Cause: There are more than string Private and ASM & Private interfaces selected.
Action: Ensure that the number of selected Private and ASM & Private interfaces does not exceed string.
- INS-41170: You have chosen not to configure the Grid Infrastructure Management Repository. Not configuring the Grid Infrastructure Management Repository will permanently disable the Cluster Health Monitor, QoS Management, Memory Guard, and Rapid Home Provisioning features. Enabling of these features will require reinstallation of the Grid Infrastructure.
Cause: n/a
Action: n/a