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: E-mail address for database management using e-mail notifications was empty.

Action: Specify an e-mail address for notification functions.

Cause: The value for the outgoing main (SMTP) server is empty. You must provide a SMTP server to enable database management with e-mail notifications.

Action: Specify an outgoing main (SMTP) server for e-mail notifications.

Cause: Either the e-mail address provided contains invalid characters, or it 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 provided outgoing mail (SMTP) server was not valid. You must specify a valid SMTP server to enable database management with e-mail notifications.

Action: Specify an outgoing mail (SMTP) server for e-mail notifications.

Cause: The database recovery backup location was empty.

Action: Specify a path for the database recovery backup location.

Cause: The database recovery user name text field was empty.

Action: Provide the user name permitted to perform database recovery.

Cause: The database recovery password was empty.

Action: Enter a password for database recovery.

Cause: The installer was unable to detect an agent home corresponding to the URL in the Management Service field.

Action: Specify a valid URL for Management Service field that has a corresponding agent configured on the host.

Cause: No value specified for Management Service field.

Action: Specify a valid Management service URL.

Cause: The database backup and recovery area is not located on a shared file system.

Action: Enter a backup and recovery area that is located on a shared file system.

Cause: The Global database name was left blank.

Action: Specify a value for the Global database name.

Cause: The Oracle system identifier (SID) was left blank.

Action: Specify a value for Oracle system identifier (SID).

Cause: The value given for the name portion of Global database name exceeds 30 characters. The maximum length is 30 characters.

Action: Enter a legal Global database name not exceeding 30 characters.

Cause: The specified SID was already registered in the oratab file (string ) on the server. The oratab file is used by Oracle products to detect existing database instances.

Action: Specify a unique Oracle system identifier (SID).

Cause: The Oracle system identifier (SID) given was already in use.

Action: Specify a unique Oracle system identifier (SID).

Cause: The length of the Oracle system identifier (SID) on Linux and UNIX platforms either exceeded 12 characters for single-instance installations or 8 characters for Oracle RAC installations.

Action: Specify an Oracle system identifier (SID) shorter than 12 characters for single-instance installation or 8 characters for Oracle RAC installation.

Cause: The length of the Oracle system identifier (SID) on Windows platforms either exceeded string characters for single-instance installations or string characters for Oracle RAC installations.

Action: Specify a Windows Oracle system identifier (SID) shorter than string characters for a single-instance installation or string characters for an Oracle RAC installation.

Cause: The ORACLE_HOME environment variable was already set. This prevents proper use of multiple Oracle homes and, as it is not required for any Oracle products to function, it will be unset in your environment.

Action: The ORACLE_HOME environment variable will be unset automatically.

Cause: The global database name began with a character that was not an alphabetic character.

Action: Specify a global database name that begins with an alphabetic character.

Cause: The domain portion entered for Global database name exceeded 128 characters.

Action: Specify a domain for the Global database name that is less than 128 characters in length.

Cause: The specified domain portion of the global database name contained invalid characters.

