120 INS-40001 to INS-45000

INS-40102: Specified grid Oracle home is invalid: Cause: The grid installation for a cluster Oracle home was placed in the installation users home directory; Action: Oracle recommends that the grid Oracle home is not placed 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 Grid Infrastructure software for a Cluster is not supported on OCFS2 partition.; Action: If you intend to configure Grid infrastructure software for a Cluster, specify a 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 Grid Infrastructure software for a Cluster is not supported on OCFS2 partition.; Action: If you intend to configure Grid infrastructure software for a Cluster, specify a location that is not an OCFS2 partition.

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.; 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 grid software on the system.: Cause: You have chosen to install and configure a new instance of grid software (Oracle Clusterware and ASM). However, only one configured instance of the software is allowed on the system at a time; Action: You must deconfigure the existing Grid Infrastructure software before installing and configuring a new instance of the software.

INS-40405: The installer has detected a configured instance of grid software on the system.: Cause: You have chosen to install and configure a new instance of Grid Infrastructure software. However, only one configured instance of the software is allowed on the system at a time.; Action: You must deconfigure the existing grid software before installing and configuring a new instance of the software.

INS-40406: There is no previous version of grid software detected on the system.: Cause: The installer was not able to detect any existing Oracle Clusterware or ASM installation to upgrade.; Action: You can choose to install a new grid installation (Oracle Clusterware and ASM), and add it to an existing cluster, or you can 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 add node procedure. If you want to create a new cluster, then select the option for a new installation.

INS-40407: The installer has detected that an ASM instance is already configured on the computer.: Cause: You can have only one ASM instance configured on the node.; Action: You can select a Software only installation of Grid Infrastructure into a new home, and configure the new ASM installation later.

INS-40409: The installer has detected local Cluster Synchronization Services (CSS) configured on this host. Local CSS is running from: string.: Cause: You have chosen to install and configure a new instance of Grid Infrastructure software. However, the CSS daemon running on this host conflicts with the software.; Action: Before you install, you must deconfigure and delete the existing local CSS daemon and restart the installer.

INS-40410: The installer has detected a configured instance of grid software on the system.: Cause: You have chosen to install and configure a new instance of grid software (Oracle Clusterware and ASM). However, only one configured instance of the software is allowed on the system at a time. Action: You must deconfigure the existing grid software before installing and configuring a new instance of the software.; Action: You must deconfigure the existing Grid Infrastructure software before installing and configuring a new instance of the software.

INS-40412: This system does not satisfy the network requirements to install and configure this product.: 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.

INS-40413: Existing ASM instance detected.: Cause: The installer has detected that an earlier version of ASM is configured on the system.; Action: If you intend to upgrade the ASM instance as part of this installation session, then you must shut down the ASM instance before proceeding. Oracle recommends that you shut down database instances using ASM before shutting down the 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.

INS-40415: Upgrade the database instances that use Automatic Storage Management (ASM).: Cause: Installer has detected presence of database instances running software version string.; Action: If you intend to upgrade ASM instance as part of this upgrade, it is recommended that software version of database instances that use ASM must be upgraded to string or higher before proceeding with the install.

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: Grid Infrastructure release string or above is needed to upgrade Grid Infrastructure.; Action: Install the patchset to upgrade the configured instance of Grid Infrastructure to version string or higher.

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.

INS-40602: Baseboard Management Controller (BMC) user name text field cannot be left blank.: 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.

INS-40603: Invalid characters in User Name.: 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(_).

INS-40604: Password field is blank.: Cause: The password field was left blank.; Action: Enter a password.

INS-40701: Invalid characters in Grid Naming Service (GNS) subdomain.: 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(.).

INS-40702: GNS subdomain is blank.: Cause: The Grid Naming Service (GNS) subdomain was blank.; Action: Provide a value for GNS subdomain.

INS-40704: GNS subdomain cannot be resolved.: Cause: The GNS subdomain could not be resolved using TCP/IP host name lookup.; Action: Specify a subdomain that can be resolved.

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.; 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(.).

INS-40706: Grid Naming Service (GNS) Virtual IP Address is blank.: Cause: The GNS virtual IP address was blank.; Action: Provide a valid value for the GNS virtual IP address.

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.; Action: Specify a valid GNS virtual IP address.

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).; Action: Enter a virtual host name for GNS in the cluster that is not currently in use, or provide a GNS VIP in numeric format.

INS-40709: Cluster name: string contains invalid characters.: 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(-).

