Oracle Installer Error Codes

Cause: The string password should not be empty.

Action: Provide a non-empty password.

Cause: The string password and string confirm password should be the same.

Action: Ensure that string password and string confirm password are the same.

Cause: The string password length cannot exceed string characters.

Action: Provide a password lesser than string characters.

Cause: Passwords may contain only alphanumeric characters from the chosen database character set, underscore (_), dollar sign ($), or pound sign (#).

Action: Provide a password as per recommendations.

Cause: The string password entered is missing recommended characters. Oracle recommends that passwords contain at least one string .

Action: Provide a password which contains at least one string .

Cause: Oracle recommends that the string password entered should be at least string characters in length.

Action: Provide a password which is at least string characters in length.

Cause: Unexpected error occurred while trying to get the raw device partition size.

Action: Refer to the logs for more details.

Cause: Unexpected error occurred while trying to get the FS device partition size.

Action: Refer to the logs for more details.

Cause: Unable to get the FS partition free space size

Action: Unable to get the FS partition free space size

Cause: Unexpected error occurred while trying to get the file system type.

Action: Refer to the logs for more details.

Cause: Oracle recommends that the password entered should be at least string characters in length, contain at least 1 uppercase character, 1 lower case character and 1 digit [0-9].

Action: Provide a password that conforms to the Oracle recommended standards.

Cause: Unexpected error occurred while trying to check whether the partition is raw.

Action: Refer to the logs for more details.

Cause: The location specified might not have the required permissions.

Action: Provide a location which has the appropriate required permissions.

Cause: Unexpected error occurred during setting permission.

Action: Refer to the logs for more details.

Cause: Unable to lock or read the install inventory.

Action: Check the permissions on the inventory location.

Cause: Install inventory does not exist.

Action: Ensure that the install inventory exists.

Cause: Error occurred while retrieving the oracle home locations.

Action: Check if the existing inventory location is accessible.

Cause: Unexpected error occurred while trying to get the default oradata location.

Action: Refer to the logs for more details.

Cause: Unexpected error occurred while trying to get RAC databases info.

Action: Refer to the logs for more details.

Cause: Unexpected error occurred while trying to get SIDs and DB Homes on remote nodes.

Action: Refer to the logs for more details.

Cause: Unexpected error occurred while trying to get SIDs and DB Homes on node string .

Action: Refer to the logs for more details.

Cause: IO Exception occurred.

Action: Refer to the logs for more details.

Cause: Installer has detected Grid Infrastructure home (string ) registered in the Inventory. But the home location does not exist or is empty.

Action: Check if the location specified is a valid Grid Infrastructure home. If not unregister the home from inventory using deinstall procedures.

Cause: Refer to the logs for more details.

Action: Refer to the logs for more details.

Cause: Refer to the logs for more details.

Action: Refer to the logs for more details.

Cause: Refer to the logs for more details.

Action: Refer to the logs for more details.

Cause: Refer to the logs for more details.

Action: Refer to the logs for more details.

Cause: The content of cluster configuration file do not conform to the format recommended.

Action: Ensure that the contents of the cluster configuration file conform to the expected format.

Cause: Unexpected error while reading the given cluster configuration file.

Action: Ensure that the given cluster configuration file exists and has the read permissions.

Cause: User equivalence may not be setup between the local node and the remote nodes or sufficient file permissions are not set.

Action: Setup user equivalence or ensure sufficient file permissions are set.

Cause: Unexpected error occurred while trying to check free disk space across nodes.

Action: Refer to the logs or contact Oracle Support Services. Note for advanced users: Launch the installer by passing the following flag '-ignoreInternalDriverError'.

Cause: Unexpected error occurred while trying to get shared partitions across nodes.

Action: Refer to the logs or contact Oracle Support Services. Note for advanced users: Launch the installer by passing the following flag '-ignoreInternalDriverError'.

Cause: Unexpected error while detecting file system type across nodes.

Action: Refer to the logs or contact Oracle Support Services.

Cause: Unexpected error occurred while trying to check for group existence.

Action: Refer to the logs or contact Oracle Support Services. Note for advanced users: Launch the installer by passing the following flag '-ignoreInternalDriverError'.

Cause: Software is already running from the home selected for the install.

Action: Shutdown the following processes before continuing: string

Cause: A runtime error

Action: Refer to the logs or contact Oracle Support Services.

Cause: Files that need to be reinstalled or upgraded in this home are currently in use by running services.

Action: Please stop the following services before continuing: string

Cause: Files that need to be reinstalled or upgraded in this home are currently in use by one or more applications.

Action: Please close any running applications before continuing.

Cause: n/a

Action: n/a

Cause: n/a

Action: n/a

Cause: Unexpected error while checking connectivity of nodes through the interface.

Action: Refer to the logs or contact Oracle Support Services.

Cause: Specified location is on a volume without enough disk space on nodes: string .

Action: Choose a location that has enough space (minimum of string MB) or free up space on the existing volume.

Cause: Unexpected error occurred while trying to perform status check on existing Oracle Clusterware.

Action: Refer to the logs or contact Oracle Support Services. Note for advanced users: Launch the installer by passing the following flag '-ignoreInternalDriverError'.

Cause: n/a

Action: n/a

Cause: Prior to configuring a database to use Automatic Storage Management (ASM), you must install and configure Grid Infrastructure, which includes ASM software.

Action: Grid Infrastructure can be installed from the separate installation media included in your media pack. Alternatively, it can be downloaded separately from Electronic Product Delivery (EPD) or the Oracle Technology Network (OTN). This is typically installed as a separate operating system user than the Oracle database and may have been installed by your system administrator. See the installation guide for more details.

Cause: There were no disk groups managed by the ASM instance string .

Action: Use Automatic Storage Management Configuration Assistant to add disk groups.

Cause: There was no disk groups named string managed by ASM instance string

Action: Enter a valid existing ASM disk group or use Automatic Storage Management Configuration Assistant to add the desired ASM disk group.

Cause: ASM disk group name was not entered in the text field.

Action: Enter a valid ASM disk group name.

Cause: A disk group name specified was invalid. It must start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters $ ,# and _.

Action: Enter a valid disk group name containing only alphanumeric characters and possibly a few special characters allowed by your platform.

Cause: Redundancy level was invalid.

Action: Choose and complete a valid redundancy level: Normal or External.

Cause: No disks were selected from a managed ASM disk group.

Action: Select appropriate number of disks from a managed ASM disk group.

Cause: The disks string were not valid.

Action: Please choose or enter valid ASM disks.

Cause: Insufficient space available in the selected disk group. At least, string MB of space is required.

Action: Use Automatic Storage Management Configuration Assistant to add more disks to the selected disk group or create a new disk group with as least string MB of space.

Cause: The number of disks selected were insufficient for the selected redundancy level.

Action: For a disk group with redundancy level 'string ', at least 'string ' disks are recommended.

Cause: Automatic Storage Management (ASM) string instance is found.

Action: Upgrade the existing ASM instance to version string .

Cause: Prior to configuring a cluster database to use Automatic Storage Management (ASM), you must configure ASM software in the Grid Infrastructure home.

Action: Grid Infrastructure installation on this cluster was only configured to run Oracle Clusterware. You will need to go back to the Grid Infrastructure home and configure ASM for storing database. Grid Infrastructure is typically installed as a separate operating system user than the Oracle database and may have been installed by your system administrator. See the installation guide for more details.

Cause: The following nodes did not have an ASM instance running on them.
Node list: string

Action: Before creating a database that uses ASM on all of the nodes chosen for this installation, you should extend the ASM cluster of instances using the Add Instance procedure to the desired set of nodes.
Node list: string

Cause: The ASM diskgroup name has exceeded string characters.

Action: Specify diskgroupname lesser than string characters.

Cause: Insufficient space available in the selected Disks. At least, string MB of free space is required.

Action: Choose additional disks such that the total size should be at least string MB.

Cause: Installer has detected that the diskgroup name provided already exists on the system.

Action: Specify different disk group.

Cause: n/a

Action: n/a

Cause: The Disk Discovery Path specified is invalid. Disk Discovery Path must not contain $, \\ or ? characters.

Action: Ensure Disk Discovery Path provided does not contain $, \\ or ? characters.

Cause: The allocation unit size (AU Size) is set to an invalid number.

Action: Set the allocation unit size be one of the following value set string .

Cause: File access permissions error encountered.

Action: Ensure proper file access permissions are granted.

Cause: A connection to the Automatic Storage Management (ASM) instance on this system could not be established.

Action: To ensure a proper connection, the operating system user performing this installation must be a member of the OSDBA group of the ASM instance. See the installation guide for more information on the proper system setup required for running ASM and database instances as separate operating system users. Refer to Oracle error description for ORA-01031 for additional details.

Cause: Cluster Ready Services (CRS) on the local node was not running.

Action: Perform a CRS, Grid Infrastructure, installation and configuration.

Cause: Required drivers were not found to perform the operation.

Action: Ensure that all required drivers were installed.

Cause: ASM instance was down.

Action: Bring up ASM in order to proceed.

Cause: Directories or files or both were missing.

Action: Clean up ASM home and reinstall ASM.

Cause: n/a

Action: n/a

Cause: The partition provided was not available on the system.

Action: Provide a partition that is available on the system.

Cause: A value was not specified for the Password field.

Action: Choose a nonempty password.

Cause: The password entered in the Confirm Password field did not match the password entered in the Password field.

Action: Enter the same password in both Password and Confirm Password fields for confirmation purposes.

Cause: The specified Oracle base is same as the user home directory.

Action: Provide an Oracle base location other than the user home directory.

Cause: The specified string contained one or more invalid characters.

Action: Choose a string containing only alphanumeric characters and a few additional characters that are allowed for your platform.

Cause: The string you entered contains the space character.

Action: Please choose a string containing only alphanumeric, and a few additional characters that are allowed for your platform.

Cause: Either proper permissions were not granted to create the directory or there was no space left in the volume.

Action: Check your permission on the selected directory or choose another directory.

Cause: The string location was empty.

Action: Specify a path for string location.

Cause: The specified location cannot be used for string . Either the specified location is not found on the system or is detected to be a file.

Action: Specify a valid location for string .

Cause: The selected Oracle home contained directories or files.

Action: To start with an empty Oracle home, either remove its contents or choose another location.

Cause: Path specified for string contains one or more folders which exceeds maximum folder name length.

Action: Specify the location which contains folders name length not more than string characters.

Cause: The Oracle home selected was outside of Oracle base.

Action: Oracle recommends installing Oracle software within the Oracle base directory. Adjust the Oracle home or Oracle base accordingly.

Cause: The selected Oracle home was on a volume without enough disk space.

Action: Choose a location for Oracle home that has enough space (minimum of string MB) or free up space on the existing volume.

Cause: Grid infrastructure for a cluster installations assign root ownership to all parent directories of the Grid home location. As a result, ownership of all named directories in the software location path are changed to root, creating permissions errors for all subsequent installations into the same Oracle base.

Action: Specify software location outside of an Oracle base directory for grid infrastructure for a cluster installations.

Cause: The specified Oracle base location is identical to an existing Oracle home location.

Action: Specify a location for Oracle base which is not an existing Oracle home.

Cause: The chosen installation conflicted with software already installed in the given Oracle home.

Action: Install into a different Oracle home.

Cause: Grid Infrastructure for a Cluster installation will assign root ownership to all parent directories of Oracle Clusterware software location. As a result, all named directories in the software location path will acquire root ownership. This may create problems for subsequent installations into the same Oracle base.

Action: Specify software location outside of Oracle base.

Cause: The Central Inventory location provided was empty.

Action: Provide a valid location for the inventory.

Cause: Inventory location was invalid.

Action: Specify a valid inventory location.

Cause: Central Inventory location was not writable.

Action: Ensure that the inventory location is writable.

Cause: The inventory directory contained one or more invalid characters.

Action: The inventory directory can contain only alphanumeric, hyphen, and underscore characters.

Cause: The central inventory location provided is not empty.

Action: Please provide another location for the inventory, or clean up the current location.

Cause: User home directory has been chosen as inventory directory. Oracle recommends that the inventory directory is not users home directory, because members of inventory group will be given write permission to the inventory directory.

Action: Choose a directory other than users home as inventory location.

Cause: No value specified for central inventory (oraInventory) ownership group.

Action: Specify an operating system group whose members should have write permission to the central inventory directory (oraInventory).

Cause: User performing installation is not a member of the operating system group specified for central inventory(oraInventory) ownership.

Action: Specify an operating system group that the installing user is a member of. All the members of this operating system group will have write permission to the central inventory directory (oraInventory).

Cause: The current user and current group do not match with the user and group of inventory location.

Action: Ensure that the file user and group are same as the installer user and install group respectively.

Cause: Oracle base and Oracle home locations were same.

Action: Oracle base and Oracle home locations cannot be same. Oracle recommends installing Oracle software within the Oracle base directory. Adjust the Oracle home or Oracle base accordingly.

Cause: The Oracle home name specified on the command line corresponded to an existing Oracle home name in the Central Inventory.

Action: Choose another Oracle home name. Abort this installation session and try again.

Cause: The Central Inventory string was located on a shared file system.

Action: Oracle recommends placing this Central Inventory on a local file system that is not shared by other systems, because it is a server-specific inventory of the installation on this server. Oracle strongly recommends that you move the Central Inventory to a local disk so that installations from other servers do not corrupt the Central Inventory for this server.

Cause: The Central Inventory is located in the Oracle base.

Action: Oracle recommends placing this Central Inventory in a location outside the Oracle base directory.

Cause: Insufficient write permissions were granted to create this directory on the specified node.

Action: Ensure that you have the required write permissions. Alternatively, you may want to choose another location.

Cause: An invalid or non-existent ASM disk group has been selected.

Action: Ensure that the selected ASM disk group exists.

Cause: The string location provided is not absolute path.

Action: Please provide absolute location for the string .

Cause: The MTS port text field is either empty or containing non-numeric characters

Action: Provide a valid value for MTS port.

Cause: Refer to the error message for details.

Action: Specify a valid port number.

Cause: The value you have entered for the MTS Port is out of the valid range.

Action: Enter a MTS Port number between 1024 and 65535.

Cause: No product language selected for installation.

Action: Select at least one product language for installation.

Cause: An attempt was made to remove English from the selected languages list.

Action: Select English as one of the selected product languages.

Cause: Not all selected product languages are supported.

Action: Refer to the sample response file for more information.

Cause: Refer the log files for details.

Action: Refer to the logs or contact Oracle Support Services.

Cause: Software installation was successful. But some configuration assistants failed, were cancelled or skipped.

Action: Refer to the logs or contact Oracle Support Services.

Cause: My Oracle Support username cannot be empty..

Action: Provide a valid My Oracle Support username.

Cause: My Oracle Support password cannot be empty..

Action: Provide a valid My Oracle Support password.

Cause: Credentials provided may be invalid, or there may be a network connection issue.

Action: Check the My Oracle Support credentials. Also check the proxy setting and authentication credentials, and the network connection.

Cause: The installer is unable to locate the software updates in the specified directory.

Action: For software updates to work in offline mode, the downloaded updates must be in a particular path location format. Refer to your installation manual for details.

Cause: n/a

Action: n/a

Cause: n/a

Action: n/a

Cause: n/a

Action: n/a

Cause: n/a

Action: n/a

Cause: The My Oracle Support credentials you provided may not have download privileges, or there may be a network or proxy authentication issue.

Action: Provide credentials with download privileges. Also check the network connection and, if you have a proxy realm, your proxy credentials.

Cause: This may be due to a network connection problem.

Action: Check the connection to My Oracle Support.

Cause: The patch download location cannot be empty.

Action: Provide the location where the updates have been downloaded.

Cause: The downloaded metadata for software updates is not properly formatted.

Action: Refer to the logs or contact Oracle Support Services.

Cause: n/a

Action: n/a

Cause: The user name provided is invalid. It either contains invalid characters or does not follow the standard e-mail address format.

Action: Specify an e-mail address that is consistent with RFC 2822 and RFC 2821 format.

Cause: The location provided does not have space for downloading all the updates.

Action: Choose a location with enough space or free up space on the existing volume.

Cause: n/a

Action: n/a

Cause: My Oracle Support credentials provided does not have download privileges.

Action: Provide My Oracle Support credentials with download privileges in order to check for latest updates.

Cause: The Oracle Grid Infrastructure for a cluster home (Grid home) was placed in the installation owners home directory.

Action: Oracle recommends that you do not place the Grid home in a user home directory, because ownership of the path to that directory is changed to root.

Cause: Configuration of an Oracle Grid Infrastructure for a cluster Grid home is not supported on OCFS2 partitions.

Action: Specify a Grid home location that is not an OCFS2 partition.

Cause: Configuration of an Oracle Grid Infrastructure for a cluster Grid home is not supported on OCFS2 partitions.

Action: Specify a Grid home location that is not an OCFS2 partition.

Cause: The installer detects that you have configured Oracle Grid Infrastructure software on this server, and that the Oracle base you provided for this install is not the same as the existing Oracle Grid Infrastructure software Oracle base.

Action: Provide the same Oracle base location for this Oracle Grid Infrastructure installation that is used for the existing Oracle Grid Infrastructure.

Cause: The installer detects that the Oracle home location you provided is on an Oracle ASM Cluster File System (ACFS) mountpoint. You cannot place Oracle Grid Infrastructure binaries on an ACFS mount point.

Action: Specify a Grid home location that is on a location other than an ACFS mount point.

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.

Cause: You selected to install and configure a new Oracle grid infrastructure installation (Oracle Clusterware and Oracle ASM). However, only one installation of Oracle Clusterware and Oracle ASM can be configured on a server at the same time.

Action: Deconfigure the existing Oracle Grid Infrastructure software before installing and configuring a new instance of Oracle Grid Infrastructure software.

Cause: You selected to install and configure a new Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle ASM). However, only one installation of Oracle Clusterware and Oracle ASM can be configured on a server at the same time.

