Cause: An attept was made to modify optimizer statistics of the object.

Cause: INSERT VALUES clause refers to the destination table columns

Cause: INSERT WHERE clause refers to the destination table columns

Cause: UPDATE SET clause refers to the source table columns in the LHS

Cause: LHS of UPDATE SET contains the columns referenced in the ON Clause

Cause: When Update Row-Migration is possible, Delete in MERGE is not yet supported

Cause: The MERGE operation contained a join view or view with INSTEAD of trigger which is not supported.

Cause: The specified SQL handle did not exist in the repository.

Cause: The SQL statement for SQL ID did not exist in the cursor cache.

Cause: An invalid parameter name was specified.

Cause: An invalid parameter value was specified.

Cause: Specified fixed status value was neither YES or NO.

Cause: An invalid attribute name was specified.

Cause: An invalid attribute value was specified.

Cause: A valid plan name was not specified.

Cause: A concurrent DDL operation was performed during a load plans operation.

Cause: No SQL plan baselines were found during pack or unpack operation.

Cause: A SQL plan baseline name was specified that did not exist.

Cause: A SQL plan baseline already exists with the name specified.

Cause: Specified enabled status value was neither YES or NO.

Cause: The specified plan name did not exist in the repository.

Cause: The SQL handle or plan name was not specified. The SQL handle or plan name is required.

Cause: Specified verify value was neither YES or NO.

Cause: Specified commit value was neither YES or NO.

Cause: Specified time limit value was not a positive integer.

Cause: The advisor did not generate a recommended action for the given object and task.

Cause: An auto-capture filter was too large to fit in the remaining space. Each filter requires a number of characters equal to the size of its value plus one.

Cause: The provided module name was too long.

Cause: The provided action name was too long.

Cause: SQL plan management could be used only with Oracle Database Enterprise Edition.

Cause: A DDL operation was attempted on a SQL management object by a session without the proper privileges.

Cause: An attempt was made to perform an operation by specifying filters that did not target any SQL management objects.

Cause: An invalid attribute value was specified.

Cause: Tried to perform DDL or DML operation on Recycle Bin object.

Cause: Invalid purge option specified.

Cause: Either a token other than USER was found following the tablespace name or some text was found following USER user name.

Cause: A valid user name was expected.

Cause: Trying to Flashback Drop an object which is not in RecycleBin.

Cause: Trying to flashback drop an object other than of type TABLE.

Cause: Trying to Purge the object which is not in RecycleBin.

Cause: Invalid Flashback Drop option specified.

Cause: An attempt was made to purge an object that is either not purgable or else dependent upon some other object.

Cause: An attempt was made to purge the tablespace for a different user by a user who does not have system DBA priviledges.

Cause: An attempt was made to purge an object which is owned by some other user.

Cause: An attempt was made to recover an object preserving the original name, but that name is taken up by some other object.

Cause: An attempt was made to delete a nonexistent policy.

Cause: A policy name was specified that already existed under this schema.

Cause: An attempt was made to add a policy without the scope.

Cause: An attempt was made to create a policy with the same action type and based on the same statistic as another policy on the object.

Cause: An attempt was made to create a policy with the same action, scope and compression level as another policy on the object.

Cause: An attempt was made to create a compression policy that conflicts with another policy on the object.

Cause: Attempt was made to create a schema level policy.

Cause: The specified API argument values were of the wrong value range.

Cause: An inconsistency was detected in ILM related data in the dictionary.

Cause: An internal error occurred during execution of ILM related activity. Further information can be found in the alert log.

Cause: Sufficient privileges were not granted for the ILM operation.

Cause: An attempt was made to create a modification time-based policy when row-level write tracking was not enabled on the object.

Cause: An attempt was made to create a valid time-based policy when valid time periods were not present on the table.

Cause: An attempt was made to create an access time-based policy when row-level access tracking was not enabled on the object.

Cause: An attempt was made to create an access time-based policy when segment-level access tracking was not enabled on the object.

Cause: SYSDBA privilege is required for applying ILM policies on a tablespace.

Cause: A row level policy was used with a compression level other than OLTP.

Cause: A custom policy is only allowed at the segment level.

Cause: An attempt was made to create an Information Lifecycle Management (ILM) policy with incompatible scope.

Cause: An invalid action was specified in the policy definition.

Cause: An attempt was made to create a custom policy at the tablespace level.

Cause: An attempt was made to create more than one storage tiering policy directly on an object.

Cause: An attempt was made to create an Information Lifcecycle Management (ILM) policy when heat map was not enabled.

Cause: An attempt was made to perform an automatic data optimization (ADO) operation with supplemental logging enabled.

Cause: An attempt was made to create a policy on an object that was not enabled for in-memory column store.

Cause: An attempt was made to use an Information Lifecycle Mangement (ILM) operation that is not supported for the current SQL statement.

Cause: Join group cannot be created on the specified tables.

Cause: The specified join group cannot be dropped.

Cause: The specified join group cannot be altered.

Cause: One of the columns used for the join group was not supported because the column property field was non-zero.

Cause: One of the columns used for the join group was of the abstract data type.

Cause: The alter table operation caused one of the columns to become unsupported for a join group.

Cause: An attempt was made to create or alter table to enable ROW ARCHIVAL, but ROW ARCHIVAL is not supported for these table types.

Cause: There was a syntax error found for either the create, alter, or drop in-memory join group.

Cause: Information Lifecycle Management (ILM) internal operation encountered out-of-space error.

Cause: Internal testing event for table Information Lifecycle Management (ILM) operations.

Cause: There was an internal debugging event for table Information Lifecycle Management (ILM) operations.

Cause: The table was already enabled for the specified Information Lifecycle Management (ILM) feature.

Cause: An attempt was made to perform an Information Lifecycle Management (ILM) operation on a table on which the specified ILM feature is not enabled.

Cause: An attempt was made to drop, rename, or modify a system Information Lifecycle Management (ILM) column.

Cause: An attempt was made to update a system Information Lifecycle Management (ILM) column.

Cause: An attempt was made to combine Information Lifecycle Management (ILM) operation with other ALTER TABLE operations.

Cause: An attempt was made to use a synonym for a data type of an attribute or a table alias.

Cause: There were spaces in the name.

Cause: The attribute set name was longer than 22 characters.

Cause: There was a schema extension for the attribute set name. Attribute sets are always created in the current schema and thus schema extended names are not allowed.

Cause: The attribute set name contained quotes.

Cause: An attribute set with a matching name already exists in the current schema.

Cause: The Abstract type (ADT) with the same name as the attribute set already exists in the current schema.

Cause: An attempt was made to create the attribute set from a nonexistent ADT.

Cause: An invalid name or option was used for the attribute set.

Cause: An attempt was made to use a schema extended name for the table storing expressions.

Cause: An attempt was made to create an expression column from a column of invalid datatype.

Cause: The column storing expressions does not exist.

Cause: An attempt was made to create an elementary attribute with a name longer than 32 characters.

Cause: The datatype specified for the attribute was invalid.

Cause: An invalid name or datatype was used for the attribute.

Cause: An attempt was made to create a stored or indexed attribute longer than 300 characters.

Cause: An attempt was made to use an attribute set that does not exist.

Cause: The ADT with the same name as the attribute set was not found in the current schema.

Cause: An identifier used in the stored/indexed attribute sub-expression was not defined or was invalid.

Cause: The sub-expression used for the stored expression was invalid.

Cause: An attribute with a matching name (or form) already exists in the attribute set.

Cause: An attempt was made to create an attribute with invalid datatype.

Cause: An attempt was made to add an elementary attribute to an attribute set created from an ADT.

Cause: An attempt was made to un-assign an attribute set from an expression set when there is no attribute set assigned to it.

Cause: An attempt was made to un-assign an attribute set from an expression set when there is an Expression Filter index defined on the column.

Cause: An attempt was made to drop an attribute set when it is still associated with an expression set.

Cause: An attempt was made to use an attribute set that does not exist.

Cause: An attempt was made to create an expression filter index with more than 490 indexed attributes.

Cause: The (resulting) datatype for the attribute was not appropriate for storing.

Cause: An attempt was made to perform an unsupported operation.

Cause: Either the expression was not a valid SQL-WHERE clause format or it had references to nonexistent schema objects.

Cause: An attempt was made to use the EVALUATE operator on a column not configured as a column storing expressions.

Cause: The error was caused by the recursive operation.

Cause: Either the expression was not in a valid SQL-WHERE clause format or it had references to nonexistent schema objects or there is a missing attribute value.

Cause: The second argument to the EVALUATE operator had either a missing attribute or an invalid value for an attribute.

Cause: An attempt was made to add an elementary attribute to an attribute set assigned to an expression set.

Cause: An attempt was made to create an attribute set from an ADT that has one or more user methods.

Cause: An attempt was made to use the getVarchar API when the attribute set has one or more non-scalar types.

Cause: An attempt was made to use an invalid operation.

Cause: An attempt was made to copy an attribute set that is not accessible from the current schema.

Cause: The attribute set was created without default index parameters.

Cause: An attempt was made to use an ADT that is not in a valid state.

Cause: An attempt was made to collect statistics for an expression set with no attribute set assigned to it.

Cause: An attempt was made to clear the statistics that do not exist.

Cause: An attempt was made to use the TOP parameters clause with no statistics available for the expression set.

Cause: The embedded ADT has errors.

Cause: Object type required for the embedded ADT was missing.

Cause: An unsupported operator was used in the exf$indexoper array.

Cause: An attempt was made to create a table alias for a table that does not exist or is not accessible.

Cause: Either values for one of the attributes was incorrect or a stored attribute was invalid due to broken dependencies.

Cause: One or more secondary objects used to maintain the index did not exist

Cause: An attempt was made to use a name longer than 25 characters for the Expression Filter index.

Cause: An attempt was made to create the Expression Filter index in a schema other than that of the base table.

Cause: An attempt was made to create an Expression Filter index on a column with no attribute set association.

Cause: An attempt was made to create the Expression Filter index by a user who is not the owner of the index.

Cause: The attribute set was in an inconsistent state due to broken dependencies.

Cause: An attempt was made to use a non-XMLType attribute to configure XPath filtering.

Cause: An attempt was made to use an invalid operation.

Cause: An Attempt was made to use a non-existent XML Tag.

Cause: An attempt was made to configure XPath filtering with an XML Tag of unsupported datatype.

Cause: An attempt was made to create a duplicate XML Tag.

Cause: The input was missing an attribute list or had null values for the attribute names.

Cause: The input was missing a tag list or had null values for the tag names.

Cause: An attempt was made to assign an attribute set to a non-empty expression set.

Cause: Creation of the trigger failed due to the error listed in the message.

Cause: An attempt was made to INSERT or UPDATE a column storing expression without appropriate permissions.

Cause: An attempt was made to GRANT or REVOKE privileges to or from the current user.

Cause: An attempt was made to grant permission on a nonexistent expression set.

Cause: An attempt was made to use an invalid privilege.

Cause: An attempt was made to revoke a privilege that had not been granted.

Cause: An attempt was made to pass a null value for the table alias attribute in the data item, which is not permitted.