INS-40710: Cluster name:string does not start with a letter.: Cause: The cluster name did not start with a letter.; Action: Provide a value for the cluster name that starts with a letter

INS-40711: Cluster Name is blank.: Cause: The Cluster name text field was blank.; Action: Provide a valid value for the cluster name.

INS-40712: Cluster Name:string is too long.: Cause: The specified cluster name was too long.; Action: Provide a cluster name that is 15 or fewer characters in length.

INS-40713: SCAN Name and cluster name,string is too long. SCAN Name is also used for setting cluster name in this installation type.: Cause: The specified SCAN name, which also serves as cluster name in typical installation type, is more than 15 characters long.; Action: Because in typical installation SCAN Name is also used for setting cluster name, you need to provide a SCAN name that complies with cluster name maximum length. Cluster name must be 15 or fewer characters in length.

INS-40714: Single Client Access Name (SCAN) Name: string contains invalid characters.: Cause: The specified SCAN name contained one or more invalid characters.; Action: Enter a valid value for SCAN name. Valid characters can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), hyphen(-), and period(.).

INS-40715: Single Client Access Name (SCAN) Name: string contains invalid characters.: Cause: The specified SCAN name contained one or more invalid characters. For typical installation this also includes invalid characters for Cluster name since it is set to be the same as SCAN name.; Action: Enter a valid value for SCAN name and also for cluster name. Valid characters can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen(-).

INS-40716: Single Client Access Name (SCAN) Name:string does not start with a letter.: Cause: The SCAN name did not start with an alphabetic character.; Action: Provide a value for SCAN name that starts with an alphabetic character.

INS-40717: Single Client Access Name (SCAN) name is blank.: Cause: The SCAN name was blank.; Action: Provide a valid value for the SCAN name.

INS-40718: Single Client Access Name (SCAN) name:string could not be resolved.: Cause: The SCAN name could not be resolved using TCP/IP host name lookup.; Action: Specify a SCAN name 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 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.

INS-40720: Single Client Access Name (SCAN) name:string is not associated with any IP address.: Cause: The configured SCAN name was not associated with any IP address.; Action: Ensure the SCAN names you provide are associated with IP addresses.

INS-40721: Single Client Access Name (SCAN) port is blank.: Cause: The SCAN port text field was empty.; Action: Provide a valid value for SCAN port.

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.; Action: Enter a valid numeric value for the SCAN port.

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.; Action: Enter a SCAN port number between 1024 and 65535.

INS-40724: No locally defined network interface matches the SCAN VIP subnet.: Cause: None of the locally defined network interfaces has a subnet matching the SCAN VIP subnet.; Action: Define a public interface with a subnet matching the SCAN VIP or choose a SCAN VIP with a subnet matching the public interface.

INS-40725: Unable to determine the existence of an interface with a subnet matching the SCAN VIP subnet.: Cause: A failure has occurred during the determination of the existence of an interface with a subnet matching the SCAN VIP subnet.; Action: Be sure there is a public interface with a subnet matching the SCAN VIP or choose a SCAN VIP with a subnet matching the public interface.

INS-40726: Single Client Access Name (SCAN) name:string is not in the GNS subdomain string.: Cause: The SCAN name is not in the GNS subdomain.; Action: Ensure the SCAN name you provide is in the same domain as GNS subdomain.

INS-40727: Single Client Access Name (SCAN) name:string is associated with an IP address.: Cause: The configured SCAN name is associated with an IP address.; Action: Ensure the SCAN names you provide is not associated with any IP address if GNS configuration is required.

INS-40901: The cluster node information table is blank.: Cause: The cluster node information table is blank.; Action: Provide valid data in the cluster node information table.

INS-40902: Missing entries in the node Information table.: Cause: Some fields were left blank in the node Information table.; Action: Ensure that all information in the table is filled in.

INS-40903: Host name contains invalid characters.: Cause: The value entered for host name contains one or more invalid characters.; Action: Ensure host name contains valid characters. Valid characters for host name can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen (-).

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.; Action: Provide a valid host name for ORACLE_HOSTNAME, and restart the installer.

INS-40905: Unresolved host IP addresses.: Cause: One or more IP addresses do not resolve to valid host names.; Action: Enter a valid IP address that resolves to a host name to continue.

INS-40906: Duplicate host names 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 the duplicates 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.; Action: Include the local node in the list of host names for grid installation.

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.; Action: Enter valid host names.

INS-40909: Host names from multiple domains entered.: Cause: Node information was entered for two or more nodes that belonged to different domains.; Action: Enter host names belonging to the same domain.

