ORA-39096: invalid input value string for parameter string

ORA-39096: invalid input value string for parameter string

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

Action: Correct the input value and try the call again.

ORA-39095: Dump file space has been exhausted: Unable to allocate string bytes

ORA-39095: Dump file space has been exhausted: Unable to allocate string bytes

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

Action: Reattach to the job and add additional dump files to the job restarting the job.

ORA-39094: Parallel execution not supported in this database edition.

ORA-39094: Parallel execution not supported in this database edition.

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

Action: Specify a parallelism of 1 for jobs not running on Enterprise Edition databases.

ORA-39093: FLASHBACK automatically enabled to preserve database integrity.

ORA-39093: FLASHBACK automatically enabled to preserve database integrity.

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.

Action: None

ORA-39092: unable to set SCN metadata for object string.string of type string

ORA-39092: unable to set SCN metadata for object string.string of type string

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

Action: The subsequent message describes the error that was detected. Correct the specified problem and restart the job.

ORA-39091: unable to determine logical standby and streams status

ORA-39091: unable to determine logical standby and streams status

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

Action: The subsequent message describes the error that was detected. Correct the specified problem and restart the job.

ORA-39090: Cannot add devices to file oriented job.

ORA-39090: Cannot add devices to file oriented job.

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

Action: Only specify one file for jobs that contain sequential devices.

ORA-39088: file name cannot contain a path specification

ORA-39088: file name cannot contain a path specification

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

Action: Use the name of a directory object to indicate where the file should be stored.

ORA-39087: directory name string is invalid

ORA-39087: directory name string is invalid

Cause: A corresponding directory object does not exist.

Action: Correct the directory object parameter, or create a corresponding directory object with the CREATE DIRECTORY command.

ORA-39086: cannot retrieve job information

ORA-39086: cannot retrieve job information

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

Action: Eliminate the problems indicated by the secondary errors.

ORA-39085: cannot update job string for user string

ORA-39085: cannot update job string for user string

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

Action: Eliminate the problems indicated.

ORA-39084: cannot detach job string for user string

ORA-39084: cannot detach job string for user string

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

Action: Eliminate the problems indicated.

ORA-39083: Object type string failed to create with error: string Failing sql is: string

ORA-39083: Object type string failed to create with error: string Failing sql is: string

Cause: Examine original error code to determine actual cause

Action: Original error code will contain more information

ORA-39082: Object type string created with compilation warnings

ORA-39082: Object type string created with compilation warnings

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.

Action: This is a warning. The object may have to be recompiled before being used.

ORA-39081: failed to unsubscribe agent string from queue string

ORA-39081: failed to unsubscribe agent string from queue string

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.

Action: Fix the problem if possible, or contact Oracle Customer Support.

ORA-39080: failed to create queues string and string for Data Pump job

ORA-39080: failed to create queues string and string for Data Pump job

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.

Action: Fix the problem if possible, or contact Oracle Support.

ORA-39079: unable to enqueue message string

ORA-39079: unable to enqueue message string

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.

Action: Fix the problem if possible, or contact Oracle Customer Support.

ORA-39078: unable to dequeue message for agent string from queue string

ORA-39078: unable to dequeue message for agent string from queue string

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.

Action: Fix the problem if possible, or contact Oracle Customer Support.

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

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.

Action: Fix the problem if possible, or contact Oracle Customer Support.

ORA-39076: cannot delete job string for user string

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-39071: Value for string is badly formed.

ORA-39071: Value for string is badly formed.

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

Action: Fix the problems outlined in the secondary messages.

ORA-39070: Unable to open the log file.

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-39068: invalid master table data in row with PROCESS_ORDER=string

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-39067: Unable to close the log file.

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-39065: unexpected master process exception in string

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-39064: unable to write to the log file

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-39062: error creating master process string

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-39061: import mode string conflicts with export mode string

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-39060: table(s) dropped because of conflict with master table

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-39059: dump file set is incomplete

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-39058: current object skipped: string of type string

ORA-39058: current object skipped: string of type string

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-39057: invalid worker request string for string jobs.

ORA-39057: invalid worker request string for string jobs.

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

Action: Internal error -- contact Oracle Customer Support and report the error.

ORA-39056: invalid log file specification.

ORA-39056: invalid log file specification.

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

Action: Specify a valid directory name and file name for the log file.

ORA-39055: The string feature is not supported in version string.