Cause: The VARCHAR representation of data item was too long.

Cause: An attempt was made to drop an ADT that was used to maintain an attribute set for the Expression Filter.

Cause: An attempt was made to create an attribute with a TABLE COLLECTION type.

Cause: The ADT was directly modified by CREATE or ALTER operations.

Cause: An attempt was made to alter a type (ADT) that is used to maintain an attribute set of an Expression set.

Cause: An attempt was made to create an attribute set from an evolved ADT or a subtype.

Cause: The creation of the system trigger EXPFIL_DROPOBJ_MAINT failed due to missing Expression Filter dictionary tables.

Cause: The creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed due to missing Expression Filter dictionary tables.

Cause: The creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed due to errors in SYS.EXF$DBMS_EXPFIL_SYSPACK package.

Cause: An attempt was made to create an attribute set from an ADT which is used by one or more dependent objects.

Cause: An attempt was made to use an empty attribute set.

Cause: An attempt was made to use an invalid name format.

Cause: Attempt was made to use a object that does not exist.

Cause: An attempt was made to use an invalid object as a function.

Cause: An attempt was made to add a duplicate function to the list.

Cause: An attempt was made to use an un-approved function in the expression.

Cause: An attempt was made to reassign an attribute set to an expression column.

Cause: Predicate table creation failed due to the reported error.

Cause: The quotes in the name did not match.

Cause: Either the expression was not in a valid SQL-WHERE clause format or it had references to nonexistent schema objects.

Cause: An invalid parameters clause was specified with the ALTER INDEX command.

Cause: An attempt was made to create an Expression Filter index in Standard Edition.

Cause: One of the attributes in the set has the same name as the name of one of the columns in the table configured for table alias.

Cause: The actual data type for the stored attribute configured for the Expression Filter index object did not match the data type recorded in the Expression Filter dictionary.

Cause: An attempt was made to REBUILD an Expression Filter index that was not valid.

Cause: Index with a matching name does not exist or the index was not created using ExpFilter indextype.

Cause: The expression filter index object has a stored or indexed attribute that had broken dependencies.

Cause: The expression set already had a list of stored and indexed attributes. Additional attributes cannot be specified in the CREATE INDEX parameters clause.

Cause: There was a generic error

Cause: An attempt was made to use a sub-query in the expression.

Cause: An attempt was made to use an invalid XML tag for the index.

Cause: An attempt was made to modify the index parameters after the index creation.

Cause: An attempt was made to use the operator binding with an attribute set containing more than one (table alias) attribute. This is not permitted.

Cause: An attempt was made to use an invalid default value or a default that is larger than 100 characters.

Cause: An attempt was made to use an invalid type for an attribute configured for text predicates.

Cause: An attempt was made to configure an attribute of spatial or text data type as stored predicate group.

Cause: The memory size did not satisfy the minimum memory requirement.

Cause: The input cursor did not return exactly two columns for transactional input format or the input cursor didn't have consistent data types for horizontal input format

Cause: The including & excluding cursor did not return exactly one column.

Cause: The including & excluding cursor item-id type did not match input cursor item-id type

Cause: There was insufficient available memory for candidate generation.

Cause: The user inputed a support threshold not in the range of [0, 1].

Cause: The inputed minimum or maximum itemset length exceed the internal maximum itemset length or less than 1.

Cause: The user inputed minimum length is more than maximum length.

Cause: The memory size did not satisfy the minimum memory requirement for tree counting.

Cause: An error occurred because DBMS_FREQUENT_ITEMSET and prefix ORA_FI are reserved for the DBMS_FREQUENT_ITEMSET package's internal use.

Cause: The input cursor's item type is not number or character type

Cause: The item's length was more than half of one database block.

Cause: Cursor parameter is returning less than 2 columns.

Cause: Expressions in input cursor do not have an alias name.

Cause: The user specified a max tree depth not in the range of [2, 20].

Cause: The memory size did not satisfy the minimum memory requirement for decision tree building.

Cause: The maximum number of flashback database log files was exceeded.

Cause: This message reports the filename for details of another message.

Cause: Could not write to the flashback database log file.

Cause: A corrupt flashback database log file header was read.

Cause: The flashback database log file header contained a checksum that does not match the value calculated from the file header as read from disk. This means the file header was corrupt.

Cause: When the flashback log file header was read, the block size in the control file did not match the block size contained in the header.

Cause: An ALTER DATABASE FLASHBACK ON command failed. Other messages in the alert log describe the problem.

Cause: An ALTER DATABASE FLASHBACK ON command failed because media recovery was not enabled.

Cause: An ALTER DATABASE FLASHBACK ON command failed because there was not enough space in the Recovery Area for the first flashback database log file.

Cause: An ALTER DATABASE FLASHBACK ON command failed because the Recovery Area was not enabled.

Cause: The flashback database log file was rejected because it appeared to be written by an incompatible version of Oracle.

Cause: A corrupt Flashback Database log file block header was read. More information was dumped to the trace file.

Cause: A corrupt flashback database log record header was read. Either the record type or length were incorrect. More information was dumped to the trace file.

Cause: An ALTER DATABASE FLASHBACK ON command had no effect because flashback database logging was already on.

Cause: An ALTER DATABASE FLASHBACK ON command failed because the database either crashed or was shutdown with the ABORT option.

Cause: An invalid log number was used when dumping a flashback database log file.

Cause: An invalid value was specified for TYPE in the DUMP FLASHBACK command.

Cause: An invalid option was specified in the DUMP FLASHBACK command. Currently the only options allowed are: DBA, TYPE, and LOGICAL.

Cause: An invalid thread number was used in dumping the flashback database log files for a thread.

Cause: An invalid object was specified in a DUMP FLASHBACK command. Currently the only objects allowed are: LOGFILE or THREAD.

Cause: A log file name or number was missing in a DUMP FLASHBACK LOGFILE command.

Cause: An invalid file number was specified in the DBA clause of a DUMP FLASHBACK command.

Cause: The ALTER DATABASE FLASHBACK command was specified without the ON or OFF keyword.

Cause: The SCN keyword was specified in a FLASHBACK DATABASE command but the SCN expression was invalid.

Cause: An invalid option was specified to the FLASHBACK DATABASE command. Valid options are: SCN or TIMESTAMP.

Cause: The database name specified in a FLASHBACK DATABASE command did not match the name of the currently mounted database.

Cause: A FLASHBACK DATABASE command was tried but flashback database logging has not been enabled.

Cause: The control file being used is a backup control file.

Cause: An SCN or time stamp provided in a FLASHBACK DATABASE command was in the future.

Cause: There was not enough flashback database log data to do the FLASHBACK DATABASE.

Cause: The expression supplied in a FLASHBACK DATABASE command was invalid.

Cause: The version of the flashback database log file header was corrupt.

Cause: The file size indicated in the control file did not match the file size contained in the flashback log file header. The flashback database log file was corrupt.

Cause: A flashback database log file shrank in size. This was likely to have been caused by operator or operating system error.

Cause: The database ID in the flashback database log file did not match the database ID in the control file.

Cause: The log file number in the flashback database log file did not match the control file.

Cause: The thread number in the flashback database log file did not match the control file.

Cause: The flashback database log is corrupted or is an old version.

Cause: A check of flashback database log file header at database open found that the flashback database log appeared to be an incorrectly restored backup. Flashback database log files cannot be backed up and restored.

Cause: The control file change sequence number in the flashback database log file was greater than the number in the control file. This implies that the wrong control file was being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.

Cause: A flashback database log file header contained a usable blocks value greater than the file size. The flashback database log file file is corrupt.

Cause: The formatted blocks value in the flashback database log file was greater than the file size. The flashback database log file was corrupt.

Cause: The flashback database log file header had log reset data that was different than the control file. The log was probably an incorrectly restored backup. Flashback database logs cannot be backed up.

Cause: The Time/SCN provided in a FLASHBACK DATABASE command was in the future of the database.

Cause: A different copy of the file was accessed the last time FLASHBACK DATABASE looked at the file header. A backup of the file was restored or the meaning of the file name changed during FLASHBACK DATABASE.

Cause: An error occurred during a FLASHBACK DATABASE command. See other errors on error stack.

Cause: A corrupt data block before image was encountered during a FLASHBACK DATABASE command.

Cause: An attempt to do FLASHBACK DATABASE found that the file was not available for recovery. Either it was online and the database was open in some instance, or another process was currently doing media recovery or flashback on the file.

Cause: An attempt was made to start a FLASHBACK DATABASE in the same session as a media recovery.

Cause: An attempt was made to use a dispatcher process for FLASHBACK DATABASE. Memory requirements disallow this recovery method.

Cause: This message reports the filename for details of another message.

Cause: During an RMAN FLASHBACK DATABASE conversation, a file was listed which was not part of the database. The RMAN conversation was aborted.

Cause: An attempt to perform a FLASHBACK DATABASE failed because the file does not have enough flashback log data to cover the time to flash back. Either the file did not have flashback generation enabled for it, or had flashback generation turned off for it some time during the time span of the flashback.

Cause: A FLASHBACK DATABASE command did not start. A redo log needed for the recovery part of FLASHBACK DATABASE could not be found or accessed.

Cause: An attempt was made to turn on flashback database logging for a tablespace that already has flashback turned on.

Cause: An attempt was made to turn off flashback database logging for a tablespace that already has flashback off.

Cause: An attempt to Flashback a database was made when the database was not mounted or was already open.

Cause: An attempt to do FLASHBACK DATABASE found that the file was restored since the last standby recovery. The file cannot be flashed back.

Cause: An attempt to turn on or off Flashback Database logging was made when the database was open or mounted by more than one instance.

Cause: Database flashback is on but this instance failed to start generating flashback data. Look in alert log for more specific errors.

Cause: A redo log needed for the recovery portion of FLASHBACK could not be read or opened. The FLASHBACK operation failed.

Cause: The FLASHBACK DATABASE operation failed. The recovery portion of FLASHBACK DATABASE needed redo from the first SCN to the second, but one or more of the redo logs in the range could not be read or opened.

Cause: A FLASHBACK DATABASE command did not start. The set of enabled threads changed during the time to flash back.

Cause: A FLASHBACK DATABASE command did not start. The datafile was restored from a backup taken when the enabled threads were different than at the time of the flashback.

Cause: A complete recovery was performed after a database flashback but the database was not opened for read-write access, or a FLASHBACK DATABASE command failed.

Cause: An attempt to do FLASHBACK DATABASE found that the file was shrunk during the time to flash back.

Cause: The value of parameters DB_FLASHBACK_RETENTION_TARGET must be same in all instances. All databases must have same flashback retention target parameters.

Cause: An operating system error occurred when Flashback Database tried to shrink (resize) a datafile. Flashback shrinks a file in order to undo the effects of a file expand, for example, an autoextension of the file.

Cause: A FLASHBACK DATABASE command failed after modifying the the database. Look in the alert log for more information about the failure.

Cause: A FLASHBACK DATABASE command successfully restored the database but failed during the recovery step. Look in the alert log for more information about the failure.

