19 ORA-38029 to ORA-39961

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

Action: Unlock statistics with the DBMS_STATS.UNLOCK_TABLE_STATS procedure on base table(s). Retry the operation if it is okay to update statistics.

ORA-38101: Invalid column in the INSERT VALUES Clause: string

Cause: INSERT VALUES clause refers to the destination table columns

Action: none

ORA-38102: Invalid column in the INSERT WHERE Clause: string

Cause: INSERT WHERE clause refers to the destination table columns

Action: none

ORA-38103: Invalid column in the UPDATE SET Clause: string

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

Action: none

ORA-38104: Columns referenced in the ON Clause cannot be updated: string

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

Action: none

ORA-38105: Delete not yet supported when Update row-migration is possible

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

Action: none

ORA-38201: assert if pin during flush

Cause: internal use only

Action: enables checking for bugs in upper layers when there is a pin on a buffer or there are users for buffer and we are trying to flush the object associated with the buffer

ORA-38303: invalid option for PURGE TABLESPACE

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

Action: Place nothing or only USER <user name> after the tablespace name

ORA-38304: missing or invalid user name

Cause: A valid user name was expected.

Action: Specify a valid user name.

ORA-38305: object not in RECYCLE BIN

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

Action: Only the objects in RecycleBin can be Flashback Dropped.

ORA-38306: this object is not recoverable standalone

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

Action: Only tables are recoverable.

ORA-38307: object not in RECYCLE BIN

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

Action: Only the objects in RecycleBin can be PURGEDED.

ORA-38309: object not purgable

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

Action: Cannot purge this object.

ORA-38310: cannot purge tablespace for other users

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

Action: Cannot purge the tablespace for some other user.

ORA-38311: cannot purge objects owned by other users

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

Action: Cannot purge this object.

ORA-38312: original name is used by an existing object

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

Action: use the RENAME clause to recover the object with a different name.

ORA-38401: synonym string not allowed

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

Action: Use the object name instead of the synonym.

ORA-38402: invalid name: empty string or spaces in the name

Cause: There were spaces in the name.

Action: Remove spaces in the name or use quotes around the name.

ORA-38403: attribute set name may not be longer than 22 characters

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

Action: Choose a name that has 22 or fewer characters.

ORA-38404: schema extension not allowed for the attribute set name

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.

Action: Create the attribute set from the appropriate schema.

ORA-38405: quotes not allowed in the attribute set name

Cause: The attribute set name contained quotes.

Action: Remove quotes in the attribute set name.

ORA-38406: attribute set string already exists

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

Action: Drop the existing attribute set or choose a different name.

ORA-38407: The ADT associated with the attribute set already exists.

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

Action: Create the attribute set for the existing ADT or drop the ADT.

ORA-38408: The ADT "string" does not exist in the current schema.

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

Action: Make sure that the ADT with the same name as the attribute set exists in the current schema.

ORA-38409: invalid name or option for the attribute set: string

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

Action: Set serveroutput ON and repeat the operation for additional information.

ORA-38410: schema extension not allowed for the table name

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

Action: The table storing expressions and the corresponding attribute set should be created in the same schema.

ORA-38411: invalid datatype for the column storing expressions

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

Action: Create a VARCHAR2 or CHAR column to store expressions in a table.

ORA-38412: Expression set column string does not exist.

Cause: The column storing expressions does not exist.

Action: Pass a valid name for the column storing expressions.

ORA-38413: elementary attribute name may not be longer than 32 characters

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

Action: Use a shorter name for the elementary attribute.

ORA-38414: invalid datatype for the attribute string

Cause: The datatype specified for the attribute was invalid.

Action: If the datatype is an ADT, make sure that the ADT exists and the current user has execute permissions to it.

ORA-38415: invalid name or datatype for the attribute: string

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

Action: Set serveroutput ON and repeat the operation for additional information.

ORA-38416: A stored attribute may not be longer then 300 characters.

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

Action: A predicate with such attribute may not be indexed. It will be evaluated as sparse predicate.

ORA-38417: attribute set string does not exist

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

Action: Create the attribute set or choose an existing attribute set.

ORA-38418: ADT associated with the attribute set string does not exist

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

Action: Drop the attribute set and recreate it.

ORA-38419: invalid identifier in attribute : string

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