ORA-39055: The string feature is not supported in version string.

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.

Action: Specify the current database version as a version parameter for the the job.

ORA-39054: missing or invalid definition of the SQL output file.

ORA-39054: missing or invalid definition of the SQL output file.

Cause: The job being defined cannot be started because it is missing the file to receive the SQL output of the job or the definition is unusable.

Action: Specify a valid directory name and file name for the SQL file.

ORA-39053: parameter or attribute string must be defined for a string job

ORA-39053: parameter or attribute string must be defined for a string job

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

Action: Specify the omitted parameter or attribute before starting the job.

ORA-39052: cannot specify SKIP_CURRENT on initial start of a job.

ORA-39052: cannot specify SKIP_CURRENT on initial start of a job.

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

Action: Only specify SKIP_CURRENT when restarting a job.

ORA-39051: parameter string specified multiple times

ORA-39051: parameter string specified multiple times

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

Action: Specify non-repeatable parameters only once.

ORA-39050: parameter string is incompatible with parameter string

ORA-39050: parameter string is incompatible with parameter string

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

Action: Decide which parameter is to be used and stick to it.

ORA-39049: invalid parameter name string

ORA-39049: invalid parameter name string

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

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

ORA-39048: Unable to start all workers; only string worker(s) available.

ORA-39048: Unable to start all workers; only string worker(s) available.

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

Action: Increase process or resource limits for the job.

ORA-39047: Jobs of type string cannot use multiple execution streams.

ORA-39047: Jobs of type string cannot use multiple execution streams.

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

Action: Specify only a parallelism of 1 for this type of job.

ORA-39046: Metadata remap string has already been specified.

ORA-39046: Metadata remap string has already been specified.

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

Action: Specify a different original value.

ORA-39045: invalid metadata remap name string

ORA-39045: invalid metadata remap name string

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

Action: Correct the metadata remap name parameter and reissue the API request.

ORA-39044: Metadata transform string has already been specified.

ORA-39044: Metadata transform string has already been specified.

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

Action: Specify a different object_type for the transform.

ORA-39043: Object type string is not supported for string.

ORA-39043: Object type string is not supported for string.

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

Action: Correct the object type.

ORA-39042: invalid transform name string

ORA-39042: invalid transform name string

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

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

ORA-39041: Filter string either identifies all object types or no object types.

ORA-39041: Filter string either identifies all object types or no object types.

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

Action: Correct the the metadata filter specification.

ORA-39040: Schema expression string must identify exactly one schema.

ORA-39040: Schema expression string must identify exactly one schema.

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

Action: Correct the the SCHEMA_EXPR filter specification.

ORA-39039: Schema expression string contains no valid schemas.

ORA-39039: Schema expression string contains no valid schemas.

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

Action: Correct the the SCHEMA_EXPR filter specification.

ORA-39038: Object path string is not supported for string jobs.

ORA-39038: Object path string is not supported for string jobs.

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

Action: Correct the object type path.

ORA-39037: Object type path not supported for string metadata filter.

ORA-39037: Object type path not supported for string metadata filter.

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

Action: Remove the object type path parameter.

ORA-39036: invalid metadata filter name string

ORA-39036: invalid metadata filter name string

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

Action: Correct the metadata filter name parameter and reissue the API request.

ORA-39035: Data filter string has already been specified.

ORA-39035: Data filter string has already been specified.

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

Action: Specify a different data filter.

ORA-39034: Table string does not exist.

ORA-39034: Table string does not exist.

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

Action: Correct table name and retry API.

ORA-39033: Data cannot be filtered under the direct path access method.

ORA-39033: Data cannot be filtered under the direct path access method.

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

Action: Use the SUBQUERY or the SAMPLE data filter with the automatic data access method.

ORA-39032: function string is not supported in string jobs

ORA-39032: function string is not supported in string jobs

Cause: The specified API is not supported for the specified class of jobs.

Action: Recreate the job with the appropriate mode or operation type.

ORA-39031: invalid filter name string

ORA-39031: invalid filter name string

Cause: An invalid filter name was specified on a DBMS_DATAPUMP.DATA_ FILTER

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

ORA-39030: invalid file type string

ORA-39030: invalid file type string

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

Action: Correct the filetype parameter and reissue the API request.

ORA-39029: worker string with process name string prematurely terminated

ORA-39029: worker string with process name string prematurely terminated

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

Action: If problem persists, contact Oracle Customer Support.