INS-40910: Virtual IP: string entered is invalid.: Cause: The Virtual IP did not resolve to an IP address.; Action: Enter a valid VIP that resolves to an IP address.

INS-40911: Not all public nodes appear to be reachable.: Cause: Some public nodes were either down or belonged to a different subnet.; Action: Check that nodes in the list are up and reachable, and that they are all on the same 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.; 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.

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.; Action: If necessary, refer to the installation guide for information about how to set up user equivalence manually on cluster nodes.

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.; 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 10g on the remote node string.: Cause: Oracle Clusterware 10g is present on remote node string, but not on the local node.; Action: To upgrade the Oracle Clusterware 10g installation to this release, run the installer on a node where the Oracle Clusterware 10g installation is located. To create a new cluster, choose a set of nodes that are not part of an existing cluster.

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; Action: Before proceeding with the installation, you must deconfigure CSS, shut down any Automatic Storage Management (ASM) instances, and shut down all databases that use ASM for storage on all of the nodes previously listed. This installation brings up a clusterwide version of CSS after installation is complete. At that point, you may start up any databases and ASM instances that previously used CSS. When they are brought back up, they will use the clusterwide CSS version.

INS-40917: Host name cannot be in IP Address format.: Cause: Host name cannot be in IP address format.; Action: Provide the host name for host name.

INS-40918: Virtual IP name: string cannot be in IP Address format.: Cause: Virtual IP name cannot be in IP address format.; Action: Provide a valid virtual IP name.

INS-40919: Host name cannot be left blank.: Cause: The host name field is blank.; Action: Ensure to enter a valid host name.

INS-40920: Virtual IP name cannot be left blank.: Cause: The virtual IP name field is blank.; Action: Enter a valid virtual IP name.

INS-40921: Virtual IP name contains invalid characters.: Cause: The value you have entered for virtual IP name contains one or more invalid characters.; Action: Ensure virtual IP name 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(-).

INS-40922: Invalid SCAN Name - unresolvable to IP address.: Cause: Unable to resolve SCAN Name to an IP Address; Action: Be sure the SCAN Name is valid and resolvable to an IP Address.

INS-40923: Unable to match local interface or subnet against SCAN VIP.: Cause: No locally defined network interface was found with matching subnet to SCAN VIP.; Action: Ensure the SCAN VIP subnet matches an existing local network interface subnet.

INS-40924: Failure while initializing search for common interface or subnets across cluster nodes.: Cause: Unable to initialize search for common interfaces or subnets across cluster nodes.; Action: Ensure the local host has valid network interfaces with valid subnets defined.

INS-40925: One or more nodes have interfaces not configured with a subnet that is common across all cluster nodes.: Cause: Not all nodes have network interfaces that are configured on subnets that are common to all nodes in the cluster.; Action: Ensure all cluster nodes have a public interface defined with the same subnet accessible by all nodes in the cluster.

INS-40926: Cluster node interfaces are configured in subnets different from the SCAN VIP subnet.: Cause: One or more nodes have interfaces configured with subnets that are different than the SCAN VIP subnet.; Action: Ensure all nodes have a public interface configured with a subnet matching the SCAN VIP subnet.

INS-40927: Interfaces with common subnets that have different names on different nodes.: Cause: The following nodes have interfaces in common subnets, but their interface names are different: string; Action: Be sure the names of interfaces defined on common subnets also match across the cluster nodes.

INS-40928: An unknown error was encountered while validating across nodes.: Cause: An unknown error occurred during validation of interfaces or of subnet matching across cluster 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) process is 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.

INS-40930: The following nodes were not resolvable during host IP address lookup: string.: Cause: Unknown host exception thrown during node VIP validation.; Action: Be sure all node VIPs are resolvable to a valid IP address.

INS-40931: The following nodes do not have interfaces configured on a subnet matching the SCAN VIP subnet: string.: Cause: Some node VIPs are on subnets not matching the SCAN VIP subnet.; Action: Be sure all node VIPs are on subnets matching the SCAN VIP subnet.

INS-40932: An unknown error has occurred while validating Node Virtual IPs: string: Cause: Unknown errors were encountered while validating Node VIPS.; Action: Ensure all node VIPs resolve to a valid IP address.

INS-40933: Interface collection failed on node string.: Cause: Interface information collection failed.; Action: Be sure all nodes are accessible and have valid network interfaces defined.

INS-40934: A remote directory operation failed on node string: Message: string: Cause: A remote directory operation failed.; Action: Be sure all nodes are accessible across the network.