Cause: The recovery step of FLASHBACK DATABASE encountered the creation of a datafile that could not be added to the control file. An entry has been added to the control file for the new datafile, but with the file name UNNAMEDnnnn, where nnnn is the file number. Related error messages provide the file names that were originally used to create the files.

Cause: The recovery step of FLASHBACK DATABASE encountered the creation of a datafile and could not recreate the file. The error from the creation attempt is displayed in another message. The control file file entry for the file is 'UNNAMEDnnnnn'.

Cause: The recovery step of FLASHBACK database encountered the creation of a datafile and could not create the file because the file name is already in use in the database. The control file file entry for the file is 'UNNAMEDnnnnn'.

Cause: An attempt was made to disable media recovery while flashback database was enabled.

Cause: An attempt was made to set DB_RECOVERY_FILE_DEST to null while flashback database was enabled. Flashback database requires DB_RECOVERY_FILE_DEST to be set.

Cause: During a database mount, the RVWR process discovered that the recovery area was disabled. DB_RECOVERY_FILE_DEST must have been set null or removed from the INIT.ORA file while the database was unmounted.

Cause: A command was attempted that required the database to be mounted in this instance and not started in any other instance. ALTER DATABASE OPEN RESETLOGS requires that the database be started in only one instance if flashback database logging is enabled.

Cause: The restore point name of the CREATE RESTORE POINT command already exists. A restore point name must be unique.

Cause: The maximum number of restore points already have been created.

Cause: The restore point name specified in the command did not exist.

Cause: An attempt was made to disable media recovery while there is at least one guaranteed restore point.

Cause: An attempt was made to flashback database to a non-guaranteed restore point while flashback database is off. You can only flashback a database to guaranteed restore point when flashback database is not on.

Cause: An attempt was made to create a restore point when the database is in mount mode but it was not shutdown cleanly before it was mounted. In order to create a restore point when the database is mounted, the database must be shutdown cleanly before it is mounted.

Cause: An attempt to create a restore point failed. See other errors on the error stack and in the alert log for the specific reason.

Cause: Media recovery is not enabled. Media recovery must be enabled in order to create a guaranteed restore point.

Cause: An attempt was made to perform a command that requires Flash recovery area to be enabled.

Cause: While flashback database is not on, an attempt was made to create the first guaranteed restore point while the database is open.

Cause: An attempt was made to create a restore point or a guaranteed while a physical standby database is not cleanly checkpointed.

Cause: The file name provided in the command was longer than the maximum allowed.

Cause: The FLASHBACK DATABASE command included the RESETLOGS parameter but not the BEFORE parameter.

Cause: Flashback could not be started because a file was checkpointed or fuzzy at a point where the file can neither be restored nor recovered to our restore target. In order for a file to be brought to the restore target, the file has to be in one of the incarnations along the ancestral path from the current incarnation to the restore incarnation.

Cause: A Flashback Database logfile contains a record written by a future Oracle release and is unknown by this release.

Cause: The Flashback Pluggable Database target SCN or timestamp is greater than the current database or pluggable database SCN/timestamp and the database or pluggable database incarnation is not the last opened incarnation.

Cause: The Flashback Database target timestamp is not in the database's current incarnation or any of its ancestors.

Cause: FLASHBACK DATABASE succeeded. However, if ALTER DATABASE OPEN RESETLOGS command was attempted now, it would fail with the specified error.

Cause: There was not enough flashback log data to undo the flashback so a flashback was not started.

Cause: An attempt was made to recover some datafiles or tablespaces of a database after the database had been flashed back. In order to recover control file and all datafiles correctly, full database recovery is required after a database has been flashed back.

Cause: See other other messages on error stack for the cause.

Cause: An attempt is made to drop the guaranteed restore point Oracle created internally for a snapshot standby.

Cause: An attempt was made to start Redo Apply on an open physical standby database instance.

Cause: An improper value was used for ORA_EDITION when trying to specify an edition to use at login time. The value is not understandable as an identifier, or is too long.

Cause: This error occurred because a reference was made to an edition that does not exist or that the current user does not have privileges on.

Cause: This error occurred because a reference was made to an unusable edition.

Cause: This error occurred because an attempt was made to create an edition called ORA$BASE, DATABASE_DEFAULT, or USER_DEFAULT. These are not legal edition names. Or a value provided as an edition name is not understandable as an identifier, or is too long.

Cause: An attempt was made to ALTER or DROP an edition that was being used in another session or was the database default edition.

Cause: An attempt was made to use an edition that was in the process of being altered or dropped.

Cause: This error occurred because an attempt was made to create more than one child edition for a parent edition.

Cause: An attempt was made to make an edition with a usable parent and a usable child edition unusable.

Cause: This error occurred because an attempt was made to drop a usable edition.

Cause: This error occurred because an attempt was made to drop an edition that has a parent and a child edition.

Cause: This error occurred because an attempt was made to drop an edition that has actual objects.

Cause: The number of editions has reached the limit.

Cause: The Oracle-supplied schema did not support editions.

Cause: An attempt was made to execute an edition switch within an open transaction.

Cause: An edition switch failed because it was executed from a PL/SQL block or using recursive SQL.

Cause: This error occurred because an attempt was made to drop an edition that a child that inherits objects from the edition.

Cause: You did not have sufficient privileges to execute the subprogram package DBMS_EDITIONS_UTIL.

Cause: An attempt was made to violate the rule "A noneditioned object may not depend on an editioned object."

Cause: An attempt was made to violate the rule "A noneditioned object may not depend on an editioned object."

Cause: User could not be edition enabled if it has evolved object type.

Cause: Could not bind or define ADT, VARRAY, nested table or REF data type when the specified Edition is different from the current edition.

Cause: An attempt was made to create a referential integrity constraint to or from an editioned view or enable editions for a user that has views with referential integrity constraints.

Cause: An attempt was made to drop the root edition when enabled crossedition trigger exists.

Cause: An attempt was made to replace an existing object with a different value for the EDITIONABLE property.

Cause: An attempt was made to alter the EDITIONABLE property of an object whose type has been enabled for editioning in the owner's schema.

Cause: An attempt was made to create a TYPE or PACKAGE specification or body whose EDITIONABLE property did not match its counterpart.

Cause: An edition switch failed because an attempt was made to change pluggable database (PDB) before the edition switch took effect.

Cause: A change of the session-level edition failed because the overriding USE_DEFAULT_EDITION_ALWAYS mode was on.

Cause: The FLASHBACK DATABASE command failed before modifying the the database. Look in the alert log for more information about the failure.

Cause: A CREATE CONTROLFILE statement was given that did not list all the enabled threads for the database.

Cause: The standby switchover or failover operation failed because it needs to mark the current instance (redo thread) as disabled.

Cause: The open resetlogs or standby activation operation failed because it must use a different instance (redo thread) than the current instance (redo thread) to open the database.

Cause: The standby switchover or failover operation failed because it needs to mark an instance (redo thread) as disabled. That instance was up, which prevented it from being disabled.

Cause: The open resetlogs or standby activation operation failed because it needs to mark an instance (redo thread) as disabled. That instance was up, which prevented it from being disabled.

Cause: The standby switchover or failover operation failed because it needs to mark an instance (redo thread) as enabled. However, it had less than 2 online redo logs, which prevented it from being enabled.

Cause: The open resetlogs or standby activation operation failed because it needs to mark an instance (redo thread) as enabled. However, it had less than 2 online redo logs, which prevented it from being enabled.

Cause: The standby switchover or failover operation failed because it needs to mark a redo thread as enabled. However, the control file was recreated with a MAXINSTANCES value smaller than the thread number of the redo thread.

Cause: The open resetlogs or standby activation operation failed because it needs to mark a redo thread as enabled. However, the control file was recreated with a MAXINSTANCES value smaller than the thread number of the redo thread.

Cause: The command attempted to switch the instance (thread) into a new log before disabling it. The switch attempt failed because all eligible online logs were either being cleared or not completely archived yet.

Cause: The command was not permitted because the controlfile indicates the database was in the process of becoming a logical standby database but the controlfile conversion had not completed.

Cause: Flashback recovery on the standby ended early because the user attempted to flashback to an SCN or time for which there were no redo logs. Most likely, the user is trying to flashback to a future time in the database that the database has never recovered through. Check the alert log to find out which SCN the database recovered to.

Cause: The command could not be performed because the flashback database logs were locked by another operation, such as FLASHBACK DATABASE or a query of V$FLASHBACK_DATABASE_LOG.

Cause: Flashback Database could not flash back the file because it was restored from an RMAN optimized backup with deallocated objects. Flashback cannot revert the file to a time before the last deallocation in the datafile backup.

Cause: An SCN or timestamp was specified when creating a guaranteed restore point. This is not supported. You can only create a guaranteed restore point as of the current time.

Cause: An attempt was made to create a restore point with an SCN or timestamp that is in the future.

Cause: An attempt was made to create a restore point with an SCN or timestamp that is before the beginning of the current database incarnation.

Cause: An attempt was made to create a restore point with the specified timestamp while the database was not open. The database must be open in order to map the timestamp to an SCN.

Cause: This control file was created or converted based on a control file from a time different from the time of the database.

Cause: Flashback Database could not flash back the database because a file was restored from an RMAN backup with undo block compression, and the Flashback target was to a time when the missing undo may be needed to open the database.

Cause: This control file was created or converted based on a control file from a time different from the time of the database.

Cause: To enable flashback on a primary database, the database must be clean without requiring open resetlogs.

Cause: RECOVER DATABASE with the BACKUP CONTROLFILE option, or a database recovery that required the control file be made a backup failed because Flashback Database was enabled or there was a guaranteed restore point.

Cause: Flashback Database failed because incarnation information was not found in the control file. The Flashback target incarnation was not in the control file or had a missing parent incarnation.

Cause: Flashback Database failed because incarnation information for the start of the offline range for a file was not found in the control file. Flashback could not update the file's header with the missing incarnation's resetlogs information.

Cause: The FLASHBACK DATABASE command was not performed because it was started in test mode.

Cause: The FLASHBACK DATABASE command was performed in test mode and determined that no redo logs were required to perform the tested FLASHBACK DATABASE command.

Cause: The FLASHBACK DATABASE command was performed in test mode and determined that no redo logs required to perform the tested FLASHBACK DATABASE command were missing.

Cause: A redo log needed for the recovery part of FLASHBACK DATABASE could not be found or accessed.

Cause: A data file was plugged in when there was a guaranteed restore point, but Flashback Database was not enabled. It is possible that some changes to the data file, after it was converted, were not logged to the Flashback Database logs.

Cause: Flashback database cannot undo the advance of database compatibility. Therefore, one cannot advance the compatibility of the database while there are guaranteed restore points in the database.

Cause: An attempt was made to drop a tablespace on a primary database while there are guaranteed restore points. You cannot do this because Flashback database cannot undo dropping of a tablespace.

Cause: An attempt was made to drop a tablespace on a standby database while there are guaranteed restore points. You cannot do this because Flashback database cannot undo dropping of a tablespace.

Cause: An attempt was made to shrink a data file on a primary database while there are guaranteed restore points. You cannot do this because Flashback database cannot undo the shrinking of a data file.

