40 INS-40001 to INS-45000
- 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.
- 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.
- 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.
- INS-40105: The location specified for Oracle Base is invalid.
-
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.
- INS-40106: Invalid location specified for Grid home.
-
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.
- 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.
- 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 .
- INS-40401: The Installer has detected a configured Oracle Clusterware home on the system.
-
Cause: The Installer has detected the presence of Oracle Clusterware software configured on the node.
- 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.
- 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.
- 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.
- INS-40407: The installer has detected an Oracle ASM instance is already configured on the computer.
-
Cause: You can have only one Oracle ASM instance configured on the node.
- 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.
- 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.
- INS-40412: This server does not meet network requirements to install and configure this product.
-
Cause: None of the network interfaces detected on this system supports IPv4 protocol.
- INS-40413: Existing Oracle ASM instance detected.
-
Cause: The installer has detected that an earlier version of Oracle ASM is configured on the server.
- 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.
- INS-40415: Upgrade database instances using Oracle Automatic Storage Management (Oracle ASM).
-
Cause: The installer has detected the presence of Oracle Database release string instances.
- 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.
- 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.
- INS-40418: The installer has detected that Oracle Clusterware is not running on local node.
-
Cause: The installer has detected that the Oracle Clusterware stack on the local node is not running.
- 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.
- 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.
- 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.
- 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.
- INS-40423: The Oracle Cluster Registry and the Voting disk are located on a Oracle Cluster File System.
-
Cause: 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
- INS-40425: Installer has detected that the Oracle Cluster Registry (OCR) is not managed through Automatic Storage management (ASM).
-
Cause: n/a
- INS-40426: Grid installation option has not been specified.
-
Cause: 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.
- 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.
- INS-40602: Baseboard Management Controller (BMC) user name text field cannot be left blank.
-
Cause: The BMC user name text field was blank.
- INS-40603: Invalid characters in User Name.
-
Cause: Invalid characters were specified in the user name.
- INS-40604: Password field is blank.
-
Cause: n/a
- INS-40701: Invalid characters in Grid Naming Service (GNS) subdomain.
-
Cause: The specified value for the GNS subdomain contained one or more invalid characters.
- INS-40702: Specify a value for Grid Naming Service (GNS) subdomain.
-
Cause: n/a
- INS-40704: GNS subdomain cannot be resolved.
-
Cause: The GNS subdomain could not be resolved using TCP/IP host name lookup.
- INS-40705: Invalid characters in Grid Naming Service (GNS) Virtual IP Address.
-
Cause: The specified value for the GNS virtual IP address contained one or more invalid characters.
- INS-40706: Grid Naming Service (GNS) Virtual IP Address is blank.
-
Cause: n/a
- INS-40707: Grid Naming Service (GNS) Virtual IP Address string cannot be resolved.
-
Cause: The GNS virtual IP address could not be resolved using TCP/IP host name lookup.
- INS-40708: Grid Naming Service (GNS) Virtual IP Address string already assigned to another system.
-
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).
- INS-40709: Cluster name: string contains invalid characters.
-
Cause: The specified value for the cluster name contained one or more invalid characters.
- INS-40710: Cluster name:string does not start with a letter.
-
Cause: The cluster name did not start with a letter.
- INS-40711: Cluster Name is blank.
-
Cause: The Cluster name text field was blank.
- INS-40712: Cluster Name:string is too long.
-
Cause: The specified cluster name was too long.
- INS-40713: Installer will use \"string\" as cluster name.
-
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.
- INS-40714: Single Client Access Name (SCAN) Name: string contains invalid characters.
-
Cause: The name you provided as the SCAN contained one or more invalid characters.
- INS-40715: Single Client Access Name (SCAN) Name: string contains invalid characters.
-
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.
- INS-40716: Single Client Access Name (SCAN) Name:string does not start with a letter.
-
Cause: The SCAN did not start with an alphabetic character.
- INS-40717: Single Client Access Name (SCAN) is unfilled.
-
Cause: No name was provided as the SCAN.
- INS-40718: Single Client Access Name (SCAN):string could not be resolved.
-
Cause: The name you provided as the SCAN could not be resolved using TCP/IP host name lookup.
- 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.
- INS-40720: Single Client Access Name (SCAN):string is not associated with any IP address.
-
Cause: The name configured as the SCAN was not associated with an IP address.
- INS-40721: Single Client Access Name (SCAN) port is blank.
-
Cause: The SCAN port text field was empty.
- INS-40722: Single Client Access Name (SCAN) port: string contains non-numeric characters.
-
Cause: The value entered for the SCAN port contained one or more invalid characters. A valid SCAN port is a number.
- INS-40723: Invalid Single Client Access Name (SCAN) port number:string.
-
Cause: The value entered for the SCAN Port was out of the valid range.
- INS-40724: No locally defined network interface matches the SCAN subnet.
-
Cause: None of the locally defined network interfaces has a subnet matching the SCAN subnet.
- 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.
- INS-40726: Single Client Access Name (SCAN):string is not in the GNS subdomain string.
-
Cause: The name you provided as the SCAN is not in the GNS subdomain.
- INS-40727: Single Client Access Name (SCAN):string is already associated with an IP address.
-
Cause: The name for the configured SCAN is already associated with an IP address.
- INS-40728: Invalid Single Client Access Name (SCAN) port number:string.
-
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.
- INS-40729: Invalid Single Client Access Name (SCAN) specified:[string].
-
Cause: Single Client Access Name (SCAN) cannot have a domain name suffix when configuring cluster to use shared GNS
- INS-40729: GNS Client data file not specified.
-
Cause: To configure Shared GNS, a GNS Client data file has to be specified.
- INS-40730: Hostname portion of the specified Single Client Access Name (SCAN) Name: string is longer than 63 characters.
-
Cause: n/a
- INS-40730: File name specified as GNS Client data file is not a valid file.
-
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.
- INS-40731: You have not chosen to configure Grid Naming Service(GNS).
-
Cause: Configuring Grid Naming Service(GNS) is mandatory to configure Flex Cluster.
- INS-40732: Configuring Grid Infrastructure with shared GNS option is currently not supported.
-
Cause: n/a
- INS-40733: Configuring Grid Infrastructure with shared GNS option for big cluster is not supported.
-
Cause: n/a
- INS-40734: Configure DHCP option is not supported for IPV6 GNS VIP
-
Cause: The specified value for the GNS virtual IP address is IPV6, for which DHCP is not supported.
- INS-40735: Specified Grid Naming Service (GNS) subdomain is not valid. It does not follow the standard domain name format.
-
Cause: n/a
- INS-40736: The provided GNS Client data file location is not supported.
-
Cause: The GNS Client data file location should not be a UNC path.
- INS-40737: Installer was unable to verify the GNS client data file.
-
Cause: n/a
- INS-40901: The cluster node information table is unfilled.
-
Cause: Values in the cluster node information table are unfilled.
- INS-40902: Missing entries in the node Information table.
-
Cause: Some fields were left blank in the cluster node information table.
- INS-40903: Host name contains invalid characters.
-
Cause: The name you provided as the host name contains one or more invalid characters.
- INS-40904: ORACLE_HOSTNAME does not resolve to a valid host name.
-
Cause: The value provided for ORACLE_HOSTNAME does not resolve to a valid host name.
- INS-40905: Unresolved host IP addresses.
-
Cause: One or more IP addresses do not resolve to valid host names.
- 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.
- INS-40907: Local node not included in the list of host names for grid installation.
-
Cause: The local node (the node where you are running the installer) was missing from the list of host names you provided.
- INS-40908: Invalid host names.
-
Cause: One or more host names you provided are invalid, as they do not resolve to a valid IP address.
- INS-40909: Host names from multiple domains entered.
-
Cause: Node information was entered for two or more nodes that belonged to different domains.
- INS-40910: Virtual IP: string entered is invalid.
-
Cause: The Virtual IP did not resolve to an IP address.
- INS-40911: Some public node names could not be resolved.
-
Cause: Some public nodes either were unreachable, or they belonged to a different subnet.
- INS-40912: Virtual host name: string is assigned to another system on the network.
-
Cause: One or more virtual host names appeared to be assigned to another system on the network.
- INS-40913: The following nodes cannot be clustered due to user equivalence issue: string.
-
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.
- INS-40914: The installer has detected the presence of Oracle9i RAC on the remote node, string.
-
Cause: An Oracle9i RAC installation was present on remote node string, but not on the local node.
- 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.
- INS-40916: Single-instance versions of Cluster Synchronization Services (CSS) are detected.
-
Cause: The installer detected single-instance versions of Cluster Synchronization Services (CSS) on the following nodes in the cluster:string
- INS-40917: Host name cannot be in IP Address format.
-
Cause: n/a
- INS-40918: Virtual IP name: string cannot be in IP Address format.
-
Cause: Virtual IP name cannot be in IP address format.
- INS-40919: Hostname cannot be left unfilled.
-
Cause: You did not provide a hostname for the node.
- INS-40920: No name was provided as the virtual IP name.
-
Cause: You did not enter a name for the virtual IP address.
- INS-40921: Virtual IP name contains invalid characters.
-
Cause: The name you provided for the virtual IP name contains one or more invalid characters.
- INS-40922: Invalid SCAN - unresolvable to an IP address.
-
Cause: SCAN provided does not resolve to an IP address.
- INS-40923: Unable to match a local interface or subnet with the SCAN.
-
Cause: No local network interface was found with an address matching the subnet for the SCAN.
- INS-40924: Failure while initializing search for common interface or subnets across cluster nodes.
-
Cause: Unable to locate common interfaces or subnets 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.
- INS-40926: Cluster node interfaces are configured in subnets different from the SCAN subnet.
-
Cause: One or more nodes have interfaces configured with subnets that are different than the SCAN subnet.
- INS-40927: Interfaces with common subnets have different names on different nodes.
-
Cause: The following nodes have interfaces in common subnets that have different interface names: string
- INS-40928: An unknown interface error occurred during validation of cluster member nodes.
-
Cause: An unknown error occurred during validation of addresses or subnets on cluster member nodes.
- 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.
- INS-40930: The following nodes were not resolvable during host IP address lookup: string.
-
Cause: One or more node VIPs could not be resolved 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.
- INS-40932: An unknown error has occurred while validating Node Virtual IPs: string
-
Cause: Unknown errors were encountered while validating Node VIPS.
- INS-40933: Interface collection failed on node string.
-
Cause: Interface information collection failed.
- INS-40934: A remote directory operation failed on node string: Message: string
-
Cause: 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
- INS-40936: A command tool operation failed on node string: Message: string
-
Cause: A cluster operation (for example, list interfaces) failed.
- INS-40937: The following hostnames are invalid:string
-
Cause: The hostname or names listed are invalid.
- 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.
- 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.
- INS-40940: Nodes : string are not in the domain : string
-
Cause: Nodes are not configured on the same domain.
- INS-40941: Unable to retrieve domain information on one or more nodes.
-
Cause: The installer cannot collect domain information from one or more nodes you selected.
- INS-40942: Invalid value specified for Target Hub node size.
-
Cause: Target Hub node size for a cluster should be an integer value between string and string.
- INS-40943: No Hub nodes/Auto nodes specified.
-
Cause: A Flex Cluster type Oracle Clusterware can be configured only if there is at least one Hub node or Auto Node.
- INS-40944: The length of upper bound and lower bound of ranges is not same.
-
Cause: n/a
- INS-40945: The value of upper bound is lesser than or equal to lower bound.
-
Cause: n/a
- INS-40946: The vip suffix provided has invalid characters.
-
Cause: The value provided for vip suffix has one or more invalid characters.
- INS-40947: No value was provided as the virtual IP suffix.
-
Cause: You did not enter a value for virtual IP suffix.
- INS-40949: Host Prefix cannot be left unfilled.
-
Cause: You did not provide a host prefix for the node range.
- INS-40950: Host prefix contains invalid characters.
-
Cause: Host prefix provided contains one or more invalid characters.
- INS-40951: The lower or upper bound of the range cannot be empty.
-
Cause: Either the lower or the upper bound of the node range is blank.
- INS-40952: The lower or upper bound of the range contain invalid characters.
-
Cause: The lower or the upper bound of the node range contain one or more invalid characters.
- INS-40953: Local node cannot be a Leaf node.
-
Cause: 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
- 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
- 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
- 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
- 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.
- INS-41101: The specified interface information is incorrect.
-
Cause: Either the format of the information entered was incorrect, or the interface name or subnet information was incorrect.
- INS-41102: No public interface designated.
-
Cause: None of the network interfaces were designated as public.
- INS-41103: Interface string has multiple subnets associated with it.
-
Cause: Interface string has been marked as both Public and Private.
- INS-41104: No Private Interface designated.
-
Cause: There is no interface marked as Private.
- INS-41105: string on subnet string chosen as public does not match subnet of SCAN VIP.
-
Cause: The chosen public interface is not on the same subnet as the SCAN VIP.
- INS-41106: Invalid choice for public/private interface.
-
Cause: The chosen public or private interface subnet is not identical on all 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.
- 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.
- 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.
- 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
- INS-41111: The installer has detected that multiple interfaces configured on a subnet (string).
-
Cause: You have specified generic name for the interface configured on the subnet (string). But installer detected that multiple interfaces configured on this subnet.
- INS-41112: Specified network interface doesnt maintain connectivity across cluster nodes.
-
Cause: Installer has detected that network interface string does not maintain connectivity on all cluster nodes.
- INS-41113: Specified public and private interfaces are configured on the same subnet: string
-
Cause: Installer has detected that both public and private interfaces are configured on the same subnet.
- 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.
- INS-41115: The number of selected Private and ASM & Private interfaces (string) exceeds the limit.
-
Cause: There are more than string Private and ASM & Private interfaces selected.
- 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
- INS-41204: No shared partition are available between nodes.
-
Cause: The specified nodes did not have at least one shared partition.
- INS-41205: Client ASM data file not specified.
-
Cause: To configure storage on a client ASM, a valid client data file has to be specified.
- INS-41206: File name specified as client ASM data file is not a valid file.
-
Cause: Installer has detected that the specified client ASM data file is not a valid file, or does not exist, or is not a readable file.
- INS-41208: None of the available network subnets is marked for use by Oracle Automatic Storage Management (ASM)
-
Cause: At least one of the available network subnets should be configured for use by Oracle Automatic Storage Management (ASM).
- INS-41210: One of the available network subnets is marked for use by Automatic Storage Management(ASM).
-
Cause: This storage option does not require configuring a network subnet for use by ASM.
- INS-41212: Specified ASM client data file is invalid.
-
Cause: The cluster name in the ASM client data file doesnt match with the cluster name specified for this installation.
- INS-41213: Oracle Cluster File system is not supported on windows.
-
Cause: n/a
- INS-41214: Disk group name not specified.
-
Cause: n/a
- INS-41215: No Disk groups detected on remote cluster.
-
Cause: Installer has not detected any diskgroups configured on the remote cluster.
- INS-41216: Specified disk group is not found on the remote cluster
-
Cause: n/a
- INS-41302: Normal redundancy requires three locations for the Oracle Cluster Registry.
-
Cause: Fewer than three locations were provided for the Oracle Cluster Registry.
- INS-41303: External redundancy requires a location for the Oracle Cluster Registry.
-
Cause: A location for the Oracle Cluster Registry was not specified.
- INS-41305: Invalid characters in one or more Oracle Cluster Registry (OCR) locations.
-
Cause: One or more Oracle Cluster Registry (OCR) locations contained bad characters.
- INS-41306: Invalid Oracle Cluster Registry (OCR) Locations.
-
Cause: One or more Oracle Cluster Registry (OCR) locations are not valid.
- INS-41307: Insufficient space in shared file system for Oracle Cluster Registry (OCR).
-
Cause: Insufficient free space was available in the file system. Oracle Cluster Registry requires a minimum of string MB of free space in the file system.
- INS-41309: The Oracle Cluster Registry (OCR) cannot be placed on a block or character device.
-
Cause: The Oracle Cluster Registry (OCR) location you provided is on a block or character device.
- INS-41310: More than one Oracle Cluster Registry is in the same partition.
-
Cause: The Oracle Cluster Registry was located more than once on the same partition. For normal redundancy, Oracle recommends that you specify three locations on separate partitions for the Oracle Cluster Registry.
- INS-41311: One or more Oracle Cluster Registry (OCR) locations specified are in an existing OCR directory.
-
Cause: One or more Oracle Cluster Registry (OCR) locations specified were in directories with existing OCR files.
- INS-41312: One or more locations specified for the Oracle Cluster Registry (OCR) cannot be used.
-
Cause: One or more Oracle Cluster Registry (OCR) locations specified did not have proper permissions or ownership for the installation to proceed.
- INS-41313: Duplicate entries found in one or more Oracle Cluster Registry (OCR) locations.
-
Cause: One or more Oracle Cluster Registry locations specified were duplications.
- INS-41314: File string already exists. The installer will make an attempt to replace this file.
-
Cause: The specified OCR file already exists.
- INS-41315: File string already exists.
-
Cause: The specified OCR file already exists.
- INS-41316: Unable to delete file string
-
Cause: The attempt to delete the file was not successful.
- INS-41317: Invalid Oracle Cluster Registry (OCR) locations.
-
Cause: One or more Oracle Cluster Registry (OCR) locations were not valid.
- INS-41318: One or more files string already exist. The installer will attempt to replace existing files.
-
Cause: One or more specified files already exist.
- INS-41319: File(s) string already exist(s).
-
Cause: The specified shared location is in use.
- INS-41320: Unable to delete one or more files string.
-
Cause: The attempt to delete files was unsuccessful.
- INS-41321: Invalid Oracle Cluster Registry (OCR) location.
-
Cause: The installer detects that the storage type of the location (string) is not supported for Oracle Cluster Registry.
- INS-41322: The provided OCR Location (string) can not be configured.
-
Cause: string name is reserved for the backup locations for OCR.
- INS-41502: Insufficient number of voting disk locations provided for normal redundancy configuration.
-
Cause: You did not provide enough separate locations for voting disk files. To provide normal redundancy, you must specify three separate locations for voting disk files.
- INS-41503: Missing voting disk file locations for external redundancy configuration.
-
Cause: A voting disk file location was not specified. For external redundancy, you must specify a location for the voting disk file.
- INS-41505: The voting disk file locations contain one or more invalid characters.
-
Cause: n/a
- INS-41506: One or more voting disk file locations are not valid.
-
Cause: One or more voting disk file locations were not placed in an existing directory.
- INS-41508: More than one voting disk file is located on the same partition.
-
Cause: Normal redundancy for voting disk files requires that each file is placed on a different partition, to avoid a single point of failure.
- INS-41509: Duplicate locations used for one or more voting disk file locations.
-
Cause: One or more voting disk file locations you provide are duplicate. Each voting disk location must be on separate devices.
- INS-41510: One or more voting disk file locations are the same as an OCR location.
-
Cause: One or more voting disk file locations you provided are the same as an OCR location. Voting disk files cannot be on the same location as Oracle Cluster Registry (OCR) locations.
- INS-41511: One or more of the locations you specified for voting disk files are the same as an Oracle 9i quorum location.
-
Cause: Oracle 9i quorum disks are located on one or more of the locations you specified for voting disk files.
- INS-41512: Voting disk files cannot be located on block or character devices.
-
Cause: The voting disk file location you provided is on a block or character device.
- INS-41513: Voting disk file locations cannot be in a directory with existing voting disks.
-
Cause: One or more voting disk file locations you provided have an existing voting disk file.
- INS-41514: One or more locations you specified for voting disk files cannot be used.
-
Cause: One or more locations you specified for placing voting disk files did not have proper permissions or ownership for installation to proceed.
- INS-41515: Insufficient space in shared file system for voting disk file.
-
Cause: Insufficient space was available in the storage location for a voting disk file. Voting disk files require a minimum of string MB of free space.
- INS-41516: File string already exists. The installer will make an attempt to replace this file.
-
Cause: The specified voting disk file already exists.
- INS-41517: File string already exists.
-
Cause: The specified voting disk file already exists.
- INS-41518: Unable to delete file string
-
Cause: The attempt to delete the file was not successful.
- INS-41519: One or more voting disk file locations are not valid.
-
Cause: One or more voting disk file locations may not be shared on all nodes.
- INS-41520: For high availability, Oracle recommends that you have this storage mirrored at the hardware level. Alternatively, you can select \"Normal Redundancy\" option and specify three locations that are on different disks.
-
Cause: n/a
- INS-41521: Invalid Voting Disk location.
-
Cause: The installer detects that the storage type of the location (string) is not supported for voting disk files.
- INS-41702: No nodes selected for upgrade.
-
Cause: Node selection was blank.
- INS-41703: The local node is not selected as one of the nodes for upgrade.
-
Cause: The nodes selected for upgrade did not include the local node.
- INS-41704: Selected nodes should be members of the same cluster. The following nodes are not in the cluster: string.
-
Cause: One of more nodes selected were not in the same cluster.
- INS-41705: The installer has detected that one or more nodes (string) that are part of the cluster are down.
-
Cause: n/a
- INS-41706: Only subset of nodes selected for upgrade.
-
Cause: You have chosen a subset of the cluster nodes for the upgrade.
- INS-41707: Not all cluster member nodes are selected for upgrade.
-
Cause: The installer detects that this server has an earlier release of Oracle Grid Infrastructure software installed on this system. However, you have selected to upgrade a subset of the cluster nodes.
- INS-41708: Oracle Automatic Storage Management (Oracle ASM) is not selected for upgrade.
-
Cause: The installer detects that an earlier release of Oracle ASM is installed on this server. Oracle ASM needs to be upgraded as part of this installation.
- INS-41709: Oracle Automatic Storage Management (Oracle ASM) is not installed on this server.
-
Cause: You selected to upgrade Oracle ASM. However, the installer does not detect Oracle ASM on this server.
- INS-41710: Oracle Automatic Storage Management (Oracle ASM) configured in your cluster cannot be upgraded in a rolling manner. During the upgrade process, any databases using the active Oracle ASM will be forcibly shutdown.
-
Cause: The installer has detected that the version of the configured instance of Oracle ASM is not compatible for rolling upgrade to this release of Oracle Grid Infrastructure.
- INS-41711: The upgrade process upgrades the stack one node at a time, even though you selected to upgrade all nodes. Database service will be disrupted for any database that uses Oracle Automatic Storage Management (Oracle ASM), and that is not managed by Oracle Clusterware, or that uses Oracle Clusterware manual management policy. All other databases and services should not be affected, and should continue to function. If this is not desirable, then before proceeding with the upgrade, ensure that Oracle Clusterware manages databases using Oracle ASM, and set the automatic management policy on databases managed by Oracle Clusterware.
-
Cause: n/a
- INS-41712: Installer has detected that the Oracle Clusterware software on this cluster is not functioning properly on the following nodes string.
-
Cause: The Oracle Clusterware software configured on the system is not in a suitable state to upgrade.
- INS-41713: The installer has detected that one or more nodes (string) that are part of the cluster are down. Installer will perform upgrade of Grid Infrastructure only on the nodes that are up. The remaining nodes can be upgraded later, following the manual steps as detailed in the documentation.
-
Cause: n/a
- INS-41714: The installer has detected that you are performing a non-rolling upgrade. Oracle recommends that you perform rolling upgrade of Oracle Grid Infrastructure operated in Flex Cluster Mode.
-
Cause: n/a
- INS-41802: Unable to determine release of Oracle Automatic Storage Management running from home string.
-
Cause: An Oracle Automatic Storage Management (Oracle ASM) home was found, but the Oracle ASM instance was down. The installer was unable to determine the Oracle ASM release.
- INS-41803: An entry for Oracle ASM is found in the system registry or oratab, but it is not associated with a software home location.
-
Cause: An Oracle ASM entry was listed in the system registry or oratab, but Oracle ASM home string was missing.
- INS-41804: An instance of a prior release Oracle ASM is running.
-
Cause: There is an Oracle ASM instance already running on the server.
- INS-41806: Virtual IP name cannot be the same as the Single Client Access Name (SCAN): string
-
Cause: The name you provided for the virtual IP name is the same name used as the SCAN.
- INS-41807: The installer has detected that Oracle Clusterware is not running on the following nodes: string.
-
Cause: Either there was an error in starting the Oracle Clusterware stack on the specified nodes, or the root scripts on the specified nodes were not run.
- INS-41808: Possible invalid choice for OSASM Group.
-
Cause: The name of the group you selected for the OSASM group is commonly used to grant other system privileges (For example: asmdba, asmoper, dba, oper).
- INS-41809: Possible invalid choice for OSDBA Group.
-
Cause: The group name you selected as the OSDBA for ASM group is commonly used for Oracle Database administrator privileges.
- INS-41810: Possible invalid choice for OSOPER Group.
-
Cause: The group name you selected as the OSOPER for ASM group is commonly used for Oracle Database administrator privileges.
- INS-41811: OSDBA for ASM and OSOPER for ASM groups are the same OS group.
-
Cause: The groups you selected granting the OSDBA for ASM and OSOPER for ASM system privileges are the same group.
- INS-41812: string and OSASM are the same OS group.
-
Cause: The chosen values for string group and the chosen value for OSASM group are the same.
- INS-41813: OSDBA for ASM, OSOPER for ASM, and OSASM are the same OS group.
-
Cause: The group you selected for granting the OSDBA for ASM group for database access, and the OSOPER for ASM group for startup and shutdown of Oracle ASM, is the same group as the OSASM group, whose members have SYSASM privileges on Oracle ASM.
- INS-41814: The installer has detected that some of the services of Oracle Grid Infrastructure are not running on this system.
-
Cause: There may have been an error in starting the Oracle Grid Infrastructure services, or you may not have run the root scripts starting these services on this server.
- INS-41815: The installer has detected that Oracle Clusterware is not upgraded to string version.
-
Cause: Either there was an error in starting the Oracle Clusterware stack on some of the nodes, or the root scripts on some nodes were not run. If the Clusterware is upgraded from earlier versions, root upgrade script might not be run successfully on the specified nodes.
- INS-41816: The installer has detected that Oracle Clusterware is not upgraded to string version.
-
Cause: There might be an error in starting the Oracle Clusterware stack on the some of the nodes or there might be unreachable node(s) which are part of Oracle Clusterware.
- INS-41817: The installer has detected that Oracle Clusterware is not running on the following nodes: string.
-
Cause: There may have been an error in starting the Oracle Clusterware stack on the specified nodes.
- INS-41818: The installer has detected that some of the services of Oracle Grid Infrastructure are not running on this system.
-
Cause: There may have been an error in starting the Oracle Grid Infrastructure services.
- INS-41871: The user account you are using to install the software is not a member of the following OS groups: string
-
Cause: The installation user account must be a member of all groups required for installation.
- INS-41872: The OS group you selected as the ASM Administration Operator Group (ASMOPER) may not exist on the server.
-
Cause: The installer cannot find the group you selected to be the ASMOPER group in the groups defined on the server, or in the Network Information Service (NIS).
- INS-41873: Invalid value specified for OSOPER Group.
-
Cause: OS group string specified for OSOPER Group contains one or more invalid characters.
- INS-41874: Oracle ASM Administrator (OSASM) Group specified is same as the inventory group.
-
Cause: Operating system group string specified for OSASM Group is same as the inventory group.
- INS-41875: Oracle ASM Administrator (OSASM) Group specified is same as the users primary group.
-
Cause: Operating system group string specified for OSASM Group is same as the users primary group.
- INS-41876: The node listener user name provided cannot be root.
-
Cause: n/a
- INS-41877: The node listener user name provided cannot be same as the installing user.
-
Cause: n/a
- INS-41878: The node listener user ('string') provided does not exist on nodes which are provided for cluster configuration.
-
Cause: n/a
- INS-41879: User name for node listener was not provided for clusterware configuration.
-
Cause: n/a
- INS-41880: User for node listener cannot be a member of Oracle ASM Administrator (OSASM) group.
-
Cause: n/a
- INS-41881: Installer has detected that the group specified for string is not same as the group retrieved from the current configuration of grid software. The upgrade operation may not be successful if the same group name is not selected.
-
Cause: n/a
- INS-41882: The node listener user name provided cannot be nobody.
-
Cause: n/a
- INS-41901: The Oracle Grid Infrastructure Typical installation cannot be performed on this system.
-
Cause: The installer has detected the existence of vendor-specific clusterware. The typical Oracle Grid Infrastructure installation is a simplified configuration that is not designed to co-exist with clusterware other than Oracle Clusterware.
- INS-41902: The Oracle Grid Infrastructure Typical installation cannot be performed on this system.
-
Cause: The installer has detected the existence of Oracle RAC 9i release 9.x on this server. The Oracle Grid Infrastructure Typical installation is a simplified configuration that is not designed to support older versions of Oracle RAC.
- INS-42001: The same drive letter string cannot be assigned to more than one partition
-
Cause: n/a
- INS-42002: The specified partition cannot be used.
-
Cause: The specified partition was selected for storing the software binaries.
- INS-42003: No partitions selected
-
Cause: No partitions were selected or partition details provided were incomplete.
- INS-42004: No free drive letters available
-
Cause: The local server did not have any available drive letters to assign to partitions.
- INS-42005: The drive letter is not assigned to one or more partitions
-
Cause: Each partition you select must have an assigned drive letter.
- INS-42006: Selected drive letter (string) is invalid or not available for usage.
-
Cause: Either the drive letter is invalid, or it is already assigned to an existing partition.
- INS-42011: The operating system group specified for oraInventory group is invalid.
-
Cause: The user account running the installation must have the oraInventory group as its primary group.
- INS-42012: The current Grid home is not registered in the central inventory on this host.
-
Cause: The wizard finds that this Grid home is not registered in the central inventory.
- INS-42013: Installation user cannot configure the Grid home.
-
Cause: The wizard detects that the existing Grid home was not installed or cloned using the current user id: string.
- INS-42014: Oracle Grid Infrastructure cannot be configured.
-
Cause: The wizard detects that Oracle Grid Infrastructure is already configured on this server.
- INS-42015: File missing from Grid home: string
-
Cause: The installer cannot find the specified file in the Grid home. The wizard requires this file to be present in the Grid home before it can proceed.
- INS-42016: The current Grid home is not registered in the central inventory on the following nodes: string
-
Cause: The wizard does not find this Grid home to be registered with the central inventory on some or all of the nodes specified.
- INS-42017: The Grid home is inconsistent on the following nodes: string
-
Cause: The wizard detects that the Grid home is inconsistent on some or all of the nodes specified. Review the log file for further details.
- INS-42018: Specified disk group is invalid.
-
Cause: The installer detects that the specified disk group is not on the discovery path you provided.
- INS-42019: The wizard is unable to detect a configured prior release instance of Oracle Grid Infrastructure for a cluster or Cluster Ready Services.
-
Cause: You can only use Oracle Grid Infrastructure Configuration Wizard to upgrade earlier releases of Oracle Grid Infrastructure for a cluster or Cluster Ready Services.
- INS-42020: The Wizard is unable to detect the user of Grid home.
-
Cause: The wizard is not able to detect the user of the existing Grid home. This might be because configuration file (string) is modified/corrupted in the Grid home.
- INS-42021: Multibyte characters in SCAN Name
-
Cause: In Typical install SCAN Name is also used as Cluster Name. The SCAN name contains multibyte characters which are invalid for Cluster Name.
- INS-42022: Multibyte characters in Cluster Name.
-
Cause: Multibyte characters are not allowed in Cluster Name.
- INS-42023: Invalid option specified for Oracle Grid Infrastructure Wizard.
-
Cause: The Oracle Grid Infrastructure Wizard only supports Configuring Oracle Grid Infrastructure for a cluster or Upgrading an existing Grid Infrastructure.
- INS-42024: Installer has detected that the group configured for string privilege in the current home does not match with the group name retrieved (string) from the home where earlier version of Oracle Clusterware is configured presently.
-
Cause: n/a
- INS-42025: Grid Infrastructure Home is not suitable to be configured on this cluster
-
Cause: The Grid Infrastructure Home is registered with the local user. Confinguration cannot continue.
- INS-42099: Oracle Service username is not specified.
-
Cause: For Management Database option its mandatory to specify Oracle Service username.
- INS-43001: Cluster type not specified
-
Cause: Either cluster type is not specified or invalid value is specified
- INS-43002: Big Cluster cannot be configured on this host.
-
Cause: Installer has detected 9i Oracle Real Application Cluster Database on this host. Flex Cluster cannot be configured on a host that has 9i Oracle RAC database configured on it.
- INS-43003: Big Cluster cannot be configured on this host.
-
Cause: Installer has detected operating system provided clustering software on this host. Flex Cluster cannot be configured on a host that is managed by operating system provided clustering software.
- INS-43004: Big Cluster cannot be configured on this host.
-
Cause: Installer has detected Oracle Clusterware on this host. Flex Cluster cannot be configured on a host that already has Oracle Clusterware installed.
- INS-43021: All the nodes (string) are down in the last batch.
-
Cause: Installer has detected that all the nodes specified in the last batch are down. There sould be atleast one node up and running to complete the Grid Infrastructure upgrade.
- INS-43022: You have selected to execute the root script manually. If some of the nodes are not reachable at the time of upgrade root script execution and if you would want to complete the Grid Infrastructure upgrade on the reachable nodes, you may be required to rerun the string with -force flag from the last node after you have completed the execution of this script on all the reachable nodes.The remaining unreachable nodes can be upgraded later, following the manual steps as detailed in the documentation.
-
Cause: n/a
- INS-43023: Specified sudo user name ('string') cant be used to execute configuration script(s).
-
Cause: Only current installation user name is allowed to execute configuration script(s) using sudo option.
- INS-43024: n/a
-
Cause: n/a
- INS-43025: Installer has detected that there are nodes of different role in batch(string).
-
Cause: n/a
- INS-43026: Installer has detected that batch(string) contains LEAF nodes and batch(string) contains HUB nodes.
-
Cause: n/a
- INS-43041: CLUSTER_NEW_VIRTUAL_HOSTNAMES parameter was not specified.
-
Cause: The CLUSTER_NEW_VIRTUAL_HOSTNAMES parameter was not provided for performing addnode operation.
- INS-43042: The cluster nodes string specified for addnode is already part of a cluster.
-
Cause: Cluster nodes specified already has clusterware configured.
- INS-43043: Parameters specified for addnode operation are missing details for nodes.
-
Cause: Some of the parameters passed for addnode operation have incomplete details of the node to be added.
- INS-43044: Addnode operation cannot be performed from a Leaf node.
-
Cause: Leaf node cannot be local node while performing addnode operation.
- INS-43045: string parameter was not specified.
-
Cause: The string parameter was not provided for performing addnode operation.
- INS-43046: The Oracle home location contains directories or files on following remote nodes:string.
-
Cause: n/a
- INS-43047: Clusterware configured in Auto mode cannot have nodes of type HUB or LEAF.
-
Cause: n/a
- INS-43048: An Auto node cannot be added to a cluster having only Hub and Leaf nodes.
-
Cause: n/a
- INS-43049: Hub nodes cannot be added to the cluster as it is already having string Hub nodes which is the maximum number of Hub nodes for a big cluster.
-
Cause: n/a
- INS-43050: Installer has detected that the clusterware configured on the system is not running from the grid home on which addnode is being performed.
-
Cause: n/a
- INS-43051: Virtual Hostname was not specified for performing addnode operation.
-
Cause: n/a
- INS-43052: The Oracle home location contains directories or files on following remote nodes:string.
-
Cause: n/a
- INS-43066: The installer has detected that Oracle Clusterware is not running on the following nodes: string. Ignore the warning if any policy managed databases software are not extended to new nodes yet.
-
Cause: Either there was an error in starting the Oracle Clusterware stack on the specified nodes, or the root scripts on the specified nodes were not run.
- INS-43080: Some of the configuration assistants failed, were cancelled or skipped.
-
Cause: n/a
- INS-43100: Insufficient space available in the ASM diskgroup string.
-
Cause: n/a
- INS-43101: Insufficient space available in shared file system for Oracle Cluster Registry (OCR) Location string.
-
Cause: n/a
- INS-43102: You cannot upgrade Oracle Grid Infrastructure as Built-In Account.
-
Cause: The installer has detected that the Oracle Home user of the active Oracle Grid Infrastructure home is (string). Oracle GI cannot be upgraded using Built-In Account for the current installation.
- INS-43103: Oracle Grid Infrastructure Home is not suitable for upgrade.
-
Cause: The wizard has detected that the Oracle Home user of the active Oracle Grid Infrastructure home is string, whereas the Oracle Home user of the current home is Built-In Account.
- INS-43104: If you intend to use this Oracle Grid Infrastructure home to upgrade the active instance of Oracle Grid Infrastructure, then the specified user is invalid.
-
Cause: The installer has detected that the specified Oracle Home user does not match the Oracle Home user of the active Oracle Grid Infrastructure home(string).
- INS-43105: Specified Oracle Home User (string) is invalid.
-
Cause: The installer has detected that the specified Oracle Home user does not match the Oracle Home user of the active Oracle Grid Infrastructure home (string).
- INS-43106: Oracle Grid Infrastructure Home is not suitable for upgrade
-
Cause: The wizard has detected that the Oracle Home user of this home (string)does not match the Oracle Home user of the active Oracle Grid Infrastructure home (string).
- INS-43110: Empty value provided for OMS Host.
-
Cause: n/a
- INS-43111: Empty value provided for Enterprise Manager Admin password.
-
Cause: n/a
- INS-43112: Empty value provided for Enterprise Manager Admin user.
-
Cause: n/a
- INS-43113: Empty value provided for OMS Port.
-
Cause: n/a
- INS-43114: Unable to connect to Enterprise Manager Cloud Control.
-
Cause: Invalid connection information specified.