39 INS-35001 to INS-40000
- INS-32120: The current install user is not part of ORA_ASMADMIN group.
-
Cause: n/a
- INS-32121: The current install user is not part of ORA_ASMDBA group.
-
Cause: n/a
- INS-35011: E-mail address cannot be empty.
-
Cause: E-mail address for database management using e-mail notifications was empty.
- INS-35012: Outgoing main (SMTP) server cannot be empty.
-
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.
- INS-35013: Check e-mail address.
-
Cause: Either the e-mail address provided contains invalid characters, or it does not follow the standard e-mail address format.
- INS-35014: Outgoing mail (SMTP) server is invalid.
-
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.
- INS-35015: Recovery location cannot be empty.
-
Cause: The database recovery backup location was empty.
- INS-35016: User name cannot be empty.
-
Cause: The database recovery user name text field was empty.
- INS-35017: Password cannot be empty.
-
Cause: The database recovery password was empty.
- INS-35019: Invalid value specified for Management Service field.
-
Cause: The installer was unable to detect an agent home corresponding to the URL in the Management Service field.
- INS-35020: Invalid value specified for Management Service field.
-
Cause: No value specified for Management Service field.
- INS-35021: The recovery location is on a file system that is not shared across the cluster.
-
Cause: The database recovery area is not located on a shared file system.
- INS-35022: Shared file system is not supported on windows for recovery area.
-
Cause: n/a
- INS-35022: Empty value provided for OMS Host.
-
Cause: n/a
- INS-35023: Empty value provided for Enterprise Manager Admin user.
-
Cause: n/a
- INS-35024: Empty value provided for Enterprise Manager Admin password.
-
Cause: n/a
- INS-35025: Empty value provided for OMS Port.
-
Cause: n/a
- INS-35026: Unable to connect to Enterprise Manager Cloud Control.
-
Cause: Invalid connection information specified.
- INS-35027: Selected storage type is not valid.
-
Cause: You cannot use file system storage for backup and recovery files, with Standard Edition Oracle Real Application Clusters databases.
- INS-35071: Global database name cannot be left blank.
-
Cause: The Global database name was left blank.
- INS-35072: The SID cannot be left blank.
-
Cause: The Oracle system identifier (SID) was left blank.
- INS-35073: Invalid global database name.
-
Cause: The value given for the name portion of Global database name exceeds 30 characters. The maximum length is 30 characters.
- INS-35074: The specified SID is already in use.
-
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.
- INS-35075: A database instance with the specified identifier already exists.
-
Cause: n/a
- INS-35076: The specified SID exceeds the number of characters allowed.
-
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.
- INS-35077: The specified SID exceeds the number of characters allowed.
-
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.
- INS-35081: The ORACLE_HOME environment variable is currently set.
-
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.
- INS-35082: Global database name did not begin with an alphabetic character.
-
Cause: The global database name began with a character that was not an alphabetic character.
- INS-35083: The specified domain of the Global database name exceeds 128 characters.
-
Cause: The domain portion entered for Global database name exceeded 128 characters.
- INS-35084: The specified global database name contains invalid characters.
-
Cause: The specified domain portion of the global database name contained invalid characters.
- INS-35085: Invalid value specified for string.
-
Cause: The string derived from string contains one or more invalid characters.
- INS-35086: Invalid value specified for Global database name.
-
Cause: Database name cannot be empty.
- INS-35087: Invalid value specified for SID
-
Cause: The system identifier (SID) that you entered begins with a non-alphabetic character.
- INS-35088: The specified Global database name exceeds string characters.
-
Cause: The name and domain portion entered for Global database name exceeded string characters.
- INS-35089: The specified domain of the Global database name exceeds string characters.
-
Cause: The domain portion entered for Global database name exceeded string characters.
- INS-35090: The service name provided for RAC One is empty.
-
Cause: n/a
- INS-35091: The service name provided for RAC One did not begin with an alphabetic character.
-
Cause: The service name provided for RAC One began with a character that was not an alphabetic character.
- INS-35092: The service name provided for RAC One cannot be the same as the global database name.
-
Cause: n/a
- INS-35093: Invalid value provided for the RAC One service name.
-
Cause: The service name provided for RAC One may contain invalid characters.
- INS-35094: Invalid value provided for Oracle RAC One service name.
-
Cause: The domain portion in the Oracle RAC One service name may contain invalid characters.
- INS-35095: The specified domain of the Oracle RAC One service name exceeds 128 characters.
-
Cause: The domain portion entered for Oracle RAC One service name exceeded 128 characters.
- INS-35096: The pluggable database name did not begin with an alphabetic character.
-
Cause: n/a
- INS-35097: The pluggable database name cannot be left blank.
-
Cause: n/a
- INS-35098: Invalid pluggable database name.
-
Cause: The value provided for pluggable database name exceeds string characters.
- INS-35099: The pluggable database name provided is same as the container database name.
-
Cause: n/a
- INS-35100: The Oracle home location contains directories or files on following remote nodes:string.
-
Cause: n/a
- INS-35101: Installer has detected that an Oracle Real Application Cluster (RAC) database with the given Global Database name (string) is already configured on this server.
-
Cause: n/a
- INS-35102: Invalid value specified for Pluggable Database name.
-
Cause: The Specified Pluggable Database name is same as RAC One database service name.
- INS-35171: Target database memory (stringMB) exceeds at least one of the selected nodes available shared memory (stringMB).
-
Cause: The total available shared memory on at least one of the selected nodes (stringMB) was less than the chosen target database memory (stringMB).
- INS-35172: Target database memory (stringMB) exceeds available shared memory (stringMB) on the system.
-
Cause: The total available shared memory (stringMB) on the system was less than the chosen target database memory (stringMB).
- INS-35173: Invalid value for allocated memory.
-
Cause: The allocated memory specified was greater than or equal to the total memory available on the system.
- INS-35174: A minimum of stringMB (string% of total physical memory) is required.
-
Cause: Allocated memory was less than the required memory.
- INS-35175: No value given for the allocated memory of the database.
-
Cause: A value was not specified for the allocated memory of the database.
- INS-35176: Invalid value for allocated memory.
-
Cause: The allocated memory specified was greater than 3GB.
- INS-35205: Specified data file storage location is invalid.
-
Cause: The data file storage location for Oracle Real Application Clusters was not on a shared file system.
- INS-35206: Directory is already in use.
-
Cause: The specified directory for the database files was already in use by the Global database name that was provided.
- INS-35207: The location string you selected is on an Oracle ASM Cluster File System (ACFS).
-
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.
- INS-35208: The location string you selected is on an Oracle ASM Cluster File System (ACFS).
-
Cause: You cannot use ACFS as shared storage for Oracle RAC.
- INS-35209: Selected storage type is not valid.
-
Cause: You cannot use file system storage with Standard Edition Oracle Real Application Clusters databases.
- INS-35210: Installing a database with storage on Oracle Automatic Storage Management (Oracle ASM) is not supported on this system.
-
Cause: Oracle Database 11g Release 2 and later supports Oracle ASM only on 64-bit Windows operating systems.
- INS-35211: Selected storage type is not valid.
-
Cause: n/a
- INS-35255: Invalid password.
-
Cause: One of the Database Administrative account password was either CHANGE_ON_INSTALL or MANAGER or DBSNMP or SYSMAN or PDBADMIN.
- INS-35256: The password for account string is not allowed to be string.
-
Cause: The administrative account password you entered was string which is not allowed for string user.
- INS-35341: The installation user is not a member of the following groups: string
-
Cause: The installation user account must be a member of all groups required for installation.
- INS-35342: The specified group for string may not be defined in the system.
-
Cause: The OS group you specified as string may not be configured on the server, or in the Network Information Service (NIS).
- INS-35343: Invalid value specified for string.
-
Cause: OS group string specified for string contains one or more invalid characters.
- INS-35344: The value is not specified for string.
-
Cause: n/a
- INS-35351: Inconsistent versions detected.
-
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.
- INS-35352: There are no disk groups selected for storage and backup.
-
Cause: n/a
- INS-35354: The system on which you are attempting to install Oracle string is not part of a valid cluster.
-
Cause: Before you can install Oracle string, you must install Oracle Grid Infrastructure (Oracle Clusterware and Oracle ASM) on all servers to create a cluster.
- INS-35355: The node string specified in response file is not part of the Oracle Clusterware detected.
-
Cause: The node list for the Oracle RAC database specified in the response file does not match the configuration stored in the OCR.
- INS-35356: Oracle recommends that you install the database on all nodes that are part of the Oracle Grid Infrastructure cluster.
-
Cause: All Oracle Grid Infrastructure nodes were not selected for installing Oracle RAC.
- INS-35357: Oracle RAC is not supported on this system.
-
Cause: Oracle Database 11g Release 2 and later supports Oracle RAC only on 64-bit Windows operating systems.
- INS-35358: Oracle RAC is not supported on this system.
-
Cause: Oracle Database 11g Release 2 and later supports Oracle RAC only on 64-bit Windows operating systems.
- INS-35359: Only one node is selected for database creation.
-
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.
- INS-35360: No nodes are specified for RAC One Node install.
-
Cause: n/a
- INS-35361: One or more selected nodes are down.
-
Cause: One or more selected nodes cannot be reached
- INS-35362: Admin managed database can not be installed on following set of nodes: string
-
Cause: Admin managed database can be created only on HUB nodes.
- INS-35371: Oracle RAC databases not detected.
-
Cause: The installer could not detect any Oracle Real Application Clusters databases that could be upgraded.
- INS-35372: Oracle RAC databases not detected.
-
Cause: The installer could not detect any Oracle Real Application Clusters databases that could be upgraded on the selected nodes.
- INS-35373: Single-instance database not detected
-
Cause: The installer could not detect a single-instance database that could be upgraded.
- INS-35375: The installer detects an older version of Oracle ASM on the system. If you intend to upgrade a database using Oracle ASM for storage, then you must first upgrade Oracle ASM. Refer to Oracle Grid Infrastructure Installation Guide for further information.
-
Cause: An earlier release version of Oracle Automatic Storage Management (Oracle ASM) is detected on the server.
- INS-35376: Passsword cannot be empty for the ASMSNMP user.
-
Cause: The ASMSNMP user password was not specified.
- INS-35377: An earlier release version of Oracle Automatic Storage Management (Oracle ASM) exists on this system. If you intend to upgrade an earlier release database that uses Oracle ASM to Oracle Database 11g Release 2, then the upgrade will fail on 32-bit systems.
-
Cause: Oracle Database 11g Release 2 and later supports Oracle ASM only on 64-bit Windows operating systems.
- INS-35378: The installer has detected that the configured Oracle Restart software is a release version earlier than the database release you want to install. Oracle Restart must be the same release or a later release than Oracle Database.
-
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).
- INS-35379: The installer has detected that configured Oracle Restart software is not upgraded to current install version.
-
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).
- INS-35380: Installer has detected one or more policy managed databases eligible for upgrade. If you wish to upgrade one of these policy managed databases, it is recommended that you select all the nodes of the Clusterware. This will ensure the database software availability on all the nodes.
-
Cause: n/a
- INS-35421: This option installs a single-instance database only.
-
Cause: You have chosen to perform a Desktop class install on a cluster. This option will not install Oracle RAC.
- INS-35422: The installer has detected that configured Oracle Restart software is not upgraded to current install version. This database installation does not register the database with lower version of High Availability service.
-
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).
- INS-35423: The installer has detected that Oracle Clusterware is not running on local node.
-
Cause: You have chosen to install Oracle RAC when Oracle Clusterware stack is not running on the local node.
- INS-35431: Invalid Location Specified for Oracle home.
-
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.
- INS-35432: The installer has detected that the software location you have specified contains Oracle Database software version string. Oracle recommends that when upgrading to string, you perform an installation of the software into a new Oracle home and then upgrade the database using the new software binaries.
-
Cause: n/a
- INS-35433: The installer has detected that the specified location string is on an Oracle ASM Cluster File System that is not registered as a resource in Oracle Grid Infrastructure.
-
Cause: The specified location string is on an Oracle ASM Cluster File System that is not registered as a resource in Oracle Grid Infrastructure.
- INS-35434: Oracle Home cannot be on Oracle Cluster File System.
-
Cause: Oracle Home provided was detected to be on Oracle Cluster File System.
- INS-35435: Oracle home of the Policy managed database on a Flex Cluster cannot be on ASM Cluster File System.
-
Cause: Oracle home location specified was detected to be on ASM Cluster File System.
- INS-35436: Oracle home of a Software Only database installation cannot be on ASM Cluster File System when LEAF type nodes are chosen for the installation.
-
Cause: Oracle home location specified was detected to be on ASM Cluster File System and LEAF type nodes were chosen for the installation.
- INS-35437: Invalid location specified for Oracle home.
-
Cause: Installer has detected that the location specified for Oracle home is a sub directory under an Automatic Cluster File System(ACFS) mount point that does not provide permissions to your user id.
- INS-35438: The specified software location is found to be on ASM Cluster File System (ACFS) configured to be available only on one node (string). Oracle RAC software can not be installed on a single-node ACFS.
-
Cause: n/a
- INS-35439: The specified base location is found to be on ASM Cluster File System (ACFS) on node (string) and LEAF nodes were selected. Oracle RAC base location can not be installed on ACFS when LEAF nodes are selected.
-
Cause: n/a
- INS-35461: Standard Edition One (SE One) is not supported for this installation.
-
Cause: Standard Edition One (SE One) is not supported for Oracle Real Application Clusters database installation.
- INS-35462: Personal Edition is not supported for this installation.
-
Cause: You selected an Install Edition that is not supported for UNIX or Linux operating systems, and for Oracle RAC installations.
- INS-35463: This option is not supported on Exadata configuration.
-
Cause: n/a
- INS-35464: The installer does not support installing the string of Oracle Database.
-
Cause: n/a
- INS-35481: Server pool name is not specified.
-
Cause: You have not specified a valid name for the server pool.
- INS-35482: Server pool cardinality is invalid.
-
Cause: Server pool cardinality should be a number between string and string
- INS-35483: Server pool name is invalid.
-
Cause: The specified Server pool name contains an invalid character.
- INS-35491: There are no Hub nodes detected in this cluster
-
Cause: Admin-managed Real Application Cluster database can be deployed only on Hub nodes.
- INS-35492: Local node is not a Hub node
-
Cause: Local Node has to be a Hub node in order to deploy a Admin-managed Real Application Cluster database.
- INS-35501: Nodes string specified for addnode are not part of the Clusterware yet. Ensure that the configuration scripts from the Grid Infrastructure home are executed after the database addnode is performed.
-
Cause: n/a
- INS-35502: Cluster nodes string are already having a database software in the same location as local node.
-
Cause: Nodes are already having a database software.
- INS-35503: Nodes string are duplicately specified for addnode operation.
-
Cause: n/a
- INS-35504: Node name cannot be left unfilled.
-
Cause: n/a
- INS-35505: Oracle RAC software location can not be installed on ASM Cluster File System (ACFS) when LEAF nodes are selected. You have selected following LEAF nodes:string
-
Cause: n/a
- INS-35506: Oracle RAC software location can only be installed on ASM Cluster File System (ACFS) on HUB nodes. You have selected following nodes that are not detected to be configured as HUB nodes:string
-
Cause: n/a
- INS-35810: You have selected to use Built-in Account for installation and configuration of Oracle Home. Oracle recommends that you specify a Windows User Account with limited privilege to install and configure a secure Oracle Home.
-
Cause: n/a
- INS-35850: The installer has detected that you are trying to install a cluster database from a leaf node of a Flex cluster.
-
Cause: n/a