INS-40935: A cluster operation (copy file, file exists, etc) failed on node string: Message: string: Cause: A cluster operation (copy file, file exists, etc) failed.; Action: Be sure all nodes are accessible across the network.

INS-40936: A command tool operation failed on node string: Message: string: Cause: A cluster operation (for example, list interfaces) failed.; Action: Ensure that all cluster member nodes are accessible on the network.

INS-40937: Following hostnames are not valid:string: Cause: Hostname specified may be an alias.; Action: Ensure that valid hostname is specified.

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.; Action: Enter the correct interface information before proceeding

INS-41102: No public interface designated.: Cause: None of the network interfaces were designated as public.; Action: Designate at least one interface as a public interface.

INS-41103: Interface string has multiple subnets associated with it.: Cause: Interface string has been marked as both Public and Private.; Action: Be sure that interface string is marked either as Public or Private, not both.

INS-41104: Multiple interfaces present with no Private Interface designated.: Cause: There are multiple interfaces available, but none marked as Private.; Action: Be sure there is at least one interface designated 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.; Action: Be sure that the chosen public interface is on a subnet which matches the SCAN VIP subnet and is common across all cluster nodes.

INS-41106: Invalid choice for public/private interface.: Cause: The chosen public or private interface is not on a subnet common across nodes.; Action: Be sure that the chosen public or private interface is on a subnet which is common across all cluster nodes.

INS-41107: string selected for one or more of the public or private interfaces is not on a shared subnet. Nodes not defining are: string: Cause: The chosen public or private interface is not on a subnet present across nodes.; Action: Ensure that all public interfaces share the same subnet, and ensure that all private interfaces share the same subnet.

INS-41204: No shared partition are available between nodes.: Cause: The specified nodes did not have at least one shared partition.; Action: Provide nodes that have at least one shared partition before proceeding with the installation.

INS-41302: Normal redundancy requires three locations for the Oracle Cluster Registry.: Cause: Fewer than three locations were provided for the Oracle Cluster Registry.; Action: Specify three locations 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.; Action: Specify a location for the Oracle Cluster Registry.

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.; Action: Provide an OCR location that uses valid characters in the path.

INS-41306: Invalid Oracle Cluster Registry (OCR) Locations.: Cause: One or more Oracle Cluster Registry (OCR) locations are not valid.; Action: Provide valid OCR locations.

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.; Action: Enter a shared file system that has at least string MBs of free space.

INS-41309: The specified Oracle Cluster Registry (OCR) location cannot be a block or character device, or placed inside either device.: Cause: The specified Oracle Cluster Registry (OCR) location is a block or character device, or is placed inside either device.; Action: Select one of the following alternative locations: ASM (Automatic Storage Management), an OCFS partition, or an NFS shared partition.

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.; Action: Select separate partitions for each Oracle Clusterware Registry location.

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.; Action: Specify locations for Oracle Cluster Registry that are not in use.

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.; Action: Specify a location for Oracle Cluster Registry locations where the installation owner and oraInventory group members have read and write permissions

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.; Action: Specify a unique location for each Oracle Cluster Registry location.

INS-41314: File string already exists. The installer will make an attempt to replace this file.: Cause: The specified OCR file already exists.; Action: You may choose a different location or let the installer replace this file. Replacing it will overwrite its current contents.

INS-41315: File string already exists.: Cause: The specified OCR file already exists.; Action: Ensure that the OCR file you have specify is a nonexistent file.

INS-41316: Unable to delete file string: Cause: The attempt to delete the file was not successful.; Action: Ensure that the proper permissions have been granted to the current user to replace the file.

INS-41317: Invalid Oracle Cluster Registry (OCR) locations.: Cause: One or more Oracle Cluster Registry (OCR) locations were not valid.; Action: Provide valid OCR locations.

INS-41318: File(s) string already exist(s). The installer will make an attempt to replace existing file(s).: Cause: The specified file(s) already exist(s).; Action: You may choose a different location or let the installer clear and reuse this location and replace the existing file(s). Cleaning it will overwrite its current contents.

INS-41319: File(s) string already exist(s).: Cause: The specified shared location is in use.; Action: Ensure that the shared location you have specify is a not already being used or has been cleaned.

INS-41320: Unable to delete file(s) string: Cause: The attempt to delete the file(s) was not successful.; Action: Ensure that the proper permissions have been granted to the current user to replace the file(s).