Cause: An attempt was made to shrink a data file on a standby database while there are guaranteed restore points. You cannot do this because Flashback database cannot undo the shrinking of a data file.

Cause: Flashback database was disabled while fast-start failover was enabled.

Cause: Recovery writer (RVWR) encountered an error when writing flashback database logs.

Cause: An error occurred while writing to the flashback database logs.

Cause: The provided thread number was invalid.

Cause: Mandatory column of error logging table is not present

Cause: Mandatory information column of error logging table is present, but must be at the beginning of the row.

Cause: The operation failed because the array DML had more errors than can be stored internally for BATCH ERRORs.

Cause: A DML Error Logging operation was attempted on a table which has an ADT, REF, VARRAY, or nested table column type, and the error logging table referred to the specified column.

Cause: A DML Error Logging operation was attempted on a table which has a CLOB, NCLOB, or BLOB column type, and the error logging table referred to the specified column.

Cause: A DML Error Logging operation was attempted on a table which has a LONG, or LONG RAW column type, and the error logging table referred to the specified column.

Cause: An error occurred when attempting to log a DML Error on behalf of the DML Error logging clause. This may be intended if a trigger is defined on the error table (which in turn errors out in certain cases).

Cause: A DML Error Logging operation was attempted on a table which has a BFILE column and the Error Logging table referred to the specified column.

Cause: An unexpected error occurred while executing recursive SQL to insert a row into the DML Error Logging table.

Cause: A DML Error Logging operation was attempted on a table which has BATCH ERROR mode also specified.

Cause: BATCH ERROR mode specified for this operation.

Cause: An INSERT statement with a CHANGE_DUPKEY_ERROR_INDEX hint tried to insert a duplicate key into a table.

Cause: Index specification was missing in an IGNORE_ROW_ON_DUPKEY_INDEX or CHANGE_DUPKEY_ERROR_INDEX hint.

Cause: The index specified in an IGNORE_ROW_ON_DUPKEY_INDEX or CHANGE_DUPKEY_ERROR_INDEX hint could not be found.

Cause: IGNORE_ROW_ON_DUPKEY_INDEX and CHANGE_DUPKEY_ERROR_INDEX were both specified in the same statement.

Cause: Multiple indexes were specified in an IGNORE_ROW_ON_DUPKEY_INDEX or CHANGE_DUPKEY_ERROR_INDEX hint.

Cause: CHANGE_DUPKEY_ERROR_INDEX hint was specified for the operation.

Cause: IGNORE_ROW_ON_DUPKEY_INDEX hint was specified for the operation.

Cause: RETRY_ON_ROW_CHANGE hint was specified for the operation.

Cause: A remote table was specified in the DML error logging clause.

Cause: Cross platform transport was not allowed for this platform.

Cause: Cross platform transport was not allowed for this platform.

Cause: Cross platform transport is not supported unless database compatibility is advanced to 10.0.0.0 or higher

Cause: The platform identifier in the transported file indicated that the datafile format was different than the target database datafile format.

Cause: The platform identifier in the transported file indicated that this platform is not supported for a cross platform transport.

Cause: Cross platform transport was not allowed for this platform.

Cause: Probably a conversion was not done before the import phase of the transport.

Cause: An attempt was made to update block 0 to version 10 format.

Cause: The file was directly copied to this platform from a platform with a different endian ordering.

Cause: Reporting file name for details of another error.

Cause: The user specified a dump file that could not be used in the current job. Subsequent error messages describe the inadequacies of the dump file.

Cause: The user specified API parameters were of the wrong type or value range. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

Cause: The current API cannot be executed because of inconsistencies between the API and the current definition of the job. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

Cause: Attempt to get count of total worker processes alive failed.

Cause: The state of the job precludes the execution of the API.

Cause: The current API cannot be executed because of inconsistencies between arguments of the API call. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

Cause: An unexpected error occurred while processing a Data Pump job. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

Cause: The client detached or ended their session before the Data Pump job was started.

Cause: A remap_schema transform with the SYSTEM schema was specified.

Cause: One or more of the worker processes exited before the job was completed. With no workers, the master process will terminate the job.

Cause: An API was executed that required the job to be running, but the job was not active.

Cause: The state of the job precludes the execution of the API.

Cause: The state of the job precludes the execution of a worker request. This is an internal error.

Cause: Internal Error

Cause: User specified an invalid operation name on an DBMS_DATAPUMP.OPEN API or an invalid operation name was specified in the master table for a restart API.

Cause: User specified an invalid mode on an DBMS_DATAPUMP.OPEN API or an invalid mode was specified in the master table for a restart API.

Cause: User selected COMPATIBLE as the version on an DBMS_DATAPUMP.OPEN API, but the current database compatibility version is not supported by the Data Pump API. Database versions before 9.2 are not supported by the Data Pump.

Cause: User selected LATEST as the version on an DBMS_DATAPUMP.OPEN API, but the current database version is not supported by the Data Pump API. Database versions before 9.2 are not supported by the Data Pump.

Cause: User specified an explicit version on an DBMS_DATAPUMP.OPEN API, but the current database version is not supported by the Data Pump API. Database versions before 9.2 are not supported by the Data Pump.

Cause: Internal error caused by the master process finding inconsistencies between the schemas specified for the job.

Cause: Attempt to restart a job which was not restartable.

Cause: Job cannot be restarted because it failed a validation check. Validation checks are of the form -xx.y where -xx is the value of the PROCESS_ORDER column in the master table where the error was detected and y is the actual validity check for the row.

Cause: Job cannot be restarted because the version of the database upon which the job started is different than the current version of the database and the format of the master table has changed between the versions.

Cause: The job was not in a suitable state for restart. Jobs must begin executing before they can be restarted.

Cause: The specified worker process terminated unexpectedly. Subsequent messages describe the reason for the termination.

Cause: An invalid filetype was specified for an DBMS_DATAPUMP.ADD_FILE API call.

Cause: An invalid filter name was specified on a DBMS_DATAPUMP.DATA_FILTER API call.

Cause: The specified parameter was not supported for the specified class of jobs.

Cause: The user specified that the data access method for the job was direct which precludes the use of certain data filters.

Cause: The user referenced a table in an API that did not exist.

Cause: The user has already specified a data filter that matches on the filter name, schema name, and table.

Cause: An invalid metadata filter name was specified on a DBMS_DATAPUMP.METADATA_FILTER API call.

Cause: An object type path was specified for the filter, but the filter does not support the object type path parameter.

Cause: The specified object type path is invalid for the job mode.

Cause: The specified SCHEMA_EXPR filter resulted in no schemas being selected.

Cause: For TABLE mode jobs, the SCHEMA_EXPR filter must identify exactly one schema.

Cause: A Metadata filter specifying path names either returned all objects or no objects in the job.

Cause: An invalid transform name was specified on a DBMS_DATAPUMP.METADATA_TRANSFORM API call.

Cause: The specified object type is invalid for the specified transform or remap.

Cause: The user has already specified the metadata transform for the same class of object types.

Cause: An invalid metadata remap name was specified on a DBMS_DATAPUMP.METADATA_REMAP API call.

Cause: The user has already specified a metadata remap that matches on the remap name and original value.

Cause: The user specified a value of parallelism that is precluded by the operation type or mode of the job.

Cause: The full degree of parallelism could not be honored due process limits, resource limits, or other internal errors.

Cause: An invalid parameter name was specified on a DBMS_DATAPUMP.SET_PARAMETER API call.

Cause: Two parameters were set that were incompatible with each other. Only the first parameter setting will be used.

Cause: The user has already specified a parameter that matches on the name and the specific parameter doesn't support duplicate definitions.

Cause: The user has already specified SKIP_CURRENT for a job that has never executed.

Cause: The job being defined cannot be started because it is missing the specified definition.

Cause: The job being defined could not be started because it was missing the file to receive the SQL output of the job, the SQL output file name conflicted with the output LOG file, or the definition was unusable.

Cause: The user attempted to use a feature that was not enabled in the database version specified for the current job. Typically, this error occurs if the compatibility level of the database is below the current version of the database or if the user explicitly specifies a version for a Data Pump job.

Cause: The log file for the job was incorrectly specified.

Cause: The worker process sent a message that wasn't supported for the current job.

Cause: The user specified SKIP_CURRENT when restarting a job. This message is a confirmation that the object will not be imported.

Cause: An IMPORT or SQL_FILE operation was being performed but not all of the files from the EXPORT dump file set were included.

Cause: A table specified by a job was not included because its definition would collide with the master table definition for the current job.

Cause: The mode used for import cannot be used with a dump file set of specified mode. Transportable jobs are not compatible with other modes.

Cause: An attempt to create the listed master process failed.

Cause: Errors were detecting while writing to the log file. Subsequent messages will detail the problems.

Cause: An unhandled exception was detected internally within the master control process for the Data Pump job. This is an internal error. messages will detail the problems.

Cause: Errors were detecting while closing the log file. Subsequent messages will detail the problems.

Cause: A corruption was detected in the master table in the specified row(s). Either the row wasn't found, it was missing columns or had illegal values in its columns.

Cause: Errors were detecting while opening the log file. Subsequent messages will detail the problems.

Cause: The value of the user specified filter did not contain a legitimate SQL clause. Subsequent messages will detail the problems.

Cause: Unable to delete a job. Refer to the any following or prior error messages for clarification.

Cause: The Data Pump's communication layer was unable to attach one of its processes to the control or status queue. Subsequent messages will detail the problem.

Cause: The Data Pump's communication layer was unable to retrieve a message from the control or status queue. Subsequent messages will detail the problem.

Cause: The Data Pump's communication layer was unable to send the specified message on the control or status queue. Subsequent messages will detail the problem.

Cause: The Data Pump's communication layer was unable to create the status and control queues required for interprocess communication. Subsequent messages will detail the problem.

Cause: The Data Pump's communication layer was unable to unsubscribe a process from the control or status queue. Subsequent messages will detail the problem.

Cause: The object in the SQL statement following this error was created with compilation errors. If this error occurred for a view, it is possible that the base table of the view was missing.

Cause: Examine original error code to determine actual cause

Cause: Unable to detach a job from the session. Refer to any following error messages for clarification.

Cause: Unable to update the fixed table information for a job. Refer to any following or prior error messages for clarification.

Cause: Unable to retrieve fixed table information for a job. Refer to the secondary error messages that follow this one for clarification.

Cause: A corresponding directory object does not exist.

Cause: The name of a dump file, log file, or sql file contains a path specification.

Cause: Attempt to add a device to a job that already contains more than one disk file.

Cause: An error occurred when determining if the Data Pump job needed to support logical standby or streams.

Cause: An error occurred when applying a SCN to the specified object to support logical standby or streams.

Cause: A Data Pump job was required to enable flashback support to specific SCNs in order to preserve the consistency of a logical standby or streams instantiation.

Cause: Parallel execution of Data Pump jobs is not supported for this database edition.

Cause: The Export job ran out of dump file space before the job was completed.

Cause: A NULL or invalid value was supplied for the parameter.

Cause: An unexpected, potentially non-fatal error occurred while processing a Data Pump job.

Cause: This is an internal error. Messages will detail the problem.

