ORA-39028: cannot restart job from string state

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.

Action: Recreate the job.

ORA-39027: wrong version of master table

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-39026: master table is inconsistent on validation string

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-39025: jobs of type string are not restartable

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-39024: wrong schema specified for 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-39023: Version string is not supported.

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-39022: Database version string is not supported.

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-39021: Database compatibility version string is not supported.

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-39020: invalid mode type string

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-39019: invalid operation type string

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-39018: master process received invalid message number string

ORA-39018: master process received invalid message number string

Cause: Internal Error

Action: Contact Oracle Customer Support.

ORA-39017: Worker request not supported when job is in string 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-39016: Operation not supported when job is in string state.

ORA-39016: Operation not supported when job is in string 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-39015: job is not running

ORA-39015: job is not running

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

Action: Retry the API. If problem persists, contact Oracle Customer Support.

ORA-39014: One or more workers have prematurely exited.

ORA-39014: One or more workers have prematurely exited.

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

Action: Rerun the job. If problem persists, contact Oracle Customer Support.

ORA-39012: Client detached before the job started.

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-39006: internal error

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-39005: inconsistent arguments

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-39004: invalid state

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-39003: unable to get count of total workers alive

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-39002: invalid operation

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-39001: invalid argument value

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-39000: bad dump file specification

ORA-39000: bad dump file specification

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-38959: Failed to update block 0 to new version 10 format

ORA-38959: Failed to update block 0 to new version 10 format

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

Action: check additional error messages and contact Oracle Support Services.

ORA-38958: Source platform string is in different byte order than target platform string

ORA-38958: Source platform string is in different byte order than target platform string

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

Action: Use RMAN CONVERT functionality to convert endian ordering.

ORA-38957: Target database not 10.0.0.0 compatible

ORA-38957: Target database not 10.0.0.0 compatible

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

Action: Use the compatible parameter to advance source database compatibility

ORA-38956: Target platform string not cross platform compliant

ORA-38956: Target platform string not cross platform compliant

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

Action: For a list of supported platforms, query fixed view SYS.V$TRANSPORTABLE_PLATFORM.

ORA-38955: Source platform string not cross platform compliant

ORA-38955: Source platform string not cross platform compliant

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

Action: For a list of supported platforms, query fixed view SYS.V$TRANSPORTABLE_PLATFORM.

ORA-38954: Cross platform transport is not supported between source platform identifier string and target platform identifier string

ORA-38954: Cross platform transport is not supported between source platform identifier string and target platform identifier string

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

Action: For a list of supported platforms, query fixed view SYS.V$TRANSPORTABLE_PLATFORM. If both platforms are present, Contact Oracle support

ORA-38952: Source database not 10.0.0.0 compatible

ORA-38952: Source database not 10.0.0.0 compatible

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

Action: Use the compatible parameter to advance source database compatibility and redo the transport

ORA-38951: Target platform string not cross platform compliant

ORA-38951: Target platform string not cross platform compliant

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

Action: none

ORA-38950: Source platform string not cross platform compliant

ORA-38950: Source platform string not cross platform compliant

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

Action: For a list of supported platforms, query fixed view SYS.V$TRANSPORTABLE_PLATFORM.

ORA-38908: internal error occurred during DML Error Logging

ORA-38908: internal error occurred during DML Error Logging

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

Action: Report this error to Oracle Support.

ORA-38907: DML error logging is not supported for FILE column string

ORA-38907: DML error logging is not supported for FILE column string

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.

Action: Either don t use DML Error Logging on such table or remove the offending column from the error logging table. The scalar columns can be logged, but not BFILE column types.

ORA-38906: insert into DML Error Logging table string failed

ORA-38906: insert into DML Error Logging table string failed

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).

Action: Determine root cause of error (in error stack).

ORA-38905: DML error logging is not supported for LONG column string

ORA-38905: DML error logging is not supported for LONG column string

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.

Action: Either do not use DML Error Logging on such a table or remove the offending column from the error logging table. The scalar columns can be logged, but not long column types.

ORA-38904: DML error logging is not supported for LOB column string

ORA-38904: DML error logging is not supported for LOB column string

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.

Action: Either do not use DML Error Logging on such table or remove the offending column from the error logging table. The scalar columns can be logged, but not LOB column types.

ORA-38903: DML error logging is not supported for abstract column string

ORA-38903: DML error logging is not supported for abstract column string

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.

Action: Either do not use DML Error Logging on such a table or remove the offending column from the error logging table. The scalar columns can be logged, but not abstract column types.

ORA-38902: errors in array insert exceed string

ORA-38902: errors in array insert exceed string

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

Action: Do not use BATCH ERROR mode when array INSERT has more error rows than the number specified in the error.

ORA-38901: column string of table string must be one of the first number columns

ORA-38901: column string of table string must be one of the first number columns

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

Action: Create the error logging table correctly. Consult ORACLE documentation for the correct format of an error logging table.

ORA-38900: missing mandatory column string of error log table string

