99 ORA-60001 to ORA-65535
- ORA-60001: adding (string) blocks to save undo segment in tablespace string with MAXSIZE (string)
-
Cause: Save undo for the offline tablespace at segment MAXSIZE.
- ORA-60002: adding (string) blocks to temporary segment in tablespace string with MAXSIZE (string)
-
Cause: Extending a temporary segment violated MAXSIZE limit.
- ORA-60003: adding (string) blocks to table string.string partition string with MAXSIZE (string)
-
Cause: Extending a table partition violated MAXSIZE limit.
- ORA-60004: adding (string) blocks to table string.string with MAXSIZE (string)
-
Cause: Extending a table violated MAXSIZE limit.
- ORA-60005: adding (string) blocks to cluster string.string with MAXSIZE (string)
-
Cause: Extending a cluster violated MAXSIZE limit.
- ORA-60006: adding (string) blocks to index string.string partition string with MAXSIZE (string)
-
Cause: Extending an index partition violated MAXSIZE limit.
- ORA-60007: adding (string) blocks to index string.string subpartition string with MAXSIZE (string)
-
Cause: Extending an index subpartition violated MAXSIZE limit.
- ORA-60008: adding (string) blocks to index string.string with MAXSIZE (string)
-
Cause: Extending an index violated MAXSIZE limit.
- ORA-60009: adding (string) blocks to LOB segment string.string partition string with MAXSIZE (string)
-
Cause: Extending a LOB segment violated MAXSIZE limit.
- ORA-60010: adding (string) blocks to LOB segment string.string with MAXSIZE (string)
-
Cause: Extending a LOB segment violated MAXSIZE limit.
- ORA-60011: adding (string) blocks to lob segment string.string subpartition string with MAXSIZE (string)
-
Cause: Extending a LOB segment violated MAXSIZE limit.
- ORA-60012: adding (string) blocks to table string.string subpartition string with MAXSIZE (string)
-
Cause: Extending a table subpartition violated MAXSIZE limit.
- ORA-60013: invalid MAXSIZE storage option value
-
Cause: Invalid value was specified for MAXSIZE storage clause.
- ORA-60014: invalid MAXSIZE storage option value
-
Cause: Minimum of 1M should have been specified against the MAXSIZE storage clause.
- ORA-60015: invalid RETENTION storage option value
-
Cause: Value of MIN retention should have been nonzero.
- ORA-60016: Operation not supported on SECUREFILE segment
-
Cause: The operation to ALTER FREELIST/RETENTION was not supported on SECUREFILE segment.
- ORA-60018: adding string blocks to rollback segment string with MAXSIZE (string)
-
Cause: Extending a rollback segment violated MAXSIZE limit.
- ORA-60019: Creating initial extent of size string in tablespace of extent size string
-
Cause: Creation of SECUREFILE segment failed due to small tablespace extent size.
- ORA-60025: Event for temp segment cleanup used for temp lobs
-
Cause: Temp LOB segments used for temporary LOBs are deleted only on session exit which may lead to large amounts of memory being held across multiple sessions.
- ORA-60072: adding (string) blocks to heat map segment with MAXSIZE (string)
-
Cause: Extending the heat map segment violated the MAXSIZE limit.
- ORA-60073: Heat map segment cannot be created
-
Cause: SYSAUX tablespace has uniform extent allocation and the extent size is not a multiple of megabyte.
- ORA-60082: incorrect tablespace specified
-
Cause: Clear free space operation was used on the temporary, undo, or SYSTEM tablespace, which is not supported.
- ORA-60084: inmemory_xmem_size specified is less than a minimum of (string) bytes
-
Cause: inmemory_xmem_size was less than the minimum expected by the system.
- ORA-60085: invalid combination of parameters passed to the DBMS_SPACE_ADMIN function
-
Cause: Object ID could not be specified for undo or save undo segments.
- ORA-60100: dropping temporary tablespace with tablespace ID number (tsn) string is blocked due to sort segments
-
Cause: The temporary tablespace had sort segments in use.
- ORA-60209: invalid value string for parameter string; must be smaller than string%% of available SYSTEM temporary space
-
Cause: The value for this parameter was invalid.
- ORA-60210: specified data file or temporary file size exceeded the maximum allowed size
-
Cause: An attempt was made to resize the data file or temporary file with a value beyond the maximum allowed file size (MAXSIZE).
- ORA-60300: cannot use virtual column as ORDER BY or FILTER BY column of domain index
-
Cause: An attempt was made to create a composite domain index by specifying a virtual column as an ORDER BY or FILTER BY column.
- ORA-60301: cannot create sharded local domain index with indextype string.string
-
Cause: An attempt was made to create local domain indexes on sharded tables that were only allowed for a subset of native indextypes.
- ORA-60302: partition maintenance operation cannot affect more than string partitions in presence of local domain indexes
-
Cause: An invalid number of partitions were specified for a partition maintenance operation. A partition maintenance operation can only affect a maximum number of partitions when there was a local domain index on the table: - One partition or subpartition for ADD PARTITION or ADD SUBPARTITION. - One partition or subpartition for DROP PARTITION or DROP SUBPARTITION. - One partition or subpartition for TRUNCATE PARTITION or TRUNCATE SUBPARTITION. - Two source partitions or subpartitions for MERGE PARTITION or MERGE SUBPARTITION. - Two target partitions or subpartitions for SPLIT PARTITION or SPLIT SUBPARTITION.
- ORA-60303: unsupported partitioning scheme for local domain indexes
-
Cause: Creation of local domain index was not supported for the partitioning scheme of the base table. For referenced partitioned base tables, the parent table was using an unsupported partitioning scheme for local domain indexes.
- ORA-60304: cannot modify partitioning scheme of local domain index string.string
-
Cause: An attempt was made to modify the partitioning scheme of a table with a local domain index to an unsupported configuration.
- ORA-60305: cannot modify local domain index string.string into non-partitioned table
-
Cause: An attempt was made to modify a partitioned table with local domain indexes into a non-partitioned table.
- ORA-60306: ARRAY DML type of indextype must be a VARRAY
-
Cause: An attempt was made to use a type that was not a VARRAY inside the ARRAY DML clause of the CREATE INDEXTYPE or ALTER INDEXTYPE statement.
- ORA-60307: could not validate return type of generic pipelined table function
-
Cause: The ANYTYPE description of the generic pipelined table function was not found or did not describe a collection type.
- ORA-60308: Mismatched data type descriptor from opaque object instance.
-
Cause: The data type descriptor returned by the ODCITABLEFETCH interface inside an ANYDATA or ANYDATASET instance did not match the output data type described by the ODCITABLEDESCRIBE interface.
- ORA-60400: Had error executing RMAN. Error code: string
-
Cause: Had error either when spawning a process to execute RMAN commands or getting RMAN process exit status.
- ORA-60401: RMAN exited with status: string, more details are available in the RMAN output file: string
-
Cause: RMAN process exited with non-zero status.
- ORA-60402: Failed to read RMAN output from scheduler backup job. Log file: string
-
Cause: An error occurred when reading a RMAN output file.
- ORA-60403: Internal error: database connection should be to the shard PDB when PDB name is not provided
-
Cause: An error occurred when updating a sharded database backup wallet.
- ORA-60404: Internal error: database connection should be to the CDB when the shard PDB name is provided
-
Cause: An error occurred when updating a sharded database backup wallet.
- ORA-60405: Internal error: Failed to update backup wallet
-
Cause: An error occurred when updating a sharded database backup wallet.
- ORA-60406: HOST command is not supported when the RMAN command is submitted from GDSCTL command interface.
-
Cause: RMAN command HOST was submitted from GDSCTL.
- ORA-60450: transaction ID specified is not quarantined
-
Cause: The transaction ID (usnslotsqn) specified in the command was not quarantined.
- ORA-60451: unable to recover a quarantined transaction (string.string.string) holding a transaction lock required by this transaction
-
Cause: A quarantined transaction holding a conflicting transaction lock failed to recover.
- ORA-60500: invalid refresh SCN string specified
-
Cause: An attempt was made to refresh the pluggable database to a system change number (SCN) that was less than or equal to the last refresh SCN.
- ORA-60501: insufficient disk space
-
Cause: There was insufficient disk space at the specified location.
- ORA-60502: string is the wrong type of pluggable database
-
Cause: A list of pluggable databases was given to a command but the named one is not of the same type as the earlier ones in the list. The different types are Data Guard pluggable databases and non Data Guard pluggable databases.
- ORA-60503: remote site string not found
-
Cause: An attempt was made to create a standby pluggable database before the remote site had been defined.
- ORA-60504: Missing credential for remote site string
-
Cause: The credential required to access the remote site could not be found.
- ORA-60505: unable to refresh the pluggable database
-
Cause: An attempt was made to refresh a pluggable database (PDB) using a catalog without specifying the source database link name.
- ORA-60506: operation not allowed for standby pluggable database string
-
Cause: An attempt was made to perform an operation on a standby pluggable database (PDB) that was not appropriate for such a PDB.
- ORA-60507: invalid refresh time string specified
-
Cause: An attempt was made to refresh the pluggable database to a time that was less than or equal to the last refresh time.
- ORA-60508: invalid refresh SCN string specified. Max possible refresh SCN string
-
Cause: An attempt was made to refresh the pluggable database to a system change number (SCN) that was greater than the source Container Database's (CDB) current SCN or the maximum SCN of the archive logs available in the refresh catalog or in the remote_recovery_file_dest
- ORA-60509: invalid refresh time string specified. Max possible refresh time string
-
Cause: An attempt was made to refresh the pluggable database to a time that was greater than the source Container Database's (CDB) current time or the maximum time of the archive logs available in the refresh catalog or in the remote_recovery_file_dest
- ORA-60510: encountered an error during Replay Upgrade
-
Cause: An error was encountered during Replay Upgrade of a pluggable database (PDB).
- ORA-60511: missing or invalid application name
-
Cause: A valid application name was not present where required.
- ORA-60512: invalid source for a standby pluggable database
-
Cause: An attempt was made to create a standby pluggable database from an inappropriate source pluggable database, such as an existing standby pluggable database.
- ORA-60513: cannot synchronize an application version or patch that is blocked
-
Cause: An attempt was made to synchronize an application version or patch that was blocked.
- ORA-60514: implicit application common user cannot own common objects
-
Cause: An attempt was made to set the sharing status to metadata, data, or extended data on an object owned by an implicit user.
- ORA-60515: standby pluggable database string requires more recovery
-
Cause: An attempt was made to open a standby pluggable database (PDB) before recovery had applied sufficient redo from the primary to make the PDB consistent.
- ORA-60516: Pluggable database (PDB) string has a per PDB physical standby
-
Cause: An attempt was made to drop a pluggable database (PDB) that was protected by one or more per PDB physical standbys.
- ORA-60517: Unimplemented operation for pluggable database string
-
Cause: An attempt was made to perform an operation on the pluggable database (PDB) that had not yet been implemented.
- ORA-60518: cannot enable per PDB supplemental logging without local undo enabled
-
Cause: Local undo mode was disabled.
- ORA-60519: encountered an error during application sync
-
Cause: An error was encountered during application sync.
- ORA-60520: unable to switchover when a TDE SEPS wallet is not configured
-
Cause: This operation could not be completed because Transparent Data Encryption (TDE) Secure External Password Store (SEPS) wallet was not configured.
- ORA-60521: operation not allowed due to lockdown
-
Cause: Lockdown is enforced to disallow the operation, as configured by the administrator.
- ORA-60522: unable to create pluggable database using XML
-
Cause: An attempt was made to create a pluggable database using XML with a fuzzy data file.
- ORA-60523: invalid pluggable database name specified for root clone
-
Cause: The pluggable database specified for USING ROOT CLONE was either nonexistent or not a root clone.
- ORA-60524: too many database links in use
-
Cause: The pluggable database exceeded the maximum open links.
- ORA-60526: cannot switch to shared undo mode when perPDB supplemental logging is enabled
-
Cause: Supplemental logging is disabled at CDB$ROOT container but enabled at pluggable databases (PDBs). Switching to shared undo mode would cause PDB-level supplemental logging to be lost.
- ORA-60527: cannot externally modify partition containing dblink
-
Cause: An attempt was made to external modify a partition containing a dblink.
- ORA-60528: operation not supported for a PET having all dblink partition
-
Cause: An attempt was made to perform an operation on a Partition External Table (PET) having all dblink partition.
- ORA-60529: more than one database link specified
-
Cause: Only one value of database link is allowed for database link location.
- ORA-60530: cannot exchange partition containing dblink
-
Cause: An attempt was made to exchange a partition containing a dblink
- ORA-60600: maximum number of columns in a table or view is 1000
-
Cause: An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit.
- ORA-61800: invalid boolean literal: string
-
Cause: The specified boolean literal was invalid.
- ORA-61801: only boolean column can be used as a predicate
-
Cause: The specified column was not a boolean column and could not be used as a predicate.
- ORA-61803: argument of string must be a column or an expression of boolean data type
-
Cause: The specified argument of the IS [NOT] {TRUE|FALSE} clause was not a boolean column or a boolean expression.
- ORA-61804: boolean data type is invalid for an arithmetic function or operation
-
Cause: Boolean data type is not valid arithmetic functions or operations
- ORA-61805: invalid boolean value: string
-
Cause: The specified boolean value was invalid.
- ORA-61850: Oracle version mismatch between primary database and active data cache.
-
Cause: Oracle primary database received an unsupported message format from active data cache, or vice versa.
- ORA-61851: Active data cache instance does not allow string operation.
-
Cause: The specified operation was invalid on active data cache instance.
- ORA-61852: CREATE ACTIVE DATA CACHE failed.
-
Cause: An error occurred during the creation of the active data cache
- ORA-61853: Cannot start active data cache.
-
Cause: An error occurred during database open on active data cache
- ORA-61854: Cannot start active data cache with non active data cache control file.
-
Cause: There was an error when the database or control file was created or you are using the wrong control file
- ORA-61855: Invalid ACTIVE_DATA_CACHE_CONFIG.
-
Cause: Invalid attributes for ACTIVE_DATA_CACHE_CONFIG.
- ORA-61856: Failed to boot or create active data cache because the parameter string is not set.
-
Cause: Active data cache requires a minimum set of parameters to be set.
- ORA-61857: Communication with the primary failed.
-
Cause: The process lost connection with the primary.
- ORA-61858: Unable to translate FAL_SERVER initialisation parameter string.
-
Cause: Invalid connect string specified in fal_server.
- ORA-61859: There was en error when executing a remote procedure call at primary server string.
-
Cause: The primary server failed to return the resquested information.
- ORA-62001: value for parameter cannot contain a comma
-
Cause: Parameter value contained a comma.
- ORA-62002: circular dependency error while evaluating expression string for parameter string
-
Cause: One or more of the parameters used in the expression value was dependent on the parameter being set.
- ORA-62003: parameter set completed with errors in (string) pluggable database(s)
-
Cause: Parameter value was invalid or illegal for one or more pluggable databases.
- ORA-62007: Encountered a value of unsupported type or size for XPath (string)
-
Cause: Encountered a value of unsupported type in a SQL/XML DML operator. SQL/XML operators, such as UPDATEXML, expect value operands of type VARCHAR2 and XMLTYPE. XML DML replication is not supported for SQL/XML DML operators with values of unsupported types or very large values of supported types.
- ORA-62008: Cannot rewrite a newer version of XML redo diff (encountered: string, supported: string)
-
Cause: Encountered a newer version of XML redo diff that is not supported.
- ORA-62009: cannot encode an invalid XML character 0xstring in supplemental log
-
Cause: An attribute was being populated or updated with characters which are not valid for XML and therefore could not be supplementally logged.
- ORA-62035: KEY VECTOR duplication failed
-
Cause: Parallel query failed to duplicate KEY VECTOR across Oracle RAC instances.
- ORA-62036: out of memory for KEY VECTOR
-
Cause: A query undergoing vector transform ran out of memory in an unrecoverable way. This may indicate that poor statistics caused vector transform to be used for an unsuitable query.
- ORA-62037: KEY VECTOR with repeated values require join keys to match
-
Cause: A KEY VECTOR with repeated join key values required the JOIN KEYS of SYS_OP_KEY_VECTOR_PAYLOAD to match the JOIN KEYS of the related SYS_OP_KEY_VECTOR_USE.
- ORA-62038: missing GROUP BY clause in statement containing KEY VECTOR function
-
Cause: A statement containing a KEY VECTOR function did not have a GROUP BY clause.
- ORA-62039: KEY VECTOR function not allowed in WHERE clause
-
Cause: The WHERE clause contained one of the following KEY VECTOR functions, which are not allowed in the WHERE clause: SYS_OP_KEY_VECTOR_CREATE, SYS_OP_KEY_VECTOR_USE, SYS_OP_KEY_VECTOR_SUCCEEDED, SYS_OP_KEY_VECTOR_PAYLOAD.
- ORA-62040: KEY VECTOR ID string is used in more than one SYS_OP_KEY_VECTOR_CREATE
-
Cause: More than one SYS_OP_KEY_VECTOR_CREATE had the same ID.
- ORA-62041: SYS_OP_KEY_VECTOR_USE does not have a corresponding SYS_OP_KEY_VECTOR_CREATE
-
Cause: A SYS_OP_KEY_VECTOR_USE function did not have a corresponding SYS_OP_KEY_VECTOR_CREATE.
- ORA-62042: The load key defined in SYS_OP_KEY_VECTOR_CREATE is missing a corresponding SYS_OP_KEY_VECTOR_PAYLOAD function
-
Cause: A load key defined in a SYS_OP_KEY_VECTOR_CREATE function had no corresponding SYS_OP_KEY_VECTOR_PAYLOAD function.
- ORA-62043: The SYS_OP_KEY_VECTOR function is missing a corresponding SYS_OP_KEY_VECTOR_CREATE or SYS_OP_KEY_VECTOR_USE
-
Cause: A SYS_OP_KEY_VECTOR_PAYLOAD or SYS_OP_KEY_VECTOR_SUCCEEDED function had no corresponding SYS_OP_KEY_VECTOR_CREATE or SYS_OP_KEY_VECTOR_USE function.
- ORA-62044: The SYS_OP_KEY_VECTOR_PAYLOAD load key does not exist.
-
Cause: The load index specified in a SYS_OP_KEY_VECTOR_PAYLOAD function did not exist.
- ORA-62045: KEY VECTOR could not be loaded from disk
-
Cause: The process ran out of memory (PGA) while loading a paged KEY VECTOR from disk.
- ORA-62081: duplicate or conflicting VECTOR ENCODE or NO VECTOR ENCODE specifications
-
Cause: The specifications were either a duplicate of each other or were conflicting.
- ORA-62082: VECTOR ENCODE only valid for Oracle number column
-
Cause: VECTOR ENCODE was specified on a column that is not an Oracle number.
- ORA-62083: operation not allowed for system hidden virtual column
-
Cause: The system hidden virtual columns could not be dropped or modified directly.
- ORA-62085: invalid value while deserializing
-
Cause: The value being deserialized was invalid.
- ORA-62131: MEMOPTIMIZE FOR WRITE feature cannot be enabled on IOTs.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on index-organized tables (IOT).
- ORA-62132: MEMOPTIMIZE FOR WRITE feature cannot be enabled on TEMPORARY TABLE.
-
Cause: An attempt was made to CREATE TEMPORARY TABLE with MEMOPTIMIZE FOR WRITE feature.
- ORA-62133: MEMOPTIMIZE FOR READ feature is not supported on ADG.
-
Cause: An attempt was made to populate data into hash index when in Active Data Guard mode.
- ORA-62134: MEMOPTIMIZE FOR READ feature cannot be used on table with ROW MOVEMENT enabled.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with row movement enabled.
- ORA-62135: Specified schema name is invalid.
-
Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with an invalid schema name.
- ORA-62136: Specified table name is invalid.
-
Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with an invalid table name.
- ORA-62137: Specified schema and table names are either non-existent or MEMOPTIMIZE FOR READ is not enabled on the table.
-
Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with invalid information. Either the specified schema and table names are non-existent or MEMOPTIMIZE FOR READ feature is not enabled on the table.
- ORA-62138: MEMOPTIMIZE memory area does not exist.
-
Cause: An attempt was made to use the DBMS_MEMOPTIMIZE package without creating the MEMOPTIMIZE memory area.
- ORA-62139: MEMOPTIMIZE_WRITE hint disallowed for this operation
-
Cause: MEMOPTIMIZE_WRITE hint was specified for the operation.
- ORA-62141: MEMOPTIMIZE FOR READ feature cannot be used with COMPRESS option
-
Cause: An attempt was made to use the COMPRESS option with MEMOPTIMIZE FOR READ feature.
- ORA-62142: MEMOPTIMIZE FOR READ feature requires NOT DEFERRABLE PRIMARY KEY constraint on the table
-
Cause: An attempt was made to use MEMOPTIMIZE FOR READ on a table that did not have the PRIMARY KEY constraint or the PRIMARY KEY constraint is DEFERRABLE.
- ORA-62143: MEMOPTIMIZE FOR WRITE feature not allowed on table with trigger.
-
Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with trigger.
- ORA-62144: MEMOPTIMIZE FOR WRITE feature not allowed on table with foreign key constraint.
-
Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with foreign key constraint.
- ORA-62145: MEMOPTIMIZE FOR WRITE feature not allowed on segment with deferred storage.
-
Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with deferred storage.
- ORA-62146: MEMOPTIMIZE FOR WRITE feature cannot be used with COMPRESS option.
-
Cause: An attempt was made to use the COMPRESS option with MEMOPTIMIZE FOR WRITE feature.
- ORA-62147: MEMOPTIMIZE FOR READ operations are not allowed at PARTITION or SUBPARTITION levels.
-
Cause: An attempt was made to use MEMOPTIMIZE FOR READ option on a PARTITION table or SUBPARTITION table level.
- ORA-62148: MEMOPTIMIZE FOR READ feature cannot be enabled on IOTs.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on index-organized tables (IOT).
- ORA-62149: MEMOPTIMIZE FOR READ feature cannot be enabled on table with VIRTUAL COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with VIRTUAL COLUMNS.
- ORA-62150: MEMOPTIMIZE FOR READ feature cannot be enabled on table with INVISIBLE COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with INVISIBLE COLUMNS.
- ORA-62151: The MEMOPTIMIZE FOR READ feature cannot be enabled on a table with specified partitioning type.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with an unsupported partitioning type.
- ORA-62152: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with LOBs.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with LOB columns.
- ORA-62153: BLOCK SIZE is not equal to DB_BLOCK_SIZE setting.
-
Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure on a tablespace whose BLOCK SIZE was not equal to DB_BLOCK_SIZE.
- ORA-62154: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with VIRTUAL COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with VIRTUAL COLUMNS.
- ORA-62155: MEMOPTIMIZE FOR READ feature cannot be enabled on table with LOBs.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with LOB columns.
- ORA-62156: MEMOPTIMIZE FOR READ feature not allowed on segment with deferred storage
-
Cause: An attempt was made to set the MEMOPTIMIZE FOR READ attribute on a table with deferred storage.
- ORA-62157: MEMOPTIMIZE FOR READ clause needs to be specified only once.
-
Cause: An attempt was made to use MEMOPTIMIZE FOR READ clause more than once.
- ORA-62158: MEMOPTIMIZE FOR WRITE clause needs to be specified only once.
-
Cause: An attempt was made to use MEMOPTIMIZE FOR WRITE clause more than once.
- ORA-62159: MEMOPTIMIZE FOR READ cannot be enabled by CREATE PARTITIONED TABLE.
-
Cause: An attempt was made to CREATE PARTITIONED table with MEMOPTIMIZE FOR READ enabled.
- ORA-62160: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with INVISIBLE COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with INVISIBLE COLUMNS.
- ORA-62161: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with default valued COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with COLUMNS with default values.
- ORA-62162: MEMOPTIMIZE FOR WRITE operations are not allowed at PARTITION or SUBPARTITION levels.
-
Cause: An attempt was made to use MEMOPTIMIZE FOR WRITE option on a PARTITION table or SUBPARTITION table level.
- ORA-62164: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with ENCRYPTED COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with ENCRYPTED COLUMNS.
- ORA-62165: MEMOPTIMIZE FOR WRITE cannot be enabled on table with specified partitioning type.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with an unsupported partitioning type.
- ORA-62166: MEMOPTIMIZE FOR WRITE cannot be enabled by CREATE PARTITIONED TABLE.
-
Cause: An attempt was made to CREATE PARTITIONED table with MEMOPTIMIZE FOR WRITE enabled.
- ORA-62167: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with COLLATED COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with COLLATED COLUMNS.
- ORA-62168: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with UNUSED COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with UNUSED COLUMNS.
- ORA-62169: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with OID COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with OID COLUMNS.
- ORA-62170: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with unsupported COLUMN type.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with unsupported COLUMN type.
- ORA-62171: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with XML COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with XML COLUMNS.
- ORA-62172: MEMOPTIMIZE FOR WRITE feature cannot be enabled on table in encrypted tablespace.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table in encrypted tablespace.
- ORA-62173: MEMOPTIMIZE FOR WRITE feature cannot be enabled on materialized view log
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a materialized view log.
- ORA-62174: MEMOPTIMIZE FOR READ feature cannot be enabled on table with ENCRYPT COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with encrypted columns.
- ORA-62175: MEMOPTIMIZE FOR READ feature cannot be enabled on table with XML COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with XML COLUMNS.
- ORA-62176: MEMOPTIMIZE FOR READ feature cannot be enabled on table with UNUSED COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with UNUSED COLUMNS.
- ORA-62177: MEMOPTIMIZE FOR READ feature cannot be enabled on table with unsupported COLUMN type.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with unsupported COLUMN type.
- ORA-62178: MEMOPTIMIZE FOR READ feature cannot be enabled on table with COLLATED COLUMNS.
-
Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with COLLATED COLUMNS.
- ORA-62179: MEMOPTIMIZE FOR READ feature cannot be enabled on TEMPORARY TABLE.
-
Cause: An attempt was made to CREATE TEMPORARY TABLE with MEMOPTIMIZE FOR READ feature.
- ORA-62180: MEMOPTIMIZE FOR WRITE unsupported DDL.
-
Cause: Unsupported DDL on MEMOPTIMIZE FOR WRITE table.
- ORA-62181: The MEMOPTIMIZE FOR READ feature is not supported on this table.
-
Cause: An attempt was made to enable the MEMOPTIMIZE FOR READ feature on an unsupported table.
- ORA-62182: external partitions not supported with MEMOPTIMIZE FOR WRITE
-
Cause: An attempt was made to use external partition with a MEMOPTIMIZE FOR WRITE table.
- ORA-62183: out of memory for MEMOPTIMIZE area
-
Cause: MEMOPTIMIZE memory area was full and did not have any free buffers.
- ORA-62184: bitmap index not supported with MEMOPTIMIZE FOR WRITE
-
Cause: An attempt was made to use a bitmap index with a MEMOPTIMIZE FOR WRITE table.
- ORA-62185: materialized view log cannot be created on a MEMOPTIMIZE FOR WRITE table
-
Cause: An attempt was made to create a materialized view log on a MEMOPTIMIZE FOR WRITE table.
- ORA-62186: online index build or rebuild not supported with MEMOPTIMIZE FOR WRITE
-
Cause: An attempt was made to build an index online with a MEMOPTIMIZE FOR WRITE table.
- ORA-62187: timeout occurred while waiting for lock to flush object string data object string
-
Cause: While waiting to lock a memoptimize flush object, a timeout occurred .
- ORA-62231: DESC is missing in ORDER BY clause within APPROX_RANK.
-
Cause: The DESC keyword was not specified in the ORDER BY clause within the APPROX_RANK function.
- ORA-62232: Invalid expression used in ORDER BY clause within APPROX_RANK.
-
Cause: An invalid expression was used in the ORDER BY clause within the APPROX_RANK function.
- ORA-62233: Multiple expressions were used in the ORDER BY clause within the APPROX_RANK function.
-
Cause: Multiple expressions are used in ORDER BY clause within APPROX_RANK.
- ORA-62234: The APPROX_RANK functions used different PARTITION BY keys.
-
Cause: APPROX_RANK functions use different PARTITION BY keys.
- ORA-62235: PARTITION BY key in APPROX_RANK is not a subset of GROUP BY key.
-
Cause: The PARTITION BY key in the APPROX_RANK function was not a subset of the key in the GROUP BY clause.
- ORA-62236: Missing GROUP BY clause when approximate top functions are used.
-
Cause: The GROUP BY clause was missing when the approximate top functions were used.
- ORA-62237: Missing HAVING clause when approximate top functions are used.
-
Cause: The HAVING clause was missing when the approximate top functions were used.
- ORA-62238: Mixed approximate top functions with window functions or non approximate top functions.
-
Cause: An attempt was made to use window functions or aggregates that were not approximate top functions along with approximate top functions.
- ORA-62239: More than one expression appears in GROUP BY clause but not in PARTITION BY clause.
-
Cause: An attempt was made to involve more than one columns as the top N key.
- ORA-62240: Missing one or more corresponding APPROX_RANK clause in HAVING list when approximate top functions are used.
-
Cause: One or more corresponding APPROX_RANK clauses were missing when approximate top functions were used.
- ORA-62242: HAVING clause can only contain AND predicates when approximate top functions are used.
-
Cause: the HAVING clause contained predicates other than AND when approximate top functions were used.
- ORA-62243: Each predicate in HAVING clause must be in the format of 'APPROX_RANK(PARTITION BY ... ORDER BY ... DESC) <(=) n' when approximate top functions are used.
-
Cause: Illegal predicates were used in the HAVING clause when approximate top functions were used.
- ORA-62244: GROUPING SETS, CUBE and ROLLUP cannot be applied to approximate functions.
-
Cause: An attempt was made to use GROUPING SETS, CUBE or ROLLUP over the approximate functions.
- ORA-62245: A negative value has been passed to APPROX_SUM function.
-
Cause: An attempt was made to pass a negative value to the APPROX_SUM function.
- ORA-62246: The subqueries that contain approximate top functions must be unnested.
-
Cause: An attempt was made to execute subqueries that contain approximate top functions without unnesting.
- ORA-62251: The Nest handle is invalid.
-
Cause: The Nest handle was not valid.
- ORA-62252: The Nest open failed.
-
Cause: The Nest open failed.
- ORA-62253: The Nest is already opened.
-
Cause: An attempt was made to open a Nest that was already opened.
- ORA-62254: The Nest lookup failed.
-
Cause: The Nest lookup for a given pluggable database (PDB) failed.
- ORA-62255: A Child Nest is present.
-
Cause: An attempt to delete a Nest that had a dependent child Nest failed.
- ORA-62256: failure to delete a Nest that is not created
-
Cause: An attempt to delete a Nest that was not created failed.
- ORA-62257: The Nest is already created.
-
Cause: An attempt was made to create a Nest that was already created.
- ORA-62258: The Nest creation failed.
-
Cause: The Nest creation failed with an operating system operation.
- ORA-62259: failure to open a Nest that was not created
-
Cause: An attempt to open the Nest before it was created failed.
- ORA-62260: The Nest open failed.
-
Cause: The Nest open failed with an operating system operation.
- ORA-62261: failure to update a Nest that is not opened
-
Cause: An attempt to update a Nest that was not opened failed.
- ORA-62262: The Nest update failed.
-
Cause: The Nest update failed with an operating system operation.
- ORA-62263: failure to close a Nest that is not opened
-
Cause: An attempt to close a Nest that was not open failed.
- ORA-62264: The Nest close failed.
-
Cause: The Nest close failed with an operating system operation.
- ORA-62265: The Nest delete failed.
-
Cause: The Nest delete failed with an operating system operation.
- ORA-62266: dedicated broker not enabled
-
Cause: Nest connections require an enabled dedicated broker. The dedicated broker was not enabled in the current instance.
- ORA-62267: invalid Nest parameter
-
Cause: An invalid value or length for the Nest parameter was specified.
- ORA-62268: The Nest creation failed due to reaching the maximum depth.
-
Cause: The child Nest could not be created due to reaching the maximum depth.
- ORA-62269: no PDB nest found for specified PDB
-
Cause: A pluggable database (PDB) nest was not found for the specified PDB.
- ORA-62270: connection outside PDB nest
-
Cause: The current pluggable database (PDB) connection was outside of the PDB nest.
- ORA-62271: connection outside CDB or PDB nests
-
Cause: The current connection was outside of the multitenant container database (CDB) or pluggable database (PDB) nests.
- ORA-62301: invalid statistic group handle
-
Cause: The statistic group handle was invalid.
- ORA-62302: invalid statistic group identifier
-
Cause: The statistic group identifier doesn't match the handle.
- ORA-62303: statistic group handle mismatch
-
Cause: Specified statistic group handle is wrong.
- ORA-62304: statistic group invalid string
-
Cause: An invalid parameter was passed to statistic group layer.
- ORA-62346: Extent allocation failed
-
Cause: PGA extent allocation in unified memory failed
- ORA-62350: invalid extent ownership
-
Cause: The current process did not own the extent.
- ORA-62351: invalid MEMORY_SIZE
-
Cause: The specified value of MEMORY_SIZE was more than maximum allowable size.
- ORA-62352: cannot dynamically set MEMORY_SIZE if not set at startup
-
Cause: MEMORY_SIZE was not set at instance startup.
- ORA-62353: cannot shrink MEMORY_SIZE
-
Cause: The new value of MEMORY_SIZE was less than its current value.
- ORA-62354: cannot set MEMORY_SIZE to zero
-
Cause: The new value of MEMORY_SIZE was not valid and will dynamically disable Unified Memory.
- ORA-62355: MEMORY_SIZE is invalid due to insufficent large pages
-
Cause: Not enough large pages were available for the new system global area (SGA) size.
- ORA-62400: invalid options were specified for FUZZY_MATCH operator
-
Cause: The options specified for FUZZY_MATCH() were invalid. For instance, RELATE_TO_SHORTER and UNSCALED options were mutually exclusive. EDIT_TOLERANCE option could only be applied to WHOLE_WORD_MATCH.
- ORA-62401: invalid numeric argument was specified for FUZZY_MATCH operator
-
Cause: The numeric argument passed into FUZZY_MATCH() was either not a constant or was outside the acceptable range. EDIT_TOLERANCE percentage should be between 0-99.
- ORA-62402: invalid numeric argument is specified for PHONIC_ENCODE operator
-
Cause: The numeric argument passed into PHONIC_ENCODE() was either not a constant or was outside the acceptable range. Maximum output code length is 12.
- ORA-62403: string argument specified for FUZZY_MATCH operator was too long
-
Cause: The string argument passed into FUZZY_MATCH() was longer than 4000 bytes. Maximum input length is 4000 bytes.
- ORA-62404: options for FUZZY_MATCH were specified in the wrong order
-
Cause: EDIT_TOLERANCE option passed into FUZZY_MATCH() has to appear before options such as RELATE_TO_SHORTER and UNSCALED.
- ORA-62500: function is not allowed outside of MATCH_RECOGNIZE clause
-
Cause: The function was specified outside of the MATCH_RECOGNIZE clause. This function is only allowed in the MATCH_RECOGNIZE clause.
- ORA-62501: invalid value specified for bounded quantifier in MATCH_RECOGNIZE clause
-
Cause: The specified lower bound or upper bound value was greater than UB4MAXVAL. The lower bound value must be non-negative. The upper bound value must be strictly positive. The upper bound value must be greater than or equal to the lower bound value.
- ORA-62502: invalid variable name
-
Cause: The specified variable name was invalid. Variable names are not allowed to be "^", "$", or "*".
- ORA-62503: illegal variable definition
-
Cause: The specified variable definition was invalid. Variables defined in the DEFINE clause must be in the PATTERN clause. Variables defined in the SUBSET clause cannot be in the PATTERN clause. Variables cannot be defined twice either in the SUBSET clause or the DEFINE clause.
- ORA-62504: illegal variable reference
-
Cause: The referenced variable was invalid. Variables referenced in the SUBSET clause must be in the PATTERN clause. Variables referenced in the DEFINE clause, the MEASURES clause, and the AFTER MATCH SKIP TO must be in the PATTERN clause or defined in the SUBSET clause.
- ORA-62505: expression needs to be aliased
-
Cause: The expression was not aliased. MEASURES clause items have to be aliased.
- ORA-62506: illegal nesting of operators in MATCH_RECOGNIZE clause
-
Cause: An attempt was made to nest aggregates/FIRST/LAST/PREV/NEXT. Aggregates/FIRST/LAST/PREV/NEXT cannot be nested. The only exception allowed is PREV/NEXT(FIRST/LAST()).
- ORA-62507: illegal use of MATCH_NUMBER or CLASSIFIER in MATCH_RECOGNIZE clause
-
Cause: An attempt was made to use MATCH_NUMBER or CLASSIFIER in the MATCH_RECOGNIZE clause. CLASSIFIER and MATCH_NUMBER can only be used in the MEASURES clause. CLASSIFIER and MATCH_NUMBER cannot be used inside aggregates/FIRST/LAST/PREV/NEXT.
- ORA-62508: illegal use of aggregates or navigation operators in MATCH_RECOGNIZE clause
-
Cause: An attempt was made to define aggregates/FIRST/LAST/PREV/NEXT over multiple variables. Aggregates/FIRST/LAST/PREV/NEXT cannot be defined over multiple variables.
- ORA-62509: illegal use of RUNNING or FINAL in MATCH_RECOGNIZE clause
-
Cause: An attempt was made to use RUNNING or FINAL in MATCH_RECOGNIZE. RUNNING or FINAL can only be used on aggregate/FIRST/LAST. FINAL aggregate/FIRST/LAST is not allowed in the DEFINE clause.
- ORA-62510: Correlated subqueries are not allowed in MATCH_RECOGNIZE clause.
-
Cause: An attempt was made to use correlated subqueries in the MATCH_RECOGNIZE clause. Correlated subqueries are currently not allowed in the MATCH_RECOGNIZE clause.
- ORA-62511: Correlation variables are not allowed in MATCH_RECOGNIZE clause.
-
Cause: An attempt was made to use correlation variables in the MATCH_RECOGNIZE clause. Correlation variables are currently not allowed in the MATCH_RECOGNIZE clause.
- ORA-62512: This aggregate is not yet supported in MATCH_RECOGNIZE clause.
-
Cause: An unsupported aggregate was specified in the MATCH_RECOGNIZE clause. Only COUNT, SUM, AVG, MIN, and MAX are currently supported in the MATCH_RECOGNIZE clause. Distinct aggregates are currently not supported in the MATCH_RECOGNIZE clause.
- ORA-62513: Quantified subpatterns that can have empty matches are not yet supported.
-
Cause: There were empty matches for the quantified subpattern in the PATTERN clause. Quantified subpatterns are currently required to match one or more rows.
- ORA-62514: AFTER MATCH SKIP TO variable is not bounded in the match found.
-
Cause: AFTER MATCH SKIP TO variable was not bound in the match found due to pattern operators such as |, *, ?, and so on.
- ORA-62515: Exclusion syntax cannot be used with WITH UNMATCHED ROWS.
-
Cause: An attempt was made to use exclusion syntax with WITH UNMATCHED ROWS. Exclusion syntax {- -} cannot be used with WITH UNMATCHED ROWS.
- ORA-62516: The PARTITION BY, ORDER BY, or MEASURES clause is too large for MATCH_RECOGNIZE.
-
Cause: The number of items in PARTITION BY, ORDER BY, or MEASURES clause exceeded the maximum allowed. There cannot be more than UB2MAXVAL elements in PARTITION BY, ORDER BY, or MEASURES clause.
- ORA-62517: Next match starts at the same point last match started.
-
Cause: AFTER MATCH SKIP TO option repositioned the next match at the start of the previous one resulting in an infinite loop.
- ORA-62518: MATCH_RECOGNIZE pattern is too large.
-
Cause: MATCH_RECOGNIZE pattern was too large. More than UB2MAXVAL elements in alternation, concatenation, or permute, or more than UB4MAXVAL states in the state machine are currently not supported. Permute with more than 7 elements or bounded quantifier bound greater than 200 are also currently not supported.
- ORA-62519: Subquery inside MATCH_RECOGNIZE cannot contain MATCH_RECOGNIZE.
-
Cause: An attempt was made to use a subquery containing a MATCH_RECOGNIZE clause inside a MATCH_RECOGNIZE clause. Subqueries containing MATCH_RECOGNIZE clauses are currently not allowed in the MATCH_RECOGNIZE clause.
- ORA-62520: illegal offset for MATCH_RECOGNIZE navigation operators
-
Cause: An attempt was made to use something other than a constant or a bind variable as the offset for MATCH_RECOGNIZE navigation operators FIRST, LAST, PREV, or NEXT. Offset for MATCH_RECOGNIZE navigation operators have to be constants or bind variables.
- ORA-62521: MATCH_RECOGNIZE is not supported on lateral views
-
Cause: An attempt was made to use MATCH_RECOGNIZE on a lateral view, which is not supported.
- ORA-62550: Invalid SQL ROW LIMITING expression was specified.
-
Cause: The SQL ROW LIMITING expression contained components other than literals, binds, correlation variables, or subqueries.
- ORA-62555: Invalid use of PARTITION BY or ORDER BY clause.
-
Cause: Either the PARTITION BY or ORDER BY was specified on more than one argument of a POLYMORPHIC TABLE FUNCTION.
- ORA-62556: Incorrect use of COLUMNS operator.
-
Cause: COLUMNS function was used outside a POLYMORPHIC TABLE FUNCTION.
- ORA-62557: Invalid use of POLYMORPHIC TABLE FUNCTION.
-
Cause: POLYMORPHIC TABLE FUNCTION was specified inside RECURSIVE WITH clause.
- ORA-62558: Unsupported data types (string) for polymorphic table function
-
Cause: Non-scalar data types were used in polymorphic table function. Only scalar data types are supported.
- ORA-62559: Data types mismatch (string<==>string) for polymorphic table function
-
Cause: Data types for the source and target did not match for polymorphic table function. In Get_Col and Put_Col APIs, both the type of the collection element and the type of the polymorphic table function column must match.
- ORA-62560: Duplicate column name (string)
-
Cause: The new column name already existed as a passthrough column in the polymorphic table function.
- ORA-62561: Invalid column ID (string) in Get_Col or Put_Col
-
Cause: The column number specified in the Get_Col or Put_Col API for polymorphic table functions was incorrect.
- ORA-62562: The API string can be called only during execution time of a polymorphic table function.
-
Cause: This API was called in a context other than the execution time context of a polymorphic table function. This API is not supported in this context.
- ORA-62563: typecode not set for a new column in the polymorphic table function
-
Cause: The type of this new column was not set.
- ORA-62564: This new column name (string) already exists.
-
Cause: This new column name was already created during the describe phase and therefore it is a duplicate column name.
- ORA-62565: The string method failed with error(s). string
-
Cause: This method of polymorphic table function had error(s) during SQL compilation.
- ORA-62566: One of the new column names is a zero-length identifier.
-
Cause: A zero-length identifier was used as a new column name that was created during the describe phase.
- ORA-62567: One of the new column names is too long.
-
Cause: An identifier with more than 128 bytes was used for one of the new column names that was created during the describe phase.
- ORA-62568: invalid use of PARTITION BY or ORDER BY clause
-
Cause: Either the PARTITION BY or the ORDER BY clause was specified on an argument of a non-table semantic POLYMORPHIC TABLE FUNCTION.
- ORA-62569: nested polymorphic table function is disallowed
-
Cause: A polymorphic table function was specified as an argument of a table function.
- ORA-62570: new column name (string) is invalid
-
Cause: The new column name was invalid. It should be valid Oracle identifier and should not be an Oracle reserved word.
- ORA-62571: new column (string) has length (string) that is greater than the maximum allowed length (string)
-
Cause: The length specified for a new column for the polymorphic table function was greater than the maximum allowed length.
- ORA-62572: object views are not supported with polymorphic table functions
-
Cause: An object view was being created with polymorphic table function in the select query.
- ORA-62573: new column (string) is not allowed with describe only polymorphic table function
-
Cause: The new column name was created in describe only polymorphic table function.
- ORA-62574: row replication flag was not set
-
Cause: A row replication API was called, but the Describe method set ROW_REPLICATION to FALSE (default).
- ORA-62575: more than one parameter of TABLE type is not allowed
-
Cause: An attempt was made to use more than one argument with TABLE or DBMS_TF.TABLE_T as the type specification.
- ORA-62576: target size(string) is smaller than source size(string) for column(string) in string
-
Cause: When reading a column from database or writing a column to the database, destination buffer should not be smaller than the source.
- ORA-62577: character set IDs do no match string
-
Cause: When reading a column from the database or writing a column to the database, character set did not match.
- ORA-62578: cursor expressions are not allowed with polymorphic table functions
-
Cause: A cursor expression was used as an argument to polymorphic table function.
- ORA-62600: Invalid value is passed to a bitmap operator.
-
Cause: An attempt was made to pass an invalid value to a bitmap operator.
- ORA-62601: invalid size value for BITMAP_BUCKET_NUMBER or BITMAP_BIT_POSITION operator
-
Cause: An attempt was made to pass an invalid size value for a BITMAP_BUCKET_NUMBER or BITMAP_BIT_POSITION operator.
- ORA-62602: The bitmap size exceeds maximum size of its SQL data type.
-
Cause: An attempt was made to construct a bitmap larger than its maximum SQL type size.
- ORA-62603: The input is not a valid bitmap produced by BITMAP COUNT DISTINCT operators.
-
Cause: An attempt was made to pass a bitmap that was not produced by one of the BITMAP COUNT DISTINCT operators.
- ORA-62611: operation disallowed; cluster cannot be created in Oracle Autonomous Database Cloud
-
Cause: Cluster feature is not supported in Oracle Autonomous Database Cloud.
- ORA-62612: operation disallowed; column with ROWID type cannot be created in Oracle Autonomous Database Cloud
-
Cause: An attempt was made to create a table with ROWID column type. By default, Oracle Autonomous Database Cloud runs with ROW MOVEMENT enabled. Hence, ROWIDs stored in ROWID column may not be valid if rows are moved by automated maintenance operations, such as table shrink.
- ORA-62700: A DBMS_KAFKA application does not exist for cluster %0!s and application %1!s.
-
Cause: The procedure call was provided values for a nonexistent cluster and application pair.
- ORA-62701: DBMS_KAFKA cluster ID cannot be a NULL value.
-
Cause: A cluster ID was specified as NULL.
- ORA-62702: DBMS_KAFKA generated cluster ID '%0!s' is greater than 40 characters.
-
Cause: The generated cluster ID was too long.
- ORA-62703: DBMS_KAFKA cluster not found. Cluster ID is %0!s.
-
Cause: A DBMS_KAFKA cluster was not found with the specified cluster ID.
- ORA-62704: An attempt to create a connection to Kafka cluster %0!s failed with status %1!s and secondary status %2!s.
-
Cause: An attempt to connect to a Kafka cluster failed.
- ORA-62705: Property %0!s is not allowed because it would obscure a 'librdkafka' property with the same name.
-
Cause: An Oracle SQL Access to Kafka (OSAK) property was specified with a property name that was also used by 'librdkafka'.
- ORA-62706: Property %0!s cannot be NULL.
-
Cause: The property was specified without a value.
- ORA-62707: OSAK Cluster configuration directory is not specified.
-
Cause: The cluster configuration directory was specified as NULL.
- ORA-62708: The OSAK properties file '%0!s' could not be read.
-
Cause: An Oracle SQL Access to Kafka (OSAK) 'osakafka.properties' file could not be read.
- ORA-62709: OSAK SASL/SSL credential name is NULL.
-
Cause: An attempt to configure an Oracle SQL Access to Kafka (OSAK) cluster failed because the SASL/SSL credential name was NULL.
- ORA-62710: The %0!s parameter is required.
-
Cause: The specified parameter was specified as NULL.
- ORA-62711: The %O!s value is NULL. The value must be an existing file name.
-
Cause: A value was specified as NULL instead of a file name.
- ORA-62712: The directory path is not an absolute path for directory %0!s.
-
Cause: The directory path retrieved for the directory object was not specified as an absolute directory path.
- ORA-62713: File '%0!s' that was specified for property %1!s does not exist.
-
Cause: The file name provided for the property listed in the Oracle SQL Access to Kafka properties file did not exist.
- ORA-62714: error loading global temporary table %0!s from %1!s
-
Cause: Inserting data from the Oracle SQL Access to Kafka view into an associated global temporary table failed.
- ORA-62715: unsupported call, call %0!s instead
-
Cause: An undocumented API was called instead of the documented API.
- ORA-62716: Application %0!s already exists for cluster %1!s.
-
Cause: An attempt to create an application failed because an application of that name already exists.
- ORA-62717: The VIEW_COUNT parameter must be between 0 and the number of 'partitions' for the 'topic'. The supplied value is %0!s and the number of 'partitions' is %1!s.
-
Cause: View count was specified outside the valid range.
- ORA-62718: VIEW_COUNT must be equal to or less than the SESSIONS_PER_USER quota. View count is %0!s and SESSIONS_PER_USER is %1!s.
-
Cause: The specified value for the VIEW_COUNT parameter was larger than the user's session limit.
- ORA-62719: The specified time zone [%0!s] is longer than 64 bytes.
-
Cause: The specified value was larger than 64 bytes".
- ORA-62720: Invalid time zone [%0!s] is specified.
-
Cause: The specified value was not a valid time zone.
- ORA-62721: The specified parallel hint [%0!s] exceeds the granule count {%1!s}.
-
Cause: The specified value was greater than the maximum possible parallelism, which is determine by the granule count.
- ORA-62722: The parameter %0!s must be greater than or equal to 0. The specified value is %1!s.
-
Cause: The specified value was less than 0.
- ORA-62723: The WATER_MARK parameter must be DBMS_KAFKA.WATER_MARK_HIGH {%0!s} or DBMS_KAFKA.WATER_MARK_LOW {%1!s}. The specified value is %2!s.
-
Cause: The specified value was not in the valid list for water marks.
- ORA-62724: The calculated time stamp [%0!s = %1!sms] must be greater than or equal to the UNIX epoch.
-
Cause: The specified value was converted to a number of milliseconds that represents a time before the UNIX epoch. Kafka time stamps are restricted to time stamps since the UNIX epoch.
- ORA-62725: The end time stamp {%0!s} must be greater than start time stamp {%1!s}.
-
Cause: The end time stamp was equal to or less than the start time stamp.
- ORA-62726: error preparing %0!s for seeking data using time stamps
-
Cause: Updating the metadata failed while processing the DBMS_KAFAK.SEEK_OFFSET_TS procedure.
- ORA-62727: No offset data is recorded for view %0!s. A successful load involving the view is required.
-
Cause: The offset information was not recorded for the specified view name.
- ORA-62728: error while processing offset data for view %0!s
-
Cause: There was an unexpected problem processing the offset information associated with the specified view name.
- ORA-62729: The length of the %0!s parameter exceeds the allowed value {%1!s}.
-
Cause: The specified value for the argument exceeded the allowed length.
- ORA-62730: The DBMS_KAFKA cluster {%0!s} does not exist.
-
Cause: The specified cluster name was not a known Kafka cluster.
- ORA-62731: Required credential is not specified for a cluster associated with an Oracle Streaming Service 'stream'.
-
Cause: The specified credential name was NULL for a cluster whose provider is the Oracle Streaming Service (OSS).
- ORA-62732: The options specified contain duplicate keys.
-
Cause: The JavaScript Object Notation (JSON) document contained duplicate keys.
- ORA-62733: The specified options are not a properly formatted JSON document.
-
Cause: The JavaScript Object Notation (JSON) document contained errors and could not be converted to a JSON_OBJECT_T structure.
- ORA-62734: Invalid option specified. Option {%0!s} is not supported. %1!s
-
Cause: The JavaScript Object Notation (JSON) document contained a key that was not one of the valid options. Invalid options generate / a suggested option in the error message.
- ORA-62735: Option names are case sensitive. Name specified is {%0!s}; name expected is {%1!s}.
-
Cause: The JavaScript Object Notation (JSON) document contained a key that failed to match the option name due to case sensitivity.
- ORA-62736: The %0!s option must be one of {%1!s|%2!s}. The specified value is %3!s.
-
Cause: The specified value was not in the valid list for the option.
- ORA-62737: The DBMS_KAFKA cluster %0!s already exists.
-
Cause: Registering a Kafka cluster failed because a cluster of that name already exists.
- ORA-62738: The DBMS_KAFKA cluster %0!s is still in use by some number {%1!s} of applications.
-
Cause: Deregistering a cluster failed because the cluster still had DBMS_KAFKA applications associated with it.
- ORA-62739: The DBMS_KAFKA cluster %0!s is already disabled.
-
Cause: The DBMS_KAFKA cluster was already disabled or deregistered.
- ORA-62740: The DBMS_KAFKA cluster %0!s cannot be enabled.
-
Cause: The DBMS_KAFKA cluster was already enabled or deregistered.
- ORA-62741: failed to add 'partitions' to DBMS_KAFKA application
-
Cause: There was a failure in the processing of the DBMS_KAFKA.ADD_PARTITIONS logic.
- ORA-62742: failed to ALTER TABLE %0!s while processing DBMS_KAFKA.ADD_PARTITIONS
-
Cause: There was a failure in the processing of the ALTER TABLE statement in the DBMS_KAFKA.ADD_PARTITIONS logic.
- ORA-62743: Application name for a DBMS_KAFKA application cannot be PARTITIONS.
-
Cause: The application name was specified as PARTITIONS. This name is reserved and cannot be used as an application name.
- ORA-62744: Application type for a DBMS_KAFKA application must be one of the following values [%0!s|%1!s|%2!s].
-
Cause: The specified application type was not a supported type.
- ORA-62745: application associated with the view name %0!s not found
-
Cause: The specified view name was not associated with a known DBMS_KAFKA application.
- ORA-62746: The procedure only supports application types in this list: {%0!s}. Current application is of type %1!s.
-
Cause: The procedure called was not appropriate for the type of application associated with the specified view name.
- ORA-62747: The BOOTSTRAP_SERVERS parameter is a comma-separated list of 'host:port' values. Value {%0!s} in {%1!s} needs to be a 'host:port' value.
-
Cause: The bootstrap server list contained a value that was not a 'host:port' pair.
- ORA-62748: The BOOTSTRAP_SERVERS parameter is a comma-separated list of 'host:port' values. The supplied value {%0!s} does not contain a 'host:port' pair.
-
Cause: The bootstrap server list did not contain a 'host:port' pair.
- ORA-62749: The %0!s parameter [%1!s] is not a known directory object.
-
Cause: The directory object did not exist.
- ORA-62750: The DBMS_KAFKA cluster %0!s is not enabled. Current state is %1!s.
-
Cause: The cluster was not in the enabled state. The procedure required an enabled cluster.
- ORA-62751: The %0!s parameter {%1!s} is not a SQL name.
-
Cause: The credential name was not a valid SQL name.
- ORA-62752: The %0!s parameter {%1!s} does not exist.
-
Cause: The credential name was not an existing credential.
- ORA-62753: The KAFKA_PROVIDER parameter {%0!s} must be one of the following {%1!s|%2!s}.
-
Cause: The specified KAFKA_PROVIDER was not one of the known providers.
- ORA-62754: The 'format' {%0!s} requires a '%1!s' option to be defined.
-
Cause: The required option was missing for the format specified.
- ORA-62755: The 'format' option is missing from the specified options.
-
Cause: The 'format' option was missing in the specified options. The 'format' option is required.
- ORA-62756: The '%0!s' option is currently an unsupported option.
-
Cause: An unsupported option was present in the specified options.
- ORA-62757: The '%0!s' option must be a single printable character. The specified value is [%1!s].
-
Cause: A single character option was specified with more than one character.
- ORA-62758: The '%0!s' option cannot be a digit. The specified value is [%1!s].
-
Cause: A single character option was specified as a digit character, which is not allowed.
- ORA-62759: The '%0!s' option is not specified as an allowed escaped character {n|t|r|\\}. The specified value is [%1!s].
-
Cause: An unsupported escape character was specified for an option requiring a single character.
- ORA-62760: The '%0!s' option is not allowed for the 'format' specified.
-
Cause: A known option was specified, but the option was not appropriate for the 'format' specified.
- ORA-62761: The %0!s option must be one of {%1!s|%2!s|%3!s|%4!s}. The specified value is %5!s.
-
Cause: The specified value was not in the valid list for the option.
- ORA-62762: The %0!s option must between %1!s and %2!s. The specified value is %3!s.
-
Cause: The specified value was not within the range of the valid values for the option.
- ORA-62763: The %0!s option cannot be NULL.
-
Cause: A NULL value was specified that was not allowed for the option.
- ORA-62764: The %0!s option must be either the value UNLIMITED or a number equal to or greater than 0. The specified value is %1!s.
-
Cause: The specified value was not UNLIMITED or a number greater than or equal to 0.
- ORA-62765: The %0!s option is not a valid date format. The specified value is %1!s.
-
Cause: The specified value was not a valid date format.
- ORA-62766: The %0!s option is not a valid time stamp format. The specified value is %1!s.
-
Cause: The specified value was not a valid time stamp format.
- ORA-62767: The %0!s option must be one of {%1!s|%2!s|%3!s|%4!s|%5!s}. The specified value is %6!s.
-
Cause: The specified value was not in the valid list for the option.
- ORA-62768: The %0!s option is not an existing table name. The specified value is %1!s.
-
Cause: The specified value was not the name of an existing table.
- ORA-62769: The %0!s option is not a valid JSON formatted Avro schema.
-
Cause: The specified value failed to be converted to a JSON_OBJECT_T data type.
- ORA-62770: The %0!s option lacks required validation logic.
-
Cause: The specified option was not allowed because it lacked validation support.
- ORA-62771: The %0!s parameter is restricted to the following characters {%1!s}. The specified value is [%2!s].
-
Cause: The specified value included a character that was not in the valid range.
- ORA-62772: The %0!s parameter must be a simple SQL name. The specified value is %1!s.
-
Cause: The specified value could not be used in the name of a SQL object.
- ORA-62773: The %0!s parameter must be the name of an existing SQL object. The specified value is %1!s.
-
Cause: The specified value was not the name of an existing SQL object.
- ORA-62774: The %0!s option must be one of the following {%1!s|%2!s|%3!s}. The specified value is %4!s.
-
Cause: The specified value was not in the valid list for the option.
- ORA-62775: The generated %0!s name [%1!s] is too long.
-
Cause: The object name generated was longer than the acceptable SQL object name length maximum.
- ORA-62776: The %0!s name must be the name of an existing SQL object. The specified value is %1!s.
-
Cause: The specified value was not the name of an existing SQL object.
- ORA-62777: The type of object [%0!s] to rollback is not a supported type.
-
Cause: The specified type was not one of the expected types.
- ORA-62778: The data type of the column [%0!s] for the reference table [%1!s] is currently not supported.
-
Cause: The data type of the column was not one of the supported data types.
- ORA-62779: An unexpected 'topic' format value [%0!s] is provided.
-
Cause: The format value for a 'topic' was an unrecognized value.
- ORA-62780: The number of '%0!s' must be greater than 0. Retrieved value is %1!s.
-
Cause: The value stored in the database was invalid. This was because of data corruption or an attempt at SQL injection.
- ORA-62781: The value of '%0!s' is invalid. Retrieved value is %1!s.
-
Cause: The value stored in the database was invalid. This was because of data corruption or an attempt at SQL injection.
- ORA-62782: Error getting 'partition' count for 'topic' %0!s from the Kafka cluster. Check the status of the Kafka cluster: %1!s.
-
Cause: There was a failure to fetch the 'partition' count from the Kafka cluster. This could be caused by access errors to the Kafka cluster.
- ORA-62783: Error getting 'partition' count for 'topic' %0!s from the Kafka cluster. Check that the topic exists in the Kafka cluster %1!s.
-
Cause: There was a failure to fetch the 'partition' count from the Kafka cluster. This occurred usually when the 'topic' specified did not exist. This could also be caused by access errors to the Kafka cluster.
- ORA-62784: An attempt to manually rollback a change to an external table [%0!s] failed.
-
Cause: Altering an external table to its original configuration during a rollback failed.
- ORA-62785: An attempt to manually rollback an unknown type [%0!s] was made.
-
Cause: The type of object to rollback was not one of the known types.
- ORA-62786: The specified object name [%0!s] could not be parsed into SQL object tokens.
-
Cause: The specified object name failed to be parsed into schema and object names.
- ORA-62787: The specified object name [%0!s] parsed into more tokens than expected. Expected name is either an object name or a schema-qualified object name.
-
Cause: The specified object name parsed into more than just schema and object names.
- ORA-62788: The directory [%0!s] either does not exist or does not have read/write privileges granted to the user.
-
Cause: Either the directory did not exist or did not have read or write privilege granted to the user.
- ORA-62789: The user cannot have EXECUTE access to the directory [%0!s].
-
Cause: EXECUTE access to the directory was granted to the user. This was not allowed.
- ORA-62790: The OSAK view [%0!s] does not exist.
-
Cause: The specified view name was not a known Oracle SQL Access to Kafka (OSAK) view.
- ORA-62791: The OSAK temporary table [%0!s] does not exist.
-
Cause: The specified temporary table name was not a known Oracle SQL Access to Kafka (OSAK) temporary table.
- ORA-62792: The Avro name is NULL.
-
Cause: The specified Avro name was NULL.
- ORA-62793: The Avro name starts with an invalid character. The specified value is %0!s.
-
Cause: The Avro name did not begin with an underscore or an alphabetic character.
- ORA-62794: The Avro name contains an invalid character. The specified value is %0!s.
-
Cause: The Avro name contained a character that was not an underscore or an alphanumeric character.
- ORA-62795: The Avro type [%0!s] already exists and cannot be redefined.
-
Cause: The specified Avro type was already defined and could not be redefined.
- ORA-62796: The Avro %0!s %1!s is NULL.
-
Cause: The schema was not specified.
- ORA-62797: The attribute [%0!s] is not present in schema [%1!s].
-
Cause: The specified attribute was not defined in the schema.
- ORA-62798: The attribute [%0!s] is not a string in the schema [%1!s].
-
Cause: The specified attribute was not defined as a string.
- ORA-62799: The attribute [%0!s] is not an integer in the schema [%1!s].
-
Cause: The specified attribute was not defined as an integer.
- ORA-62800: The attribute 'aliases' is not an array in the schema [%0!s].
-
Cause: The specified attribute was not defined as an array.
- ORA-62801: The attribute array element 'aliases[%0!s]' is not a string in the schema [%1!s].
-
Cause: The specified attribute array element was not defined as a string.
- ORA-62802: Schema name [%0!s] cannot be a primitive name in the schema [%1!s].
-
Cause: The specified named schema was a primitive name. This was not an allowed value.
- ORA-62803: A fixed type size must be between 0 and 2147483647 in the schema [%0!s].
-
Cause: The specified size was not within the range of acceptable values.
- ORA-62804: The 'symbols' attribute is missing for the enum in the schema [%0!s].
-
Cause: The required 'symbols' attribute was not provided for the enum.
- ORA-62805: The 'symbols' attribute is not an array for the enum in the schema [%0!s].
-
Cause: The 'symbols' attribute was not an array.
- ORA-62806: The element [%0!s] in the enum 'symbols' attribute array is not a string in the schema [%1!s].
-
Cause: The 'symbols' attribute array contained a non string value.
- ORA-62807: The element [%0!s] in the enum 'symbols' attribute array is a duplicate in the schema [%1!s].
-
Cause: The 'symbols' attribute array contained a duplicate string value.
- ORA-62808: The default value [%0!s] is not in the array [%1!s] for the enum 'symbols' attribute in the schema [%2!s].
-
Cause: The 'symbols' attribute default value did not exist in the array.
- ORA-62809: The type [%0!s] is not defined in the schema [%1!s].
-
Cause: The type did not exist in the schema.
- ORA-62810: An illegal value for 'order' [%0!s] is specified for the field [%1!s].
-
Cause: The value for 'order' was not from the list of supported values.
- ORA-62811: The record has an empty or missing 'fields' array [%0!s].
-
Cause: The 'fields' array was missing or empty in the record.
- ORA-62812: The element [%0!s] in the 'fields' array for the record is not an object [%1!s].
-
Cause: An element in the 'fields' array was not an object.
- ORA-62813: Union [%0!s] is not allowed to be nested within union [%1!s].
-
Cause: A union was nested within a union. This is not allowed.
- ORA-62814: A duplicate type [%0!s] is present within union [%1!s].
-
Cause: A duplicate type was specified within a union. This was not allowed.
- ORA-62815: The Avro schema is NULL.
-
Cause: The Avro schema was specified as NULL. This was not allowed.
- ORA-62816: Undefined name [%0!s] in the current type map.
-
Cause: The specified name was not in the type map.
- ORA-62817: The 'items' attribute is not defined for the array [%0!s].
-
Cause: The array was defined without an 'items' attribute.
- ORA-62818: The 'values' attribute is not defined for the map [%0!s].
-
Cause: The map was defined without a 'values' attribute.
- ORA-62819: The type [%0!s] is not supported in the current type map.
-
Cause: The current map did not contain a valid type.
- ORA-62820: Schema [%0!s] is not supported.
-
Cause: The schema contained an unrecognized element.
- ORA-62821: Schema type [%0!s] is not supported.
-
Cause: The schema contained an unsupported type.
- ORA-62822: Avro schema is not a JSON object. Schema is [%0!s].
-
Cause: The Avro schema was not a JavaScript Object Notation (JSON) object.
- ORA-62823: Avro schema is not a 'record' type. Schema is [%0!s].
-
Cause: The Avro schema was not a 'record' type.
- ORA-62824: The maximum allowed number of 'fields' in an Avro record is 997. The number of 'fields' is %0!s.
-
Cause: The specified number of fields was more than the allowed limit.
- ORA-62825: The 'field' name [%0!s] exceeds the maximum column name length [%1!s] in the schema [%2!s].
-
Cause: The name of the field was more than the allowed number of characters for a column name.
- ORA-62826: The 'field' [%0!s] maps to the same column name as field [%1!s] in the schema [%2!s].
-
Cause: The 'field' name was a duplicate of another column name.
- ORA-62827: failed to ALTER TABLE %0!s while updating the access parameters.
-
Cause: There was a failure in the processing of the ALTER TABLE statement in the DBMS_KAFKA.SET_TRACING logic.
- ORA-62828: The target table contains one or more column names that do not exist in the provided OSAK view %0!s.
-
Cause: There were one or more columns names in the target table that did not match column names for the Oracle SQL Access to Kafka (OSAK) view.
- ORA-62829: The 'size' attribute must be greater than 0 in the schema [%0!s].
-
Cause: The specified 'size' was not within the range of acceptable values.
- ORA-62830: The 'precision' must be greater than 0 in the schema [%0!s].
-
Cause: The specified 'precision' was not within the range of acceptable values.
- ORA-62831: The 'precision' must be less than or equal to %0!s in the schema [%1!s].
-
Cause: The specified 'precision' was not within the range of acceptable values.
- ORA-62832: The 'scale' must be between 0 and %0!s in the schema [%1!s].
-
Cause: The specified 'scale' was not within the range of acceptable values.
- ORA-62833: An empty union definition [%0!s] is not allowed.
-
Cause: The union schema was empty.
- ORA-62834: The record must define at least one supported field type.
-
Cause: The schema did not define any supported field types;
- ORA-62835: The application %0!s is still being used by %1!s and cannot be dropped. Stop all programs that are using this application and retry the drop procedure.
-
Cause: There were one or more programs still using the application with either an uncommitted DBMS_KAFKA.UPDATE_OFFSET call or a global temporary table with pending inserts.
- ORA-63000: operation disallowed: data file string is being moved
-
Cause: The specified data file was being moved.
- ORA-63001: file error during move operation
-
Cause: The move operation encountered an error for the moved data file. The error might be caused by file going offline or by an I/O error. See alert or trace files in all instances for further information.
- ORA-63002: a data file copy that is not current
-
Cause: An obsolete copy of a data file left from a data file move operation was used for the CREATE CONTROLFILE command or file header read.
- ORA-63003: a half-done data file copy
-
Cause: A half-done copy of a data file created from a previous data file move operation was used for the CREATE CONTROLFILE command or file header read.
- ORA-63004: Database names in file headers are inconsistent: string and string.
-
Cause: Differing database names were found in database file headers.
- ORA-63005: Header validation failed for string File ('string').
-
Cause: Oracle server failed to read or write to the specified file because the file has an SCN value which is too high for this release.
- ORA-63006: only PDB files can be moved to or from the object store
-
Cause: Either the root CDB or the non-CDB file could not be moved to or from the object store.
- ORA-63007: only read-only files can be moved to or from the object store
-
Cause: The read/write file could not be moved to or from the object store.
- ORA-63008: cannot move file to or from the object store on ADG
-
Cause: The data file move operation to or from object store was not supported on Active Data Guard (ADG).
- ORA-63009: cannot make object store files read/write
-
Cause: Tablespaces with object store files could not be read/write.
- ORA-63010: trace event for recovery data file pre-creation
-
- ORA-63011: created file 'string' is located in object store
-
Cause: Files could not be created in the object store.
- ORA-63012: no DEFAULT_CREDENTIAL in PDB string available for data file move
-
Cause: When moving a data file to the object store, the DEFAULT_CREDENTIAL was not found.
- ORA-63013: no DEFAULT_CREDENTIAL in PDB string available for data file drop
-
Cause: When dropping a data file in the object store, the DEFAULT_CREDENTIAL was not found.
- ORA-63014: cannot make object store data file read/write during recovery
-
Cause: Object store data files cannot be made read/write during recovery.
- ORA-63600: failure to detach from a persistent memory region
-
Cause: An attempt to detach a persistent memory region failed because one or more processes were still attached to it.
- ORA-63702: event for slave mapping skew handling test
-
Cause: This is an internal event to test slave mapping skew handling and is for internal use only.
- ORA-63800: maximum number of elements in a tuple exceeded for a Table Value Constructor
-
Cause: An attempt was made to specify more than allowed number of elements in a tuple of Table Value Constructor.
- ORA-63801: each tuple should have same number of elements in a Table Value Constructor
-
Cause: An attempt was made to specify different number of elements in a tuple of Table Value Constructor.
- ORA-63802: tuple in a Table Value Constructor cannot be empty
-
Cause: An attempt was made to specify a tuple of Table Value Constructor that had no elements.
- ORA-63803: columns must be specified with string
-
Cause: Column names must be specified when Table Value Constructor is used in this context.
- ORA-63804: Number of Columns must be same as number of elements
-
Cause: Number of columns aliases is not same as number of elements of each tuple of Table Value Constructor.
- ORA-63805: Maximum number of tuples in Table Value Constructor exceeded
-
Cause: Number of tuples in the values clause of Table Value Constructor is more than the allowed limit.
- ORA-63806: Duplicate name in column alias list for Table Value Constructor
-
Cause: Column aliases specified for Table Value Constructor had one or more names spefified more than once.
- ORA-63807: Materialized Views can not contain a Table Value Constructor
-
Cause: Materialized views can not be created when it referenced a Table Value Constructor in its query.
- ORA-63995: fractured block detected in control file: (block string, # blocks string)
-
Cause: A fractured block or checksum error was detected on reading the control file under no-enqueue control file transaction. The reason could be a stalled concurrent block update.
- ORA-63996: A local temporary file remote call failed
-
Cause: An operating system error or network error occurred when making a remote call to another instance during a local temporary space DDL operation.
- ORA-63997: file size refresh failed
-
Cause: An operating system error or device error occurred when retrieving the file's size.
- ORA-63998: undo tablespace file suffered media failure
-
Cause: An undo tablespace file was detected as inaccessible due to media failure.
- ORA-63999: data file suffered media failure
-
Cause: A data file was detected as inaccessible due to media failure.
- ORA-64000: specified path already exists
-
Cause: The pathname of a new item specified in a DBFS API operation already exists.
- ORA-64001: invalid parent directory in specified path
-
Cause: The pathname of an item specified in a DBFS API operation has one or more invalid parent components.
- ORA-64002: specified path is invalid
-
Cause: The pathname of an item specified in a DBFS API operation is invalid.
- ORA-64003: An unsupported operation was invoked.
-
Cause: The current Database File System (DBFS) API operation was unsupported by a provider.
- ORA-64004: an invalid combination of arguments was specified
-
Cause: The current DBFS API operation specifies an invalid combination of arguments for the specified pathname(s) and operation.
- ORA-64005: access control checks failed
-
Cause: The current DBFS API operation failed access control checks for the pathname(s) being accessed.
- ORA-64006: lock conflict in current operation
-
Cause: A DBFS API locking operation could not be completed due to conflicts in the locking protocol.
- ORA-64007: invalid store specified
-
Cause: The current operation specifies an invalid store name.
- ORA-64008: invalid mount-point specified
-
Cause: The current operation specifies an invalid mount-point.
- ORA-64009: invalid provider specified
-
Cause: The current operation refers to an invalid or incomplete or non-conformant store provider package.
- ORA-64010: cannot modify store via read-only mount
-
Cause: The current operation attempts to modify a store via a read-only mount (or specifies a read-only store).
- ORA-64011: cross store operation
-
Cause: The current operation attempts to span 2 or more different stores and cannot be implemented entirely by the DBFS API.
- ORA-64012: specified path is a directory
-
Cause: The current operation specifies a path that is a directory element, when a non-directory element is expected.
- ORA-64013: specified path is not a directory
-
Cause: The current operation specifies a path that is not a directory element, when a directory element is expected.
- ORA-64014: directory not empty
-
Cause: The current operation specifies a directory element that is not empty as required.
- ORA-64015: cannot drop tablespace used by Database File System (DBFS)
-
Cause: An attempt was made to drop a tablespace containing DBFS metadata tables.
- ORA-64016: string is not a valid compression option. Use LOW, MEDIUM or HIGH
-
Cause: An invalid value was specified for compression option
- ORA-64017: string is not a valid encryption option
-
Cause: An invalid value was specified for encryption option
- ORA-64101: Cannot alter both a structured and an unstructured component of an XMLIndex in the same ALTER INDEX statement.
-
Cause: An attempt was made to alter the unstructured component and structured component of an XMLIndex at the same time.
- ORA-64102: Cannot create an XMLIndex with a structured component on a CLOB column within the object-relational storage model.
-
Cause: An attempt was made to create an XMLIndex with a structured component on a CLOB column within the object-relational storage model.
- ORA-64103: Cannot create an XMLIndex on an object-relational XML type table or column.
-
Cause: An attempt was made to create an XMLIndex on an XML type table or column that uses the object-relational storage model.
- ORA-64104: Column name already used by internal column of the structured component of the XMLIndex.
-
Cause: An attempt was made to use a column name already in use by an internal column of the structured component of the XMLIndex.
- ORA-64105: Cannot create domain index on XMLIndex internal tables.
-
Cause: An attempt was made to create a domain index on an internal table of an XMLIndex.
- ORA-64106: Incorrect use of comma(,) punctuation in COLUMN definitions.
-
Cause: An attempt was made to define COLUMNS with incorrect use of comma punctuation.
- ORA-64107: The XMLIndex has been successfully altered but the metadata could not be updated.
-
Cause: An internal error occurred when updating the index metadata. The dbms_metadata.get_ddl function may return improper metadata.
- ORA-64108: Cannot truncate a table that has an XMLIndex whose internal table has been indexed using Oracle Text.
-
Cause: An attempt was made to truncate a table that has an XMLIndex whose internal table has been indexed using Oracle Text.
- ORA-64109: XMLIndex: problems encountered during the dropping of statistics
-
Cause: See associated error message.
- ORA-64110: XMLIndex: problems encountered during the gathering of statistics
-
Cause: See associated error message.
- ORA-64111: XMLIndex: problems encountered during EXPORT
-
Cause: See associated error message.
- ORA-64112: XMLIndex: problems encountered during IMPORT
-
Cause: See associated error message.
- ORA-64113: XMLIndex: XDB.XDB$XIDX_IMP_T still has bad data for "string"."string"
-
Cause: See associated error message.
- ORA-64114: XMLIndex: reserved for EXPORT or IMPORT
-
- ORA-64115: XMLIndex Exchange Partition: the table has no XMLIndex
-
Cause: The non-partitioned table had no XMLIndex.
- ORA-64116: XMLIndex Exchange Partition: incompatible XPath subsets
-
Cause: The XMLIndexes on the two tables had different path subsets.
- ORA-64117: XMLIndex Exchange Partition: incompatible modes for asynchronous DML
-
Cause: The XMLIndexes on the two tables had different deferred DML modes.
- ORA-64118: XMLIndex Exchange Partition: incompatible unstructured components
-
Cause: One of the XMLIndexes had no unstructured component.
- ORA-64119: XMLIndex Exchange Partition: incompatible structured components
-
Cause: One of the XMLIndexes had no structured component.
- ORA-64120: XMLIndex Exchange Partition: incompatible structured components
-
Cause: The XMLIndexes had different structured components.
- ORA-64121: XMLIndex DDL: failure of the internal "string"
-
Cause: See associated error message.
- ORA-64122: XMLIndex DDL: failure of the recursive "string"
-
Cause: See associated error message.
- ORA-64123: A recursive DDL failed during the XMLIndex DDL processing.
-
Cause: A recursive DDL (Data Definition Language) command failed during an XMLIndex DDL processing.
- ORA-64124: XMLIndex: failure during the setting of an event
-
Cause: See associated error message.
- ORA-64125: XMLIndex: failure during the resetting of an event
-
Cause: See associated error message.
- ORA-64126: XMLIndex Table Function: failure at the start of the function
-
Cause: See associated error message.
- ORA-64127: A problem occurred at the beginning of the XMLIndex Table function.
-
Cause: A problem occurred at the beginning of an XMLIndex table function. This message will be followed by a second message giving more details about the error.
- ORA-64128: A problem occurred during the evaluation of an XML index table function.
-
Cause: A problem occurred when evaluating an XML Index Table function.
- ORA-64129: XMLIndex Table Function: failure at the end of the function
-
Cause: See associated error message.
- ORA-64130: XMLIndex: invalid namespace mapping "string"
-
Cause: Namespace mapping was invalid. The syntax is XMLNS="string".
- ORA-64131: XMLIndex Metadata: failure during the looking up of the dictionary
-
Cause: See associated error message.
- ORA-64132: A problem occurred updating the metadata of the XML Index.
-
Cause: A problem occurred when updating the metadata of an XML Index.
- ORA-64133: XMLIndex DML: failure of the internal "string"
-
Cause: See associated error message.
- ORA-64134: XMLIndex DML: failure of the recursive "string"
-
Cause: See associated error message.
- ORA-64135: A problem occurred while updating an XMLIndex.
-
Cause: A problem occurred while updating an XMLIndex.
- ORA-64136: XMLIndex Asynchronous DML: synchronization failure
-
Cause: See associated error message.
- ORA-64137: Cannot drop an XMLIndex whose internal table has been indexed using Oracle Text.
-
Cause: An attempt was made to drop an XMLIndex whose internal table has been indexed using Oracle Text.
- ORA-64138: Cannot drop groups from an XMLIndex whose internal table has been indexed using Oracle Text.
-
Cause: An attempt was made to drop groups from an XMLIndex whose internal table has been indexed using Oracle Text.
- ORA-64139: The type of VIRTUAL column is not XMLTYPE
-
Cause: An attempt was made to create an XML index with VIRTUAL column not of XMLTYPE.
- ORA-64140: missing chaining XMLTABLE for VIRTUAL column in the index
-
Cause: An attempt was made to create an XML index with VIRTUAL column but without required chaining XMLTABLE.
- ORA-64141: Can only have a single XMLType column when a table is shared.
-
Cause: An attempt was made to create a shared table with more than one columns.
- ORA-64142: Shared tables must have same semantics for truncation.
-
Cause: An attempt was made to create shared tables with inconsistent semantics for truncation. Either all shared tables should have or should not have (TRUNCATE) keyword.
- ORA-64143: Can only share an existing XMLIndex table with an XMLTYPE column.
-
Cause: An attempt was made to share a table without an XMLTYPE column.
- ORA-64144: Shared tables must have equivalent paths.
-
Cause: An attempt was made to share a table with different paths.
- ORA-64145: This XMLIndex rewrite failed
-
Cause: One of the rewrites being tried by XMLIndex engine failed.
- ORA-64146: Nonblocking alter XMLIndex error
-
Cause: Internal error.
- ORA-64147: Invalid use of NONBLOCKING COMPLETE or ABORT.
-
Cause: NONBLOCKING COMPLETE or ABORT is only allowed for XMLIndex that is being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN.
- ORA-64148: Cannot complete nonblocking alter index operation.
-
Cause: NONBLOCKING COMPLETE is only allowed for XMLIndex that is being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN and there are no pending rows left.
- ORA-64149: Invalid alter XMLIndex operation.
-
Cause: An attempt was made to alter an XMLIndex that is already being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN. Only NONBLOCKING COMPLETE or ABORT alter index operations are allowed. Also, NONBLOCKING operation is not allowed with alter index rebuild.
- ORA-64151: Invalid use of DBMS_XMLINDEX.PROCESS_PENDING.
-
Cause: DBMS_XMLINDEX.PROCESS_PENDING was called on an index that was not modified using NONBLOCKING ADD_GROUP or ADD_COLUMN.
- ORA-64152: There are no pending rows to process.
-
Cause: DBMS_XMLINDEX.PROCESS_PENDING was called on an index that does not have any pending rows to process.
- ORA-64153: Cannot create XMLIndex for data stored in a CLOB column within the object-relational storage model.
-
Cause: An attempt was made to create an XMLIndex on an XML CLOB column stored with object-relational storage.
- ORA-64154: XMLIndex cannot be created on an autolist partitioned table.
-
Cause: An attempt was made to create an XMLIndex on a table that had an autolist partition.
- ORA-64155: XMLIndex with unstructured component cannot be created on an interval partitioned table.
-
Cause: There was an attempt to create an Unstructured XMLIndex (UXI) component on a table with interval partitioning.
- ORA-64201: unregistered LOB value encountered
-
Cause: The LOB value associated with the input locator did not exist in client-side reference tables.
- ORA-64202: remote temporary or abstract LOB locator is encountered
-
Cause: Local database encountered a temporary or abstract LOB created on a remote database. Remote access to temporary or abstract LOB is not supported.
- ORA-64203: Destination buffer too small to hold CLOB data after character set conversion.
-
Cause: An attempt was made to convert CLOB to CHAR, where the LOB size was bigger than the buffer limit for CHAR types or the CHAR buffer was not big enough to hold all data after character set conversion.
- ORA-64204: encountered partial multibyte character
-
Cause: The requested operation could not complete because a partial multibyte character was found at the end of the input.
- ORA-64205: Cannot use other triggering events along with LOGICAL LOB UPDATE event
-
Cause: An attempt was made to use other triggering events (such as INSERT, DELETE and UPDATE) with the LOGICAL LOB UPDATE event.
- ORA-64206: Cannot create INSTEAD OF LOGICAL LOB UPDATE trigger
-
Cause: INSTEAD OF LOGICAL LOB UPDATE trigger was not allowed.
- ORA-64207: Invalid LOGICAL LOB UPDATE trigger definition
-
Cause: The LOGICAL LOB UPDATE trigger could not be created on a non-LOB column of a table. The column name has to be specified while creating the trigger. Only one column name can be specified while creating the trigger.
- ORA-64208: FOR EACH ROW clause is required for before or after LOGICAL LOB UPDATE triggers
-
Cause: An attempt was made to create a before or after LOGICAL LOB UPDATE trigger without a FOR EACH ROW clause.
- ORA-64209: WHEN clause is not allowed for LOGICAL LOB UPDATE triggers
-
Cause: WHEN clause was specified for a LOGICAL LOB UPDATE trigger.
- ORA-64210: Cannot reference a trigger of a different type
-
Cause: The LOGICAL LOB UPDATE trigger did not follow other LOGICAL LOB UPDATE triggers. Non-LOGICAL LOB UPDATE triggers cannot follow LOGICAL LOB UPDATE triggers.
- ORA-64211: Cannot access other columns within a LOGICAL LOB UPDATE trigger body
-
Cause: An attempt was made to access an invalid column. A LOGICAL LOB UPDATE trigger can only access ROWID column and the column for which it was specified. Access to other columns is not allowed.
- ORA-64212: Cannot create a LOGICAL LOB UPDATE trigger on a view
-
Cause: A LOGICAL LOB UPDATE trigger could not be created on view.
- ORA-64213: Cannot create a compound LOGICAL LOB UPDATE trigger with statement level actions
-
Cause: A compound LOGICAL LOB UPDATE trigger could not contain statement level actions.
- ORA-64214: Cannot create a crossedition LOGICAL LOB UPDATE trigger
-
Cause: Crossedition LOGICAL LOB UPDATE triggers were not supported.
- ORA-64215: PL/SQL subprogram 'string' for internal use only
-
Cause: An attempt was made to use a subprogram that is for internal Oracle development use only.
- ORA-64219: invalid LOB locator encountered
-
Cause: The LOB locator sent from client to server was invalid.
- ORA-64220: LOB signature is not supported for clients on Oracle Database Release 19c or earlier.
-
Cause: The buffer size allocated for the locator at the client side was not big enough to hold the locator with a signature. Large Object (LOB) signature is not supported for clients earlier than Oracle Database Release 19c.
- ORA-64221: cannot use BFILE locators selected from remote tables or shards
-
Cause: A remote BFILE column cannot be referenced.
- ORA-64300: Invalid compression level specified.
-
Cause: The archive compression level must be LOW or HIGH.
- ORA-64307: Exadata Hybrid Columnar Compression is not supported for tablespaces on this storage type
-
Cause: An attempt was made to use Exadata Hybrid Columnar Compression on unsupported storage.
- ORA-64308: hybrid columnar compressed table cannot have column with LONG data type
-
Cause: One of the following was attempted: - Create a hybrid columnar compressed table with a LONG data type. - Alter an existing table with a LONG data type to be hybrid columnar compressed. - Add a LONG data type column to a hybrid columnar compressed table.
- ORA-64309: Hybrid Columnar Compression with row-level locking is not supported for tablespaces on this storage type.
-
Cause: An attempt was made to use Hybrid Columnar Compression with row-level locking on an unsupported storage type.
- ORA-64310: could not get compression analysis lock
-
Cause: An operation could not obtain the compression analysis lock in a reasonable amount of time.
- ORA-64350: only one INMEMORY clause may be specified
-
Cause: INMEMORY was specified more than once.
- ORA-64356: The in-memory area is out of space.
-
Cause: The in-memory area did not have any free space.
- ORA-64357: In-Memory area is out of space for the current container.
-
Cause: There was no free space in the In-Memory area for the current container.
- ORA-64364: In-memory column store on Oracle RAC is only supported on Oracle-engineered systems.
-
Cause: An attempt was made to use the in-memory column store feature with Oracle RAC on an unsupported system.
- ORA-64367: In-memory column store FastStart tablespace is offline.
-
Cause: The FastStart feature was enabled but its tablespace was offline.
- ORA-64368: In-memory FastStart is only supported on Oracle-engineered systems.
-
Cause: An attempt was made to use the in-memory column store FastStart feature on an unsupported system.
- ORA-64369: In-memory FastStart Oracle Call Interface (OCI) error string
-
Cause: An OCI error occurred when enabling or disabling FastStart.
- ORA-64370: INMEMORY clause with DISTRIBUTE BY PARTITION specified for a table that is not partitioned.
-
Cause: DISTRIBUTE BY PARTITION was specified for a table that is not partitioned.
- ORA-64371: INMEMORY clause with DISTRIBUTE BY SUBPARTITION specified for a table that is not composite.
-
Cause: DISTRIBUTE BY SUBPARTITION was specified for a table that is not composite.
- ORA-64372: INMEMORY clause with DISTRIBUTE BY SUBPARTITION specified for a table that is not partitioned.
-
Cause: DISTRIBUTE BY SUBPARTITION was specified for a table that is not partitioned.
- ORA-64373: Unable to get FastStart Admin Enqueue in mode string
-
Cause: An attempt was made to do FastStart administrative tasks while FastStart is in use.
- ORA-64374: This action cannot be performed when FastStart is not enabled.
-
Cause: An attempt was made to perform a FastStart-related action when FastStart was not enabled.
- ORA-64375: FastStart is already enabled.
-
Cause: Attempting to enable FastStart when it was already enabled.
- ORA-64376: FastStart is already enabled on this tablespace
-
Cause: This tablespace is already assigned to FastStart or some FastStart internal objects already exists on this tablespace.
- ORA-64377: Action cannot be performed when database is in read-only mode
-
Cause: An attempt make changes to FastStart objects on a read-only database.
- ORA-64378: Action cannot be performed on the tablespace assigned to FastStart while FastStart is enabled.
-
Cause: Attempted to take the FastStart tablespace offline while the feature was enabled.
- ORA-64379: Action cannot be performed on the tablespace assigned to FastStart while the feature is enabled
-
Cause: An attempt drop FastStart tablespace when the feature is enabled.
- ORA-64380: IM FastStart cannot be enabled or migrated to a non-automatic segment space management tablespace (string).
-
Cause: An attempt was made to enable or migrate In-Memory FastStart (IM FastStart) to a non-automatic segment space management tablespace.
- ORA-64381: Unable to acquire the tablespace enqueue for the given FastStart operation.
-
Cause: The given tablespace was locked by another operation.
- ORA-64382: FastStart checkpoint has already started.
-
Cause: An attempt was made to initiate a checkpoint when one was already started.
- ORA-64383: FastStart string was incomplete.
-
Cause: The previous FastStart administrative procedure was incomplete.
- ORA-64384: invalid FastStart catalog version detected
-
Cause: The version number of the FastStart catalog was invalid or too old.
- ORA-64386: string not supported for proxy PDB
-
Cause: An attempt was made to use FastStart in the case of a proxy pluggable database (PDB).
- ORA-64387: inmemory_size cannot be modified
-
Cause: An attempt was made to modify inmemory_size parameter when database was not opened, was read-only, or was being migrated.
- ORA-64388: inmemory_size specified is less than a minimum of (string) bytes
-
Cause: inmemory_size was less than the minimum expected by the system.
- ORA-64389: The tablespace string where FastStart is being migrated has insufficient space.
-
Cause: An attempt was made to migrate FastStart to a tablespace having insufficient space.
- ORA-64390: FastStart not supported for string
-
Cause: An attempt was made to use FastStart along with the feature that is not supported.
- ORA-64393: In-Memory Expressions capture window is already OPEN
-
Cause: An attempt was made to open an In-Memory Expressions capture window with another capture window already in the OPEN state.
- ORA-64394: In-Memory Expressions capture window is not OPEN
-
Cause: An attempt was made to CLOSE an In-Memory Expressions capture window before opening it first.
- ORA-64395: error encountered while changing the state of In-Memory Expressions capture window
-
Cause: An internal error was encountered in the In-Memory Expressions procedure.
- ORA-64396: Resize of In-Memory Xmem area is not supported.
-
Cause: Resize of In-Memory Xmem area was not supported on non multitenant container database (CDB) and root pluggable database (PDB).
- ORA-64397: The new Xmem area size %0!s M is larger than configured Xmem area size %1!s M.
-
Cause: The specified In-Memory area size was larger than the configured In-Memory XMem area size.
- ORA-64398: invalid INMEMORY_SIZE value for cloud configuration, it must be zero
-
Cause: A nonzero value was specified for the INMEMORY_SIZE initialization parameter for a non-Oracle cloud.
- ORA-64399: In-Memory population or repopulation cannot be run for this segment.
-
Cause: Either the segment requested for In-Memory did not exist, or a population or repopulation task was already in progress for this segment, or this segment was not In-Memory enabled.
- ORA-64401: This manageability package is only supported on Oracle RDBMS versions 10.2, 11.1, and 11.2.
-
Cause: Package installation invoked on database version that was not 10.2, 11.1 or 11.2..
- ORA-64402: Invalid input. XMLSchema is null.
-
Cause: XMLSchema was not provided to the procedure or function call..
- ORA-64403: Input cannot be null
-
Cause: An input parameter was null.
- ORA-64404: Input string exceeds the maximum size
-
Cause: An input string was provided whose length exceeded the maximum size allowed. This size is 30 bytes for clients prior to Oracle Database 12c Release 2 (12.2) and 128 bytes otherwise.
- ORA-64405: No matching elements found. Zero annotations were applied.
-
Cause: The parameters provided to annotate the XMLSchema did not match any entities in the XMLSchema.
- ORA-64406: No matching elements found. Zero annotations were removed.
-
Cause: The parameters provided to annotate the XMLSchema did not match any entities in the XMLSchema.
- ORA-64407: Annotation maps to multiple elements.
-
Cause: The parameters provided to annotate the XMLSchema matched to multiple entities in the XMLSchema.
- ORA-64408: Name for collection table too long.
-
Cause: The name for the collection table exceeded 25 characters.
- ORA-64409: XPath could not be mapped to exactly one table.
-
Cause: XPath could not be mapped to existing table.
- ORA-64410: Invalid XPath.
-
Cause: The XPath string provided to the procedure was not valid.
- ORA-64411: Invalid collection table specified by XPath.
-
Cause: An invalid collection table was specified by the XPath string.
- ORA-64412: Procedure called on XML table with BINARY storage model.
-
Cause: The procedure renameCollectionTable did not work on binary storage model.
- ORA-64413: Cannot disable constraints/indexes for non-global schemas owned by other users or a non schema based table/column.
-
Cause: An attempt was made to disable constraints or indexes for non-global schemas owned by other users or a non schema based table/column.
- ORA-64414: Cannot enable constraints/indexes for non-global schemas owned by other users or a non schema based table/column.
-
Cause: An attempt was made to enable constraints or indexes for schemas owned by other users or for a non schema based table/column.
- ORA-64415: Error in namespace declaration.
-
Cause: The namespace declaration was invalid.
- ORA-64416: Table does not exist.
-
Cause: The tab_name parameter provided the name of a table that did not exist..
- ORA-64417: Column does not exist in table.
-
Cause: The col_name parameter provided the name of a column that did not exist in the given table.
- ORA-64418: Column not of XMLType.
-
Cause: The col_name parameter provided the name of a column that was not an XMLType column.
- ORA-64419: Name for collection table already exists.
-
Cause: The name for the collection table could not be used because it already exists.
- ORA-64420: Table not of XMLType.
-
Cause: The table_name parameter provided the name of a table that was not an XMLType table.
- ORA-64477: Multiple token tables are not supported.
-
Cause: An attempt was made to create a new token table. If encountered during an import, a critical patch was possibly missing on the export database.
- ORA-64479: element 'string' is missing 'string' annotation; schema cannot be registered by common users
-
Cause: A common user tried to register a schema with missing type name annotations. All type names from the schema and its dependencies should be annotated.
- ORA-64480: element 'string' is missing default table name annotation; schema cannot be registered by common users
-
Cause: A common user tried to register a schema with missing default table name annotations. All table names from the schema and its dependencies should be annotated.
- ORA-64481: invalid tablespace name
-
Cause: The tablespace name did not have a closing double quotation mark.
- ORA-64482: Moving XDB to string is not allowed.
-
Cause: An attempt was made to move XDB to a system tablespace.
- ORA-64483: New tablespace string is smaller than the current tablespace string.
-
Cause: The new tablespace was smaller than the current tablespace.
- ORA-64484: New tablespace string is not automatic segment space management.
-
Cause: The new tablespace was not automatic segment space management.
- ORA-64485: Invalid resource handle or path name passed.
-
Cause: An invalid resource handle or path name was passed.
- ORA-64486: The internal table is empty.
-
Cause: The internal input table containing the schemas was empty.
- ORA-64487: XML schema string exists for user string
-
Cause: The XML schema existed for the user.
- ORA-64488: cannot migrate inherited type string
-
Cause: The inherited type could not be migrated.
- ORA-64489: cannot migrate XML schema string
-
Cause: The XML schema could not be migrated.
- ORA-64490: cannot migrate owner from string to string for XML schema string
-
Cause: The owner could not be migrated for the XML schema.
- ORA-64491: cannot grant XML schemas to public
-
Cause: The XML schema could not be granted to public.
- ORA-64492: The level up the hierarchy must be greater than 0.
-
Cause: The level up the hierarchy was less than 1.
- ORA-64493: The resource type is unknown.
-
Cause: The resource type was not recognized.
- ORA-64494: Substitution group is not supported when maintainDOM is not set.
-
Cause: maintainDOM was not set to TRUE.
- ORA-64495: XQuery data model has to be allowed.
-
Cause: XQuery data model is not allowed.
- ORA-64496: Position predicate on out-of-line table is not supported when maintainDOM is set to FALSE.
-
Cause: An attempt was made to use position predicate on an out-of-line table when maintainDOM was set to FALSE.
- ORA-64497: File access not over XDB repository is not allowed on server side.
-
Cause: For security reasons, ftp and http access over XDB repository is not allowed on server side.
- ORA-64498: FTP and HTTP access over XDB repository is not allowed on server side
-
Cause: For security reasons, ftp and http access over XDB repository is not allowed on server side.
- ORA-64499: ORADB operations not allowed on client-side.
-
Cause: ORADB client access was a security issue.
- ORA-64500: invalid PL/SQL XML parser handle
-
Cause: The PL/SQL XML parser handle was invalid.
- ORA-64501: invalid PL/SQL XSL processor handle
-
Cause: The PL/SQL XSL processor handle was invalid.
- ORA-64502: invalid PL/SQL XSL stylesheet handle
-
Cause: The PL/SQL XSL stylesheet handle was invalid.
- ORA-64503: invalid PL/SQL DOM handle
-
Cause: The PL/SQL DOM handle was invalid.
- ORA-64504: invalid PL/SQL DOM string handle
-
Cause: The named PL/SQL DOM handle was invalid.
- ORA-64505: NULL or invalid string argument specified
-
Cause: The named argument was either invalid or was specified as a NULL.
- ORA-64506: procedure or function not supported
-
Cause: The PL/SQL procedure or function was not supported.
- ORA-64507: ACL path is not valid.
-
Cause: ACL path was not valid.
- ORA-64508: XSLT parameter is not valid.
-
Cause: XSLT parameter was not valid.
- ORA-64509: Mismatch between complexType and SQLType "string".
-
Cause: The attributes referenced in schema definition differ from the attributes referenced by SQLType.
- ORA-64510: Attribute "string" from type "string" is not referenced in schema definition.
-
Cause: At least one attribute, from an existing type, was not referenced in the schema definition.
- ORA-64511: Type "string" is not defined in schema namespace "string".
-
Cause: The specified type was not defined for the given schema component.
- ORA-64512: Storage type "string" in schema is not supported for the packed XML memory object.
-
Cause: The storage type was not supported for the packed XML memory object. The expected type is either RAW or VARCHAR2.
- ORA-64513: invalid use of VIRTUAL COLUMNS clause of XMLType table
-
Cause: There was an invalid use of the VIRTUAL COLUMNS. VIRTUAL COLUMNS clause is only available during XMLType table creation.
- ORA-64514: registration of port failed
-
Cause: The registration of the port failed.
- ORA-64600: duplicate or conflicting SCALE or EXTEND specifications
-
Cause: The specifications were either a duplicate of each other or were conflicting.
- ORA-64601: duplicate RESTART specified
-
Cause: The specified RESTART was a duplicate.
- ORA-64602: CREATE SEQUENCE cannot have a RESTART clause
-
Cause: The RESTART clause was specified in the CREATE SEQUENCE statement.
- ORA-64603: NEXTVAL cannot be instantiated for string. Widen the sequence by string digits or alter sequence with SCALE EXTEND.
-
Cause: The NOEXTEND constraint was specified for the scalable sequence and the generated value was wider than the sequence maximum value.
- ORA-64604: One or more Sharded Sequence objects exist that cannot be downgraded.
-
Cause: There were Sharded Sequence objects in the database that were created in a release later than the selected release for downgrade.
- ORA-64620: duplicate user tablespace specification
-
Cause: An attempt was made to create more than one user tablespace during database creation.
- ORA-64621: SQL statement length (string) exceeds maximum allowed length (string)
-
Cause: An attempt was made to issue a SQL statement that exceeded the maximum allowed length of a statement.
- ORA-64625: bind variables not allowed in the string returned from SQL macro
-
Cause: The string returned from SQL macro contained bind variables.
- ORA-64626: invalid SQL text returned from SQL macro: string
-
Cause: The string returned from the SQL macro was invalid.
- ORA-64627: cycle detected in SQL macro expansion
-
Cause: A SQL macro expansion had a reference to an earlier SQL macro.
- ORA-64628: scalar SQL macro cannot appear in FROM clause of a SQL statement
-
Cause: The scalar SQL macro was called in the FROM clause of a SQL query.
- ORA-64629: table SQL macro can only appear in FROM clause of a SQL statement
-
Cause: The table SQL macro was called from outside of a FROM clause of a SQL query.
- ORA-64630: unsupported use of SQL macro: string
-
- ORA-64632: SQL macro is not supported with string
-
Cause: The SQL macro was not supported with this feature.
- ORA-64633: SQL macro cannot be used remotely
-
Cause: A SQL macro was referenced remotely (for example, through a database link).
- ORA-64634: SQL macro length(string) was too big
-
Cause: SQL Macro created was too big for current memory configuration. Note: Length comprise of user returned string and internally generated SQL fragment.
- ORA-64650: database character set conversion finished with errors.
-
Cause: Conversion of blockchain tables failed while converting the database to Unicode.
- ORA-64651: database not ready for conversion to Unicode
-
Cause: The repository of Database Migration Assistant for Unicode (DMU) indicated that the database was not ready for conversion to Unicode. Or, the repository of DMU was not found in the database.
- ORA-64652: operation not allowed while converting database character set
-
Cause: The requested operation was not allowed while converting the database character set.
- ORA-64653: connection restricted to SYSDBA users while converting database character set
-
Cause: The database was available only to SYSDBA users while converting the database character set.
- ORA-64670: failure to create persistent memory region
-
Cause: An attempt to create a persistent memory region failed.
- ORA-64671: failure to delete persistent memory region
-
Cause: An attempt to delete a persistent memory region failed.
- ORA-64672: failure to attach to a persistent memory region
-
Cause: A process failed to attach to a persistent memory region.
- ORA-64673: failure to detach from a persistent memory region
-
Cause: A process failed to detach from a persistent memory region.
- ORA-64674: failure to allocate persistent memory region
-
Cause: System did not have %llu bytes of available persistent memory.
- ORA-64675: failure to open a persistent memory region
-
Cause: An attempt to open a persistent memory region failed.
- ORA-64677: failure to query system state
-
Cause: An attempt to query the system state failed.
- ORA-64678: enables XGA tracing
-
Cause: Tracing was enabled while doing an operation on XGA memory.
- ORA-64679: failure to read from the persistent memory region backup file
-
Cause: An attempt to read from the persistent memory region backup file failed.
- ORA-64680: failure to write to the persistent memory region backup file
-
Cause: An attempt to write to the persistent memory region backup file failed.
- ORA-64681: The persistent memory region header is corrupt.
-
Cause: An attempt to attach a persistent memory region failed because the region header was corrupt.
- ORA-64682: failed to identify the root object of the persistent memory region
-
Cause: An attempt to attach a persistent memory region failed because the root object could not be identified.
- ORA-64683: out of persistent memory region descriptor slots
-
Cause: Assigning a region descriptor to a persistent memory region failed.
- ORA-64692: too many open files
-
Cause: The system-wide limit on number of open files has been reached.
- ORA-64693: invalid file system for persistent memory region backup file
-
Cause: An attempt to create or open a persistent memory region failed because an invalid file system was specified for the persistent memory region backup file.
- ORA-64700: Recovery Appliance is shutting down
-
Cause: The Recovery Appliance was in the process of shutting down. This message is recorded in the incident log for the Recovery Appliance. When the shutdown completes, the incident is marked as FIXED.
- ORA-64701: storage location string can no longer honor its reservations.
-
Cause: The specified storage location did not contain enough space to fulfill the reservations of all of the databases assigned to it. This error will be seen if a storage location lost part of its disk space and was in the process of being repaired.
- ORA-64702: error repairing container files for storage location string:\nstring
-
Cause: An error was returned while trying to rebuild or repair the container files used to store data from protected databases.
- ORA-64703: resource error detected
-
Cause: A task needed to be interrupted because it detected a resource limitation such as insufficient temporary table space or a snapshot being too old. It will be retried once the contention for the resource decreases. The secondary messages will identify the resource that has been exhausted.
- ORA-64705: no destination in "string" at column string
-
Cause: The storage destination contained a syntax error.
- ORA-64708: more than one polling_location in "string" at column string
-
Cause: More than one polling_location was specified. Only one polling_location is allowed.
- ORA-64709: ASM polling_location is not supported in "string" at column string
-
Cause: The polling_location specified an ASM-based location. Only non-ASM-based polling_locations are supported.
- ORA-64711: storage destination do not reference an ASM diskgroup
-
Cause: The storage destination referenced a non-ASM storage location. Only ASM-based storage destinations are allowed. The operation has been rolled back.
- ORA-64713: requested size string for string was too small; already using string
-
Cause: The size requested for the storage destination was smaller than its current size.
- ORA-64714: requested size string for string was larger than total available space string
-
Cause: The size requested for the storage destination was larger than its current used space plus its currect free space.
- ORA-64715: instance string is not available to Recovery Appliance
-
Cause: The Recovery Appliance could not utilize the specified instance due to its absence from Oracle RAC.
- ORA-64716: storage location string allocation size string does not equal diskgroup string allocation size string
-
Cause: The minimum allocation size of the specified storage location was not the same as the specified diskgroup allocation unit size.
- ORA-64717: network chunk size string is not a multiple of diskgroup string allocation size string
-
Cause: The configured network chunk size was not a multiple of the specified diskgroup allocation unit size.
- ORA-64718: diskgroup string allocation size string is not a power of two
-
Cause: The diskgroup allocation unit size was not a power of two.
- ORA-64719: diskgroup string allocation size string is less than two megabytes string
-
Cause: The diskgroup allocation unit size was less than two megabytes.
- ORA-64720: no containers were created for storage location string
-
Cause: No storage was allocated and initialized for the specified storage location.
- ORA-64721: reserved space string is less than the minimum reservation string
-
Cause: No storage was allocated and initialized for the specified storage location.
- ORA-64722: number of drives must be greater than zero
-
Cause: The specified number of tape drives was NULL or was less than or equal to zero.
- ORA-64723: number of drives reserved for restore operations must be greater than or equal to zero
-
Cause: The number of tape drives reserved for restore operations was NULL or was less than zero.
- ORA-64724: number of restore drives string too large; must be less than string
-
Cause: The number of tape drives reserved for restore operations was at least as large as the total number of drives available. The number of tape drives reserved for restore operations must be at least one less than the total number of drives available.
- ORA-64725: number of streams must be greater than zero
-
Cause: The number of streams was less than or equal to zero.
- ORA-64726: number of streams string too large; must be no larger than string
-
Cause: The number of streams was larger than the total number of drives available. The number of streams must be no larger than the total number of drives available.
- ORA-64727: number of copies string not in the range 1 through 4
-
Cause: The number of copies was either NULL or not in the range 1 through 4 inclusive.
- ORA-64728: replication server name length string is too long
-
Cause: The replication server name was longer than 128 characters.
- ORA-64729: replication server proxy port string must be greater than zero
-
Cause: The replication server proxy port number was less than or equal to zero.
- ORA-64730: replication server proxy URL provided but proxy port is NULL
-
Cause: A replication server proxy URL was provided but a proxy port number was not. If either a proxy URL or a proxy port are specified, both must be specified.
- ORA-64731: replication server proxy port provided but proxy URL is NULL
-
Cause: A replication server proxy port number was provided but a proxy URL was not. If either a proxy URL or a proxy port are specified, both must be specified.
- ORA-64732: HTTP server not configured at replication host
-
Cause: The HTTP server at the replication host site has not been configured.
- ORA-64733: unable to move individual backup piece with BP_KEY string; not a KEEP backup
-
Cause: An attempt was made to move an individual backup piece, but the backup set of which this backup piece was a member was not a KEEP backup.
- ORA-64735: unknown incarnation detected at Recovery Appliance, need catalog resync
-
Cause: A new archived log or backup set belonging to the new incarnation was received at Recovery Appliance.
- ORA-64736: Task ID string of type string has been interrupted string times.
-
Cause: The specified task was restarted an unexpected number of times. Tasks get interrupted when there is competition for resources. This is only a warning. It does not necessarily indicate a problem with the Recovery Appliance.
- ORA-64737: unable to copy a full backup of database string to tape or replicated Recovery Appliance
-
Cause: While creating a full database backup to tape or to a replicated recovery appliance, level 0 backups of one or more data files were missing.
- ORA-64738: guaranteed copy suspended for database string
-
Cause: One of the following operations was performed resulting in the database using more than its allotted disk space: - UPDATE_DB lowering the DISK_SPACE_RESERVE value. - UPDATE_PROTECTION_POLICY setting the guaranteed_copy parameter to YES - DELETE_SBT_LIBRARY where backup data for the given database existed. New backup requests may be stalled until the system can recompute the safety of allowing additional backup data or backup data may be lost.
- ORA-64740: Redo and backups from database string have not been seen for more than UNPROTECTED_WINDOW period.
-
Cause: An UNPROTECTED_WINDOW parameter in a protection policy was specified and the Recovery Appliance could not receive sufficient online redo, archive log backups, or data file backups from the specified target database for at least that period.
- ORA-64741: Scheduler string running task string of type string did not stop after string requests.
-
Cause: The specified Recovery Appliance scheduler process could not be stopped.
- ORA-64742: database string is being deleted
-
Cause: The current command failed because the database was in the process of being deleted.
- ORA-64743: database string failed to purge all data files during a delete_db operation
-
Cause: Attempts to remove all data from the database failed.
- ORA-64744: Argument string is null, invalid, or out of range.
-
Cause: The argument was expecting a non-null, valid value but the argument value passed in was null, invalid, or out of range.
- ORA-64745: Name length is string characters; maximum length is string characters.
-
Cause: The length of the name exceeded the limit.
- ORA-64746: Name contains invalid characters.
-
Cause: The name incorrectly started with "_", "-", ":", "#" or digits or contained non-alphanumeric characters. Verify that all other double quotation marks, if any, in the string are adjacent pairs of double quotation marks. Double quotation marks must not be used in the middle of the name.
- ORA-64747: Name contains invalid character "string" at the position [string].
-
Cause: The name incorrectly started with "_", "-", ":", "#" or digits or contained non-alphanumeric characters. Verify that all other double quotation marks, if any, in the string are adjacent pairs of double quotation marks. Double quotation marks must not be used in the middle of the name.
- ORA-64748: trace file writing initiated using string
-
Cause: The configuration of the Recovery Appliance was modified to enable the production of trace files. Trace files have the capacity to exhaust disk space on the Recovery Appliance.
- ORA-64750: Instance string is unable to access string.
-
Cause: The Recovery Appliance was unable to find a file that is required for its operation.
- ORA-64751: replication setup error during string; replication server: string database: string
-
Cause: The Recovery Appliance was unable to complete the configuration and setup of replication for the database specified.
- ORA-64752: storage unavailable for new redo or backups for database string
-
Cause: There was a failure while backing up redo or copying backups from a polling location. This condition may be due to one of the following reasons: * An individual backup piece exceeded the database protection policy DISK_RESERVE_SPACE value. * Guaranteed_copy is enabled but not enough data has been spooled to tape. * Misconfiguration of the storage location size.
- ORA-64753: Incorrect object type specified; specified string, expected string
-
Cause: An incorrect object type was given to an API command.
- ORA-64754: unable to perform operation with associated tape or replication objects
-
Cause: An attempt to execute 'update_db' or 'update_protection_policy' and change storage locations with a replication server or tape job associated with the protection policy failed.
- ORA-64755: failed to delete database string; the Recovery Appliance is not running
-
Cause: An attempt was made to delete a database, but the Recovery Appliance has been deactivated by the administrator.
- ORA-64757: unable to restore backup piece with BP_KEY string
-
Cause: An attempt was made to restore the specified backup piece which resulted in an error. An explanation of the error appears in the following messages.
- ORA-64758: unable to grow delta store metadata in tablespace string
-
Cause: Additional extents could not be allocated for the tables used to implement the delta store.
- ORA-64759: Recovery Appliance is leaving restricted resources state
-
Cause: The Recovery Appliance ended its restrictions on task execution. The restricted resources state was entered when tasks could not run due to insufficient temporary table space or insufficient undo space. At that time, resource intensive tasks were put into RESOURCE_WAIT state.
- ORA-64760: Database string has had tasks in ordering wait state for over string days.
-
Cause: The specified database had an INDEX_BACKUP task that could not be run because the task did not tile against the delta store. An incremental backup piece could not tile into the delta store because the necessary control file information was missing or because the backup that it depended upon was not found in the delta store.
- ORA-64761: disk group string is not usable by the Recovery Appliance
-
Cause: A disk group was supplied to either the create_storage_location or update_storage_location APIs that was not previously prepared by the installation software for the Recovery Appliance.
- ORA-64762: Task string of type string has been running for string.
-
Cause: The specified task did not complete its execution after a reasonable period. This is only a warning message.
- ORA-64763: Task string of type string was terminated after running for string.
-
Cause: The specified task did not complete and was presumed hung. Its process was stopped and restarted.
- ORA-64766: backup deletion using RMAN prevented by protection policy
-
Cause: Recovery Manager was prevented from deleting a backup piece because the 'allow_backup_deletion' parameter of the applicable Recovery Applicance protection policy was 'NO'.
- ORA-64767: restore timed out
-
Cause: The Recovery Appliance terminated the restore operation due to unresponsiveness of the client database.
- ORA-64768: KEEP file size string cannot exceed available DISK_RESERVED_SPACE string.
-
Cause: There was no more space for a KEEP backup piece. The total DISK_RESERVED_SPACE minus the space currently consumed by KEEP backups was less than the size of the current KEEP backup piece. The piece that caused the error was deleted.
- ORA-64771: reconcile error during string; replication server: string; database: string
-
Cause: The specified database was unable to reconcile with the specified replication server. This is typically due to either a network communication failure, missing or incorrect credentials, incorrect wallet credentials, missing or incorrectly ordered add_db and grant_db_access calls.
- ORA-64772: downstream replication server: string is not accessible
-
Cause: The specified downstream replication server was not running, was not accesible, had incorrect credentials for the replication user in the upstream wallet, or was in the process of starting up or shutting down.
- ORA-64773: Note: string generated during execution of API command: string
-
Cause: The specified command was entered correctly but an unexpected event occurred during its processing.
- ORA-64774: database string has replication tasks in reconcile wait state for over string days
-
Cause: The specified database had a BACKUP_SBT task that could not be run because the task was waiting for a successful reconcile.
- ORA-64775: unable to execute required code on the downstream replication server for the specified database
-
Cause: The specified database could not execute the required code on the downstream replication server. This is typically due to a missing add_db or grant_db_access on the downstream or the commands were issued in the incorrect order.
- ORA-64776: message from downstream replication server during string: string
-
Cause: An unexpected event occurred at the downstream replication server.
- ORA-64777: deletion of polled file failed
-
Cause: The Recovery Appliance could not delete the file that was backed up from the polling location.
- ORA-64778: privilege not granted to string for database: string
-
Cause: The privilege that was revoked was not granted to the user for this protected database, the revoke was not required.
- ORA-64779: The catalog is missing necessary control file information for database string.
-
Cause: A backup arrived before the Recovery Appliance could receive all the necessary control file information. INDEX_BACKUP tasks for these data files remain in ORDERING_WAIT state until the catalog receives all the information.
- ORA-64780: Section 1 of multi-section backup set string of data file string has not reached this Recovery Appliance.
-
Cause: Section 1 of the multi-section backup did not reach the Recovery Appliance. Without the section, INDEX_BACKUP tasks of other sections of the backup set remain in ORDERING_WAIT state.
- ORA-64781: Section string of the prior multi-section backup set string of data file string is missing.
-
Cause: A section of the previous multi-section backup prior to the current backup was missing. Without the section, INDEX_BACKUP tasks for processing the current backup set remain in ORDERING_WAIT state.
- ORA-64782: Missing backups between SCNs string and string for data file string.
-
Cause: There was a gap in backups provided to the Recovery Appliance. Without the backup, the current backup could not be processed, and the INDEX_BACKUP task remained in ORDERING_WAIT state.
- ORA-64783: The backup of data file string is tiling with a backup written to different media.
-
Cause: The backup on which the current backup piece depends was written to different media and no longer resides on this Recovery Appliance.
- ORA-64784: Corruption found in backup string of data file string in Recovery Appliance. New backup cannot be processed.
-
Cause: A new backup could not be processed because the most recent backup piece of the data file residing in the Recovery Appliance was corrupt.
- ORA-64785: Online redo shipping for DBID string cannot be performed because the Recovery Appliance is not available.
-
Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the Recovery Appliance was not running.
- ORA-64786: Online redo shipping for DBID string cannot be performed because the delta store is under repair.
-
Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the delta store was under repair.
- ORA-64787: Online redo shipping for DBID string cannot be performed because it is removed from the Recovery Appliance
-
Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the database was removed.
- ORA-64788: Online redo shipping for DBID string cannot be performed because its platform is unknown.
-
Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because an initial backup from the database was not supplied. The initial backup provides the platform identification to the Recovery Appliance.
- ORA-64789: Online redo shipping for DBID string cannot be performed because its storage location needs repair.
-
Cause: The database for the Recovery Appliance was opened by specifying resetlogs.
- ORA-64790: Online redo shipping for DBID string cannot be performed because it is not known by the Recovery Appliance.
-
Cause: The database was not identified in the catalog of the Recovery Appliance.
- ORA-64792: incorrect catalog_user_name parameter specified in create_replication_server
-
Cause: An incorrect catalog_user_name parameter was specified in the create_replication_server or update_replication_server API.
- ORA-64793: unexpected scheduler exit
-
Cause: The task scheduler failed with an unexpected error code in the Recovery Appliance.
- ORA-64794: unable to access the encryption HSM wallet or the encryption wallet is not open on the current instance
-
Cause: Encryption required a Hardware Security Module (HSM) wallet that was open across all instances.
- ORA-64795: unable to access or create the encryption key
-
Cause: Encryption could not create or obtain the required access to a valid backup encryption key during the copy to tape operation.
- ORA-64796: unable to create encrypted backup during copy to tape
-
Cause: During the copy to tape operation, backup encryption could not create or obtain the required access to a valid encryption key.
- ORA-64797: waiting for recall of backup piece string from cloud storage
-
Cause: Restore was waiting for a recall of the backup piece from cloud storage.
- ORA-64798: encryption key does not exist in wallet of executing instance
-
Cause: The protected databases current encryption key did not exist in the wallet of the Oracle RAC instance or the instance that was executing the copy to tape operation.
- ORA-64799: System Backup to Tape (SBT) job template requires encryption for the specified library.
-
Cause: Encryption was not specified for a library that requires encryption.
- ORA-64800: unable to create encrypted backup for big endian platform
-
Cause: Copy to tape operation could not create encrypted backup for big endian platform.
- ORA-64801: Altering RASYS password in SQL is not allowed.
-
Cause: RASYS Password modification attempted via SQL.
- ORA-64803: failure to get ingest name for archivelog grouping
-
Cause: The Oracle backup process was unable to get the ingest name needed to connect to the Oracle restore process.
- ORA-64804: cannot reinsert deleted backup into delta store
-
Cause: The specified backup could not be reinserted into the delta store, because it either was previously deleted or contained a corresponding virtual backup in the same backup set that was removed from the catalog.
- ORA-64805: cannot reinsert virtual full backup into delta store
-
Cause: Virtual full backups or copies of virtual full backups could not be reinserted into the delta store because it could corrupt existing backups of the database.
- ORA-64806: incorrect or all NULL input parameters specified for reset_error API
-
Cause: Some or all of the input parameters specified for reset_error API were incorrect or they were all NULL input parameters.
- ORA-64807: datafile encryption information for database string does not match
-
Cause: A datafile was encrypted or rekeyed on the protected database and now the encryption key for the current INCREMENTAL LEVEL 1 backup does not match the prior encryption key.
- ORA-64808: Initialization parameter string has more than one SID value specified
-
Cause: There were multiple instance settings for one initialization parameter.
- ORA-64809: Initialization parameter string does not match the recommended value
-
Cause: Initialization parameter did not match the recommended value.
- ORA-64810: Initialization parameter string is not set with the proper value
-
Cause: Initialization parameter was not set with the proper value.
- ORA-64811: Initialization parameter string has a non-default value.
-
Cause: Initialization parameter had a non-default value.
- ORA-64812: -force option is required to ignore checking string initialization parameter
-
Cause: An attempt was made to ignore checking the initialization parameter value without specifying the -force option.
- ORA-64813: Task string is being suspended.
-
Cause: A Recovery Appliance task failed 10 times and is now going into SUSPENDED state. A suspended task will be retried every few days until it successfully completes.
- ORA-64816: cannot create a replication server to an old version downstream Recovery Appliance
-
Cause: The downstream Recovery Appliance was an older version.
- ORA-64817: error interacting with downstream Recovery Appliance during string; replication server: string; database: string
-
Cause: An error was encountered during communication or conversation with a downstream Recovery Appliance for the specified database with the specified replication server. This was typically due to a network communication failure, missing or incorrect wallet credentials, or missing or incorrectly ordered ADD_DB and GRANT_DB_ACCESS calls. The error could also indicate an issue during the conversation with the remote Recovery Appliance.
- ORA-64818: The polling feature is not supported for multiple tenants.
-
Cause: The polling feature did not work on multiple tenants.
- ORA-64819: Database string (string), string (string) does not exist.
-
Cause: The database did not exist.
- ORA-64820: DB_KEY string does not exist.
-
Cause: The database associated with the specified DB_KEY was not found in the Recovery Appliance.
- ORA-64821: DF_KEY string does not exist.
-
Cause: The data file associated with the specified DF_KEY was not found in the Recovery Appliance.
- ORA-64822: Log file cannot be accepted from DBID string on Tkey string.
-
Cause: While performing redo shipping for the specified database, an error was detected that prevented the creation of the log file.
- ORA-64823: unable to move individual backup piece with BP_KEY string; backup piece is not ready to move
-
Cause: An attempt was made to move an individual backup piece, but the move backup operation encountered the resource busy issue for this backup piece. The backup piece still needed to replicate.
- ORA-64830: Incremental backup for database string is not up-to-date.
-
Cause: This could be caused by an undersized appliance or it indicates that there was a problem with the backup for a particular database.
- ORA-64831: There are no outstanding backups to request for the specified group.
-
Cause: The backup request group was either empty or had requested all of the backups.
- ORA-64832: error interacting with remote Recovery Appliance: string; replication server: string; database: string
-
Cause: An error was encountered during communication or conversation with a remote Recovery Appliance for the specified database with the specified replication server. This is typically due to a network communication failure, missing or incorrect wallet credentials, or missing ADD_DB and GRANT_DB_ACCESS calls. The error could also indicate an issue during the conversation with the remote Recovery Appliance.
- ORA-64901: INMEMORY_SIZE may not exceed 16 GB with Database In-Memory Base Level
-
Cause: INMEMORY_SIZE cannot be greater than 16 GB because the Database In-Memory Base Level was enabled.
- ORA-64902: Database In-Memory Base Level can only be modified in the initialization parameter file
-
Cause: The Database In-Memory Base Level could not be enabled or disabled dynamically.
- ORA-64903: Database Cell Memory Level can only be modified in the initialization parameter file
-
Cause: The Database Cell Memory Level could not be enabled or disabled dynamically.
- ORA-64904: In-Memory not supported on HDFS tablespace
-
Cause: An attempt was made to enable In-Memory on a table or fragment with data in Hadoop Distributed File System (HDFS) tablespace.
- ORA-64905: score operator not supported for INMEMORY TEXT
-
Cause: An attempt was made to use the score operator on an In-Memory Oracle Text query.
- ORA-64906: DBMS_INMEMORY_ADMIN package invalid option specification.
-
Cause: The value of one of the option parameters was incorrect.
- ORA-64907: DBMS_INMEMORY_ADMIN required parameter is NULL or missing.
-
Cause: Some of the procedures were called with missing or NULL parameters.
- ORA-64908: The Database In-Memory size cannot be increased.
-
Cause: Oracle Database In-Memory (Database In-Mmeory) could not be enabled because an invalid value was specified for the initial Database In-Memory size.
- ORA-64909: The Database In-Memory size must be increased by a minimum of string MB.
-
Cause: Oracle Database In-Memory (Database In-Memory) size did not increase by the minimum required value.
- ORA-64910: A reduction in the Database In-Memory size cannot be completed.
-
Cause: The parameter was set to disable any reduction of the Oracle Database In-Memory size (Database In-Memory).
- ORA-64911: The Database In-Memory size must be at least the initial value string MB.
-
Cause: The attempt to reduce the Oracle Database In-Memory (Database In-Memory) size was less than the initialized size.
- ORA-64912: The Database In-Memory size must be less than string MB.
-
Cause: The Oracle Database In-Memory (Database In-Memory) size was larger than 70% of the system global area (SGA) target.
- ORA-64913: The Database In-Memory size cannot be increased more than string MB for PDB ID string.
-
Cause: The The Oracle Database In-Memory (Database In-Memory) size for the pluggable database (PDB) exceeded the total Database In-Memory size for the container.
- ORA-64914: The Database In-Memory size cannot be increased more than string MB for PDB ID string.
-
Cause: The Oracle Database In-Memory (Database In-Memory) size of the pluggable database (PDB) exceeded the PDB system global area (SGA) target size.
- ORA-64915: A Database In-Memory resize is already in progress
-
Cause: Changing the Oracle Database In-Memory (Database In-Memory) size could not be performed until the current resize completed.
- ORA-64916: The Database In-Memory resize cannot be completed.
-
Cause: Changing the Oracle Database In-Memory (Database In-Memory) size could not be performed due to insufficient space for the resize.
- ORA-65000: missing or invalid pluggable database name
-
Cause: A valid pluggable database name was not present where required.
- ORA-65001: missing or invalid administrative user name
-
Cause: A valid administrative user name was not present where required by the syntax of CREATE PLUGGABLE DATABASE statement.
- ORA-65002: missing or invalid administrative user password
-
Cause: A valid administrative user password was not present where required by the syntax of CREATE PLUGGABLE DATABASE statement.
- ORA-65003: missing or invalid XML file name
-
Cause: A valid XML file name was not present where required by the syntax of CREATE PLUGGABLE DATABASE statement.
- ORA-65004: missing or invalid database link name
-
Cause: A valid database link name was not present where required by the syntax of CREATE PLUGGABLE DATABASE statement.
- ORA-65005: missing or invalid file name pattern for file - string
-
Cause: Either source or replacement file name pattern was missing or invalid in a SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause.
- ORA-65006: missing or invalid ENABLE PLUGGABLE DATABASE clause
-
Cause: An ENABLE PLUGGABLE DATABASE clause was not present where required by the syntax of CREATE DATABASE statement.
- ORA-65007: duplicate ENABLE PLUGGABLE DATABASE clause
-
Cause: A duplicate ENABLE PLUGGABLE DATABASE clause was specified in a CREATE DATABASE statement.
- ORA-65008: missing or invalid SEED clause
-
Cause: A SEED clause was not present where required by the syntax of CREATE DATABASE statement.
- ORA-65009: cannot open pluggable database in read-write mode
-
Cause: The datafiles belonging to the pluggable database were read-only.
- ORA-65010: maximum number of pluggable databases created
-
Cause: The number of pluggable databases exceeded either the MAX_PDBS property value or the maximum supported number of pluggable databases.
- ORA-65011: Pluggable database string does not exist.
-
Cause: User attempted to specify a pluggable database that does not exist.
- ORA-65012: Pluggable database string already exists.
-
Cause: User attempted to create a pluggable database with a name that already exists.
- ORA-65013: invalid CONTAINER clause
-
Cause: An invalid CONTAINER clause was encountered.
- ORA-65014: invalid SHARING clause
-
Cause: An invalid SHARING clause was encountered.
- ORA-65015: missing or invalid container name
-
Cause: A valid container name was not present where required by the syntax of ALTER SESSION SET CONTAINER or ALTER USER ... SET|ADD|REMOVE CONTAINER_DATA statement.
- ORA-65016: FILE_NAME_CONVERT must be specified
-
Cause: Data files, and possibly other files, needed to be copied as a part of creating a pluggable database. However, Oracle Managed Files (OMF) was not enabled, PDB_FILE_NAME_CONVERT was not defined, and there was a failure to specify the FILE_NAME_CONVERT clause.
- ORA-65017: seed pluggable database may not be dropped or altered
-
Cause: User attempted to drop or alter the Seed pluggable database which is not allowed.
- ORA-65018: FILE_NAME_CONVERT or NOCOPY must be specified
-
Cause: Oracle Managed Files (OMF) was not enabled and PDB_FILE_NAME_CONVERT was not defined. The FILE_NAME_CONVERT or the NOCOPY clause was not specified as a part of creating a pluggable database using data files.
- ORA-65019: pluggable database string already open
-
Cause: An attempt was made to open a pluggable database that was already opened.
- ORA-65020: pluggable database string already closed
-
Cause: An attempt was made to close a pluggable database that was already closed.
- ORA-65021: illegal use of SHARING clause
-
Cause: A SHARING clause was encountered in unexpected context.
- ORA-65022: CONTAINER clause already specified
-
Cause: A statement contained multiple CONTAINER clauses.
- ORA-65023: active transaction exists in container string
-
Cause: A statement attempted to create a new transaction in the current container while there was an active transaction in another container.
- ORA-65024: Pluggable database string is not open.
-
Cause: An operation was attempted on a pluggable database that was not open.
- ORA-65025: Pluggable database string is not closed on all instances.
-
Cause: An operation was attempted on a pluggable database that was not closed on all Oracle RAC instances.
- ORA-65026: XML metadata file error : string
-
Cause: An error occurred while trying to parse or write to the XML metadata file.
- ORA-65027: XML metadata file error while getting node or value for (string - string)
-
Cause: An error occurred while trying to parse the XML metadata file.
- ORA-65028: Unable to open plugin data file at path string
-
Cause: Error occurred while trying to open the data file.
- ORA-65029: a Local User may not grant or revoke a Common Privilege or Role
-
Cause: A Local User issued a GRANT or REVOKE statement specifying CONTAINER=ALL, which is illegal.
- ORA-65030: cannot grant a privilege commonly to a local user or role
-
Cause: A GRANT statement was issued specifying CONTAINER=ALL and naming a local user or role as a grantee, which is illegal.
- ORA-65031: cannot revoke a privilege commonly from a local user or role
-
Cause: A REVOKE statement was issued specifying CONTAINER=ALL and naming a local user or role as a revokee, which is illegal.
- ORA-65032: A local role may only be granted or revoked within the current container.
-
Cause: A GRANT or REVOKE statement was issued specifying CONTAINER=ALL and listing a local role among the roles to be granted or revoked, which is illegal.
- ORA-65033: a common privilege may not be granted or revoked on a local object
-
Cause: A GRANT or REVOKE statement was issued specifying CONTAINER=ALL and naming a local object on which privileges are to be granted or revoked, which is illegal.
- ORA-65034: PDB describe output file not specified
-
Cause: User attempted to describe a pluggable database without specifying an output XML file location.
- ORA-65035: unable to create pluggable database from string
-
Cause: An attempt was made to clone a pluggable database that did not have local undo enabled.
- ORA-65036: pluggable database string not open in required mode
-
Cause: Attempted to perform an operation on a pluggable database in incorrect open mode.
- ORA-65037: A privilege on a local user may not be granted or revoked commonly.
-
Cause: A GRANT or REVOKE statement was issued specifying CONTAINER=ALL and naming a local user on which privileges are to be granted or revoked, which is illegal.
- ORA-65039: container identifier column missing or is of unexpected type in a definition of a CONTAINER_DATA object
-
Cause: Table or view whose definition contained a CONTAINER_DATA clause lacked a column used to identify a container to which data belongs or the column was of unexpected type.
- ORA-65040: operation not allowed from within a pluggable database
-
Cause: An operation was attempted that can only be performed in the root or application root container.
- ORA-65041: CONTAINER_DATA attribute for this user cannot be modified
-
Cause: An attempt was made to modify CONTAINER_DATA attribute for user SYS or SYSBACKUP which is disallowed.
- ORA-65042: name is already used by an existing container
-
Cause: The name was already used by another container.
- ORA-65043: TABLESPACE keyword expected
-
Cause: TABLESPACE keyword was missing.
- ORA-65044: missing or invalid option following STORAGE keyword
-
Cause: An option other than MAXSIZE or MAX_SHARED_TEMP_SIZE was specified.
- ORA-65045: pluggable database not in a restricted mode
-
Cause: An operation was attempted on a pluggable database that was not in restricted mode.
- ORA-65046: operation not allowed from outside a pluggable database
-
Cause: An operation was attempted that can only be performed from within a pluggable database.
- ORA-65047: Object string.string is invalid or compiled with errors in root.
-
Cause: An attempt was made to issue a metadata link DDL for an object that was invalid or compiled with errors in a CDB$ROOT or an application root.
- ORA-65048: error encountered when processing the current DDL statement in pluggable database string
-
Cause: An error was encountered when executing a statement in one of the pluggable databases.
- ORA-65049: Creation of local user or role is not allowed in this container.
-
Cause: An attempt was made to create a local user or role in CDB$ROOT or an application root.
- ORA-65050: Common DDLs only allowed in root.
-
Cause: An attempt was made to issue a common DDL in a pluggable database.
- ORA-65051: missing valid container identifier
-
Cause: A valid container identifer was not specified.
- ORA-65052: statement involves operations with different container scope
-
Cause: An attempt was made to combine one operation that applies to all containers with another that only applies to the local container into one statement.
- ORA-65053: A global user cannot change the container in the session.
-
Cause: An attempt was made by a global user to change the container using the ALTER SESSION SET CONTAINER statement.
- ORA-65054: Cannot open a pluggable database in the desired mode. PDB opening in string, CDB opened in string.
-
Cause: An attempt was made to open a pluggable database (PDB) in a mode incompatible with the multitenant container database (CDB) or, if the PDB belonged to an application container, in a mode incompatible with the application root.
- ORA-65056: CONTAINER_DATA attribute is not used in a pluggable database.
-
Cause: User connected to a pluggable database attempted to modify a CONTAINER_DATA attribute, which is illegal.
- ORA-65057: CONTAINER_DATA attribute must always include the current container
-
Cause: User issuing ALTER USER ... SET|REMOVE CONTAINER_DATA = ... statement attempted to exclude the current container from a CONTAINER_DATA attribute.
- ORA-65058: object-specific CONTAINER_DATA attribute may only be specified for a CONTAINER_DATA object
-
Cause: Object referenced in an ALTER USER statement modifying an object-specific CONTAINER_DATA attribute is not a CONTAINER_DATA table or view.
- ORA-65059: duplicate container name in CONTAINER_DATA clause
-
Cause: Duplicate references to a name of some container was encountered in a CONTAINER_DATA clause.
- ORA-65060: CONTAINER_DATA attribute is not set
-
Cause: User attempted to add container(s) to an object-specific CONTAINER_DATA attribute which has not been explicitly set or has been set to DEFAULT or remove containers from a CONTAINER_DATA attribute which has not been explicitly set or has been set to DEFAULT.
- ORA-65061: some of specified containers do not belong to the CONTAINER_DATA attribute
-
Cause: User attempted to remove from a CONTAINER_DATA attribute container(s) which do not belong to it.
- ORA-65062: CONTAINER_DATA attribute is set to ALL
-
Cause: User attempted to add or remove containers to or from a CONTAINER_DATA attribute whose current value is ALL, which is not supported.
- ORA-65063: CONTAINER_DATA clause has already been specified
-
Cause: The CONTAINER_DATA clause was specified twice.
- ORA-65064: incorrect contents of XML metadata file
-
Cause: The contents of the XML metadata file were different from the actual file properties.
- ORA-65065: A local user or role can only be altered within the current container
-
Cause: The ALTER USER or ALTER ROLE statement was issued specifying CONTAINER=ALL and listing a local user or role among the users or roles to be altered, which is illegal.
- ORA-65066: The specified changes must apply to all containers
-
Cause: An attempt was made to apply the specified changes to the current container.
- ORA-65067: DEFAULT ROLE clause referencing a local role can only apply to the current container
-
Cause: An attempt was made to reference a local role across all containers using the DEFAULT ROLE clause.
- ORA-65068: cannot define a trigger that fires after a pluggable database is unplugged
-
Cause: An attempt was made to create a trigger that fires after a pluggable database has been unplugged. This type of trigger is not supported.
- ORA-65069: AFTER DB_ROLE_CHANGE triggers cannot be defined on a pluggable database
-
Cause: An attempt was made to create a pluggable database trigger that fires after a role change occurs from a standby database to primary or vice versa. This type of trigger is not supported.
- ORA-65070: AFTER CLONE trigger can only be created on a pluggable database
-
Cause: An attempt was made to create an AFTER CLONE trigger on a schema or a database. This type of trigger is not supported.
- ORA-65071: BEFORE UNPLUG trigger can only be created on a pluggable database
-
Cause: An attempt was made to create a BEFORE UNPLUG trigger on a schema or a database. This type of triggers is not supported.
- ORA-65072: user must be connected to a pluggable database on which a trigger is being created
-
Cause: An attempt was made to create a database event trigger on a pluggable database while not connected to a pluggable database. This is not supported.
- ORA-65073: cannot define a trigger that fires before a pluggable database is cloned
-
Cause: An attempt was made to create a trigger that fires before a pluggable database has been cloned. This type of trigger is not supported.
- ORA-65074: editions not supported for common users
-
Cause: An attempt was made to support editions for common users.
- ORA-65075: cannot recover the pluggable database
-
Cause: The pluggable database has been dropped.
- ORA-65076: incompatible SYSTEM tablespace in database being plugged in
-
Cause: An attempt was made to plug in a database that had a SYSTEM tablespace whose relative file number was not one. The most common cause of this error is when the database has been created using Oracle Database release 7 or earlier and then upgraded using the migrate utility.
- ORA-65080: cannot determine pluggable database name
-
Cause: An attempt was made to map the database ID to the pluggable database name.
- ORA-65081: database or pluggable database is not open in read only mode
-
Cause: An operation was attempted on a database or pluggable database that is not open in read only mode
- ORA-65082: cannot add any more pluggable databases: limit of string exceeded
-
Cause: There was no more room in the control file for adding pluggable databases.
- ORA-65083: pluggable database string shutdown in progress
-
Cause: The pluggable database is in the middle of shutdown abort
- ORA-65084: object string.string does not exist in root
-
Cause: An attempt was made to create a common object that does not exist in root.
- ORA-65085: cannot open pluggable database in read-only mode
-
Cause: The pluggable database has either been created and not opened or has not been opened in read/write mode after the undo mode has been changed for the multitenant container database (CDB).
- ORA-65086: cannot open/close the pluggable database
-
Cause: The pluggable database has been unplugged.
- ORA-65087: Oracle-supplied operation not allowed from within a pluggable database
-
Cause: An operation in an Oracle-supplied script was attempted that can only be performed in the root container.
- ORA-65088: database open should be retried
-
Cause: An inconsistency between the control file and the data dictionary was found and fixed during the database open. The database open needs to be executed again.
- ORA-65089: pluggable database is not clean
-
Cause: The pluggable database was not open anywhere but was not marked as clean yet.
- ORA-65090: operation only allowed in a container database
-
Cause: User attempted an operation that is only allowed in a CDB
- ORA-65091: operation on string not allowed in a pluggable database
-
Cause: An undo tablespace or rollback segment operation was attempted that can only be performed in the root container.
- ORA-65092: system privilege granted with a different scope to 'string'
-
Cause: An attempt was made to revoke a system privilege that was granted with a different scope.
- ORA-65093: multitenant container database not set up properly
-
Cause: An attempt was made to open a multitenant container database without the correct parameter set for a multitenant container database in the initialization parameter file.
- ORA-65094: invalid local user or role name
-
Cause: An attempt was made to create a local user or role with a name that was not valid for local users or roles. In addition to the usual rules for user and role names, local user and role names cannot start with C## or c##. When connected to a locked down Pluggable Database (PDB) with LOCAL_OBJECT_RESERVED_NAME feature disabled, PDB local user or role can't have the same name as that of an Oracle reserved user or role name like MDSYS, WMSYS etc.
- ORA-65095: invalid common object name
-
Cause: An attempt was made to create a common object with a name that was not valid for common objects. In addition to the usual rules for object names, common object names must consist only of ASCII characters.
- ORA-65096: invalid common user or role name
-
Cause: An attempt was made to create a common user or role with a name that was not valid for common users or roles. In addition to the usual rules for user and role names, common user and role names must consist only of ASCII characters, and must contain the prefix specified in common_user_prefix parameter.
- ORA-65097: DML into a data link table is outside an application action
-
Cause: DML into a data link table was attempted outside an application action.
- ORA-65098: DML into an extended data link table is outside an application action
-
Cause: DML into an extended data link table was attempted in an application root outside an application action.
- ORA-65099: operation cannot be performed when the CDB is not open
-
Cause: An operation was attemped inside a pluggable database that required the container database (CDB) to be open.
- ORA-65100: missing or invalid path prefix - string
-
Cause: The path prefix was missing or invalid. This can also happen if any of the following are true: - The directory path specified by PATH_PREFIX clause contains the string '..' or an invalid path separator like // or exceeds the maximum length supported on host operating system. - The target path already exists as a file in operating system. - The ROOT container (CDB$ROOT, when connected to a pluggable database or application root, when connected to an application container) has a PATH_PREFIX set and either NONE or a directory location outside ROOT containers' PATH_PREFIX was specified.
- ORA-65101: container database set up incorrectly
-
Cause: An attempt was made to use a non container database control file to startup a container database (CDB).
- ORA-65102: missing or invalid instance name
-
Cause: A valid instance name was not present where required by the syntax of a ALTER PLUGGABLE DATABASE statement.
- ORA-65103: UPGRADE cannot be specified for PDBs being open in READ ONLY mode
-
Cause: ALTER PLUGGABLE DATABASE ... OPEN UPGRADE was specified, but the root is open READ ONLY, so the specified PDBs will also be opened READ ONLY, and UPGRADE cannot be specified for PDBs being opened READ ONLY.
- ORA-65104: operation not allowed on an inactive pluggable database
-
Cause: The pluggable database status was INACTIVE. It was still being created or there was an error during the create operation.
- ORA-65105: SYSTEM data file for pluggable database #string not found
-
Cause: Data files were not specified in a CREATE CONTROLFILE statement in the SYSTEM tablespace of a pluggable database.
- ORA-65106: Pluggable database #string (string) is in an invalid state.
-
Cause: Data files were not specified in a CREATE CONTROLFILE statement of a pluggable database.
- ORA-65107: Error encountered when processing the current task on instance:string
-
Cause: An error was encountered when executing a pluggable database task on one of the Oracle RAC instances.
- ORA-65108: invalid use of a cursor belonging to another container
-
Cause: An attempt was made to use a cursor that was parsed or executed in a different container.
- ORA-65109: operation not allowed in CDB$ROOT
-
Cause: An operation was attempted that is not supported in the Container Database root.
- ORA-65110: Invalid instance name specified
-
Cause: An attempt was made to use an invalid or inactive instance name in the INSTANCES clause.
- ORA-65111: Cannot relocate to the same instance
-
Cause: An attempt was made to relocate a pluggable database to the current instance.
- ORA-65112: pluggable database string not closed on all instances of the standby database
-
Cause: Media recovery stopped because the pluggable database was either unplugged, dropped or renamed on the primary database.
- ORA-65113: value of MAX_PDB_STORAGE property for the PDB is too low
-
Cause: The value of MAX_PDB_STORAGE specified in the ALTER or CREATE PLUGGABLE DATABASE statement is less than the current space usage of data files and temporary files of the container.
- ORA-65114: space usage in container is too high
-
Cause: Space usage in the current container exceeded the value of MAX_PDB_STORAGE for the container.
- ORA-65115: CDB resource plan string has more than string PDB directives.
-
Cause: An attempt was made to create or update the specified multitenant container database (CDB) resource plan to use more than the supported number of directives.
- ORA-65116: incompatible database character set
-
Cause: The database character set of the container database was not a superset of the database character set of the pluggable database being plugged in.
- ORA-65117: CONTAINER clause may only be specified when connected to a container database
-
Cause: The CONTAINER clause was specified when not connected to a container database (CDB).
- ORA-65118: operation affecting a pluggable database cannot be performed from another pluggable database
-
Cause: An attempt was made to perform an operation affecting a pluggable database while connected to a different pluggable database.
- ORA-65119: incompatible national character set
-
Cause: The national character set of the container database was not the same as the national character set of the pluggable database being plugged in.
- ORA-65120: illegal character set ID in XML metadata file
-
Cause: The XML metadata file for the pluggable database being plugged in contained a database or national character set ID that was not valid for the container database. This can happen if the XML file is manually modified, if it is corrupted on disk, or if the set of supported character sets differs between the container database and the source database of the pluggable database because a user-defined character set has not been installed in the Oracle Home directory of the container database.
- ORA-65121: ALTER SESSION SET CONTAINER not allowed from this client
-
Cause: Clients earlier than Oracle Database 12c Release 1 do not support this feature.
- ORA-65122: Pluggable database GUID conflicts with the GUID of an existing container.
-
Cause: While creating a pluggable database, the GUID conflicted with the GUID of an existing container in the container database.
- ORA-65123: cannot perform a SET CONTAINER operation in this context
-
Cause: An attempt was made to set the container inside a context where such an operation is prohibited.
- ORA-65125: valid XML or PDB archive file name is required
-
Cause: An attempt was made to provide a file name that did not have an XML or a PDB extension.
- ORA-65126: pluggable database string cannot be unplugged.
-
Cause: The pluggable database was not closed cleanly and there are active transactions that need to be recovered.
- ORA-65127: PDB recover output file not specified
-
Cause: An attempt was made torecover a pluggable database (PDB) without specifying an output XML file location.
- ORA-65128: missing or nonexistent data file or directory name string
-
Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by either not specifying a data file or directory location, or by specifying a nonexistent data file or directory location.
- ORA-65129: Pluggable database string cannot be relocated.
-
Cause: The pluggable database was already opened on all instances.
- ORA-65130: cannot relocate more than one pluggable database.
-
Cause: An attempt was made to relocate more than one pluggable database.
- ORA-65131: The feature string is not supported in a pluggable database.
-
Cause: An attempt was made to use a feature that is not supported in a pluggable database.
- ORA-65134: endian mismatch
-
Cause: The endian of the container database was not the same as the endian of the pluggable database being plugged in.
- ORA-65135: cannot perform ALTER SESSION SET CONTAINER operation in this context
-
Cause: An ALTER SESSION SET CONTAINER operation was attempted in a context where such an operation is prohibited.
- ORA-65136: SPFILE name cannot be specified for a pluggable database
-
Cause: An attempt was made to specify an SPFILE name for a pluggable database.
- ORA-65137: Pluggable database string is in the middle of Pluggable Database RESETLOGS operation.
-
Cause: The pluggable database is in the middle of a Pluggable Database (PDB) RESETLOGS operation.
- ORA-65138: Data file string of pluggable database string belongs to an orphan PDB incarnation.
-
Cause: Either the specified data file was restored from a backup that was taken during a period of time that was discarded by a RESETLOGS operation, or Oracle could not identify which pluggable database incarnation the file belongs to. One would also encounter this error if a pluggable database (PDB) flashback or restore was performed to an orphan PDB incarnation followed by complete recovery of the PDB. The alert log contains more information.
- ORA-65139: Mismatch between XML metadata file and data file string for value of string (string)
-
Cause: Either the XML metadata file or the data file was corrupt.
- ORA-65140: invalid common profile name
-
Cause: An attempt was made to create a common profile with a name that is not valid for common profiles. Common profile names must consist only of ASCII characters, and must contain the prefix specified in common_user_prefix parameter.
- ORA-65141: invalid local profile name
-
Cause: An attempt was made to create a local profile with a name that is not valid for local profiles. Local profile names cannot start with C## or c##. When connected to a locked down Pluggable Database (PDB) with LOCAL_OBJECT_RESERVED_NAME feature disabled, PDB local profile can't have the same name as that of an Oracle reserved profile name like ORA_STIG_PROFILE, ORA_CIS_PROFILE etc.
- ORA-65142: A local profile can be altered only within the current container
-
Cause: An attempt was made to alter a local profile using an ALTER PROFILE statement with the CONTAINER=ALL clause.
- ORA-65143: Creation of local profiles is not allowed in this container.
-
Cause: An attempt was made to create a local profile in CDB$ROOT or an application root. Except for DEFAULT and ORA_STIG_PROFILE, which are out-of-the-box Oracle supplied local profiles, no customer created local profiles are allowed in this container.
- ORA-65144: ALTER SYSTEM DISABLE RESTRICTED SESSION is not permitted
-
Cause: An attempt was made to disable a restricted session while an unresolved error existed in PDB_PLUG_IN_VIOLATIONS.
- ORA-65145: FORCE open of multiple pluggable databases is not supported
-
Cause: An attempt was made to FORCE open multiple pluggable databases at the same time.
- ORA-65146: account cannot be unlocked in a PDB while it is locked in the root
-
Cause: An attempt was made to unlock a common user account in a pluggable database (PDB) which was locked in the root of the container database.
- ORA-65147: DB_UNIQUE_NAME specified without SPFILE scope
-
Cause: An attempt was made to specify a DB_UNIQUE_NAME in an ALTER SYSTEM statement without SCOPE=SPFILE.
- ORA-65148: cannot FORCE open a pluggable database to or from upgrade mode
-
Cause: An attempt was made to FORCE open a pluggable database to or from upgrade mode.
- ORA-65149: PDB name conflicts with existing service name in the CDB or the PDB
-
Cause: An attempt was made to create a pluggable database (PDB) whose name conflicts with the existing service name in the container database (CDB) or the PDB.
- ORA-65150: unable to start the instance
-
Cause: An attempt was made to start an instance as a container or a non-container database when atleast one of the other instances was started in a different mode.
- ORA-65151: invalid tablespace name specified
-
Cause: An attempt was made to use an invalid tablespace name or a mandatory tablespace name (SYSTEM or SYSAUX) in the USER_TABLESPACES clause when creating a pluggable database.
- ORA-65152: cannot bring datafile online
-
Cause: An attempt was made to bring online one or more datafiles belonging to a pluggable database that is disabled for recovery.
- ORA-65153: cannot bring tablespace online
-
Cause: An attempt was made to bring online a tablespace that was either missing in the plug XML file or excluded when the pluggable database was created.
- ORA-65154: specified logging attribute for the pluggable database is same as the current attribute value
-
Cause: An attempt was made to change the default logging attribute to be the same as the current attribute value for the pluggable database.
- ORA-65155: missing or invalid source file directory string
-
Cause: Source file directory was missing or invalid.
- ORA-65156: pluggable database version string not allowed
-
Cause: An attempt was made to plug in a pluggable database with an incompatible version of the multitenant container database or the application root.
- ORA-65157: SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY cannot be specified together
-
Cause: SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY clauses were both specified.
- ORA-65158: could not find a matching file for - string
-
Cause: A matching file was not found in the directory specified with the SOURCE_FILE_DIRECTORY clause.
- ORA-65159: invalid service name specified
-
Cause: An attempt was made to use an invalid service name in the services clause.
- ORA-65160: invalid cleanup task ID
-
Cause: An attempt was made to pass an invalid cleanup task ID to the DBMS_PDB.CLEANUP_TASK function.
- ORA-65162: The password of the common user has expired
-
Cause: The password of the common user account has expired and needs to be changed. Connect to the CDB$ROOT or Application Root of the multitenant container database to change the password of the common user.
- ORA-65164: PDB instance recovery cannot open a required archived redo log
-
Cause: The system could not access a required archived redo log file.
- ORA-65165: missing or invalid path for file creation string
-
Cause: The path specified in CREATE_FILE_DEST clause was missing or invalid.
- ORA-65166: cannot run noncdb_to_pdb.sql if PDB's version differs from CDB's
-
Cause: An attempt was made to run noncdb_to_pdb.sql when the version of the pluggable database (PDB) was different from the version of the multitenant container database (CDB).
- ORA-65167: cannot run noncdb_to_pdb.sql if container database is in upgrade mode
-
Cause: An attempt was made to run noncdb_to_pdb.sql when the multitenant container database (CDB) was in upgrade mode.
- ORA-65168: missing PFILE name
-
Cause: An operation involving PFILE was issued in a pluggable database without specifying the PFILE name
- ORA-65169: error encountered while attempting to copy file string
-
Cause: An error was encountered while attempting to copy the file while creating a pluggable database.
- ORA-65170: XML file string already exists
-
Cause: An attempt to create an XML file failed because a file with that name already exists.
- ORA-65171: invalid value for DB_BLOCK_CHECKING parameter
-
Cause: An attempt was made to specify a value of FALSE or OFF for the DB_BLOCK_CHECKING parameter in a pluggable database (PDB), when the value of DB_BLOCK_CHECKING parameter in the multitenant container database (CDB) is neither FALSE nor OFF. If the CDB has enabled the DB_BLOCK_CHECKING parameter, then the PDB cannot disable the DB_BLOCK_CHECKING parameter.
- ORA-65172: cannot run noncdb_to_pdb.sql unless pluggable database is an unconverted non-container database
-
Cause: An attempt was made to run 'noncdb_to_pdb.sql' on a pluggable database (PDB) that was not an unconverted non-container database.
- ORA-65174: invalid or conflicting name in service string found in the pluggable database
-
Cause: The service name or network name in the specified service is invalid or it conflicts with an existing service name or network name in the container database.
- ORA-65175: cannot grant SYSDBA privilege locally in the root
-
Cause: An attempt was made to grant SYSDBA privilege locally in the root of a multitenant container database (CDB).
- ORA-65176: system tablespace block size (string) does not match configured block sizes
-
Cause: The block size of the system tablespace of the pluggable database to be plugged in did not match the block sizes configured in the container database.
- ORA-65177: cannot create non-local user, role or profile with the same name as local user, role or profile
-
Cause: An attempt was made to create a common user, role or profile with the same name as an existing local user, role or profile.
- ORA-65178: invalid logging mode specified for the pluggable database
-
Cause: An attempt was made to either enable a conflicting logging mode or to disable a logging mode when it was not enabled.
- ORA-65179: cannot keep datafiles for a pluggable database that is not unplugged
-
Cause: An attempt was made to drop a pluggable database without specifying the INCLUDING DATAFILES clause, and the pluggable database has not been unplugged.
- ORA-65180: duplicate file name encountered - string
-
Cause: An attempt was made to issue a CREATE PLUGGABLE DATABASE statement with a duplicate source or target file name for the source file name mentioned in the message. This could be caused by incorrect SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause.
- ORA-65181: invalid argument supplied to CONTAINERS function
-
Cause: An attempt was made to create a multitenant container database (CDB) view with an invalid table or view name.
- ORA-65182: unable to modify the state of pluggable database string
-
Cause: An attempt was made to modify the state of a pluggable database which is currently in the middle of a state transition.
- ORA-65183: FORCE open of a PDB on only a few instances where its open on is not allowed
-
Cause: An attempt was made to FORCE open a pluggable database on only a few Oracle RAC instances where it is currently open.
- ORA-65184: encountered data files belonging to different PDBs
-
Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying data files or a directory name containing data files belonging to different PDBs.
- ORA-65185: could not find data file belonging to SYSTEM and SYSAUX tablespaces
-
Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying data files or a directory name containing data files where no data files belonging to SYSTEM and SYSAUX tablespace were found. SYSTEM and SYSAUX tablespaces are critical to recover a pluggable database (PDB).
- ORA-65186: The user, role or profile string has sync errors.
-
Cause: There were pending SQL statements involving this user, role or profile which need to be resolved in order for the pluggable database (PDB) to be synced with ROOT.
- ORA-65187: duplicate file found string
-
Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying data files or a directory name containing data files which are duplicate copies of the same file.
- ORA-65188: cannot relocate a PDB opened with warnings
-
Cause: An attempt was made to relocate a pluggable database (PDB) which was opened with warnings or there were warnings encountered after relocating the PDB.
- ORA-65189: cannot clone a PDB from PDB$SEED as the source PDB
-
Cause: An attempt was made to clone a pluggable database (PDB) from PDB$SEED as the source PDB.
- ORA-65190: operation allowed only from within an application root
-
Cause: An operation (such as creation of an application seed) that can only be performed in an application root was attempted by a user not connected to an application root.
- ORA-65191: operation allowed only from within a CDB root
-
Cause: An operation (such as creation of an application root) that can only be performed in a multitenant container database (CDB) root container was attempted by a user not connected to the CDB root.
- ORA-65192: database must be in UPGRADE mode for this operation
-
Cause: An attempt is made to issue ALTER DATABASE LOCAL UNDO [ON | OFF] when the database is not open in UPGRADE mode.
- ORA-65194: Pluggable database string does not belong to the application container.
-
Cause: The user connected to an application root attempted to specify a pluggable database (PDB) that does not belong to the application container in a statement which can only affect PDBs belonging to the application container.
- ORA-65196: operation allowed only from within a View Pluggable Database
-
Cause: An operation (such as ALTER PLUGGABLE DATABASE VIEW LOCAL) that can only be performed in a View Pluggable Database was attempted by a user not connected to a View Pluggable Database.
- ORA-65197: cannot clone from the PDB - file string has online backup set or is being moved
-
Cause: An attempt to clone from a pluggable database (PDB) which had one one or more data files that are currently part of an online move or a hot backup operation.
- ORA-65198: operation not allowed on a PDB when it is being cloned
-
Cause: An attempt was made to perform an operation which is not allowed when the pluggable database (PDB) is being cloned concurrently.
- ORA-65199: database busy. operation not allowed now
-
Cause: An attempt was made to perform an operation while a conflicting database wide operation or a read write pluggable database (PDB) clone is in progress.
- ORA-65200: unable to create pluggable database with no data
-
Cause: An attempt was made to clone a pluggable database that contains some clustered tables or advanced queue tables.
- ORA-65201: DML on CONTAINERS() includes only the CON_ID column
-
Cause: A DML on CONTAINERS() included the CON_ID column but did not include a non-CON_ID column. A DML on CONTAINERS() including the CON_ID column can be performed only if a column other than the CON_ID column is also specified.
- ORA-65202: DML on CONTAINERS() specifies an invalid CON_ID column value
-
Cause: A DML on CONTAINERS() specified an invalid value for the CON_ID column.
- ORA-65203: invalid pluggable database name pattern
-
Cause: An attempt was made to assign an invalid pluggable database pattern for this initialization parameter.
- ORA-65204: STANDBYS clause is too long
-
Cause: The specified STANDBYS clause was too long in CREATE PLUGGABLE DATABASE statement.
- ORA-65205: missing or invalid lockdown profile name
-
Cause: A valid lockdown profile name was not present where required.
- ORA-65206: invalid value specified
-
Cause: An attempt was made to use an invalid value in the VALUE clause.
- ORA-65207: invalid statement or feature or option specified
-
Cause: An attempt was made to use an invalid statement or option or feature in ENABLE or DISABLE clause.
- ORA-65208: Lockdown profile string does not exist.
-
Cause: An attempt was made to specify a lockdown profile that did not exist.
- ORA-65209: Lockdown profile string already exists.
-
Cause: An attempt was make to create a lockdown profile with a name that already existed.
- ORA-65210: invalid value for UPGRADE PRIORITY
-
Cause: The specified value for UPGRADE PRIORITY was outside of the legal range.
- ORA-65211: UPGRADE PRIORITY may only be specified for user PDBs
-
Cause: An attempt was made to specify UPGRADE PRIORITY for CDB$ROOT or PDB$SEED, which is illegal.
- ORA-65212: operation not allowed from outside an application root
-
Cause: An operation was attempted that can only be performed in an application root.
- ORA-65213: existing application action in progress
-
Cause: An attempt was made to 'purge' or 'begin' an application action (install, uninstall, upgrade, or patch) while another action was already in progress.
- ORA-65214: application action has not begun
-
Cause: An attempt was made to end an application action (install, uninstall, upgrade, or patch) without a prior 'begin' call.
- ORA-65215: starting version does not match current version
-
Cause: The starting version of the application upgrade did not match the current version of the application.
- ORA-65216: invalid minimum version
-
Cause: The minimum version for the application patch did not exist.
- ORA-65217: application string does not exist
-
Cause: An action was attempted on an application that did not exist.
- ORA-65218: patch string for application string already installed
-
Cause: An attempt was made to start an application patch that was already installed.
- ORA-65219: patch string for application string is not in progress
-
Cause: An attempt was made to end an application patch that was not in progress.
- ORA-65220: object string.string does not exist or is not of supported common type
-
Cause: An attempt was made to change the sharing status of an object that either did not exist, or was of a type that could not be made common.
- ORA-65221: application string exists already
-
Cause: An action was attempted on an application that already exists.
- ORA-65222: string parameter is only supported in a CDB
-
Cause: An attempt was made to enable a parameter only supported in a multitenant container database (CDB), and the current database is not a CDB.
- ORA-65223: tablespace string does not exist
-
Cause: The default tablespace specified in the CREATE PLUGGABLE DATABASE statement either did not exist in the source pluggable database (PDB) or is not included in the USER_TABLESPACES clause.
- ORA-65224: SQL statement not allowed according to lock down profile string
-
Cause: An attempt was made to execute a SQL statement, in a pluggable database (PDB), which was disabled according to the corresponding lock down profile.
- ORA-65225: cannot run apex_to_common.sql or pdb_to_apppdb.sql on an unconverted non-multitenant container database
-
Cause: An attempt was made to run 'apex_to_common.sql' or 'pdb_to_apppdb.sql' on a pluggable database (PDB) that is an unconverted non-multitenant container database.
- ORA-65226: incompatible client version for the current database
-
Cause: An attempt was made to use an incompatible client version. Clients prior to Oracle Database 12c Release 2 (12.2) do not support long identifiers.
- ORA-65227: unable to open pdb archive file string
-
Cause: An attempt was made to provide an invalid file name which could not be opened for generating the unplug archive.
- ORA-65228: invalid host name specified
-
Cause: An attempt was made to use an invalid host name in the HOST clause.
- ORA-65229: invalid application version specified
-
Cause: An attempt was made to use an invalid application version.
- ORA-65230: internal database link cannot be altered or dropped
-
Cause: An attempt was made to directly alter or drop an internal database link. An internal database link can be altered or dropped only through an ALTER or DROP PLUGGABLE DATABASE statement.
- ORA-65231: The referenced pluggable database does not exist or it is closed.
-
Cause: An attempt was made to create or access a proxy pluggable database that referenced a non-existent or closed pluggable database.
- ORA-65232: unable to support PDB isolation mode in a non-PDB domain instance
-
Cause: An attempt to support pluggable database (PDB) isolation mode in a database without per-PDB recovery domains failed. PDB isolation mode is supported only on a per-PDB domain enabled instance.
- ORA-65233: unable to support PDB isolation mode in a global undo instance
-
Cause: An attempt to support pluggable database (PDB) isolation mode in a global undo enabled pluggable database failed. PDB isolation mode is supported only on a local undo enabled CDB instance.
- ORA-65234: DATA_LINK_DML should be supported only for data link tables.
-
Cause: An attempt was made to enable DATA_LINK_DML on a non-data link table.
- ORA-65235: cannot create common user, role or profile with the same name as existing common user, role or profile
-
Cause: An attempt was made to create a common user, role or profile with the same name as an existing common user, role or profile.
- ORA-65236: CON_ID column cannot be dropped or renamed
-
Cause: An attempt was made to drop or rename a CON_ID column of a CONTAINER_DATA table which is illegal.
- ORA-65237: CON_ID column must have a numeric data type
-
Cause: An attempt was made to change the data type of a CON_ID column of a CONTAINER_DATA table to a non-numeric data type, which is illegal.
- ORA-65238: operation cannot be performed when the application root is not open
-
Cause: An operation was attempted inside an application root that requires the application root to be open.
- ORA-65239: missing or invalid service name
-
Cause: A valid service name was not present where required by the syntax of ALTER SESSION SET CONTAINER= SERVICE=.
- ORA-65240: not connected to an application root
-
Cause: An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB while connected to the root of a multitenant container database (CDB).
- ORA-65241: statement can only be executed when administering an application
-
Cause: An attempt was made to issue a statement affecting a user, role, or object used by an application installed in an application container while not installing, upgrading, patching, or uninstalling such application.
- ORA-65242: CONTAINER_DATA attribute disabled
-
Cause: An attempt was made to disable a CONTAINER_DATA attribute of a table for which it was not enabled.
- ORA-65243: CONTAINER_DATA attribute already enabled
-
Cause: An attempt was made to enable a CONTAINER_DATA attribute of a table for which it is already enabled.
- ORA-65244: application action has begun
-
Cause: An attempt was made to execute an unsupported statement after an application action (install, uninstall, upgrade, or patch) was started.
- ORA-65245: application string has been uninstalled
-
Cause: An attempt was made to operate on an application after it was uninstalled.
- ORA-65246: invalid user name specified
-
Cause: An attempt was made to use an invalid user name in the USER clause.
- ORA-65247: tablespaces for subset clone or no data clone are not self-contained
-
Cause: One or more tablespaces listed in the USER_TABLESPACES clause or metadata tablespaces were not self-contained.
- ORA-65248: invalid clause
-
Cause: An attempt was made to alter a lockdown profile with an invalid clause.
- ORA-65249: invalid option
-
Cause: An attempt was made to alter a lockdown profile with an invalid option.
- ORA-65250: invalid path specified for file - string
-
Cause: An attempt was made to use a file name that does not start with CREATE_FILE_DEST for the pluggable database.
- ORA-65251: ending version already exists
-
Cause: The ending version of the application upgrade matched a previous version of the application.
- ORA-65252: cannot connect or ALTER SESSION SET CONTAINER to an application root clone
-
Cause: An attempt was made to connect or ALTER SESSION SET CONTAINER to an application root clone.
- ORA-65253: operation not allowed within a proxy pluggable database as SYSDBA or SYSOPER
-
Cause: An attempt was made to access a proxy pluggable database as SYSDBA or SYSOPER.
- ORA-65254: invalid path specified for the directory
-
Cause: An absolute path was used in the CREATE DIRECTORY statement. Since the PDB has set the PATH_PREFIX property, only relative path is allowed for directories.
- ORA-65255: invalid tablespace number
-
Cause: An attempt was made to create a pluggable database where one or more tablespaces has an invalid tablespace number.
- ORA-65256: maximum number of application root clones created for application container
-
Cause: An attempt was made to create an application root clone for an application container that has already reached the maximum permitted number of application root clones.
- ORA-65257: target is a non-CDB instance
-
Cause: An attempt was made to create a proxy pluggable database to a non-multitenant container database (non-CDB) instance.
- ORA-65258: referenced pluggable database is an application root clone
-
Cause: An attempt was made to create a proxy pluggable database that references an application root clone.
- ORA-65259: partial synchronization of application is disallowed
-
Cause: An attempt was made to synchronize an application that has not ended its install, patch, upgrade, or uninstall.
- ORA-65260: unable to create a refreshable clone
-
Cause: An attempt was made to either create a refreshable clone of a proxy pluggable database or to create a proxy pluggable database which is also enabled for refresh.
- ORA-65261: pluggable database string not enabled for refresh
-
Cause: An attempt was made to refresh a pluggable database (PDB) which was either not created as a refreshable PDB or the final refresh was already complete.
- ORA-65262: Dismount operation is not allowed.
-
Cause: An attempt was made to dismount a pluggable database with parameter enable_pdb_isolation set to FALSE.
- ORA-65263: internal error
-
Cause: This is an internally stimulated error.
- ORA-65264: Dismount operation is not allowed.
-
Cause: An attempt was made to dismount a pluggable database on a standby instance.
- ORA-65265: PDB cannot be dropped or unplugged.
-
Cause: An attempt was made to drop or unplug the root of an application container to which one or more application pluggable databases (PDBs) belong.
- ORA-65266: application root clone may not be dropped, unplugged or altered
-
Cause: An attempt was made to drop, unplug, or alter an application root clone pluggable database which is not allowed.
- ORA-65267: Application PDB string is open in an incompatible mode.
-
Cause: An attempt was made to reopen an application root in a mode incompatible with that of an application PDB belonging to the same application container.
- ORA-65268: PDB cannot be created
-
Cause: An attempt was made to either relocate a pluggable database (PDB) which was created as a refreshable PDB or to create a refreshable PDB from a PDB that was already created as refreshable PDB or was marked for relocation.
- ORA-65269: PDB cannot be refreshed
-
Cause: An attempt was made to refresh a pluggable database (PDB) with no refresh mode.
- ORA-65270: operation is not allowed in an application patch
-
Cause: An attempt was made to perform an operation that is not allowed in an application patch.
- ORA-65271: internal application may not be altered
-
Cause: An attempt was made to alter an application that was created internally.
- ORA-65272: operation not allowed from outside an application PDB
-
Cause: An operation was attempted that can only be performed in an application PDB.
- ORA-65273: The specified changes must be restricted to the current container.
-
Cause: An attempt was made to apply the specified changes to all containers.
- ORA-65274: operation not allowed from outside an application action
-
Cause: An operation was attempted that can only be performed in an application action (install, uninstall, upgrade, or patch).
- ORA-65275: invalid operation on a container database (CDB)
-
Cause: An operation was attempted that can only be performed from within a non-container database.
- ORA-65276: rule already exists in the lockdown profile
-
Cause: An attempt was made to add a rule that already exists in the lockdown profile.
- ORA-65277: Unable to support PDB isolation mode with MEMORY_TARGET or MEMORY_MAX_TARGET.
-
Cause: An attempt was made to support pluggable database (PDB) isolation mode with the MEMORY_TARGET or MEMORY_MAX_TARGET configuration parameters. PDB isolation mode is not supported with the MEMORY_TARGET or MEMORY_MAX_TARGET configuration parameters.
- ORA-65278: The PDB SGA size is larger than or equal to the CDB SGA size.
-
Cause: An attempt was made to start a pluggable database (PDB) with a system global area (SGA) size larger than or equal to the multitenant container.
- ORA-65279: The PDB SGA_MAX_SIZE is larger than or equal to the maximum CDB SGA size.
-
Cause: An attempt was made to start a pluggable database (PDB) with SGA_MAX_SIZE configuration parameter size larger than or equal to the multitenant container database (CDB).
- ORA-65280: The referenced pluggable database is a proxy pluggable database.
-
Cause: An attempt was made to create a proxy pluggable database that referenced a proxy pluggable database.
- ORA-65281: application string does not exist in application root
-
Cause: An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that does not exist in the application root where the statement was issued.
- ORA-65282: Aborting PDB string's instance recovery due to the progress of its SHUTDOWN ABORT operation
-
Cause: The instance recovery could not proceed as the pluggable database (PDB) was in the middle of the SHUTDOWN ABORT operation.
- ORA-65283: pluggable database string does not belong to the current container database
-
Cause: An attempt was made to perform an operation on a pluggable database that did not belong to the current multitenant container database (CDB) in the CDB fleet.
- ORA-65284: Version string for application string does not exist in application root
-
Cause: An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that has a higher version than the application root where the statement was issued.
- ORA-65285: Status mismatch for application string
-
Cause: An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that has a mismatch status between application PDB and the application root where the statement was issued.
- ORA-65286: object string.string cannot be made an extended data link
-
Cause: An attempt was made to change the sharing status of an object to extended data link when the object was of a type for which extended data links are not supported.
- ORA-65287: cannot set a common application context using a local package
-
Cause: An attempt was made to set a common application context using a local package.
- ORA-65288: PDB archive file string already exists.
-
Cause: An attempt to create a pluggable database (PDB) archive file failed because a file with that name already exists.
- ORA-65289: Application root cannot be relocated to another container database.
-
Cause: An attempt was made to relocate the root of an application container.
- ORA-65290: Application may not be altered.
-
Cause: An attempt was made to alter an application when the application pluggable database was not open.
- ORA-65291: invalid container map object
-
Cause: An attempt was made to assign an invalid container map object to container_map property of the database.
- ORA-65292: invalid common data map object
-
Cause: An attempt was made to assign an invalid common data map object to common_data_map property of the database.
- ORA-65293: Implicit users cannot own common objects.
-
Cause: An attempt was made to create a common object to be owned by an implicit user.
- ORA-65294: PDB's compatible parameter value (string) is higher than CDB's compatible parameter value (string).
-
Cause: An attempt was made to plug in or clone from a pluggable database with a higher compatible parameter value than the compatible parameter value of the multitenant container database (CDB).
- ORA-65295: service name or module name mismatch
-
Cause: An attempt was made to end an application action using a service name or module name that does not match the service name or module name that was in use when the application action was started.
- ORA-65296: unable to create pluggable database
-
Cause: An attempt was made to create a proxy pluggable database with relocate clause specified.
- ORA-65297: operation not allowed inside an application action
-
Cause: An operation was attempted that can only be performed outside an application action (install, uninstall, upgrade, or patch).
- ORA-65298: cannot create an application PDB in an application root which is an unconverted non-CDB
-
Cause: An attempt was made to create an application pluggable database (PDB) in an application root which was created by plugging in a non-multitenant container database (non-CDB) without first running noncdb_to_pdb.sql script.
- ORA-65299: cannot grant or revoke a privilege to or from multiple grantees
-
Cause: A GRANT or REVOKE statement was issued specifying more than one grantee on an application pluggable database (PDB).
- ORA-65300: PDB common_user_prefix conflicts with common_user_prefix in CDB.
-
Cause: An attempt was made to set the 'common_user_prefix' parameter in a pluggable database (PDB) that conflicts with the value of the same parameter in the multitenant container database (CDB.)
- ORA-65301: cannot set a deprecated property when the new property value is set
-
Cause: An attempt was made to run an ALTER DATABASE PROPERTY SET command on an older property that was deleted after setting the new property value.
- ORA-65310: blocked by COMMON_SCHEMA_ACCESS lockdown
-
Cause: An attempt was made to run an AUTHID CURRENT_USER function or procedure, or to reference a BEQUEATH CURRENT_USER view, that is not safe under the COMMON_SCHEMA_ACCESS lockdown.
- ORA-65311: cannot modify the common object of another application
-
Cause: An attempt was made to modify a common object that was created by another application.
- ORA-65312: The password of the application common user has expired and cannot be changed.
-
Cause: The password of the application common user had expired and needed to be changed in order to successfully log in to application containers. But the application ROOT container's application status did not allow this operation to succeed either because: - An implicit application common user was attempting to change the password from within an explicit application action. - A non-implicit application common user was attempting to change the password from within an implicit application action. - A non-implicit application common user was attempting to change the password from within an explicit application action, but the application, which created the application common user, was being upgraded or uninstalled.
- ORA-65313: cannot synchronize application in a proxy pluggable database without being in a SYSDBA session
-
Cause: An attempt was made to synchronize an application containing statements executed from a privileged session.
- ORA-65314: cannot use NOCOPY when plugging in a PDB using an archive file
-
Cause: An attempt was made to create a pluggable database (PDB) using an archive file using the NOCOPY clause.
- ORA-65315: invalid path specified for file - string
-
Cause: An attempt was made to use a file name that did not start with PATH_PREFIX for the pluggable database.
- ORA-65316: bad file name specified
-
Cause: An attempt was made to use an invalid file name as an argument.
- ORA-65317: cannot modify the user or role created by another application
-
Cause: An attempt was made to modify a user or a role that was created by another application. This can also happen when connected to an Application container and DBMS_PDB.SET_USER_EXPLICIT or DBMS_PDB.SET_ROLE_EXPLICIT procedure was invoked with the following type of users and roles: - Pluggable Database (PDB) Administrative user, that is, a user who has been granted PDB_DBA role inside the PDB. - The out-of-box Oracle supplied common users or roles. - Container Database (CDB) Common Users and roles, that is, users and roles created at CDB$ROOT container.
- ORA-65318: query to cross-container fixed tables not allowed
-
Cause: An attempt was made to query the cross-container fixed tables.
- ORA-65319: DML on CONTAINERS() specified an unsupported CON_ID predicate
-
Cause: A DML on CONTAINERS() included the CON_ID predicate in an OR chain or in an in-list.
- ORA-65320: value of CON_ID is not known for DML on CONTAINERS()
-
Cause: A DML on CONTAINERS() included multiple CON_ID predicates, or the single CON_ID predicate specified a value that is not a constant or a bind.
- ORA-65321: CON_ID column cannot be updated for CONTAINERS()
-
Cause: A DML on CONTAINERS() attempted to set a value for the CON_ID column.
- ORA-65322: invalid application patch specified
-
Cause: An attempt was made to use an invalid application patch.
- ORA-65323: cannot create or set an object table or object view as a data link or extended data link
-
Cause: An attempt was made to create or set an object table or an object view as a data link or an extended data link.
- ORA-65324: An invalid value is specified in an ALTER PLUGGABLE DATABASE CONTAINERS DEFAULT TARGET or ALTER DATABASE CONTAINERS DEFAULT TARGET statement.
-
Cause: An invalid value is specified in an ALTER PLUGGABLE DATABASE CONTAINERS DEFAULT TARGET or ALTER DATABASE CONTAINERS DEFAULT TARGET statement.
- ORA-65325: DML on CONTAINERS() cannot be performed outside the CDB root or application root.
-
Cause: An attempt was made to perform DML on CONTAINERS() outside the multitenant container database (CDB) root or an application root.
- ORA-65326: cannot query an object table or object view using CONTAINERS()
-
Cause: An attempt was made to query an object table or object view using CONTAINERS().
- ORA-65327: cannot modify the sharing property of an object outside an application action
-
Cause: An attempt was made to modify the sharing property of an object outside an application action.
- ORA-65328: cannot end an application action in the current session
-
Cause: An attempt was made to end an application action in a manner that is inconsistent with the order in which sessions will be replayed during application SYNC.
- ORA-65329: cannot run pdb_to_apppdb.sql unless pluggable database is an unconverted application pluggable database
-
Cause: An attempt was made to run 'pdb_to_apppdb.sql' on a pluggable database (PDB) that was not an unconverted application PDB.
- ORA-65330: cannot synchronize an application before pdb_to_apppdb.sql is executed
-
Cause: An attempt was made to synchronize an application in an unconverted application PDB before running 'pdb_to_apppdb.sql'.
- ORA-65331: DDL on a data link table is outside an application action.
-
Cause: DDL on a data link table was attempted outside an application action.
- ORA-65332: DDL on an extended data link table is outside an application action.
-
Cause: DDL on an extended data link table was attempted in an application root outside an application action.
- ORA-65333: cannot purge an application that is installed on application PDB
-
Cause: An attempt was made to purge an application that was installed in one or more application pluggable databases (PDBs).
- ORA-65334: invalid number of PDBs specified
-
Cause: An attempt was made to either set the MAX_PDBS database property to an invalid number or the number of current pluggable databases (PDBs) exceeds the number specified.
- ORA-65335: application action for application string has not started
-
Cause: An attempt was made to end an application action using an incorrect application name.
- ORA-65336: incorrect application patch number specified
-
Cause: An attempt was made to end an application action using an incorrect application patch number.
- ORA-65337: cannot modify the profile created by another application
-
Cause: An attempt was made to modify a profile that was created by another application. This can also happen when connected to an application container and the DBMS_PDB.SET_PROFILE_EXPLICIT procedure was invoked and the input profile type was one of the following: - The out-of-the-box Oracle supplied local profiles (DEFAULT, ORA_STIG_PROFILE and ORA_CIS_PROFILE). - Multitenant container database (CDB) common profiles created at CDB$ROOT container. - Protected local profiles created by CDB common users inside the pluggable database (PDB).
- ORA-65338: unable to create pluggable database
-
Cause: An attempt was made to relocate a pluggable database using a database link to the source pluggable database.
- ORA-65339: unsupported operation on the source PDB
-
Cause: An unsupported operation was performed on the source pluggable database, which rendered the target PDB invalid.
- ORA-65340: invalid application compatibility version
-
Cause: An attempt was made to set the compatibility version of an application to a version higher than that of one of the PDBs.
- ORA-65341: cannot open pluggable database in read/write mode
-
Cause: An attempt was made to open a refreshable pluggable database in read/write mode.
- ORA-65342: source pluggable database string has unrecovered transaction
-
Cause: The source pluggable database had an active transaction when it was closed.
- ORA-65343: cannot unplug pluggable database string
-
Cause: An attempt was made to unplug a pluggable database that was previously unplugged.
- ORA-65344: cannot uninstall or purge an application that has objects, users, roles, and profiles
-
Cause: An attempt was made to uninstall or purge an application that had objects, users, roles, and profiles.
- ORA-65345: cannot refresh pluggable database, archive log not found for SCN string
-
Cause: The foreign archive log required for refreshing the pluggable database was not found.
- ORA-65346: The PDB version is lower and components (string) are missing in CDB.
-
Cause: An attempt was made to plug in a pluggable database (PDB) that has a lower version and has more components than the multitenant container database (CDB) or the application root.
- ORA-65347: cannot downgrade database that has proxy pluggable databases or application containers
-
Cause: There were proxy pluggable databases or application containers in the database.
- ORA-65348: unable to create pluggable database
-
Cause: An attempt was made to relocate a pluggable database with availability max clause using a target pluggable database name which is different from source pluggable database name.
- ORA-65349: unable to create pluggable database
-
Cause: An attempt was made to relocate a pluggable database with availability max and service_name_convert clauses together.
- ORA-65350: cannot run approot_to_pdb.sql
-
Cause: An attempt was made to run 'approot_to_pdb.sql' on a pluggable database (PDB) that was already converted to a regular PDB.
- ORA-65351: invalid partition (%0!s) access with partition map size %1!s
-
Cause: An attempt was made to access an invalid partition using the CONTAINERS() clause.
- ORA-65352: Query across containers cannot have an ancillary operator.
-
Cause: An ancillary operator was used with a data link, extended data link, or CONTAINERS() clause.
- ORA-65353: The string tablespace is missing from the XML metadata file.
-
Cause: An attempt was made to plug in a pluggable database (PDB) using an XML file that does not contain the SYSTEM, SYSAUX or undo tablespace specifications.
- ORA-65355: cannot allocate PDB SGA memory
-
Cause: The multitenant container database (CDB) did not have sufficient system global area (SGA) memory available to open the pluggable database (PDB). *Result: Increase the CDB SGA size or dismount a PDB to free CDB SGA memory.
- ORA-65356: missing or invalid value for lead_cdb_uri
-
Cause: An attempt was made to specify an incorrect value for lead_cdb_uri. The lead_cdb_uri value can either specify the host name, port number and service name for the lead multitenant container database (CDB), or the value can specify a database link object name in the current CDB which connects to the lead CDB in the fleet.
- ORA-65357: lead_cdb_uri and lead_cdb cannot be specified in the same CDB
-
Cause: An attempt was made to specify the lead_cdb_uri property in the multitenant container database (CDB) where the lead_cdb property is set to TRUE or vice versa.
- ORA-65358: PDB string is not a template PDB
-
Cause: The PDB specified was not a template pluggable database (PDB) and thus pdb_template cannot be set to this PDB.
- ORA-65359: unable to create pluggable database with no data
-
Cause: An attempt was made to clone a pluggable database that was opened in read/write mode.
- ORA-65360: unable to switchover
-
Cause: An attempt was made to switchover a pluggable database (PDB) using a database link that pointed to the source pluggable database.
- ORA-65361: pluggable database string is not a refresh copy
-
Cause: An attempt was made to switchover to a pluggable database (PDB) which was not marked as a refresh copy.
- ORA-65362: pluggable database string is not a refresh copy of the source pluggable database
-
Cause: An attempt was made to switchover to a pluggable database (PDB) which was not marked as a refresh copy of the source pluggable database (PDB).
- ORA-65363: pluggable database string not enabled for snapshots
-
Cause: An attempt was made to snapshot a pluggable database (PDB) which was created with snapshots disabled.
- ORA-65364: snapshot not found
-
Cause: An attempt was made to create a pluggable database (PDB) using a snapshot or to drop a snapshot that could not be found.
- ORA-65365: unable to create pluggable database
-
Cause: An attempt was made to create a pluggable database (PDB) using a snapshot when Oracle Managed Files (OMF) was not enabled or if the CREATE_FILE_DEST clause was not specified.
- ORA-65366: snapshot already exists
-
Cause: An attempt was made to create a snapshot of a pluggable database (PDB) using a name that already existed.
- ORA-65367: unable to switchover
-
Cause: An attempt was made to switch over a pluggable database (PDB) that was not a normal pluggable database that could be opened in read/write mode.
- ORA-65368: unable to open the pluggable database due to errors during recovery
-
Cause: Recovery was required prior to opening the pluggable database, but an error during recovery was determined to be fatal enough to end both the recovery and the open operation.
- ORA-65369: The key column for the container map object has multiple values for each partition.
-
Cause: An attempt was made to generate logical partitioning key values using a container map object that had multiple values for each partition.
- ORA-65370: string initialization parameter cannot be specified in a lockdown profile
-
Cause: An attempt was made to specify an illegal initialization parameter in a lockdown profile.
- ORA-65371: string initialization parameter cannot be modified in a template pluggable database
-
Cause: An attempt was made to modify an illegal initialization parameter inside a template pluggable database (PDB).
- ORA-65372: Initialization parameter %0!s cannot be modified when initialization parameter %1!s is already set.
-
Cause: An attempt was made to set the PDB_LOCKDOWN initialization parameter along with the PDB_TEMPLATE initialization parameter.
- ORA-65373: operation not allowed in a template PDB
-
Cause: The specified operation was not allowed in a template pluggable database (PDB).
- ORA-65374: cannot set PDB_LOCKDOWN initialization parameter to an application lockdown profile
-
Cause: An attempt was made to set the PDB_LOCKDOWN initialization parameter to an application lockdown profile when the PDB_LOCKDOWN initialization parameter was already set to a container database (CDB) lockdown profile.
- ORA-65375: cannot set PDB_TEMPLATE initialization parameter to an application template string
-
Cause: An attempt was made to set the PDB_TEMPLATE initialization parameter to an application template when the PDB_TEMPLATE initialization parameter was already set to a multitenant container database (CDB) template.
- ORA-65376: unable to refresh the PDB
-
Cause: A conflicting operation was in progress in the source pluggable database (PDB) for the refresh clone.
- ORA-65377: parameter cannot be modified
-
Cause: An attempt was made to modify an in-memory value for the SGA_TARGET parameter with pluggable database isolation mode enabled.
- ORA-65378: illegal use of ALTER SYSTEM clause 'string' in the template pluggable database(PDB)
-
Cause: An invalid clause was used in an ALTER SYSTEM operation.
- ORA-65379: application string is in transient state
-
Cause: An attempt was made to unplug an application pluggable database (PDB), which had unfinished application action.
- ORA-65380: unable to materialize
-
Cause: An attempt was made to materialize a pluggable database (PDB) that was not created as a snapshot copy.
- ORA-65381: unable to rename application root
-
Cause: An attempt was made to rename an application root that has one or more open application PDBs.
- ORA-65382: operation cannot be performed when subscribed template PDB is not open
-
Cause: The template pluggable database (PDB) to which the current PDB was subscribed was not open.
- ORA-65383: unable to set MAX_PDB_SNAPSHOTS property to greater than string
-
Cause: An attempt was made to set the MAX_PDB_SNAPSHOTS property to a higher value than the allowed maximum.
- ORA-65384: missing or invalid property
-
Cause: The issued operation had a missing property name or the property specified was invalid or not found in the database.
- ORA-65385: missing or invalid value for property
-
Cause: The issued operation had a missing property value or the property value specified was invalid.
- ORA-65386: unable to alter property
-
Cause: An attempt was made to specify a property that could not be altered using ALTER DATABASE PROPERTY or ALTER PLUGGABLE DATABASE PROPERTY statement.
- ORA-65387: unable to create pluggable database with the specified USER_TABLESPACES clause
-
Cause: An attempt was made to create a pluggable database using an XML file that was generate with DBMS_PDB.RECOVER and all tablespaces were not included.
- ORA-65388: PARTITION_CONTAINED only supported in subset cloning
-
Cause: An attempt was made to use PARTITION_CONTAINED clause outside subset cloning.
- ORA-65389: unable to clone pluggable database
-
Cause: An attempt was made to create a refreshable clone of a pluggable database (PDB) or relocate a PDB from a standby database.
- ORA-65390: unable to mark the application object as specific Link
-
Cause: An attempt was made to use SET_SHARING_NONE, SET_METADATA_LINKED, SET_DATA_LINKED, or SET_EXT_DATA_LINKED on an object of an incompatible sharing mode.
- ORA-65391: violation of container map partitions
-
Cause: An attempt was made to insert or update a row in a container map enabled table that violated the partitions of the container map.
- ORA-65392: object column is accessed in a fleet proxy pluggable database
-
Cause: An attempt was made to access an object column in a fleet proxy Pluggable Database (PDB).
- ORA-65393: Media recovery to SCN string must be performed in mount mode.
-
Cause: One or more pluggable databases could not be recovered by the RESETLOGS operation because the Oracle Active Data Guard standby database was still open.
- ORA-65394: LIBRARY does not use a DIRECTORY object
-
Cause: The LIBRARY objects did not use a DIRECTORY object for the pluggable database (PDB) with a defined PATH_PREFIX.
- ORA-65395: constraint cannot be added
-
Cause: An attempt was made to add a referential integrity constraint from a table to a data-linked or an extended data-linked table.
- ORA-65396: A linked tablespace cannot be altered to READ WRITE status.
-
Cause: An attempt was made to alter a linked tablespace to READ WRITE status.
- ORA-65397: cannot open pluggable database in read/write mode
-
Cause: An attempt was made to open a pluggable database with files in object store in read/write mode.
- ORA-65398: cannot change password during application upgrade or uninstall
-
Cause: An attempt was made to change password for an application common user while the application, which created the application common user, was being upgraded or uninstalled.
- ORA-65399: cannot set object table, external table, hybrid partitioned table or object view with CONTAINER_DATA clause
-
Cause: An attempt was made to create or alter an object table, an external table, a hybrid partitioned table, or an object view with a CONTAINER_DATA clause.
- ORA-65400: Table does not have CLUSTERING clause associated with it
-
Cause: User attempts to modify clustering clasue on a table that that does not have one.
- ORA-65402: invalid option on CLUSTERING clause
-
Cause: Invalid option on CLUSTERING clause. Only [YES | NO ] ON LOAD or [YES | NO ] ON DATA MOVEMENT are valid.
- ORA-65403: invalid usage of CLUSTERING clause
-
Cause: Invalid usage of CLUSTERING clause. The clause can be specified only for [CREATE | ALTER] [TABLE | SNAPSHOT | MATERIALIZED VIEW]
- ORA-65404: a table or materialized view can only have one CLUSTERING clause, remove the redundant clause(s)
-
Cause: The CLUSTERING clause was specified multiple times for the table or the materialized view yet a table or materialized view can only be clustered by a single order.
- ORA-65405: CLUSTERING clause cannot be used with existing table options
-
Cause: The CLUSTERING clause conflicted with other clauses on the table. The CLUSTERING clause cannot be used with IOT, CLUSTERED, GLOBAL TEMPORARY TABLE, or the EXTERNAL TABLE clause.
- ORA-65406: invalid option on CLUSTERING clause
-
Cause: The CLUSTERING clause was not followed by the BY [LINEAR | INTERLEAVED] ORDER option.
- ORA-65407: CLUSTERING clause already exists on the table
-
Cause: The ADD CLUSTERING clause was specified on a table with an existing CLUSTERING clause.
- ORA-65408: CLUSTERING clause has too many columns in the BY ORDER subclause
-
Cause: More than 10 columns were specified in the BY ORDER subclause. You can have at most 10 columns in the BY ORDER subclause.
- ORA-65409: CLUSTERING clause has too many INTERLEAVED columns or groups
-
Cause: More than 40 columns or more than 4 groups were specified in the BY INTERLEAVED ORDER subclause. You can have at most 40 columns and at most 4 groups in the INTERLEAVED ORDER subclause.
- ORA-65410: CLUSTERING clause can have only scalar columns
-
Cause: A non-scalar column was specified in the BY [LINEAR | INTERLEAVED] ORDER subclause. Also, virtual or hidden columns are not allowed.
- ORA-65411: CLUSTERING clause does not exist
-
Cause: An attempt was made to modify or drop a CLUSTERING clause in a table that had no CLUSTERING clause associated with it.
- ORA-65412: invalid option on ALTER TABLE .. CLUSTERING ..
-
Cause: You specified an invalid option on ALTER TABLE...CLUSTERING. For example, you specified DROP and ADD CLUSTERING in one statement.
- ORA-65413: cannot resolve referenced object in the CLUSTERING clause
-
Cause: An object was referenced in the CLUSTERING clause that could not be resolved to a base table reference.
- ORA-65414: column resolves to multiple tables in the CLUSTERING clause
-
Cause: A column resolved to multiple tables in the CLUSTERING clause.
- ORA-65415: wrong join condition in the CLUSTERING clause
-
Cause: The CLUSTERING clause had an OR condition and the individual join condition on the base table columns was not an equijoin.
- ORA-65416: multiple dimension tables in the CLUSTERING clause
-
Cause: Joins in the CLUSTERING clause referenced a dimension table more than once.
- ORA-65417: illegal dimension table in the CLUSTERING clause
-
Cause: The dimension table in the CLUSTERING clause was illegal. Dimension table cannot be GLOBAL TEMPORARY TABLE or EXTERNAL TABLE.
- ORA-65418: primary or unique key constraint missing in CLUSTERING join
-
Cause: The join between the fact and dimension tables in the CLUSTERING clause did not have a primary or unique key constraint on the dimension table join column(s).
- ORA-65419: columns in a clustering group come from different tables
-
Cause: Columns in the clustering group did not come from the same table. For example: .. CLUSTERING BY ..( (t1.c1, t2.c2), (t2.c1, t2.c2) ). Clustering group (t1.c1, t2.c2) must contain references to only one table.
- ORA-65420: columns in a join condition in the CLUSTERING clause are not compatible
-
Cause: The data type of columns in the join condition of CLUSTERING clause were not compatible. They must be of the same type.
- ORA-65421: The CLUSTERING clause is defined on columns that are to be modified
-
Cause: An ALTER TABLE MODIFY COLUMN command was issued on a column on which a CLUSTERING clause exists.
- ORA-65422: The CLUSTERING clause already has a zonemap defined on it
-
Cause: An ALTER TABLE MODIFY CLUSTERING command was issued with the WITH MATERIALIZED ZONEMAP option but the table already had zonemap define on it.
- ORA-65423: The CLUSTERING clause does not have a zonemap associated with it
-
Cause: An ALTER TABLE MODIFY CLUSTERING command was issued with the WITHOUT MATERIALIZED ZONEMAP option but the table did not have zonemap associated with the CLUSTERING clause.
- ORA-65424: CLUSTERING clause has too many joins
-
Cause: More than 4 joins were specified in the CLUSTERING clause. You can have at most 4 joins to the dimension tables.
- ORA-65425: CLUSTERING clause not supported for table stored in tablespace of this storage type
-
Cause: An attempt was made to define clustering on a table stored in non-Oracle Exadata storage.
- ORA-65426: Non-scalar data type is used for a clustering column
-
Cause: Oracle cannot perform data clustering because an attempt was made to populate a clustering column with non-scalar data values, or a clustering column defaulted to non-scalar values was omitted.
- ORA-65427: A system-generated column or unused column is used in a join condition in the CLUSTERING clause.
-
Cause: An attempt was made to use a system-generated or unused column in a join condition in the CLUSTERING clause.
- ORA-65428: unable to create pluggable database with temporary tablespace files in object store
-
Cause: An attempt was made to create a pluggable database with temporary tablespace files in the object store.
- ORA-65429: PDB cannot be created
-
Cause: An attempt was made to clone a source pluggable database (PDB) stored in an object store using a database link.
- ORA-65430: Pluggable database string cannot be unplugged.
-
Cause: An attempt was made to unplug a pluggable database (PDB) stored in an object store using an invalid credential.
- ORA-65431: Pluggable database string cannot be unplugged.
-
Cause: An attempt was made to unplug a pluggable database (PDB) to object store without a credential.
- ORA-65432: unable to read/write XML file in object store
-
Cause: An internal error occurred when reading or writing to XML file in object store.
- ORA-65433: incomplete copy of source file - string (blocks number - number)
-
Cause: An attempt to copy a source file failed for the block ranges specified in the error message. The failure could be due to inability to access the source file.
- ORA-65434: unable to cancel relocate of pluggable database string
-
Cause: An attempt was made to cancel the relocate of a pluggable database that was not in relocate unplugged state.
- ORA-65435: unable to refresh pluggable database string
-
Cause: An attempt was made to refresh a pluggable database beyond the end of life span of the current source pdb.
- ORA-65436: unable to find new life span information for pluggable database string
-
Cause: An attempt was made to transition a pluggable database to follow a new lifespan that did not match the current state of the pluggable database's datafiles.
- ORA-65437: mismatch between new life span and data file string for value of SCN (string)
-
Cause: Either the data file or life span table was corrupt.
- ORA-65438: until SCN or until time clause not specified
-
Cause: An attempt was made to refresh the pluggable database without specifying a system change number (SCN) or a time to refresh.
- ORA-65439: general event for automatic clustering module
-
Cause: N/A
- ORA-65440: PDB creation clauses mismatch when resuming a PDB clone
-
Cause: An attempt was made to resume a PDB clone with mismatched clauses.
- ORA-65451: Advanced index compression is not supported for tablespaces on this storage type.
-
Cause: An attempt was made to use advanced index compression on an unsupported storage type.
- ORA-65452: could not clone read/write PDB to object store
-
Cause: An attempt was made to clone a pluggable database (PDB) that was open read/write to a location on the object store.
- ORA-65455: family string is invalid
-
Cause: An invalid family was used to specify a parameter value.
- ORA-65456: family string is not valid in string instance
-
Cause: The specified family could not be used in the current instance type.
- ORA-65457: family string is not valid in string instance
-
Cause: The specified family could ot be used in the current instance type.
- ORA-65458: maximum length of parameter qualifier exceeded
-
Cause: Too many characters were specified in the parameter qualifier in the initialization parameter file.
- ORA-65459: family used with a specific system identifier (SID)
-
Cause: A SID was used with FAMILY.
- ORA-65460: family string is invalid
-
Cause: An invalid family was specified for this instance in ORACLE_FAMILY.
- ORA-65461: invalid parameter name specified with CONTAINER clause set to ALL
-
Cause: The CONTAINER clause was set to ALL in the ALTER SYSTEM SET statement for a non-PDB modifiable or non-inheritable PDB parameter.
- ORA-65462: error while updating a dependent parameter 'string'
-
Cause: An internal error was encountered while trying to update dependent parameter value.
- ORA-65466: family 'string' contains an illegal character or is too long
-
Cause: The specified family contained an illegal character or the family specified was too long, which cannot occur in an SPFILE setting. Illegal characters include *,#"'=() and whitespace.
- ORA-65470: Lost write already in requested state.
-
Cause: Lost write was already in the requested state. If enable or disable lost write was specified, then lost write was already in the requested state.
- ORA-65471: LOST WRITE PROTECTION cannot be enabled on this type of tablespace.
-
Cause: LOST WRITE PROTECTION could not be enabled for lost write tablespaces or temporary tablespaces.
- ORA-65472: invalid option for ALTER lost write TABLESPACE
-
Cause: An invalid option was specified while altering a LOST WRITE PROTECTION tablespace.
- ORA-65473: invalid option for FLASHBACK
-
Cause: An invalid option was specified while creating or altering a flashback tablespace.
- ORA-65474: lost write tablespace does not exist or has insufficient space or lost write is off
-
Cause: Enabling lost write protection could not succeed because the lost write tablespaces did not exist or had insufficient space. It is possible that shadow lost write was not enabled for the database.
- ORA-65476: could not get data file space header
-
Cause: There was an internal error code.
- ORA-65477: lost write protection - invalid state transition
-
Cause: The object that was manipulated could not be set to the requested state.
- ORA-65478: shadow lost write protection - found lost write
-
Cause: A lost write was found in a data block protected by lost write.
- ORA-65479: operation affecting a pluggable database cannot be performed from another pluggable database [string]
-
Cause: An attempt was made to perform an operation affecting a pluggable database while connected to a different pluggable database.
- ORA-65480: invalid option for CREATE TABLESPACE
-
Cause: An invalid option was specified while creating LOST WRITE PROTECTION tablespace.
- ORA-65481: LOST WRITE PROTECTION option already specified
-
Cause: In CREATE TABLESPACE, the LOST WRITE PROTECTION option was specified more than once.
- ORA-65482: invalid option for CREATE TABLESPACE
-
Cause: An invalid option was specified while creating a tablespace.
- ORA-65483: invalid option for creation of LOST WRITE PROTECTION tablespace
-
Cause: The BIGFILE keyword was not specified while creating a LOST WRITE PROTECTION tablespace.
- ORA-65484: cannot specify LOST WRITE PROTECTION tablespace as default tablespace
-
Cause: An attempt was made to assign a LOST WRITE PROTECTION tablespace to be a user's default tablespace.
- ORA-65485: cannot create user objects in LOST WRITE PROTECTION tablespace
-
Cause: An attempt was made to create user objects in a LOST WRITE PROTECTION tablespace. Other system objects such as rollback segments are also illegal.
- ORA-65486: cannot specify a LOST WRITE PROTECTION tablespace as default tablespace
-
Cause: An attempt was made to assign a LOST WRITE PROTECTION tablespace to be a default tablespace.
- ORA-65487: Lost write tablespaces must all have the same block size.
-
Cause: A different block size was specified when a SHADOW LOST WRITE tablespace was created.
- ORA-65488: SHADOW LOST WRITE cannot be enabled on a standby database.
-
Cause: An attempt was made to enable SHADOW LOST WRITE on a standby database.
- ORA-65489: Lost write tablespace cannot be enabled or created
-
Cause: An attempt was made to enable lost write when the database was not open or an access error occurred when attempting to access the new_lost_write_shadows$ dictionary table
- ORA-65490: invalid parameters for LOST WRITE PROTECTION tablespace
-
Cause: Invalid parameters were specified for a LOST WRITE PROTECTION tablespace. Only BIGFILE TABLESPACE, SIZE and BLOCKSIZE for a LOST WRITE PROTECTION tablespace can be specified upon creation. ALTER cannot be used to make a LOST WRITE PROTECTION tablespace read-only.
- ORA-65491: A lost write bigfile tablespace must exist before attempting to enable lost write
-
Cause: The lost write tablespace does not exist.
- ORA-65492: Cannot get data file space header
-
Cause: An internal error occurred.
- ORA-65493: cannot shrink a lost write tablespace
-
Cause: An attempt was made to shrink a lost write tablespace.
- ORA-65494: LOST WRITE PROTECTION could not write to or read dictionary tables or inconsistent dictionary tables.
-
Cause: There was an internal error in lost write subsystem. The SYSAUX tablespace may be inaccessible or full.
- ORA-65495: LOST WRITE PROTECTION could not create shadow tablespace.
-
Cause: There was an internal error in the lost write protection subsystem.
- ORA-65496: Lost write tables are inconsistent. Delete may have occurred.
-
Cause: One of the lost write tracking tables was inconsistent. A parallel operation may have caused this problem.
- ORA-65498: SHADOW LOST WRITE tablespace could not be dropped.
-
Cause: An internal error occurred when performing drop side effects
- ORA-65499: Illegal SHADOW LOST WRITE operation on a read-only database
-
Cause: The attempted lost write operation is prohibited on a read-only database.
- ORA-65500: could not modify DB_UNIQUE_NAME, resource exists
-
Cause: DB_UNIQUE_NAME could not be modified, because a database resource identified by DB_UNIQUE_NAME existed in the cluster. To modify DB_UNIQUE_NAME, any resource it identifies must first be removed.
- ORA-65501: locator from string container cannot be used in container string for this operation
-
Cause: In a pluggable database environment, an attempt was made to modify a LOB using a locator which belongs to a different container.
- ORA-65502: cannot access temporary LOB data
-
Cause: The database did not open.
- ORA-65503: cannot send or receive temporary LOB locators over a database link
-
Cause: An attempt was made to send or receive a temporary LOB locator over a database link.
- ORA-65504: cannot send or receive LOB locators from an index-organized table over a database link
-
Cause: An attempt was made to send or receive a temporary LOB locator from an index-organized table over a database link.
- ORA-65505: cannot pass a remote LOB locator as parameter to this operation
-
Cause: An attempt was made to pass a remote LOB locator as a parameter to a LOB operation which does not accept a remote LOB locator.
- ORA-65506: cannot pass LOB locators belonging to different databases
-
Cause: An attempt was made to pass Large Object (LOB) locators belonging to a different database as a parameter to a Large Object (LOB) operation.
- ORA-65507: cannot select a LOB locator across multiple database links
-
Cause: An attempt was made to select a Large Objects (LOB) locator from a remote database that was obtained by the remote from another remote database.
- ORA-65508: cannot send or receive an invalid LOB locator over database link
-
Cause: An attempt was made to send or receive an invalid LOB locator over a database link.
- ORA-65509: Cannot use remote LOBs in INSERT AS SELECT DMLs with INSTEAD OF triggers.
-
Cause: An attempt was made to perform an operation INSERT AS SELECT on a view with INSTEAD OF trigger on it and a remote LOB column in the select list.
- ORA-65510: Distributed LOB operations are not supported on pre-12.2 databases.
-
Cause: An attempt was made to send or receive a LOB locator over a database link to a pre-12.2 database.
- ORA-65511: SQL statement executed on a remote database over a database link cannot access a LOB on the local database with parallel execution enabled on the remote side
-
Cause: This is likely the result of passing a local LOB locator as a bind value to a SQL statement that is executed on a remote database over a database link. For example, running the statement "INSERT INTO tabl1@@dblink VALUES (:1)" where the bind value is a local persistent LOB locator and parallel execution is enabled on the remote side.
- ORA-65512: cannot access temporary LOB from old incarnation of pluggable database string
-
Cause: When the pluggable database was closed, any temporary LOBs in it were freed. An attempt was made to access a freed LOB.
- ORA-65513: value LOB operand mismatch for SQL operator
-
Cause: The LOB locator operands that were passed to the SQL operator did not have the value-based property set uniformly.
- ORA-65514: invalid LOB ENABLE STORAGE IN ROW value
-
Cause: An invalid value was specified for LOB ENABLE STORAGE IN ROW. The specified value for LOB ENABLE STORAGE IN ROW should be null, 4000, 8000, 16000 or 32000 for SECUREFILE LOBS in heap tables, and null in all other cases.
- ORA-65515: LOB inline size is greater than tablespace block size
-
Cause: The inline size specified for the ENABLE STORAGE IN ROW clause of either the CREATE or ALTER TABLE was greater than the block size of the tablespace of the table.
- ORA-65516: incorrect usage of increased LOB inlining
-
Cause: An inline size greater than 4000 bytes in the LOB storage clause was specified for a case other than the top level LOB column. Increased LOB inlining is not supported in LOB usage cases like abstract data types (ADTs), nested tables and varrays.
- ORA-65531: maximum level reached in index segment with object id string
-
Cause: The attempted operation resulted in the number of index levels exceeding the maximum allowed.
- ORA-65532: cannot alter or drop automatically created indexes
-
Cause: An attempt was made to alter or drop an automatically created index.
- ORA-65533: index coalesce on object string could not complete
-
Cause: An alter index coalesce command could not fully complete. Further coalescing may still be possible.
- ORA-65535: Oracle Database client cannot handle error code exceeding 65535. Actual error code and message follow:\n
-
Cause: Oracle Database clients earlier than release 12.1 could not handle error codes larger than 65535.