Action: Deconfigure the existing Oracle Grid Infrastructure software before installing and configuring a new instance of Oracle Grid Infrastructure software.

Cause: The installer was unable to detect any existing Oracle Clusterware or Oracle ASM installation to upgrade.

Action: You can choose either to install a new Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle ASM) on this node, and add the node to an existing cluster, or you can install a new Oracle Grid Infrastructure installation and make the node part of a new cluster. If you want to add the node to an existing cluster, then review Oracle Clusterware Administration and Deployment Guide and follow the add node procedure. If you want to create a new cluster, then select the option for a new installation.

Cause: You can have only one Oracle ASM instance configured on the node.

Action: Select the Software Only installation of Oracle Grid Infrastructure into a new home, and configure Oracle ASM in the new home after installation.

Cause: You selected to install and configure an Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle ASM). However, Oracle Clusterware cannot be installed on a server with a configured CSS daemon.

Action: Deconfigure and delete the existing local CSS daemon, and then restart the installer.

Cause: You selected to install and configure a new Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle ASM). However, only one installation of Oracle Clusterware and Oracle ASM can be configured on a server at the same time.

Action: Deconfigure the existing Oracle Grid Infrastructure software before installing and configuring a new instance of Oracle Grid Infrastructure software.

Cause: None of the network interfaces detected on this system supports IPv4 protocol.