Cause: One or more indexes couldn't be created on the master table. subsequent error messages describe the failure.

Cause: The master process whose name is listed started up but did not finish its initialization within the allowed time limit.

Cause: The worker process whose name is listed started up but did not finish its initialization within the allowed time limit.

Cause: Called a Data Pump process model function from a process which is a SQL parallel query slave process

Cause: The master process whose name is listed failed during startup.

Cause: The worker process whose name is listed failed during startup.

Cause: The master process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.

Cause: The worker process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.

Cause: An unprivileged user attempted to reference another user's schema during a Data Pump operation. Because of this, no schemas were were selected for the job.

Cause: An attempt to delete the worker processes failed.

Cause: During a Data Pump import job, a dependent object is being skipped because its base object already existed.

Cause: During a Data Pump import job, a dependent object is being skipped because its base object creation failed.

Cause: The Data Pump was unable to determine the compatibility level and version of the current database using SYS.DBMS_UTILITY.DB_VERSION.

Cause: An attempt was made to add a dumpfile to an Import job that is using a network link to the source database.

Cause: An attempt was made to use an option that is not supported over network links such as the PARTITION_LIST filter.

Cause: A Data Pump load operation failed because a trigger attempted to fire on the table while it was mutating.

Cause: A create table was attempted and a dependent type does not exist in the dumpfile or on the target database. Either the export or the import Data Pump job was a table mode job and types are not included in table mode jobs.

Cause: The master process that created this worker process called delete worker processes to abort the current operation.

Cause: Table data was about to be loaded into a table that already existed and the table_exists_action parameter is truncate, but the table could not be truncated.

Cause: Table data was about to be loaded into a table that already existed and the table_exists_action parameter is replace, but the table could not be dropped.

Cause: A user attempted to remap objects during an import but lacked the IMPORT_FULL_DATABASE privilege.

Cause: A DBMS_PLUGTS procedure failed and the Data Pump operation could not continue so it was aborted. The DBMS_PLUGTS failure listed describes the original error.

Cause: The substitution variable '%' must be followed by '%','u', or 'U'.

Cause: An unhandled exception was detected internally within the worker process for the Data Pump job while calling the specified external routine. This is an internal error. Additional information may be supplied.

Cause: An unhandled exception was detected internally within the worker process for the Data Pump job. This is an internal error. Additional information may be supplied.

Cause: The exception was raised by the function invocation, a procedural action extension of export.

Cause: The error was returned from a call to a DbmsJava procedure.

Cause: The table being imported from the remote instance has the same name as the master table running this Data Pump job.

Cause: The object being imported from the remote instance is dependent on an object that has the same name as the master table running this Data Pump job.

Cause: An object type could not be created because there was already a type with the same name but a different hashcode on the target system. Tables in the transportable tablespace set that use this object type cannot be read.

Cause: An object type in a transportable tablespace set already exists on the target system, but with a different typeid. The typeid could not be changed because the type is used by an existing table. Tables in the transportable tablespace set that use this object type cannot be read.

Cause: The user attempt to specify the SYSAUX or SYSTEM tablespace as a member of the transportable tablespace list in the current job. These tablespaces may not be transported between databases.

Cause: An attempt was made to add a new file to an export job but a file with the same name already exists in the dump set for the job.

Cause: A target SCN was specified for a table in a transportable job by the streams or logical standy components which was not the defaulted SCN for the table.

Cause: A job was defined with the TABLE_EXISTS_ACTION parameter set to REPLACE or SKIP, but without metadata. Without metadata, data could not be loaded for the requested table actions.

Cause: An unprivileged user attempted to load data into a different schema.

Cause: Object had an XMLType column using either an object relational or binary storage format, which is unsupported by Data Pump in the target version.

Cause: When a dump file set consists of multiple files, all files in the set must be specified for an import operation, and all files must have been produced by the same export job. One of the files provided does not belong to the original dump file set. For instance, it was created by a different export job than the other files.

Cause: When a dump file set consists of multiple files, all files in the set must be specified for an import operation. One of the files provided to import was found to be a duplicate of another dump file in the set. This can occur if the files in the dump set were copied or renamed using operating system utilities and the same dump file was inadvertently copied more than once with different destination names.

Cause: A dump file was specified for an import operation whose version number is incompatible with the dump file version of the Data Pump product currently running on the system. Usually this message indicates that the dump file was produced by a newer version of the Data Pump export utility.

Cause: A dump file was specified for an import operation which appears to have been created using the original export utility. These dump files cannot be processed by the Data Pump import utility.

Cause: No file name was provided in an DBMS_DATAPUMP.ADD_FILE API call.

Cause: No directory object was provided in either an DBMS_DATAPUMP.ADD_FILE API call or to the directory parameter used by the Data Pump command line clients.

Cause: The specified schema was referenced as the source of a REMAP_SCHEMA parameter, but did not exist in the dump file (for file-based import) or in the source database (for network import).

Cause: There are active Data Pump jobs running on another instance in a RAC. All concurrent, active Data Pump jobs must be run on the same instance.

Cause: A Data Pump import detected that a queue table that was to be imported already exists. Importing data into pre-existing queue tables is not supported.

Cause: A Data Pump job initiated be a user with EXPORT_FULL_DATABASE/IMPORT_FULL_DATABASE roles specified a network link that did not correspond to a user with equivalent roles on the remote database.

Cause: A flashback time was specified for the Data Pump job which either could not be parsed or else could not be translated into a system change number (SCN). This typically occurs when specifying a time far in the past.

Cause: An non-privileged user attempted to import objects into a schema other than their own.

Cause: Export was unable to expand the directory object and dump file name into a full file name. Subsequent messages will detail the problems.

Cause: Export was unable to parse the dump file name. Subsequent messages will detail the problems.

Cause: Export or Import was unable to append the default extension to create the file name. The given file name could be too long or contain illegal characters. Subsequent messages will detail the problems.

Cause: Called a Data Pump process model function from a process which is not a Data Pump process.

Cause: Attempt to get the Data Pump process name failed.

Cause: Either an attempt to perform a full database export without the EXP_FULL_DATABASE role or an attempt to perform a full database import over a network link without the IMP_FULL_DATABASE role.

Cause: User attempted to perform a transportable tablespace job without being having the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role.

Cause: An attempt was made to do data sampling on a table with a value outside of the range of 0 - 100.

Cause: If exporting or importing over the network, the user specified a partition name that was not found in the source database. For importing from files, the user specified a partition name not found in the dump file set.

Cause: If exporting or importing over the network, either the user specified a schema name that was not found in the source database or else the user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role that would allow them to access another schema. For importing from files, the user specified a schema name not found in the dump file set.

Cause: If exporting to files or importing over the network, one of the following occurred: - The object specified did not exist in the source database. - The user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role that would allow access to the object. - The VIEWS_AS_TABLES object contained a type that is not supported with the VIEWS_AS_TABLES parameter. If importing from files, the user specified an object name that was not found in the dump file set.

Cause: If exporting or importing over the network, the user specified an object type path name that was not found in the source database. For importing from files, the user specified an object type path name not found in the dump file set.

Cause: A Data Pump job specified a network link, but the version on the remote database cannot interoperate with the version on the local database.

Cause: A schema expression or schema list was supplied for a Data Pump job that did not identify any schemas in the source database.

Cause: The Data Pump job is stalled with one or more of its sessions having a resumable wait. Resumable waits are typically caused by a non-expandable tablespace running out of space. The follow-on message describes the nature of the wait.

Cause: The user attempted to remap a tablespace name in a transportable tablespace job when the compatibility level was set below 10.1.

Cause: No encryption password was specified for an export job that involved data that was encrypted in the database.

Cause: No encryption password was supplied to import a dump file set that was created using an encryption password.

Cause: An encryption password was supplied to import a dump file set that was not created using an encryption password.

Cause: The wrong encryption password was supplied to import a dump file set.

Cause: An invalid value was specified for compression.

Cause: An estimate was requested for a job by specifying the ESTIMATE or ESTIMATE_ONLY parameter. However, the job was also defined to have no data. These specifications conflict with each other.

Cause: The OID transform for the job was set to false and the identified table contained either VARRAYs with non-final types or unscoped REF columns. Both of these column types have embedded OIDs so they cannot be imported correctly when OIDs are not preserved.

Cause: The specified encryption password was unable to be encrypted for placement within the master table or decrypted when it was to be restored from the master table. Subsequent messages will describe the actual error that caused the encryption to fail.

Cause: An unprivileged user has tried to export a table that has fine grain access control. The table owner is subjected to access control and may not be able to export all rows in the table. Only the rows that can be seen by that user will be exported. In order to preserve integrity of the table, the user importing the table should have enough privilege to recreate the table with the security policies at import time.

Cause: An unexpected error occurred while compressing data buffers.

Cause: An unexpected error occurred while decompressing data buffers.

Cause: A Transportable Data Pump job requires all PLUGTS% objects, but the user-supplied exclude filters were excluding these objects.

Cause: Some of the tablespaces specified for this job could not be exported.

Cause: The tablespaces specified on the EXPORT command did not exist.

Cause: The tablespaces specified for this job did not satisfy the closure checking. The list of violations specified each closure violation.

Cause: Data Pump could not create an encrypted dump file set. This message will be accompanied by other messages that give more details about why the encrypted dump file set could not be created. The most common reason for this message is that you are trying to create a dump file set that can be transparently decrypted, and the database external security device is not open.

Cause: The dump file set could not be decrypted. The reason could be either that an invalid password was entered, or that, when using transparent decryption, the database external security device was not open.

Cause: An unexpected error occurred while encrypting data buffers.

Cause: An unexpected error occurred while decrypting data buffers.

Cause: Multiple tables are not supported when specifying partitions while using transportable table mode.

Cause: The table filter included a schema expression with the % wild card.

Cause: The string describing tables in a table mode job was not comma separated.

Cause: The TABLE_FITER specified contains a schema that does not exist.

Cause: The name of the network link supplied for a Data Pump job was not usable. Secondary messages identify the problem.

Cause: An attempt was made to add a dumpfile to an Export job that only requested file estimates.

Cause: A data filter was supplied for the specified type of job, but is not supported in the specified job type. From the command line, data filters can be specified by the CONTENT, TABLES (partition specifications), SAMPLE and QUERY parameters.

Cause: Specific partitions were selected for a job operating over a network link.

Cause: A tablespace filter was applied to a transportable import job that was not performed over a network link. In this case, the tablespace may not be changed from its specification at export time.

Cause: A metadata transformation such as STORAGE or SEGMENT_ATTRIBUTES has been specified for a transportable Data Pump job.

Cause: A bad numeric was supplied for specifying the parallelism to be used within a Data Pump job. The degree of parallelism must be an integer great than 0.

Cause: A parameter for a Data Pump job was set with a NULL or invalid value.

Cause: The a parameter has been specified that is not supported for the specified type of Data Pump.

Cause: Use of the specified privileges requires the user to have the IMP_FULL_DATABASE role for import jobs or the EXP_FULL_DATABASE role for export jobs.

Cause: User specified a storage space transformation that was out of range. Values for PCTSPACE must be greater than zero.

Cause: User specified an invalid or inaccessible file with the specified filename and directory object.

