Oracle Database Errors or Warnings from Error ORA-39143 to ORA-39155


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
Action: Specify the correct name of the schema to be remapped.
ORA-39147: cannot migrate Data Pump queue table ownership to this instance
Cause: There are active Data Pump jobs running on another instance in a RAC. All concurrent, active Data Pump jobs must be run on the same instance.
Action: Start this job on the same instance where other active Data Pump jobs are running, or wait until they finish.
ORA-39148: unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table
Cause: A Data Pump import detected that a queue table that was to be imported already exists. Importing data into pre-existing queue tables is not supported.
Action: If the data from the dump file is desired, then drop the queue table and perform the import again, or use the import parameter table_exists_action=replace.

ORA-39149: cannot link privileged user to non-privileged user
Cause: A Data Pump job initiated be a user with EXPORT_FULL_DATABASE/IMPORT_FULL_DATABASE roles specified a network link that did not correspond to a user with equivalent roles on the remote database.
Action: Specify a network link that maps users to identically privileged users in the remote database.
ORA-39150: bad flashback time
Cause: A flashback time was specified for the Data Pump job which either could not be parsed or else could not be translated into a system change number (SCN). This typically occurs when
Action: Specify an explicit SCN for the desired flashback rather than a time.
ORA-39154: Objects from foreign schemas have been removed from import
Cause: An non-privileged user attempted to import objects into a schema other than their own.
Action: Either perform the import from a privileged schema or else remap all schemas that were exported into the username running the import.
ORA-39155: error expanding dump file name “string”
Cause: Export was unable to expand the directory object and dump file name into a full file name. Subsequent messages will detail the problems.
Action: Fix the problems outlined in the secondary messages.

Above are list of Oracle Database Errors or Warnings from Error ORA-39143 to ORA-39155 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.


Leave a Reply

Your email address will not be published. Required fields are marked *