Action: Create all the required elementary attributes and user-defined functions and try again.

ORA-38420: invalid stored attribute sub-expression: string

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

Action: Set serveroutput ON and repeat the operation for additional information.

ORA-38421: attribute string already exists

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

Action: Drop the existing attribute or choose a different name for the new attribute.

ORA-38422: invalid datatype for the attribute: string

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

Action: If the data type of the attribute is an ADT, make sure that the type exists.

ORA-38423: Attribute set created from an ADT may not be extended.

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

Action: Create a new attribute set and add all the required elementary attributes one at a time.

ORA-38424: no attribute set currently assigned to the expression set

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

Action: No action is required.

ORA-38425: attribute set used for an index object may not be unassigned

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.

Action: Drop the index before un-assigning the attribute set.

ORA-38426: attribute set assigned to an expression set may not be dropped

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

Action: Un-assign the attribute set from the expression set before dropping it.

ORA-38427: attribute string does not exist

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

Action: Create the attribute set.

ORA-38428: too many attributes selected for indexing

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

Action: Remove some of the indexed attributes. Make sure that the default indexed attributes associated with the attribute set combined with the indexed attributes specified in the Create Index Parameters clause are less than or equal to 490.

ORA-38429: invalid datatype for a stored attribute: string

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

Action: Choose a stored attribute that has a resulting datatype of NUMBER, VARCHAR2, CHAR or DATE.

ORA-38430: Operation "string" not supported in the current release.

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

Action: Do not use the operation.

ORA-38431: could not evaluate subexpression "string" for rowid "string"

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

Action: Correct the expression.

ORA-38432: EVALUATE operator only allowed on an expression column

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

Action: Assign an attribute set to the column.

ORA-38433: index "string" could not be maintained due to "string"

Cause: The error was caused by the recursive operation.

Action: Fix the error and retry.

ORA-38434: could not evaluate expression "string"

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 expression set already had a list of stored and indexed attributes. Additional attributes cannot be specified in the CREATE INDEX parameters clause.

Action: Remove TOP, STOREATTRS and INDEXATTRS clauses from the parameters clause or clear the expression set statistics using DBMS_EXPFIL.INDEX_PARAMETERS API.

ORA-38500: %s

Cause: There was a generic error

Action: See documentation for further information.

ORA-38501: sub-query not allowed in the expression

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

Action: Do not use sub-queries in the expressions.

ORA-38502: invalid XML tag: string

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

Action: Correct the XML tag and retry.

ORA-38503: index already defined using the parameters

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

Action: Drop the index and retry.

ORA-38504: this operator not allowed with the configured attribute set

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.

Action: Use a different operator binding.

ORA-38601: FI Not enough memory for frequent itemset counting: string

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

Action: In workarea_size_policy='manual' mode, set _fic_area_size to a reasonably larger value. Or, In workarea_size_policy='auto' mode, this error should never happen.

ORA-38602: FI invalid input cursor

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

Action: For transactional input format, specify that the input cursor returns exactly two columns: one for transaction-id, one for item-id. For horizontal input format, make sure the input cursor's columns have the same data types.

ORA-38603: FI including & excluding cursor can only return one column

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

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

Action: Correct the database name spelling or DISMOUNT the mounted database and mount the correct database.

ORA-38726: Flashback database logging is not on.

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

Action: Flashback database logging must be enabled via the ALTER DATABASE FLASHBACK ON command before a FLASHBACK DATABASE command can be tried. If the database must be taken back in time then a restore and incomplete recovery must be performed.

ORA-38727: FLASHBACK DATABASE requires a current control file.

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

Action: FLASHBACK DATABASE cannot be used with a backup control file. If the database must be taken back in time then a restore and an incomplete recovery must be performed.

ORA-38728: Cannot FLASHBACK DATABASE to the future.

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

Action: Supply a proper SCN or time stamp and retry the command.

ORA-38729: Not enough flashback database log data to do FLASHBACK.

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

Action: If the database must be taken back in time then a restore and incomplete recovery must be performed.

ORA-38730: Invalid SCN/TIMESTAMP expression.

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

Action: Retry the command using a valid number or time stamp expression.