Action: Configure at least one of the public interfaces available on this system to support IPv4.

Cause: The installer has detected that an earlier version of Oracle ASM is configured on the server.

Action: If you intend to upgrade Oracle ASM as part of this installation, then you must shut down the Oracle ASM instance before proceeding. Shut down any database instances using Oracle ASM before shutting down the Oracle ASM instance.

Cause: OCR location pointer file (string ) is left behind from a previous installation.

Action: Delete the OCR location pointer file (string ) and restart the installer.

Cause: The installer has detected the presence of Oracle Database release string instances.

Action: If you intend to upgrade Oracle ASM as part of this upgrade, then you must upgrade Oracle Database instances using Oracle ASM to release string or later before proceeding with upgrading Oracle ASM.

Cause: Oracle Clusterware or Oracle ASM release string or above is needed to upgrade to Oracle Grid Infrastructure.

Action: Install the patchset to upgrade the configured instance of Grid Infrastructure to version string or higher.

Cause: OCR location registry key (string ) is left behind from a previous installation.

Action: Delete the OCR location registry key (string ) and restart the installer.

Cause: The installer has detected that the Oracle Clusterware stack on the local node is not running.

Action: Open a terminal, log in as root or Administrator, change directory to the Oracle Clusterware home (Grid home), and start Oracle Clusterware by entering this command: crsctl start crs