Cause: The XSL stylesheets used by the Data Pump Metadata API were not loaded correctly into the Oracle dictionary table "sys.metastylesheet." Either the stylesheets were not loaded at all, or they were not converted to the database character set.

Cause: The Data Pump could not use the Metadata API. Typically, this is caused by the XSL stylesheets not being set up properly.

Cause: The object is an external table with encrypted columns and this is unsupported with Data Pump.

Cause: An object type in a transportable tablespace set could not be used because there was a type with the same name but a different hashcode (and type definition) or the same hashcode but different version numbers for the type on the target system. Tables in the transportable tablespace set that use this object type cannot be created.

Cause: An object type in a transportable tablespace set already exists on the target system, but with a different typeid. The typeid could not be changed because the type or a dependent type is used by an existing table. Tables in the transportable tablespace set that use this object be created.

Cause: The type check on a type failed. Therefore, the table create for the table which uses the type also fails.

Cause: The directory object name provided to the Data Pump Job was invalid because its length was greater than 30 characters.

Cause: The file name provided to the Data Pump Job was invalid because its length was greater than 4000 characters.

Cause: A data filter was supplied for an import job, but the dumpfile does not contain any table data. The export command created a dumpfile with metadata only. No table data was included. From the command line, data filters can be specified by the CONTENT, SAMPLE and QUERY parameters.

Cause: Data Pump tried to create a global temporary master table but could not. The errors that follow describe why the table could not be created.

Cause: An unexpected error occurred while processing the job. The data in an internal table could not be found.

Cause: These rows were not loaded due to constraint or index violations.

Cause: All (sub)partitions in the job were to be created as individual objects and the renaming was defaulted. The job will attempt to create unique object names, but the name creation algorithm was unable to find a unique object name for the specified (sub)partition.

Cause: The specified resource service name for the Data Pump job was not available.

Cause: The specified type of data remapping was not supported.

Cause: The specified package function for performing data remapping was not found.

Cause: The column name specified for the data remapping either does not exist in the specified table, is not a scalar column, or is not supported.

Cause: Data remapping was requested on a job that requires the direct path access method. Data remapping can only be performed using the external table access method.

Cause: A data remap has already been specified for the indicated column. Only one data remap may be defined for a column.

Cause: An error occurred while performing XML difference parse.

Cause: MDAPI XML difference parsing did not support node attributes.

Cause: XML documents compared were identical.

Cause: Error occurred in the MDAPI difference writer.

Cause: See the Data Pump documentation for an explanation of what table attributes prevent an export or import from succeeding.

Cause: The export job used 'TRANSPORTABLE=ALWAYS' and the import job requires TRANSPORT_DATAFILES to be specified.

Cause: A Data Pump IMPORT or SQL_FILE operation was being performed but not all of the files from the Data Pump export dump file set were included.

Cause: A Data Pump IMPORT or SQL_FILE operation was being performed but not all of the files from the Data Pump export dump file set were included. In particular, the dump file containing the export job's master table was not provided.

Cause: An import of a SecureFile LOB with metadata into a scalar column was attempted.

Cause: An attempt was made to import a SecureFile LOB that contained metadata or was archived at the time of export into a BasicFile LOB.

Cause: The tables specified for this export job did not exist.

Cause: The direct path access method could not be used to load into a preexisting table that has a column with a default value and that column is not being loaded into, or the column is default on null.

Cause: The Data Pump expected a PLUGTS_BLK object to be exported but none were.

Cause: The remote database was read-only and Data Pump export jobs using transportable tablespace over a network link require the remote database to be read/write.

Cause: DBMS_METADATA_DIFF was comparing two clusters with different names. There is no SQL ALTER statement to rename a cluster.

Cause: DBMS_METADATA_DIFF was comparing two clusters with different column lists. There is no SQL ALTER statement to add a column to a cluster.

Cause: DBMS_METADATA_DIFF was comparing two clusters with different column lists. There is no SQL ALTER statement to delete a column from a cluster.

Cause: DBMS_METADATA_DIFF was comparing two clusters with different column lists. There is no SQL ALTER statement to modify a column in a cluster.

Cause: DBMS_METADATA_DIFF was comparing two hash clusters with different sizes. There is no SQL ALTER statement to modify the size of a hash cluster.

Cause: DBMS_METADATA_DIFF was comparing two objects, both with PARALLEL but with different INSTANCES values. There is no SQL ALTER statement to modify PARALLEL INSTANCES.

Cause: DBMS_METADATA_DIFF was comparing tables of different types: relational table, object table or XMLType table. There is no SQL ALTER statement to change a table's type.

Cause: DBMS_METADATA_DIFF was comparing object tables based on different object types. There is no SQL ALTER statement to change an object table's object type.

Cause: DBMS_METADATA_DIFF was comparing two tables with different partitioning attributes. There is no SQL ALTER statement to resolve these differences.

Cause: DBMS_METADATA_DIFF was comparing two table columns, one with a default value, one without. There is no SQL ALTER syntax to remove a column default.

Cause: DBMS_METADATA_DIFF was comparing two table columns, one virtual, one real. There is no SQL ALTER statement to make a virtual column real or vice versa.

Cause: DBMS_METADATA_DIFF was comparing two table columns, the first of type LONG, the second of a data type other than LOB. There is no SQL ALTER statement to modify a long data type to anything other than a CLOB or NCLOB.

Cause: DBMS_METADATA_DIFF was comparing two table columns, the first of type CLOB, NCLOB or BLOB, the second of some other data type. There is no SQL ALTER statement to change the data type of a LOB column.

Cause: DBMS_METADATA_DIFF was comparing two table columns. This error may occur because the first column is substitutable and the second column is not, or because the first column is OF TYPE and the second column is substitutable.

Cause: DBMS_METADATA_DIFF was comparing two nested table columns. One was a heap table, the other an index-organized table. There is no SQL ALTER statement to change the organization of a nested table.

Cause: DBMS_METADATA_DIFF was comparing two XMLType columns with different storage types (CLOB, BINARY, OBJECT RELATIONAL). There is no SQL ALTER statement to change the storage type of an XMLType column.

Cause: DBMS_METADATA_DIFF was comparing two tables with different physical organizations (heap, index organized, external, or cluster). There is no SQL ALTER statement to change the physical organization of a table.

Cause: DBMS_METADATA_DIFF was comparing two tables with different FREELIST GROUPS storage options. There is no SQL ALTER statement to change a table's INITIAL storage option.

Cause: DBMS_METADATA_DIFF was comparing two tables with different MINEXTENTS storage options. There is no SQL ALTER statement to change a table's MINEXTENTS storage option.

Cause: DBMS_METADATA_DIFF was comparing two tables with different FREELIST GROUPS storage options. There is no SQL ALTER statement to change a table's FREELIST GROUPS storage option.

Cause: DBMS_METADATA_DIFF was comparing two tables, the first with allocated segments, the second with deferred segments. There is no SQL ALTER statement to change a table which already has segments to segment creation deferred.

Cause: DBMS_METADATA_DIFF was comparing two index organized tables whose overflow segments have different tablespaces. There is no SQL ALTER statement to change an overflow segment's tablespace.

Cause: DBMS_METADATA_DIFF was comparing two index organized tables, the first with an overflow segment, the second without. There is no SQL ALTER statement to drop an overflow segment.

Cause: DBMS_METADATA_DIFF was comparing two index organized materialized views with different key compression values. There is no SQL ALTER statement to modify the key compression of an index organized materialized view.

Cause: DBMS_METADATA_DIFF was comparing two partitioned tables with different default tablespaces. There is no SQL ALTER statement to change the default tablespace of a partitioned table.

Cause: DBMS_METADATA_DIFF was comparing two tables or indexes partitioned or subpartitioned by hash, and a (sub)partition in the first object was not present in the second object. Partition maintenance operations such as drop, split or merge can only be performed on list or range (sub)partitioned objects.

Cause: DBMS_METADATA_DIFF was comparing two tables subpartitioned by list, one of which has a subpartition with the same name but a different values list as a subpartition in the other. There is no SQL ALTER statement to change the list values of a list subpartition.

Cause: DBMS_METADATA_DIFF was comparing two indexes with different values of key compression. There is no SQL ALTER statement to change index key compression.

Cause: DBMS_METADATA_DIFF was comparing two indexes of different types, for example, a table index, a domain index, a cluster index, a bitmap index or a bitmap join index There is no SQL ALTER statement to change the type of an index.

Cause: DBMS_METADATA_DIFF was comparing two indexes with different column lists. There is no SQL ALTER statement to change the columns of an index.

Cause: DBMS_METADATA_DIFF was comparing two table indexes defined on different tables. There is no SQL ALTER statement to change the base table of an index.

Cause: DBMS_METADATA_DIFF was comparing two locally partitioned indexes with different partitions or subpartitions. There is no SQL ALTER statement to add or drop a partition or subpartition of a locally partitioned index.

Cause: DBMS_METADATA_DIFF was comparing two globally partitioned indexes and a partition in the first index does not exist in the second index. There is no SQL ALTER statement to drop a partition of a globally partitioned index.

Cause: DBMS_METADATA_DIFF was comparing two indexes with different values for the specified storage option. There is no SQL ALTER statement to change this storage option.

Cause: DBMS_METADATA_DIFF was comparing two bitmap join indexes with different join tables. There is no SQL ALTER statement to alter the join tables of a bitmap join index.

Cause: DBMS_METADATA_DIFF was comparing two bitmap join indexes with different join conditions. There is no SQL ALTER statement to alter the join condition of a bitmap join index.

Cause: DBMS_METADATA_DIFF was comparing two bitmap domain indexes with different indextypes. There is no SQL ALTER statement to alter the indextype of a domain index.

Cause: DBMS_METADATA_DIFF was comparing two cluster indexes defined on different clusters. There is no SQL ALTER statement to change the base cluster of a cluster index.

Cause: DBMS_METADATA_DIFF was comparing two indexes with incompatible partitioning: (1) one is partitioned and one is not (2) both are partitioned but in different ways (locally vs. globally, hash vs. range) (3) both are partitioned but on different columns. There is no SQL ALTER statement to change the way an index is partitioned.

Cause: DBMS_METADATA_DIFF was comparing two materialized views with incompatible attributes. There is no SQL ALTER statement to change this attribute of a materialized view.

Cause: DBMS_METADATA_DIFF was comparing two materialized views with incompatible partitioning: (1) one is partitioned and one is not (2) both are partitioned but in different ways (locally vs. globally, hash vs. range) (3) both are partitioned but on different columns. There is no SQL ALTER statement to change the way a materialized view is partitioned.

Cause: DBMS_METADATA_DIFF was comparing two materialized views with different physical organizations: heap, index organized, etc. There is no SQL ALTER statement to change the index organization of a materialized view.

Cause: DBMS_METADATA_DIFF was comparing two materialized view logs with incompatible partitioning: (1) one is partitioned and one is not (2) both are partitioned but in different ways (locally vs. globally, hash vs. range) (3) both are partitioned but on different columns. There is no SQL ALTER statement to change the way a materialized view log is partitioned.