ORA-38731: Expected version string does not match string in log header.

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

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38732: Expected file size string does not match string.

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.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38733: Physical size string less than needed string.

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

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38734: Flashback log is inconsistent; belongs to another database.

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

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38735: Wrong log number string in flashback log file header.

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

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38736: Wrong thread number string in flashback log file header.

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

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38737: Expected sequence number string doesn't match string

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

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38738: Flashback log file is not current copy.

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.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38739: Flashback log file is more recent than control file.

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.

Action: FLASHBACK DATABASE can only be used with the current control file. If it is not available, then a restore and an incomplete recovery must be performed instead.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38741: Formatted blocks value string is not valid.

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

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38742: Flashback log file has incorrect log reset status.

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.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38743: Time/SCN is in the future of the database.

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

Action: Retry the command with a correct Time/SCN or RECOVER the database.

ORA-38744: file string is not the same file seen at start of flashback

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.

Action: Investigate why the error occurred. It may be that the flashback database log data is corrupt. If so, a restore and an incomplete recovery must be performed instead.

ORA-38747: corrupt before image (file# string, block# string)

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

Action: The flashback log data is probably corrupt. If so, a restore and an incomplete recovery must be performed instead.

ORA-38748: cannot flashback data file string - file is in use or recovery

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.

Action: Do not do FLASHBACK DATABASE.

ORA-38749: A media recovery has been started.

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

Action: Complete or cancel the first media recovery session.

ORA-38750: FLASHBACK DATABASE may not be performed using a dispatcher.

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

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

Action: Retry the conversation with the appropriate file numbers.

ORA-38753: Cannot flashback data file string; no flashback log data.

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.

Action: The file cannot be flashed back. The file must be taken offline or the tablespace dropped before continuing with the FLASHBACK DATABASE command.

ORA-38754: FLASHBACK DATABASE not started; required redo log is not available

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.

Action: See trace files for details of the problem.

ORA-38755: Flashback is already turned on for this tablespace.

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

Action: No action required.

ORA-38756: Flashback is already turned off for this tablespace.

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

Action: No action required.

ORA-38757: Database must be mounted EXCLUSIVE and not open to FLASHBACK.

Cause: An attempt to Flashback a database was made when the database was not mounted EXCLUSIVE 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.

Action: The file must be taken offline before continuing with the FLASHBACK DATABASE command.

ORA-38759: Database must be mounted EXCLUSIVE and not open.

Cause: An attempt to turn on or off Flashback Database logging was made when the database was open.

Action: Mount the database and retry the command.

ORA-38760: This database instance failed to turn on flashback database

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

Action: Correct the error or turn off database flashback.

ORA-38761: thread string redo log sequence number string could not be accessed

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

Action: Restore the log and retry the FLASHBACK command.

ORA-38762: thread string redo log with scn string could not be found

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

Action: Restore the log and retry the FLASHBACK command.

ORA-38763: flashback not started; enabled threads have changed

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

Action: The flashback cannot be performed. Perform a restore and an incomplete recovery instead.

ORA-38764: flashback not started; datafile string enabled threads are different

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.

Action: The flashback cannot be performed. Perform a restore and an incomplete recovery instead.

ORA-38765: Flashed back database cannot be opened read-only.

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.

Action: If a complete recovery was performed after a database flashback, open the database for read-write access. If a FLASHBACK DATABASE command failed, fix what caused the command to fail and retry the command, or recover and open the database for read-write access.

ORA-38766: cannot flashback data file string; file resized smaller

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

Action: The file cannot be flashed back. The file must be taken offline or the tablespace dropped before continuing with the FLASHBACK DATABASE command.

ORA-38767: flashback retention target parameter mismatch

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

Action: Check DB_FLASHBACK_RETENTION_TARGET values in all instances.

ORA-38768: resizing datafile string failed

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.

Action: Recover the database to return it to its previous state, or fix the cause of the operating system error and retry the Flashback. If that is not possible, then the file can be taken offline and the Flashback command retried. The file will have to be restored from a backup and rolled forward.

ORA-38769: FLASHBACK DATABASE failed after modifying data.

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

Action: Recover the database to return it to its previous state, or fix the cause of the error and retry the Flashback.

ORA-38770: FLASHBACK DATABASE failed during recovery.

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.

Action: Fix the error and then recover the database to the same SCN or timestamp used in the FLASHBACK DATABASE command.

Cause: The recovery step of FLASHBACK DATABASE encountered the creation of a datafile that could not be added to the controlfile. An entry has been added to the controlfile 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.

Action: Rename the file in the controlfile, or use the ALTER ALTER DATABASE CREATE DATAFILE command to create a file suitable for recovery. If the file is not going to be recovered, then take it offline with the FOR DROP option. The recovery step of Flashback can be resumed by entering a RECOVERY command with the same SCN or timestamp as used in the FLASHBACK DATABASE command. For example, RECOVER AUTOMTAIC DATABASE UNTIL CHANGE <flashback-scn>.

ORA-38772: cannot add datafile 'string' - file could not be created

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 controlfile file entry for the file is 'UNNAMEDnnnnn'.

Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file.

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 controlfile file entry for the file is 'UNNAMEDnnnnn'.

Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file with a different name.

Cause: During a database mount, the RVWR process discovered that the flash 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.

Action: Flashback database requires the flash recovery area to be enabled. Either enable the flash recovery area by setting the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE initialization parameters, or turn off flashback database with the ALTER DATABASE FLASHBACK OFF command.

ORA-38777: database must not be started in any other instance.

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

Action: Ensure that the no other instances are started. Then retry the command.

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.

Action: Specify a dump file that is usable for the job.

ORA-39001: invalid argument value

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.

Action: Correct the bad argument and retry the API.

ORA-39002: invalid operation

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.

Action: Modify the API call to be consistent with the current job or redefine the job in a manner that will support the specified API.

ORA-39003: unable to get count of total workers alive

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

Action: Check the additional error messages to see what caused the failure. Correct the error, if possible, and try the operation again. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39004: invalid state

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

Action: Rerun the job to specify the API when the job is an appropriate state.

ORA-39005: inconsistent arguments

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.

Action: Modify the API call to be consistent with itself.

ORA-39006: internal 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.

Action: Contact Oracle Customer Support.

ORA-39012: Client detached before the job started.

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

Action: Create new job and remain attached to the job until it is started.

ORA-39013: All of the workers exited before the job completed.

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

Action: Rerun the job to specify the API when the job is an appropriate state.

ORA-39017: Worker request not supported when job is in string state.

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

Action: Contact Oracle Customer Support.

ORA-39018: master process received invalid message number string

Cause: Internal Error

Action: Contact Oracle Customer Support.

ORA-39019: invalid operation type string

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.

Action: Correct the operation name and recreate the job.

ORA-39020: invalid mode type string

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.

Action: Correct the mode and recreate the job.

ORA-39021: Database compatibility version string is not supported.

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.

Action: Specify a supported version and recreate the job.

ORA-39022: Database version string is not supported.

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.

Action: Specify a supported version and recreate the job.

ORA-39023: Version string is not supported.

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.

Action: Specify a supported version and recreate the job.

ORA-39024: wrong schema specified for job

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

Action: Contact Oracle Customer Support.

ORA-39025: jobs of type string are not restartable

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

Action: Recreate the job via the open API.

ORA-39026: master table is inconsistent on validation string

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.

Action: Recreate the job. If master table has not been modified, but problem persists, contact Oracle Customer Support.

ORA-39027: wrong version of master table

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.

Action: Recreate the job.

ORA-39028: cannot restart job from string state

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

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

Action: User must manually define the object in the target database.

ORA-39059: dump file set is incomplete

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

Action: Check the export log file and make sure all of the files that were exported are included in the current job.

ORA-39060: table(s) dropped because of conflict with master table

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

Action: After the job completes. Import the conflicting tables using a unique job name to avoid conflicts with normal user tables.

ORA-39061: import mode string conflicts with export mode string

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.

Action: Perform the import using a mode compatible with the export.

ORA-39062: error creating master process string

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

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39064: unable to write to the log file

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

Action: Fix the problems outlined in the secondary messages.

ORA-39065: unexpected master process exception in string

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.

Action: If problem persists, contact Oracle Customer Support.

ORA-39067: Unable to close the log file.

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

Action: Fix the problems outlined in the secondary messages.

ORA-39068: invalid master table data in row with PROCESS_ORDER=string

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.

Action: Rerun the job with an uncorrupted master table.

ORA-39070: Unable to open the log file.

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

Action: Fix the problems outlined in the secondary messages.

ORA-39071: Value for string filter is badly formed.

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

Action: Fix the problems outlined in the secondary messages.

ORA-39076: cannot delete job string for user string

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

Action: Eliminate the problems indicated.

ORA-39077: unable to subscribe agent string to queue "string"

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 master process whose name is listed started up but did not finish its initialization within the allowed time limit.

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

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

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

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

Action: A SQL parallel query slave process cannot create a Data Pump master process. This is not supported. If this error occurs from a Data Pump client (for example, expdp or impdp), contact Oracle Customer Support and report the error.

ORA-39105: Master process string failed during startup. Master error:

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

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39106: Worker process string failed during startup. Worker error:

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

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

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

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

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

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39109: Unprivileged users may not operate upon other users' schemas

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.

Action: Retry the operation under a username owning the schema.

ORA-39110: error deleting worker processes

Cause: An attempt to delete the worker processes failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

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

Action: If the object from the dump file is wanted, drop the base and dependent objects and try to import again using desired filters

ORA-39113: Unable to determine database version

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

Action: Make sure access to the DBMS_UTILITY package is granted to you. If this is a network job, be sure that access to the DBMS_UTILITY package is granted to you on the remote instance.

ORA-39114: Dump files are not supported for string jobs

Cause: An attempt was made to add a dumpfile to a job not configured for dumpfiles. Dumpfiles are not allowed in Export ESTIMATE_ONLY jobs or in Import/Sql_file jobs over a network link.

Action: Do not specify a dumpfile for jobs that do not require dumpfiles.

ORA-39115: %s is not supported over a network link

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

Action: Do not attempt to use Data Pump features on network jobs if they are not compatible with jobs over the network.

ORA-39116: invalid trigger operation on mutating table string.string

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

Action: Disable trigger(s) on the specified table. Also see ORA-004091.

ORA-39117: Type needed to create table is not included in this operation. Failing sql is: string

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.

Action: Determine which type(s) are missing and create them on the target system and run the Data Pump import job again.

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.

Action: If problem persists, contact Oracle Customer Support.

ORA-39126: Worker unexpected fatal error in string [string] string

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.

Action: If problem persists, contact Oracle Customer Support.

ORA-39127: unexpected error from call to stringstring

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

Action: Record the accompanying messages and report this as a Data Pump internal error to customer support.

ORA-39128: unexpected DbmsJava error number from statement string

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

Action: Record the accompanying messages and report this as a Data Pump internal error to customer support.

ORA-39129: Object type string not imported. Name conflicts with the master table

Cause: The table being imported from the remote instance 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.

Action: Drop the object type from the target system and retry the operation.

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.

Action: Drop the object type from the target system and retry the operation.

ORA-39134: Cannot include "string" tablespace as a Transportable Tablespace

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.

Action: Specify different tablespaces to be transported.

ORA-39135: SYS schema cannot read data using specific SCNs

Cause: The user was operating under the SYS schema and either explicitly specified an SCN via the FLASHBACK_SCN or FLASHBACK_TIME or TABLE_CONSISTENCY parameters or the job required that a specific SCN be used because of streams or logical replication activity.

Action: Do not perform Data Pump jobs using the SYS schema or 'AS SYSDBA'.

ORA-39136: cannot specify an SCN on a transportable 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.

Action: This is an internal error. Please report it to Oracle support.

ORA-39137: cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata

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.

Action: Change the setting of the TABLE_EXISTS_ACTION parameter to APPEND or TRUNCATE or supply Metadata with the data.

ORA-39138: Insufficient privileges to load data not in your schema

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

Action: Use a privileged account if you must load data not in your schema

ORA-39139: Data Pump does not support XMLSchema objects. string will be skipped.

Cause: Object has XMLSchema-based columns, which are unsupported by Data Pump.

Action: Use the original exp and imp utilities to move this object.

ORA-39140: dump file "string" belongs to job string

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.

Action: Remove the dump file indicated in the message and retry the import operation providing only the complete set of dump files created by a specific export job.

ORA-39141: dump file "string" is a duplicate of dump file "string"

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.

Action: Remove the dump file indicated in the message and retry the import operation providing only the complete set of dump files created by a specific export job.

ORA-39142: incompatible version number string in dump file "string"

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.

Action: Import this dump file using the Data Pump import utility with the same version as the export which created the file.

ORA-39143: dump file "string" may be an original export dump file

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.

Action: Try using the original import utility to process this dump file.

ORA-39144: file name parameter must be specified and non-null

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

Action: Correct the file name parameter and reissue the API request.

ORA-39145: directory object parameter must be specified and non-null

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.

Action: Correct the directory object parameter and retry the operation.

ORA-39146: schema "string" does not exist

Cause: The specified schema was referenced as the source of a REMAP_SCHEMA parameter, but did not exist in the dump file (for

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

Action: None Required. The error is ignored.

ORA-39600: Queue keys needs to be a suffix of cluster key.

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

Action: Only specify queue key columns as a suffix of cluster key.

ORA-39601: Hash key is required.

Cause: Missing hash key in the cluster key specification.

Action: Specify one or more hash key columns.

ORA-39700: database must be opened with UPGRADE option

Cause: The database has not been upgraded, but a standard database open was attempted.

Action: Use the UPGRADE option when opening the database to indicate that the database is being opened for upgrade.

ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE

Cause: The database was mounted for SHARED cluster access.

Action: Set the CLUSTER_DATABASE initialization parameter to FALSE and restart the server with the UPGRADE or DOWNGRADE option.

ORA-39702: database not open for UPGRADE or DOWNGRADE

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

Action: Use STARTUP UPGRADE to open the database for upgrade or to apply a patch set. Use STARTUP DOWNGRADE for running a downgrade script or the reload script.

ORA-39703: server version and script version do not match

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.

Action: Check that the correct ORACLE_HOME and ORACLE_SID environment variables are set. Also check that the SQL script is being invoked from the correct ORACLE_HOME.

ORA-39704: permission to modify component registry entry denied

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.

Action: Connect as either the CONTROL or SCHEMA user for the component.

ORA-39705: component 'string' not found in registry

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

Action: Check the spelling of the component ID and use the DBA_REGISTRY view to list the existing components.

ORA-39706: schema 'string' not found

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

Action: Create the schema before loading the component.

ORA-39707: compatibile parameter string too high for downgrade to string

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

Action: Once the compatible value has been raised, downgrade to earlier releases is not supported.

ORA-39708: component 'string' not a string component

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

Action: Either enter a valid component identifier for the namespace or set the session namespace to the correct component namespace.

ORA-39709: incomplete component downgrade; string downgrade aborted

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

Action: Correct the component problem and re-run the downgrade script.

Action: When adding a column, do not specify a default value. DROP column is only supported in the form of SET UNUSED column (meta-data drop column).

ORA-39727: COMPATIBLE must be set to 10.0.0.0.0 or higher

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.

Action: Set COMPATIBLE to 10.0.0.0.0 and retry the upgrade.

ORA-39751: partitioned table on both sides of PARTITIONED OUTER JOIN is not supported

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

Action: Specify partitioned table on one side of PARTITIONED OUTER JOIN only.

ORA-39752: redundent column in partitioning and join columns is not allowed

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

Action: Do not specify redundent column in partitioning and join columns.

ORA-39753: unsupported use of subquery in PARTITIONED OUTER JOIN condition

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

Action: Remove subquery from the join condition.

ORA-39754: FULL PARTITIONED OUTER JOIN is not supported

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

Action: Specify FULL PARTITIONED OUTER JOIN through UNION of LEFT and RIGHT PARITTION OUTER JOIN.

ORA-39950: invalid parameter for PLSQL warnings flag

Cause: The user either entered invalid value for the PLSQL_WARNINGS flag or the value of the flag conflicts with other values.

Action: Enter correct values for the switch.

ORA-39951: incomplete values specified for PL/SQL warning settings

Cause: The user either did not enter the value for the settings or entered incomplete values.

Action: Enter correct syntax for the switch.

ORA-39952: only numbers can be specified as range values

Cause: The range values did not have numerical values only.

Action: Enter only numerical values.

ORA-39953: the range value specified is beyond allowed range

Cause: The range values were either too low or too high.

Action: Specify only the allowed range values.

ORA-39954: DEFERRED is required for this system parameter

Cause: The ALTER SYSTEM command for PLSQL_WARNINGS did not include the keyword, DEFERRED.