Cause: Installer has detected that configured version of Automatic Storage Management software is lower than the Grid Infrastructure software version.

Action: Open a terminal, log in as the Grid Infrastructure installation owner, change directory to the Grid home, and run ASMCA to upgrade Oracle ASM.

Cause: The installer detects that the current installation user (string ) is not the same as the existing Oracle Grid Infrastructure software user (string ). To upgrade the existing software, run the installer as the user owning the Oracle Grid Infrastructure home.

Action: Restart the installation as the user that owns the existing Grid home.

Cause: The installer is unable to detect the owner of the existing Grid home. To upgrade the software, you must run the installer as the user owning the Grid home.

Action: Run the installer as the user owning the existing Grid home.

Cause: Patchset for the bug string is not installed on the configured instance of the Grid Infrastructure home.

Action: Install the patchset for the bug string on all the nodes to upgrade the configured instance of Grid Infrastructure to current version.

Cause: The installer detected that Intelligent Platform Management Interface (IPMI) drivers were not installed on all the nodes that you indicated should be part of the cluster. Cluster Synchronization Service (CSS) requires this driver, as it interacts with the IPMI driver to ensure cluster integrity.

Action: Download the IPMI driver from the hardware vendor website, and ensure that the driver is installed and configured on all the nodes, so that installation can continue.

Cause: The BMC user name text field was blank.

Action: You have selected Intelligent Platform Management Interface (IPMI) to use for failure isolation support. The installer requires the Baseboard Management Controller (BMC) user name to proceed with configuration. Enter the BMC user name that has privileges to interact with the IPMI-compliant hardware.

Cause: Invalid characters were specified in the user name.

Action: Enter a valid BMC user name. The Baseboard Management Controller (BMC) user name can only contain lower or uppercase alphanumeric characters (a - z, A - Z, 0 - 9), hyphen(-), period(.) and underscore(_).

Cause: The password field was left blank.

Action: Enter a password.

Cause: The specified value for the GNS subdomain contained one or more invalid characters.

Action: Enter a valid GNS subdomain name. Valid characters for the GNS subdomain can be any combination of lower or uppercase alphanumeric characters (a - z, A - Z, 0 - 9), hyphen(-), and period(.).

Cause: The Grid Naming Service (GNS) subdomain was blank.

Action: Provide a value for GNS subdomain.

Cause: The GNS subdomain could not be resolved using TCP/IP host name lookup.

Action: Specify a subdomain that can be resolved.

Cause: The specified value for the GNS virtual IP address contained one or more invalid characters.

Action: Enter a valid value for the GNS virtual IP Address. Valid characters for GNS virtual IP addresses can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), hyphen(-), and period(.).