Cause: DBMS_METADATA_DIFF was comparing two materialized view logs that are recording different values, and the set of values in the first materialized view log cannot be changed to that in the second materialized view log. The error message identifies the specific problem.

Cause: DBMS_METADATA_DIFF was comparing two materialized view logs which have different tablespaces. There is no SQL ALTER statement to change the tablespace of a materialized view log.

Cause: DBMS_METADATA_DIFF was comparing two advanced queues with attribute differences that cannot be reconciled. The error message identifies the specific problem.

Cause: DBMS_METADATA_DIFF was comparing two AQ queue tabless with attribute differences that cannot be reconciled. The error message identifies the specific problem.

Cause: DBMS_METADATA_DIFF was comparing two sequences with attribute differences that cannot be reconciled. The error message identifies the specific problem.

Cause: DBMS_METADATA_DIFF was comparing two triggers with differences that cannot be reconciled. The error message identifies the specific problem.

Cause: DBMS_METADATA_DIFF was comparing two types with differences that cannot be reconciled. The error message identifies the specific problem.

Cause: DBMS_METADATA_DIFF was comparing two views with differences that cannot be reconciled. The error message identifies the specific problem.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one bigfile, one smallfile. There is no SQL ALTER statement to change a tablespace from smallfile to bigfile or vice versa.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces of different types: permanent, temporary or undo. There is no SQL ALTER statement to change the type of a tablespace.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different blocksizes. There is no SQL ALTER statement to change the blocksize of a tablespace.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one encrypted, one not. There is no SQL ALTER statement to change the encryption property of a tablespace.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one in flashback mode, one not. There is no SQL ALTER statement to alter the flashback mode of a tablespace.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different extent management properties. There is no SQL ALTER statement to alter the extent management properties of a tablespace.

Cause: DBMS_METADATA_DIFF was comparing two permanent or undo tablespaces. The first data file in the first tablespace is missing from the second tablespace. There is no SQL ALTER statement to drop the first data file from a permanent or undo tablespace.

Cause: DBMS_METADATA_DIFF was comparing two smallfile tablespaces. A data file in the first tablespace is of a different size from the corresponding data file in the second tablespace. There is no SQL ALTER statement to resize a data file in a smallfile tablespace.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different segment space management. There is no SQL ALTER statement to change the segment space management of a tablespace.

Cause: DBMS_METADATA_DIFF was comparing two users with different names. There is no SQL ALTER statement to change the name of a user.

Cause: DBMS_METADATA_DIFF was comparing two users and the first user had an expired password. There is no SQL ALTER statement to undo the expiration of a user password.

Cause: The column names of the table being imported did not match the column names of the preexisting table.

Cause: Altered column was referenced in a virtual column or functional index expression. There is no SQL ALTER statement to change a column which is referenced in one of these types of expressions.

Cause: The source database was at a different time zone version than the target database and there were tables in the dumpfile with TIMESTAMP WITH TIME ZONE columns.

Cause: A dump file was specified for an import operation that had been created with external tables using the ORACLE_DATAPUMP access driver. This type of dump file cannot be processed using the Data Pump import utility.

Cause: A dump file was specified for a load operation that had been created using the Data Pump. This type of dump file cannot be processed by external tables using the ORACLE_DATAPUMP access driver.

Cause: An object was already in existence that uses a name in common with this table. The name collision could be the table name, a constraint, a LOB storage table, or something else in the table definition.

Cause: An unusable index existed on the table. This index prevented data from being loaded into the table associated with this index.

Cause: No encryption was specified for an export job that involved data from an Oracle Database Vault realm.

Cause: The encryption password provided to the Data Pump job was invalid because its length was greater than the maximum allowed. When using the password to encrypt the dump file set, the maximum length is 1000 bytes. When using the password to re-encrypt encrypted columns only, the maximum length is 30 bytes.

Cause: An attempt was made to run an Oracle Data Pump job with the TRANSPORTABLE=ALWAYS parameter. Tablespaces that contain data for EARLY_OPTIONS in an Oracle Data Pump job run with FULL=Y and TRANSPORTABLE=ALWAYS parameter need to be locally managed.

Cause: The security module wallet was not open on the remote node.

Cause: The source database is at a different time zone version than the target database and this table contains TIMESTAMP WITH TIME ZONE data.

Cause: Oracle Data Pump encountered an object type that it currently does not support.

Cause: An attempt was made to convert an existing column into an identity column. There is no SQL ALTER statement that will convert an existing column into an identity column.

Cause: Oracle Data Pump encountered an internal tagged object that failed to import properly. All other objects with the same tag will be skipped.

Cause: The object type could not be created. Examine the original error code to determine the actual cause.

Cause: Oracle Data Pump displayed this message at the start of the import operation because it determined that the character set or the NCHAR character set used by the export database was different from that of the target database and also that the target database character set was not a superset of the export database character set.

Cause: Oracle Data Pump import converted a metadata object from the export database character set into the target database character set prior to processing the object. Some characters could not be converted to the target database character set and so the default replacement character was used.

Cause: The row contained characters that did not exist in the destination character set.

Cause: The number of TRANSPORT_DATAFILES specified on the impdp command was not correct.

Cause: This table contains TIMESTAMP WITH TIME ZONE data and Oracle Data Pump needed to load the source version of the time zone file. This version cannot be located.

Cause: The Oracle Data Pump client was attached to the root or seed container database.

Cause: The Oracle Data Pump export job version was newer than the target compatibility version.

Cause: The time zone version of the source database is not the same as the time zone version of the target database.

Cause: The time zone of the source database is different than the time zone of the target database and this table contains TIMESTAMP WITH LOCAL TIME ZONE data.

Cause: The time zone of the source database is different than the time zone of the target database.

Cause: Trying to apply each version of the type during import resulted in compilation warnings. The type was successfully recreated to the latest version only.

Cause: The encryption password provided to the Oracle Data Pump job was invalid because its length was greater than the maximum allowed. When using the password to encrypt the dump file set, the maximum length is 128 bytes. When using the password to re-encrypt encrypted columns only, the maximum length is 30 bytes.

Cause: Examine the original error code to determine the actual cause.

Cause: Importing statistics requires that the Oracle Data Pump load the source version of the time zone file. This version cannot be located.

Cause: DBMS_METADATA_DIFF was comparing two partitioned tables. There is no SQL ALTER statement to change varray column properties.

Cause: The corrupted data blocks were ignored when Oracle Data Pump was exporting the table.

Cause: The remap value provided to the Oracle Data Pump job was invalid because its length was greater than the maximum allowed.

Cause: The 'remap_table' value specified a partition but the tables were not being departitioned.

Cause: The Oracle Data Pump job was exporting from a database version that has support for long identifiers and may have objects with long identifiers but the target version does not support long identifiers.

Cause: This object had long identifiers and could not be exported to the target version specified in the Oracle Data Pump command.

Cause: The statistics failed to export.

Cause: The statistics failed to import.

Cause: Optional data validation detected invalid data while accessing external table data.

Cause: Altering the table to read-only failed.

Cause: The mode used for import cannot be used with the underscore parameter.

Cause: The table was created with NO LOGGING specified and the restore to the original value failed.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces. There is no SQL ALTER statement to change tablespace lost write protection.

Cause: DBMS_METADATA_DIFF was comparing two tablespaces. Datafile can not be added to a bigfile tablespace.

Cause: This is an internal error. The identified package left some cursors opened.

Cause: The maximum number of replacement characters for each read operation prevented all objects within this object type that lost data from being found. There should be one or more messages preceding this one that indicate data loss for specific objects within the named object type. However, this message indicates that there may be more objects within the named object type that lost

Cause: Oracle Data Pump displayed this message while importing users because it determined that a user was created with a password version that is no longer supported. See the documentation for PASSWORD_VERSIONS in the system view DBA_USERS for more information.

Cause: The Data Pump export job had an unreported problem while exporting the data for this table, partition, or subpartition.

Cause: Data pump import operation was trying to load table data into a sharded table from the sharded catalog database. Table data for sharded tables must be loaded into the sharded databases.

Cause: Data pump import operation was trying to load metadata into a sharded database.

Cause: An attempt was made to export from a sharded database using transportable tablespace.

Cause: An attempt was made to export from a sharded catalog using a form of transportable Data Pump.

Cause: An attempt was made to perform an Oracle Data Pump operation over a network link with either the source or target database being sharded.

Cause: The value of the MAX_DATAPUMP_JOBS_PER_PDB initialization parameter exceeded the allowed value.

Cause: The Data Pump filter contained an object name that was larger than 128 characters.

Cause: Direct path operations could not be performed on a sharded table from inside of the catalog database for a sharded table. The data for sharded tables lives in other shard databases.

Cause: An attempt was made to change a column that was vector encoded with a SQL ALTER statement.

Cause: During Data Pump Export or Import, fixed user or shared database link objects were exported and the enforcement of dictionary credentials was set to ENABLED.

Cause: The encryption password was not specified for an export job that used the transportable option and included one or more encrypted tablespaces.

Cause: The Data Pump dump file was created using a value of TEST_MODE for the export TTS_CLOSURE_CHECK parameter. The Data Pump dump file was in an inconsistent state and could not be loaded.

Cause: This is an informational message to indicate that the Data Pump dump file was created using a value of TEST_MODE for the export TTS_CLOSURE_CHECK parameter. The Data Pump dump file was in an inconsistent state and could not be processed by the Data Pump import utility.

Cause: The string supplied for the parameter MAX_DATAPUMP_JOBS_PER_PDB or MAX_DATAPUMP_PARALLEL_PER_JOB was neither an integer nor was it the special value AUTO.

Cause: The name and location of the Data Pump log or SQL file matched the name of an existing Data Pump, external table, or legacy dump file. This message may be seen before the Data Pump job has started or after the job has started, if wildcard dump files are being used.

Cause: An object type in a transportable tablespace set already existed on the target system, but with a different typeid. The typeid could not be changed because either the type or a dependent type was used by an existing table. Tables in the transportable tablespace set that use this object could not be created. Further information can be found in the alert log.

Cause: The source database was at a different time zone version than the target database and there were tables that contained TIMESTAMP WITH TIME ZONE (TSTZ) data.

Cause: A mode other than transportable, table, or tablepsace was specified for the job. When running a Data Pump export or import operation as SYSBACKUP, the mode is limited to transportable, table, and tablespace.

Cause: When using the DEPARTITION transform, REMAP_TABLE should reference a specific table partition. Otherwise the REMAP_TABLE is ignored.

Cause: The instance was unable to obtain the context or information required to notify the CRS framework.

Cause: The instance was unable to communicate with the CRS framework.

Cause: The instance was unable to create an environment context.

Cause: The instance was unable to populate the environment context.

Cause: The instance was unable to find the location of the alert file.

Cause: Unable to perform action on associated CRS resource.

Cause: The Cluster Ready Services (CRS) detected an error during an attempt to start the indicated resource. The instance start operation was terminated. The accompanying messages provide detailed failure information.

Cause: The Cluster Ready Services (CRS) detected an error during an attempt to stop the indicated resource. The instance stop operation was terminated. The accompanying messages provide detailed failure information.