ORA-38900: missing mandatory column string of error log table string

Cause: Mandatory column of error logging table is not present

Action: Add the named column to the error logging table. Consult ORACLE documentation for the correct data type.

ORA-38862: FLASHBACK DATABASE in progress

ORA-38862: FLASHBACK DATABASE in progress

Cause: The operation could not be performed while FLASHBACK DATABASE was in progress.

Action: Wait for the FLASHBACK DATABASE to complete.

ORA-38861: flashback recovery stopped before reaching recovery target

ORA-38861: flashback recovery stopped before reaching recovery target

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.

Action: Flashback to an older SCN or acquire the necessary redo logs.

ORA-38860: cannot FLASHBACK DATABASE during instantiation of a logical standby

ORA-38860: cannot FLASHBACK DATABASE during instantiation of a logical standby

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.

Action: If in the process of creating a logical standby database, perform the remaining instantiation procedures to completion. If this flashback operation followed a Data Guard failure, permit the errant Data Guard operation to successfully complete. Once the instantiation is complete, reissue the flashback operation.

ORA-38859: instance string (thread string) is not ready to be disabled

ORA-38859: instance string (thread string) is not ready to be disabled

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.

Action: Wait a few minutes and retry.

ORA-38858: cannot mark redo thread string as enabled

ORA-38858: cannot mark redo thread string as enabled

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.

Action: Recreate the control file with a larger MAXINSTANCES value.

ORA-38857: cannot mark redo thread string as enabled

ORA-38857: cannot mark redo thread string as 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.

Action: Recreate the control file with a larger MAXINSTANCES value.

ORA-38856: cannot mark instance string (redo thread string) as enabled

ORA-38856: cannot mark instance string (redo thread string) as 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.

Action: Add more logfiles to the specified instance and retry the command.

ORA-38855: cannot mark instance string (redo thread string) as enabled

ORA-38855: cannot mark instance string (redo thread string) as enabled

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.

Action: Add more logfiles to the specified instance and retry the command.

ORA-38854: cannot mark instance string (redo thread string) as disabled

ORA-38854: cannot mark instance string (redo thread string) as 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.

Action: Shut down the specified instance and retry this command.

ORA-38853: cannot mark instance string (redo thread string) as disabled

ORA-38853: cannot mark instance string (redo thread string) as disabled

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.

Action: Shut down the specified instance and retry this command.

ORA-38852: cannot mark the current instance (redo thread) as disabled

ORA-38852: cannot 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.

Action: Shut down this instance and start up using a different instance name or redo thread number and retry.

ORA-38851: cannot mark the current instance (redo thread) as disabled

ORA-38851: cannot mark the current instance (redo thread) as disabled

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

Action: Shut down this instance and start up using a different instance name or redo thread number and retry.

ORA-38850: an enabled thread missing from control file

ORA-38850: an enabled thread missing from control file

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

Action: Reissue the CREATE CONTROLFILE statement, including all enabled threads.

ORA-38798: Cannot perform partial database recovery

ORA-38798: Cannot perform partial database recovery

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

Action: See other other messages on error stack for the action.

ORA-38797: Full database recovery required after a database has been flashed back

ORA-38797: Full database recovery required after a database has been flashed back

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.

Action: Recover the whole database instead.

ORA-38796: Not enough flashback database log data to undo FLASHBACK.

ORA-38796: Not enough flashback database log data to undo FLASHBACK.

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

Action: It is still possible to get to the restore target by doing a flashback until the resetlogs branch point of the restore target is reached. This can be done by executing multiple flashback to before resetlogs commands, or by doing a flashback to the exact time or SCN of the desired resetlogs branch point. Note that this flashback cannot be undone should an error occur. The only option is to complete the flashback.

ORA-38795: warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below

ORA-38795: warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below

Cause: Flashback Database ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause is that Flashback Database had to add a file back to the control file but could not restore the file s contents.

Action: If a backup is available, restore the backup, online the file, and recover the database to the original flashback target scn or timestamp. If a backup is not available, but the redo from the file creation to the target scn or timestamp is available, then create the file using the ALTER DATABASE CREATE DATAFILE command, bring the file online, and recover the database to the original flashback target scn or timestamp.

ORA-38794: Flashback target time not in current incarnation

ORA-38794: Flashback target time not in current incarnation

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

Action: Use a different target timestamp or use RMAN to reset the database to the appropriate incarnation.

ORA-38793: cannot FLASHBACK the database to a future SCN or time

ORA-38793: cannot FLASHBACK the database to a future SCN or time

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

Action: If the target SCN or timestamp is in the current incarnation or a child incarnation whose branch point is after the current database SCN then RECOVER DATABASE to the target SCN or time. If the target SCN or timestamp is in a child incarnation whose branch point is prior to the current database SCN then FLASHBACK DATABASE to before the branch point. Next use RMAN to reset the database to the child incarnation. Finally, RECOVER DATABASE to the target SCN or time.