Cause: The GNS virtual IP address was blank.

Action: Provide a valid value for the GNS virtual IP address.

Cause: The GNS virtual IP address could not be resolved using TCP/IP host name lookup.

Action: Specify a valid GNS virtual IP address.

Cause: The specified GNS virtual host name could not be resolved to an IP address. This may occur if the IP address is in use on another cluster, or the IP address has not been registered to this name in the Domain Name System (DNS).

Action: Ensure that you have entered a virtual host name that is not in use. If you continue to receive an error, then contact your network administrator for assistance.

Cause: The specified value for the cluster name contained one or more invalid characters.

Action: Provide a valid value for the cluster name. Valid characters can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen(-).

Cause: The cluster name did not start with a letter.

Action: Provide a value for the cluster name that starts with a letter

Cause: The Cluster name text field was blank.

Action: Provide a valid value for the cluster name.

Cause: The specified cluster name was too long.

Action: Provide a cluster name that is 15 or fewer characters in length.

Cause: The cluster name cannot be longer than string characters. With the Typical install type, the host portion of the SCAN is used as the cluster name. If that portion is longer than string characters, then the installer truncates the cluster name to string characters.

Action: If you want to use a specific name for the cluster, then provide a name no greater than string characters, or select the Advanced installation type.

Cause: The name you provided as the SCAN contained one or more invalid characters.

Action: Enter a valid name for the SCAN. Valid characters can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), hyphen(-), and period(.).

Cause: The name you provided as the SCAN contained one or more invalid characters. For the Typical installation type, invalid characters include those that are invalid for a cluster name, because the cluster name is derived from SCAN.

Action: Enter a valid name for the SCAN and for the cluster name. Valid characters can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), hyphen(-), and period(.).

Cause: The SCAN did not start with an alphabetic character.

Action: Provide a value for the SCAN that starts with an alphabetic character.

Cause: No name was provided as the SCAN.

Action: Provide a valid name to use for the SCAN.

Cause: The name you provided as the SCAN could not be resolved using TCP/IP host name lookup.

Action: Provide name to use for the SCAN for which the domain can be resolved.

Cause: The installer could not find the IP addresses you selected as SCAN addresses. This may be because they are assigned to another system, or because the IP addresses are not listed in the DNS or hosts files as assigned to this domain name.

Action: Enter resolvable IP addresses to use as SCAN addresses.

Cause: The name configured as the SCAN was not associated with an IP address.

Action: Ensure the names you provide as SCANs are associated with IP addresses.

Cause: The SCAN port text field was empty.

Action: Provide a valid value for the SCAN port.

Cause: The value entered for the SCAN port contained one or more invalid characters. A valid SCAN port is a number.

Action: Enter a valid numeric value for the SCAN port.

Cause: The value entered for the SCAN Port was out of the valid range.

Action: Enter a SCAN port number between 1024 and 65535.

Cause: None of the locally defined network interfaces has a subnet matching the SCAN subnet.

Action: Define a public interface with a subnet matching the one you want to use for the SCAN.

Cause: No interface was found with a subnet matching the subnet designated as the SCAN subnet.

Action: Define a public interface with a subnet matching the one you want to use for the SCAN.

Cause: The name you provided as the SCAN is not in the GNS subdomain.

Action: Ensure the name you provide as the SCAN is in the same domain as the GNS subdomain.

Cause: The name for the configured SCAN is already associated with an IP address.

Action: If you intend to use GNS resolution for your cluster, then ensure the names you provide for SCANs are not associated with IP addresses that are already in use.

Cause: The installer detects that the SCAN port number you provided is already in use. This can occur if Oracle9i RAC is installed on the server, and it is using the port.

Action: Provide a different SCAN port number in the range 1024 and 65535.

Cause: Values in the cluster node information table are unfilled.

Action: Provide valid data in the cluster node information table.

Cause: Some fields were left blank in the cluster node information table.

Action: Ensure that all information in the table is filled in.

Cause: The name you provided as the host name contains one or more invalid characters.

Action: Ensure that the host name contains valid characters. Valid characters for host names can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen (-).

Cause: The value provided for ORACLE_HOSTNAME does not resolve to a valid host name.

Action: Provide a valid host name for ORACLE_HOSTNAME, and restart the installer.

Cause: One or more IP addresses do not resolve to valid host names.

Action: You must enter valid IP addresses that resolve to hostnames before installation can continue.

Cause: Duplicate entries have been made in the node information table for Oracle Clusterware installation.

Action: Remove duplicate entries in the Oracle Clusterware node information table.

Cause: The local node (the node where you are running the installer) was missing from the list of host names you provided.

Action: Include the local node in the list of host names for grid installation.

Cause: One or more host names you provided are invalid, as they do not resolve to a valid IP address.

Action: Enter valid host names.

Cause: Node information was entered for two or more nodes that belonged to different domains.

Action: Enter host names belonging to the same domain.

Cause: The Virtual IP did not resolve to an IP address.

Action: Enter a valid name for the virtual IP that resolves to an IP address.

Cause: Some public nodes either were unreachable, or they belonged to a different subnet.

Action: Ensure that nodes in the list are up and reachable, and ensure that the node addresses are all in the same subnet.

Cause: One or more virtual host names appeared to be assigned to another system on the network.

Action: Ensure that the virtual host names assigned to each of the nodes in the cluster are not currently in use, and the IP addresses are registered to the domain name you want to use as the virtual host name.

Cause: The user performing this installation is not configured identically on all nodes. This may be due to differences in the user or group IDs, or to SSH configuration issues.

Action: If necessary, refer to the installation guide for information about how to set up user equivalence manually on cluster nodes.

Cause: An Oracle9i RAC installation was present on remote node string , but not on the local node.

Action: To install on a set of nodes on which the Oracle9i release of Oracle RAC has been configured, start the installer on the node where Oracle9i RAC is installed so that the installer can upgrade the existing installation.