Cause: Attempt to specify queue key columns that don't form a suffix of the cluster key.

Cause: Missing hash key in the cluster key specification.

Cause: A normal database open was attempted, but the database has not been upgraded to the current server version.

Cause: The database was mounted for SHARED cluster access.

Cause: An upgrade, downgrade, reload, or patch script was invoked when the database was not open for UPGRADE or DOWNGRADE.

Cause: An upgrade, downgrade, reload, or patch script was invoked, but the database instance version was not the version for which the script was intended.

Cause: An attempt was made to modify an entry in the component registry, but the session user was not authorized; only the CONTROL or SCHEMA user for the component are authorized to modify the component registry entry.

Cause: No entry in the component registry was found for the specfied component.

Cause: The schema name specified was not found in the database.

Cause: A downgrade was attempted, but the compatible initialization parameter value was greater than the downgrade release version.

Cause: The component was not a component for the specified namespace.

Cause: One or more components did not have a status of DOWNGRADED.

Cause: An attempt was made to connect to a database when the database was open for upgrade or downgrade, but a conflicting type of connection was specified. Only the SYSDBA and SYSOPER types of administrative connection are allowed while the database is open in upgrade or downgrade mode.

Cause: A Critical Patch Update (CPU) script was invoked that had a number that was less than the last CPU installed in the database.

Cause: An attempt was made to open a Standard Edition or Enterprise Edition database with the Express Edition of the server.

Cause: A normal database open was attempted, but the upgrade script utlmmig.sql failed to complete.

Cause: A normal database open was attempted, but the downgrade script UTLMMIGDOWN.SQL failed to complete.

Cause: An unsupported add/drop column operation for compressed table was attemped.

Cause: An add/drop column operation for compressed table has been performed on the database. This requires COMPATIBLE to be set to 10.0.0.0.0 or higher during upgrade from 9.2 to a 10i or higher release.

Cause: An attempt was made to partition both sides of PARTITIONED OUTER JOIN.

Cause: An attempt was made to specify redundant columns in partitioning and join columns for NATURAL or named column PARTITIONED OUTER JOIN.

Cause: An attempt was made to use subquery in PARTITIONED OUTER JOIN condition.

Cause: An attempt was made to use FULL PARTITIONED OUTER JOIN.

Cause: An attempt was made to use a PARTITIONED OUTER JOIN where the right side is a lateral view with a left correlation to the left side and is partitioned.

Cause: An attempt was made to load a stream that was previously loaded but has not been reset yet.

Cause: An attempt was made to load a stream out of conversion order.

Cause: An attempt was made to reset a stream that contains converted column array data and hasn't been completely loaded yet.

Cause: A direct path operation was attempted using a stream that was not created in the specfied direct path context.

Cause: The stream was completely loaded, but has not been reset yet.

Cause: A stream must be loaded and reset before used again in a column-array-to-stream conversion. This error is issued if another stream has subsequently been converted before the specified stream has been loaded, or if the latest load of this stream returned OCI_ERROR.

Cause: A direct path finish was attempted when at least one stream buffer has not been completely loaded.

Cause: Attempt to create multiple top level column arrays in a direct path context, when only one is allowed.

Cause: Part of a row has been loaded, but it is not complete.

Cause: An attempt was made to free a stream handle after conversion but before the stream was loaded.

Cause: An attempt was made to reset a column array when a row conversion is still in progress.

Cause: An unexpected error occured while attempting to parse the metadata // stream for a table being loaded.

Cause: An unexpected error occured while parsing the metadata stream.

Cause: An attempt was made to commit a Direct Path context after a fatal error.

Cause: A fatal error was detected loading the specified or previous table.

Cause: An attempt was made to save data when loading lob columns or columns stored as lobs (such as varrays and xml types).

Cause: An attempt was made to load lob columns using the attribute OCI_ATTR_DIRPATH_PARALLEL. This error will also be issued when loading any columns that are stored as lobs (such as varrays and xml types).

Cause: Unable to import table data using the specified type. The type was nonexistent in the database or the input type could not be converted to the existing type. The reasons why a conversion was not possible are: 1. The version of the type in the database was greater than the version of the type at export time because 1 or more attributes have been added or dropped from the type. 2. If the type existed in the database prior to the import operation, then its internal identifier may not match the internal identifier of the type from the export database. The identifiers must match for an import to succeed.

Cause: The specified direct path context was aborted or finished.

Cause: Attempt to load a stream in one context after another loading the same table has ended.

Cause: Direct path prepare called after a context loading the same table has ended.

Cause: Direct path operations were not performed in the transaction started by the first OCIDirPathPrepare call.

Cause: Another direct path operation was active.

Cause: The passed SQL expression returned a user-defined ADT which was not supported.

Cause: External tables could not import into a table with mismatched columns.

Cause: Subtype specified was not instantiable.

Cause: Subtype specified was not unique.

Cause: Subtype specified was not a valid type for the column being loaded.

Cause: Attribute specified multiple times.

Cause: Attribute was not included in the subtype indicated.

Cause: Attribute specified was not included in any subtypes specified for the column or the declared subtype of the column.

Cause: The attribute was defined in multiple lines of descent in the hierarchy being loaded.

Cause: None of the attributes loaded were included in the type shown.

Cause: The subtype index was not the first attribute when describing the atributes of an object column or object table with multiple subtypes.

Cause: This column was not part of the current subtype being loaded for this object column or table. Therefore, its entry must be null in the column array.

Cause: The subtype index value in the column array was not valid for the object column or object table.

Cause: The specified row offset was too large for the column array.

Cause: The specified column index was too large for the column array.

Cause: Direct Path API support for loading multiple subtypes of an object table or column was only present in the Oracle 11 release and higher.

Cause: Subtype specified was not the declared type nor was it derived from the declared type.

Cause: The ADT column reported in the error specified a SQL expression which returned the ADT. This is not supported.

Cause: Data saves (and the sqlldr ROWS parameter) are not allowed when loading both the parent and child tables of a partitioning referential constraint.

Cause: An error occurred while loading the child and parent table of a partitioning referential constraint. The load was aborted to ensure the partitioning referential constraint was not violated.

Cause: A parallel load was requested when loading the child and parent of a partitioning referential constraint. This is not allowed.

Cause: While loading the child table of a partitioning referential constraint, the parent table must be locked in SHARE mode.

Cause: An attempt was made to partially save data when loading both the child and parent of a partitioning referential constraint or when loading a table with a domain index.

Cause: The SINGLEROW option was not specified when loading both the parent and child table of a partitioning referential constraint.

Cause: Data saves (and the sqlldr ROWS parameter) could not be allowed when loading a table with domain indexes.

Cause: Data saves (and the sqlldr ROWS parameter) could not be allowed when loading with the NO_INDEX_ERRORS option.

Cause: An error occurred on the index; error follows.

Cause: An error occurred on the index; error follows.

Cause: A logical index error occurred on a partitioned index which affected one or more index partitions, which are listed below this message.

Cause: The SKIP_INDEX_MAINTENANCE option was used with the NO_INDEX_ERRORS option.

Cause: An attempt was made to use Direct Path API Unload to unload an external table.

Cause: An attempt was made to use Direct Path API Unload to unload a table with encrypted columns.

Cause: Index was unusable at the start of the load and it was requested that unusable indexes be skipped.

Cause: Index was unusable at the start of the load and it was requested that unusable indexes be skipped.

Cause: An attempt was made to set the OCI_ATTR_DIRPATH_NO_INDEX_ERRORS attribute to TRUE in a direct path parallel load.

Cause: A zero length piece was detected for a LONG column.

Cause: An attempt was made to load a columnar table with a domain index using SQL*Loader direct part load

Cause: All previous direct path contexts ended and the current transaction was ready for a commit or abort of those changes.

Cause: The attribute OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS was set for a nonload operation.

Cause: There was no active transaction to use.

Cause: An attempt was made to load a view or synonym which has more than a single dependency.

Cause: A synonym or view could not be translated.

Cause: An attempt was made to load a PL/SQL function with the direct path API.

Cause: The index used for the constraint was set as unusable.

Cause: An attempt was made to load a columnar table with a function-based index using SQL*Loader direct path load.

Cause: XML parser returned an error while trying to parse the document.

Cause: Object being loaded did not resolve to a table.

Cause: Direct path unload was attempted on a table with columns that have default values.

Cause: A direct path parallel load was attempted on a temporary table.

Cause: An attempt was made to specify a remote table in a direct path API load or unload.

Cause: A direct path load ran out of process memory when loading multiple partitions.

Cause: The data cartridge encountered an unexpected condition.

Cause: Direct path loading could not support loading the default value for the data type of the indicated column.

Cause: An attempt was made to load a specific partition of a table that was interval subpartitioned. This is not supported by the Direct Path API.

Cause: An attempt was made to allocate a default expression cache that was too large.

Cause: A dump file data stream format error was detected during a load operation.

Cause: A dump file data stream format error was detected during a load operation. An attempt was made to continue the load from a point beyond the corruption.

Cause: A dump file data stream format error was detected during a a load operation. The operation was aborted.

Cause: The data cartridge encountered an unexpected condition.

Cause: A dump file data stream format or initialization error was detected during a load or import operation.

Cause: A dump file data stream format error was detected during a load operation. An attempt was made to continue the load from a point beyond the corruption.

Cause: The specified number format for the column was not valid.

Cause: This message reports the filename for details of another message.

Cause: The ALTER PLUGGABLE DATABASE OPEN RESETLOGS command was issued, but the Pluggable Database was not flashed back or point-in-time recovered.

Cause: An earlier Pluggable Database flashback or point-in-time recovery failed.

Cause: A missing data file was added on a standby database in response to a Pluggable Database (PDB) OPEN RESETLOGS command on the primary database. This data file must be restored and renamed on the standby database before standby database recovery can be restarted.

Cause: An attempt was made to perform a FLASHBACK DATABASE beyond a Pluggable Database resetlogs system change number (SCN).

Cause: An attempt was made to perform a FLASHBACK DATABASE beyond a Pluggable Database (PDB) resetlogs performed at 12.1 compatibility. Futhermore, the PDB resetlogs was performed after a flashback or point-in-time recovery (PITR) of the PDB to its parent database incarnation. This is not supported unless all data files in the PDB are offline.

Cause: The specified clean PDB restore point was on an orphan incarnation of the pluggable database. One cannot flashback a pluggable database to an orphan incarnation.

Cause: A command was attempted that requires the container database (CDB) to be open in read/write mode.

Cause: An earlier ALTER PLUGGABLE DATABASE OPEN RESETLOGS command failed after it made some changes.

Cause: The data file was in the middle of a Pluggable Database resetlogs operation.

Cause: This error provides additional information for error 39874.

Cause: The Pluggable Database was recovered into an orphan branch.

Cause: The data file is in the middle of a Pluggable Database (PDB) resetlogs operation.

Cause: The data file mentioned was in the middle of a Pluggable Database (PDB) resetlogs operation.

Cause: The ONLINE or OFFLINE keyword was not specified after the ALL keyword.

Cause: Multiple Pluggable Database names were specified for the ALTER PLUGGABLE DATABASE OPEN RESETLOGS command.