INS-41502: Insufficient number of voting disk locations provided for normal redundancy configuration.: Cause: Insufficient number of voting disk locations were provided. For normal redundancy configuration, you must specify three locations for the voting disk.; Action: Specify three locations for the voting disk for normal redundancy configuration.

INS-41503: Voting disk locations provided for external redundancy configuration.: Cause: Voting disk location was not specified. For external redundancy configuration, you must specify a location for the voting disk.; Action: Specify one voting disk location for external redundancy configuration.

INS-41505: The voting disk locations contain one or more bad characters.: Cause: The voting disk locations contained one or more illegal characters, such as the following: !@%^&*()+=?`~[{]};:\",<>?. .; Action: Specify a voting disk location path that does not contain illegal characters.

INS-41506: One or more voting disk locations are not valid.: Cause: One or more voting disk locations were not an existing directory.; Action: Provide a valid voting disk location.

INS-41508: More than one voting disk location is on the same partition.: Cause: More than one voting disk location was on the same partition. Each voting disk location must be on a different partition for normal redundancy configuration.; Action: Specify three locations on separate partitions for voting disks.

INS-41509: Duplicate entries found in one or more voting disk locations.: Cause: One or more voting disk locations you provided are duplicate. Each voting disk location must be unique.; Action: Specify a unique location for each voting disk.

INS-41510: One or more voting disk locations is the same as an OCR location.: Cause: One or more voting disk locations you provided are the same as an OCR location. Voting disk locations cannot be the same as Oracle Cluster Registry (OCR) locations.; Action: Specify unique voting disk locations different from Oracle Cluster Registry (OCR) locations.

INS-41511: One or more locations specified for placing voting disks is the same as an Oracle 9i quorum location.: Cause: One or more locations you provided for voting disks is where an existing Oracle9i quorum disk is located.; Action: Provide new locations for voting disks. You cannot reuse an Oracle9i quorum disk location.

INS-41512: The specified voting disk location cannot be a block or character device, or placed inside either device.: Cause: The specified voting disk location is a block or character device, or is placed inside either device.; Action: Select one of the following alternative locations: ASM (Automatic Storage Management), an OCFS partition, or an NFS shared partition.

INS-41513: Voting disk location specified cannot be in a directory with an existing voting disk: Cause: One or more locations for voting disks that you provided were where an existing voting disk is located.; Action: Specify a new voting disk location.

INS-41514: One or more locations specified for placing voting disks cannot be used.: Cause: One or more voting disk locations specified did not have proper permission or ownership for the installation to proceed.; Action: Specify voting disk locations where the installation owner and oraInventory group members have read and write privileges.

INS-41515: Insufficient space in shared file system for voting disk.: Cause: Insufficient space was available in the storage location for a voting disk. Voting disks require a minimum of string MB of free space.; Action: Enter a shared storage location that has at least 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.; Action: You may choose a different location or let the installer replace this file. Replacing it will overwrite its current contents.

INS-41517: File string already exists.: Cause: The specified voting disk file already exists.; Action: Ensure that the voting disk file you have specify is a nonexistent file.

INS-41518: Unable to delete file string: Cause: The attempt to delete the file was not successful.; Action: Ensure that the proper permissions have been granted to the current user to replace the file.

INS-41519: One or more voting disk locations are not valid.: Cause: One or more voting disk locations provided might not be shared across nodes.; Action: Provide a voting disk location that is in an existing directory.

INS-41701: Unable to acquire node list information from inventory.: Cause: The Oracle Clusterware node list could not be acquired from the inventory.; Action: Ensure that the inventory is not corrupted, and that the inventory path is correct.

INS-41702: No nodes selected for upgrade.: Cause: Node selection was blank.; Action: Select a list of nodes to upgrade with the local node.

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.; Action: Select the local node (the node from which you are running the installer) as one of the nodes to upgrade.

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.; Action: Select nodes from the same cluster, or exclude the following nodes:string

INS-41705: One or more nodes that are part of the cluster are down.: Cause: One or more nodes that are part of the cluster cannot be reached; Action: Ensure that all the nodes selected that are part of the cluster are up.

INS-41706: Only subset of nodes selected for upgrade.: Cause: You have chosen a subset of the cluster nodes for the upgrade.; Action: As part of the install the software will be copied to all nodes of the cluster. In the end, you will be prompted to run the root script only on selected nodes. In order to complete the upgrade, you need to run the root script on the remaining nodes. You dont have to invoke the installer again on any of the remote nodes to complete the upgrade.

INS-41802: Unable to determine the version of Automatic Storage Management (ASM) running from home string.: Cause: An Automatic Storage Management (ASM) home was found, but the ASM instance was not up. The Installer was unable to determine the product version by using the ASM home information.; Action: Ensure that the Automatic Storage Management instance installed in home string is up and then retry the installation.

INS-41803: An entry for Automatic Storage Management (ASM) is found in the system registry or oratab, but it does not have a home.: Cause: An ASM entry was listed in the system registry or oratab, but ASM home string was missing.; Action: Ensure that either the oratab or the system registry is correct, or that the inventory is not corrupted.

INS-41804: An older version of Automatic Storage Management (ASM) instance is already running.: Cause: There is an ASM instance already running on the server.; Action: Upgrade the existing ASM instance to the current version.

INS-41806: Virtual IP address cannot be same as Single Client Access Name (SCAN) name: string: Cause: The Virtual IP address was the same as the SCAN name.; Action: Enter a Virtual IP address that is different than the address for the SCAN names.

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.; Action: Run the root scripts on the nodes listed. If root scripts have already been run on these nodes, then examine the log file string on each failed node to determine the reason for the Oracle Clusterware stack not starting

INS-41808: Possible invalid choice for OSASM Group.: Cause: The chosen OSASM Group is among those generally used for other ASM or DB user privileges, ie. asmdba, asmoper, dba, or oper.; Action: Oracle recommends that the OSASM group be asmadmin, if possible.

INS-41809: Possible invalid choice for OSDBA Group.: Cause: The chosen OSDBA Group is generally used for DB related privileges.; Action: Oracle recommends that the OSDBA group be asmdba, if possible.

INS-41810: Possible invalid choice for OSOPER Group.: Cause: The chosen OSOPER Group is generally used for DB related privileges.; Action: Oracle recommends that the OSOPER group be asmoper, if possible.

INS-41811: OSDBA and OSOPER are the same OS group.: Cause: The chosen OSDBA and OSOPER groups are the same.; Action: Oracle recommends that the OSDBA and the OSOPER groups be different.

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.; Action: Choose different group names such that OSASM does not match OSDBA or OSOPER.

INS-41813: OSDBA, OSOPER and OSASM are the same OS group.: Cause: The chosen value for OSDBA group and OSOPER group and the chosen value for OSASM group are the same.; Action: Choose different group names such that OSASM does not match OSDBA or OSOPER.

INS-41814: The installer has detected that some of the services of Grid Infrastructure are not running on this system.: Cause: There may have been an error in starting the Grid Infrastructure services, or you neglected to invoke the root scripts on this system.; Action: Ensure that you invoke the root scripts on this machine. If root scripts have already been executed the log file string can be examined to determine the reason for failure if any.

INS-41871: User is not a member of the following chosen OS groups: string: Cause: User is not a member of one or more of the chosen OS groups.; Action: Please choose OS groups of which user is a member.

INS-41901: The typical Grid Infrastructure installation cannot be performed on this system.: Cause: The installer has detected the existence of vendor-specific clusterware. The typical Grid infrastructure installation is a simplified configuration that is not designed to co-exist with non-Oracle clusterware.; Action: Select the advanced installation of Grid infrastructure, which will allow you to specify configuration information required to co-exist with vendor-specific clusterware.

INS-41902: The typical Grid Infrastructure installation cannot be performed on this system.: Cause: The installer has detected the existence of Oracle RAC version 9.x configured on this host. The typical Grid infrastructure installation is a simplified configuration that is not designed to co-exist with older versions of Oracle RAC.; Action: Select the advanced installation of Grid infrastructure, which will allow you to specify configuration information required to co-exist with Oracle RAC version 9.x.

INS-42001: The same drive letter string cannot be assigned to more than one partition: Cause: The same drive letter string cannot be assigned to more than one partition; Action: Provide different drive letters to each partition.

INS-42002: The specified partition cannot be used.: Cause: The specified partition was selected for storing the software binaries.; Action: Instead, choose a location that is formatted for storing data files.

INS-42003: No partitions selected: Cause: No partitions were selected or partition details provided were incomplete.; Action: Specify one or more partitions and provide the complete partition details by selecting partition, format option and drive letter to be assigned for each.

INS-42004: No free drive letters available: Cause: The local machine did not have any free drive letters to be assigned to new partitions.; Action: Make drive letters available on the server, and then restart the installer.

INS-42011: The operating system group specified for oraInventory group is invalid.: Cause: Only the primary operating system group of user can be specified for oraInventory group.; Action: Specify the primary operating system group of user for oraInventory group.