Cause: Either Oracle Clusterware is running on the listed nodes, or previous installations of Oracle Clusterware are not completely deinstalled.

Action: For each node listed, ensure that existing Oracle Clusterware is completely deinstalled. You can also choose not to include these nodes in this installation.

Cause: The installer detected single-instance versions of Cluster Synchronization Services (CSS) on the following nodes in the cluster:string

Action: Before proceeding with the installation, you must deconfigure CSS, shut down any Oracle Automatic Storage Management (Oracle ASM) instances, and shut down all databases that use Oracle ASM for storage on all of the listed nodes. Oracle Clusterware installation starts a cluster-wide version of CSS. After Oracle Clusterware installation is complete, you may start up any databases and Oracle ASM instances that previously used CSS. When they are brought back up, Oracle Clusterware provides CSS.

Cause: Host name cannot be in IP address format.

Action: Provide the host name for host name.

Cause: Virtual IP name cannot be in IP address format.

Action: Provide a valid virtual IP name.

Cause: You did not provide a hostname for the node.

Action: Enter a valid hostname.

Cause: You did not enter a name for the virtual IP address.

Action: Enter a valid virtual IP name.

Cause: The name you provided for the virtual IP name contains one or more invalid characters.

Action: Provide a name to use for the virtual IP name that contains valid characters. Valid characters for virtual IP name can be any combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen(-).

Cause: SCAN provided does not resolve to an IP address.

Action: Ensure that the SCAN is valid, and that it is resolvable to an IP address.

Cause: No local network interface was found with an address matching the subnet for the SCAN.

Action: Ensure that the SCAN subnet matches the subnet configured on an existing local network interface.

Cause: Unable to locate common interfaces or subnets on all cluster member nodes.

Action: Ensure that the local node has valid network interfaces, with valid subnets that are the same on all cluster member nodes.

Cause: One or more nodes have network interfaces configured with a subnet that is not common to all nodes in the cluster.

Action: Ensure all cluster nodes have a public interface that is defined with the same subnet, and accessible by all nodes in the cluster.

Cause: One or more nodes have interfaces configured with subnets that are different than the SCAN subnet.

Action: Ensure all nodes have a public interface configured with a subnet that matches the SCAN subnet.

Cause: The following nodes have interfaces in common subnets that have different interface names: string

Action: Ensure that the names of interfaces defined on common subnets are the same on all cluster member nodes.

Cause: An unknown error occurred during validation of addresses or subnets on cluster member nodes.

Action: Ensure network interfaces are configured correctly, and that subnets are available on all nodes of the cluster. Ensure all nodes have at least one public interface on a subnet available on all nodes, and ensure all nodes have one public interface on the same subnet.

Cause: Oracle 9i Global Services Daemon (GSD) processes are detected on some or all of the nodes specified.

Action: To allow Oracle Clusterware to serve Oracle9i RAC databases, on each cluster member node you must shut down the Oracle9i Database GSD, and shut down any Oracle RAC databases. The installer will configure a GSD to run in the new grid Oracle home. After installation, you may restart all Oracle9i databases.

Cause: One or more node VIPs could not be resolved to a valid IP address.

Action: Be sure all node VIPs are resolvable to a valid IP address.

Cause: Some node VIPs are on subnets that are different from the SCAN subnet.

Action: For each cluster member node, ensure that the VIP is configured with the SCAN subnet.

Cause: Unknown errors were encountered while validating Node VIPS.

Action: Ensure all node VIPs resolve to a valid IP address.

Cause: Interface information collection failed.

Action: Be sure all nodes are accessible and have valid network interfaces defined.

Cause: A remote directory operation failed.

Action: Be sure all nodes are accessible across the network.

Cause: A cluster operation failed.

Action: Ensure that all cluster member nodes are accessible on the network.

Cause: A cluster operation (for example, list interfaces) failed.

Action: Ensure that all cluster member nodes are accessible on the network.

Cause: The hostname or names listed are invalid.

Action: Ensure that you are not providing aliases, and that the hostnames you provide are valid.

Cause: Some of the nodes that are cluster members of the Oracle9i RAC database are not among the nodes you selected.

Action: In the list of nodes, specify all the cluster member nodes of the Oracle9i RAC database.

Cause: The installer detects that this node is a member of a vendor cluster, and that some of the nodes you selected to make members of the Oracle Clusterware cluster are not members of the vendor cluster.

Action: If you install Oracle Clusterware on a node that is a member of a vendor cluster, then all nodes that you select to be Oracle Clusterware nodes must also be members of the vendor cluster.

Cause: Nodes are not configured on the same domain.

Action: Ensure that all nodes are configured on the same domain

Cause: The installer cannot collect domain information from one or more nodes you selected.

Action: Before proceeding with the installation, ensure that all selected nodes are configured on the same domain.

Cause: Either the format of the information entered was incorrect, or the interface name or subnet information was incorrect.

Action: Enter the correct interface information before proceeding

Cause: None of the network interfaces were designated as public.

Action: Designate at least one interface as a public interface.

Cause: Interface string has been marked as both Public and Private.

Action: Designate interface string either as Public or Private, but not both Public and Private.

Cause: There is no interface marked as Private.

Action: Ensure that at least one interface is designated as Private.

Cause: The chosen public interface is not on the same subnet as the SCAN VIP.

Action: Ensure the chosen public interface is on the same subnet as the SCAN VIP subnet, and that the same subnet is configured for SCAN VIPs on all cluster nodes.

Cause: The chosen public or private interface subnet is not identical on all nodes.

Action: Ensure that the subnets configured for public and private interfaces are identical on all cluster nodes.

Cause: The public or private interface on the nodes indicated are on a different subnet than the ones used on other nodes.

Action: Ensure that all public interfaces share the same subnet, and ensure that all private interfaces share the same subnet.