Action: Specify a global database name that contains only alphanumeric, underscore (_), pound (#) and period (.) characters.

Cause: The string derived from string contains one or more invalid characters.

Action: Remove the invalid characters (string ) from the string or select Advanced install flow to be able to specify different string

Cause: Database name cannot be empty.

Action: Enter a legal Global Database Name not exceeding 30 characters.

Cause: The system identifier (SID) that you entered begins with a non-alphabetic character.

Action: Enter a SID that begins with an alphabetic character.

Cause: The name and domain portion entered for Global database name exceeded string characters.

Action: Specify the Global database name that is less than string characters in length.

Cause: The domain portion entered for Global database name exceeded string characters.

Action: Specify a domain for the Global database name that is less than string characters in length.

Cause: The service name provided for RAC One is empty.

Action: Provide a value for the RAC One service name.

Cause: The service name provided for RAC One began with a character that was not an alphabetic character.

Action: Provide a service name which begins with an alphabetic character.

Cause: The service name provided for RAC One cannot be the same as the global database name.

Action: Provide a service name that is different from the global database name.

Cause: The service name provided for RAC One may contain invalid characters.

Action: Provide a service name that consists of alphanumeric or underscore (_) characters.

Cause: The domain portion in the Oracle RAC One service name may contain invalid characters.

Action: Provide a service name whose network domain consists of alphanumeric characters or _ or $ or #.

Cause: The domain portion entered for Oracle RAC One service name exceeded 128 characters.

Action: Specify a domain for the Oracle RAC One service name that is less than 128 characters in length.

Cause: The total available shared memory on at least one of the selected nodes (string MB) was less than the chosen target database memory (string MB).

Action: Enter a value for the target database memory less than string MB.

Cause: The total available shared memory on the system (string MB) was less than the chosen target database memory (string MB).

Action: Enter a value for target database memory that is less thanstring MB.

Cause: The allocated memory specified was greater than or equal to the total memory available on the system.

Action: Enter a value less than the total available memory on the system for target database memory.

Cause: Allocated memory was less than the required memory.

Action: Enter a memory value larger than string MB.

Cause: A value was not specified for the allocated memory of the database.

Action: Specify a value for the allocated memory of the database. This corresponds to the oracle.install.db.config.starterdb.memoryLimit variable in the response file.

Cause: The allocated memory specified was greater than 3GB.

Action: Enter a value less than 3GB for target database memory.

Cause: The data file storage location for Oracle Real Application Clusters was not on a shared file system.

Action: Specify a location on a shared file system to place the data files.

Cause: The specified directory for the database files was already in use by the Global database name that was provided.

Action: Either change the location or go to the previous screen and change the Global database name.

Cause: Oracle does not recommend placing Oracle Database files on ACFS. Oracle recommends that you place database files directly on the underlying Oracle ASM disk groups, as this provides optimal database performance.

Action: Specify a location that is not on ACFS.

Cause: You cannot use ACFS as shared storage for Oracle RAC.

Action: Specify an ASM diskgroup or any other supported shared storage location.

Cause: You cannot use file system storage with Standard Edition Oracle Real Application Clusters databases.

Action: Choose Oracle Automatic Storage Management for database storage.

Cause: Oracle Database 11g Release 2 and later supports Oracle ASM only on 64-bit Windows operating systems.

Action: Place database-related files on a supported file system.

Cause: One of the Database Administrative account password was either CHANGE_ON_INSTALL or MANAGER or DBSNMP or SYSMAN.

Action: Enter a password that is not a former default password for these administrative users, such as CHANGE_ON_INSTALL, MANAGER, DBSNMP or SYSMAN.

Cause: The administrative account password you entered was string which is not allowed for string user.

Action: Enter a password that is not a former default password for the string administrative user account.

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

Action: Ensure that the installation user is a member of the system privileges operating system groups you selected.

Cause: The OS group you specified as the OSOPER group may not be configured on the server, or in the Network Information Service (NIS).

Action: Check the group name you selected, and specify a different group, or create the group on the server or in the Network Information Service.

Cause: The active version of Oracle Clusterware detected on the system(string ) was lower than the version of Oracle Database that you were attempting to install(string ). This is not supported.

Action: Upgrade Oracle Clusterware to version string or later.

Cause: There were no disk groups selected for storage and backup.

Action: Select at least one disk group for storage and backup.

Cause: Before you can install Oracle RAC, you must install Oracle Grid Infrastructure on all servers (Oracle Clusterware and Oracle ASM) to create a cluster.

Action: Oracle Grid Infrastructure is not installed. Install it either from the separate installation media included in your media pack, or install it by downloading it from Electronic Product Delivery (EPD) or the Oracle Technology Network (OTN). Oracle Grid Infrastructure normally is installed by a different operating system user than the one used for Oracle Database. It may need to be installed by your system administrator. See the installation guide for more details.

Cause: The node list for the Oracle RAC database specified in the response file does not match the configuration stored in the OCR.

Action: Please specify a valid node or add this node string to the cluster.

Cause: All Oracle Grid Infrastructure nodes were not selected for installing Oracle RAC.

Action: Oracle recommends that you deploy Oracle Real Application Clusters across all Oracle Grid Infrastructure cluster nodes.

Cause: Oracle Database 11g Release 2 and later supports Oracle RAC only on 64-bit Windows operating systems.

Action: Choose the option to install a single instance database on this system.

Cause: Oracle Database 11g Release 2 and later supports Oracle RAC only on 64-bit Windows operating systems.

Action: Migrate your existing Oracle RAC installation to a 64-bit Windows platform before upgrading it.

Cause: Only one node is selected for database creation. To protect a database against node or instance failure, at least two nodes should be selected.

Action: Provide at least two nodes for database creation.

Cause: No nodes are specified for RAC One Node install.

Action: Specify the nodes on which RAC One Node install has to be done.

Cause: One or more selected nodes that are part of the cluster cannot be reached

Action: Ensure that all the selected nodes are reachable.

Cause: The installer could not detect any Oracle Real Application Clusters databases that could be upgraded.

Action: None

Cause: The installer could not detect any Oracle Real Application Clusters databases that could be upgraded on the selected nodes.

Action: None

Cause: The installer could not detect a single-instance database that could be upgraded.

Action: None

Cause: An earlier release version of Oracle Automatic Storage Management (Oracle ASM) is detected on the server.

Action: To upgrade Oracle ASM, refer to installation guides for information about Oracle Grid Infrastructure upgrade.

Cause: The ASMSNMP user password was not specified.

Action: Provide a password for the ASMSNMP user in the password field.

Cause: Oracle Database 11g Release 2 and later supports Oracle ASM only on 64-bit Windows operating systems.

Action: Migrate database storage from Oracle ASM to a file system before upgrading, or migrate earlier release databases versions that use Oracle ASM storage to 64-bit Windows systems. See the upgrade guide for additional information.

Cause: The active Oracle Restart release detected on the system (string ) is an earlier release than the Oracle Database release to which you want to upgrade (string ).

Action: Upgrade Oracle Restart software to version string or later.

Cause: The active version of Oracle Restart detected on the system (string ) is earlier than the version of Oracle Database that you are attempting to upgrade to (string ).

Action: Upgrade Oracle Restart software to version string or later.

Cause: You have chosen to perform a Desktop class install on a cluster. This option will not install Oracle RAC.

Action: If you want to install Oracle RAC, then choose to perform a Server class install.

Cause: The active version of Oracle Restart detected on the system(string ) is lower than the version of Oracle Database that you are attempting to install to (string ).

Action: Upgrade Oracle Restart software to version string or later.

Cause: You have chosen to install Oracle RAC when Oracle Clusterware stack is not running on the local node.

Action: Start the Oracle Clusterware stack by running the following command as the root user from the Oracle Clusterware home (Grid home) : /bin/crsctl start crs. When the Oracle Clusterware stack is running, restart the installer and continue with the Oracle RAC installation.

Cause: The installer detects that the location you specified for the Oracle home is under an Oracle ASM Cluster File System (ACFS) mount point that is not registered with Oracle Grid Infrastructure on this server.

Action: Oracle Database homes can only be placed on ACFS locations registered with Oracle Grid Infrastructure software. Specify a different location for the Oracle home, or register this location with Oracle Grid Infrastructure software.

Cause: The installer has detected that the software location you have specified contains Oracle Database software version string .

Action: Perform an out-of-place upgrade. Out-of-place upgrades allow you to perform the upgrade with less downtime and more stability, due to the non-destructive nature of the software installation.

You can perform the upgrade and maintain the existing Oracle home location by taking a backup of the prior release Oracle home before upgrading, and moving the prior release binaries to a different location before installing the new binaries into the existing Oracle home location. Refer to the documentation for a precise set of steps to follow in this case.

Cause: The specified Oracle base location is on an Oracle ASM Cluster File System that is not registered as a resource on Oracle Grid Infrastructure.

Action: Register the Oracle ASM Cluster File System location that you want to use for the Oracle base with Oracle Grid Infrastructure.

Cause: Standard Edition One (SE One) is not supported for Oracle Real Application Clusters database installation.

Action: Select a different Install Edition.

Cause: You selected an Install Edition that is not supported for UNIX or Linux operating systems, and for Oracle RAC installations.

Action: Select a different Install Edition.