Cause: The chosen public interface is not on the same subnet as the GNS VIP.

Action: Be sure that the chosen public interface is on a subnet which matches the GNS VIP subnet and is common across all cluster nodes.

Cause: Installer has detected that interface string does not have the same netmask string configured on all cluster nodes.

Action: Ensure that the chosen interface has been configured with same netmask across all cluster nodes.

Cause: The installer has detected that different interface names configured for particular subnet on provided set of nodes. Installer will not consider interface names during Grid Infrastructure configuration. Because of this, installer has transferred the provided interface list to following format: string

Action: N/A

Cause: You have specified generic name for the interface configured on the subnet (string ). But installer detected that multiple interfaces configured on this subnet.

Action: Ensure that you have specified interface name appropriately.

Cause: Installer has detected that network interface string does not maintain connectivity on all cluster nodes.

Action: Ensure that the chosen interface has been configured across all cluster nodes.

Cause: Installer has detected that both public and private interfaces are configured on the same subnet.

Action: Ensure that the public and private interfaces are configured on different subnets.

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.

Cause: Fewer than three locations were provided for the Oracle Cluster Registry.

Action: Specify three locations 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.

Cause: One or more Oracle Cluster Registry (OCR) locations contained bad characters.

Action: Provide an OCR location that uses valid characters in the path.

Cause: One or more Oracle Cluster Registry (OCR) locations are not valid.

Action: Provide valid OCR locations.

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.

Cause: The Oracle Cluster Registry (OCR) location you provided is on a block or character device.

Action: Select one of the following supported locations: OCFS2 partition, or a shared NFS partition. If you intend to use block or character device, choose Oracle Automatic Storage Management (Oracle ASM) as storage option for install.

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 Cluster Registry.

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.

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

Cause: One or more Oracle Cluster Registry locations specified were duplications.

Action: Specify a unique location for each Oracle Cluster Registry location.

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.

Cause: The specified OCR file already exists.

Action: Ensure that the OCR file you have specify is a nonexistent file.

Cause: The attempt to delete the file was not successful.

Action: Ensure that the user account running the installation has the permissions to replace the file.

Cause: One or more Oracle Cluster Registry (OCR) locations were not valid.

Action: Provide valid OCR locations.

Cause: One or more specified files already exist.

Action: Either choose a different storage location, or allow the installer to overwrite this location and remove any existing files.

Cause: The specified shared location is in use.

Action: Ensure that the location you provided is not already in use, and that any past Oracle Clusterware configuration is completely removed from the partition.

Cause: The attempt to delete files was unsuccessful.

Action: Ensure that the user account running the installation has the permissions to replace files.

Cause: The installer detects that the storage type of the location (string ) is not supported for Oracle Cluster Registry.

Action: Provide a supported storage location for the Oracle Cluster Registry.

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.

Action: Specify three separate locations for voting disk files for normal redundancy.

Cause: A voting disk file location was not specified. For external redundancy, you must specify a location for the voting disk file.

Action: Specify one voting disk file location for external redundancy.

Cause: Voting disk file paths contained one or more invalid characters.

Action: Specify voting disk file location paths that do not contain illegal characters.

Cause: One or more voting disk file locations were not placed in an existing directory.

Action: Provide valid voting disk file locations.

Cause: Normal redundancy for voting disk files requires that each file is placed on a different partition, to avoid a single point of failure.

Action: Specify three locations on separate physical partitions to configure normal redundancy for voting disk files.

Cause: One or more voting disk file locations you provide are duplicate. Each voting disk location must be on separate devices.

Action: Specify a location on separate devices for each voting disk file.

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.

Action: Specify voting disk file locations that are different from Oracle Cluster Registry (OCR) locations.

Cause: Oracle 9i quorum disks are located on one or more of the locations you specified for voting disk files.

Action: Provide new locations for voting disk files. You cannot reuse an Oracle9i quorum disk location.

Cause: The voting disk file location you provided is on a block or character device.

Action: Select one of the following supported locations: Oracle Automatic Storage Management, an OCFS2 partition, or a shared NFS partition.

Cause: One or more voting disk file locations you provided have an existing voting disk file.

Action: Specify a new voting disk file location.

Cause: One or more locations you specified for placing voting disk files did not have proper permissions or ownership for installation to proceed.

Action: Specify voting disk file locations where the user account running the installation and oraInventory group members have read and write privileges.

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.

Action: Enter a shared storage location that has at least string MB of free space.

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.

Cause: The specified voting disk file already exists.

Action: Ensure that the location you specify for a voting disk file does not already have a voting disk file in that location.

Cause: The attempt to delete the file was not successful.

Action: Ensure that the user account running this installation has proper permissions in this storage area to replace the file.

Cause: One or more voting disk file locations may not be shared on all nodes.

Action: Provide valid voting disk file locations on shared paths and directories.

Cause: n/a

Action: n/a

Cause: The installer detects that the storage type of the location (string ) is not supported for voting disk files.

Action: Provide a supported storage location for the voting disk file.

Cause: The Oracle Clusterware node list could not be acquired from the Oracle inventory contents in the oraInventory directory.

Action: Ensure that the inventory is not corrupted, and that the oraInst.loc path is correct.

Cause: Node selection was blank.

Action: Select a list of nodes to upgrade with the local node.

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.

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

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.

Cause: You have chosen a subset of the cluster nodes for the upgrade.

Action: During installation, the software will be copied to all cluster nodes. However, during installation setup, you are prompted to run the rootupgrade script only on the nodes you selected for upgrade. To complete the upgrade, run the rootupgrade script on the remaining nodes. You do not need to start the installer again to upgrade the remaining nodes.

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.

Action: To complete the upgrade, select all the nodes that are part of the Oracle Grid Infrastructure cluster.

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.

Action: Select Oracle ASM upgrade option to complete the installation.

Cause: You selected to upgrade Oracle ASM. However, the installer does not detect Oracle ASM on this server.

Action: To continue with the installation, deselect the option to upgrade Oracle ASM.

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.

Action: All databases using Oracle ASM for storage will go down during this installation. Plan for databases to be unavailable during the time when the installer is running configuration tools.

Cause: n/a

Action: n/a

Cause: The Orcale Clusterware software configured on the system is not in a suitable state to upgrade.

Action: Ensure that the Oracle Clusterware software is in a consistent state to perform an upgrade.

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.

Action: Ensure that the Oracle ASM instance installed in home string is up, and then retry the installation.

Cause: An Oracle ASM entry was listed in the system registry or oratab, but Oracle ASM home string was missing.

Action: Ensure that either the oratab or the system registry is correct, or that the inventory is not corrupted.

Cause: There is an Oracle ASM instance already running on the server.

Action: Upgrade the existing Oracle ASM instance to the current release.

Cause: The name you provided for the virtual IP name is the same name used as the SCAN.

Action: Enter a name for the virtual IP that is different from the name you entered for the SCAN.

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

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

Action: Oracle recommends that you designate asmadmin as the OSASM group.

Cause: The group name you selected as the OSDBA for ASM group is commonly used for Oracle Database administrator privileges.

Action: Oracle recommends that you designate asmdba as the OSDBA for ASM group, and that the group should not be the same group as an Oracle Database OSDBA group.

Cause: The group name you selected as the OSOPER for ASM group is commonly used for Oracle Database administrator privileges.

Action: Oracle recommends that you designate asmoper as the OSOPER for ASM group, and that the group should not be the same group as an Oracle Database OSOPER group.

Cause: The groups you selected granting the OSDBA for ASM and OSOPER for ASM system privileges are the same group.

Action: Oracle recommends that you designate different OS groups to grant the OSDBA for ASM and OSOPER for ASM system privileges.

Cause: The chosen values for string group and the chosen value for OSASM group are the same.

Action: Select an OS group that is unique for ASM administrators. The OSASM group should not be the same as the OS groups that grant privileges for Oracle ASM access, or for database administration.

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.

Action: Choose different groups as the OSASM, OSDBA for ASM, and OSOPER for ASM groups.

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.

Action: Confirm that you have run the root scripts on this server. If the root scripts have been run, then examine the log file string to determine the reason for the services failing to start.

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. If the Oracle Clusterware is upgraded from earlier versions, root upgrade script might not be run successfully on the specified nodes.

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

Cause: The installation user account must be a member of all groups required for installation.

Action: Change the installation users group memberships to include the required OS system privileges groups, or select system privileges OS groups in which the installation owner is a member.

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

Action: Confirm that the group you want to use as the ASMOPER group exists on the server, or in NIS. Create or specify another group if it does not exist.

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.

Action: Select Advanced Installation for Oracle Grid Infrastructure. This option allows you to specify configuration information required for Oracle Clusterware to operate with other vendor clusterware.

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.

Action: Select Advanced Installation for Oracle Grid Infrastructure. This option allows you to specify configuration information required for Oracle Clusterware to operate with Oracle RAC release 9.x.

Cause: The same drive letter string cannot be assigned to more than one partition

Action: Provide different drive letters to each partition.

Cause: The specified partition was selected for storing the software binaries.

Action: Instead, choose a location that is formatted for storing data files.

Cause: No partitions were selected or partition details provided were incomplete.

Action: Specify one or more partitions. For each partition, select the format option and drive letter you want to have assigned to that partition.

Cause: The local server did not have any available drive letters to assign to partitions.

Action: Make drive letters available on the server, and then restart the installer.

Cause: Each partition you select must have an assigned drive letter.

Action: Ensure all partitions you want to use are configured with drive letters.

Cause: Either the drive letter is invalid, or it is already assigned to an existing partition.

Action: Select a valid drive letter.

Cause: The user account running the installation must have the oraInventory group as its primary group.

Action: Change the oraInventory group to the primary group of the installation owner account, or change the installation owner groups so that the group you want to use for the oraInventory group is the primary group of the installation owner.

Cause: The wizard finds that this Grid home is not registered in the central inventory.

Action: Register the Grid home in the central inventory by using a cloning operation, or by using an attach-home operation.

Cause: The wizard detects that the existing Grid home was not installed or cloned using the current user id: string .

Action: Either restart the wizard as the user account that was used previously to install the Grid home, or re-clone the Grid home using the current user account.

Cause: The wizard detects that Oracle Grid Infrastructure is already configured oin this server.

Action: Before you can proceed, you must completely remove the configured instance.

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.

Action: Restore the home by re-cloning the home, or re-install the software from installation media.

Cause: The wizard does not find this Grid home to be registered with the central inventory on some or all of the nodes specified.

Action: Register the Grid home on the specified nodes with the central inventory, either by using a cloning operation, or by using an attach-home operation. Restart the wizard after fixing this issue.

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.

Action: Ensure that the Grid home is consistent on all nodes.

Cause: The installer detects that the specified disk group is not on the discovery path you provided.

Action: For the selected disks, specify a valid disk group name, to which these disk previously were assigned. Also ensure that the discovery path you provide includes the disks.

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.

Action: Ensure Oracle Grid Infrastructure for a cluster or Cluster Ready Services is configured properly before using the configuration wizard. To perform any other upgrade, use the Oracle Grid Infrastructure installer, or run root configuration scripts directly.

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.

Action: Verify the correctness of the configuration file. If the file is corrupted, either restore the home by re-cloning the home or re-install the software from installation media.

Cause: In Typical install SCAN Name is also used as Cluster Name. The SCAN name contains multibyte characters which are invalid for Cluster Name.

Action: Ensure that SCAN Name contains valid characters for Cluster Name. Valid characters for Cluster Name can be lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen (-).

Cause: Multibyte characters are not allowed in Cluster Name.

Action: Ensure the Cluster Name contains valid characters. Valid characters for Cluster Name can be lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen (-).