ORA-39123: Data Pump transportable tablespace job aborted string

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

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Look at the DBMS_PLUGTS error to determine actual cause.

update : 24-06-2017
ORA-39123

ORA-39123 - Data Pump transportable tablespace job aborted string
ORA-39123 - Data Pump transportable tablespace job aborted string

  • ora-21525 : attribute number or (collection element at index) string violated its constraints
  • ora-12706 : this CREATE DATABASE character set is not allowed
  • ora-30434 : refresh method must be one of FC?AN, not 'string'
  • ora-13442 : GeoRaster metadata SRS error
  • ora-09787 : sllfop: unrecognizable processing option, incorrect format.
  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-07472 : snclrd: open error when opening sgadef.dbf file.
  • ora-07417 : sfareq: One or more database writers not active.
  • ora-17503 : ksfdopn:string Failed to open file string
  • ora-38858 : cannot mark redo thread string as enabled
  • ora-23365 : site string does not exist
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-19805 : recid string of string was deleted to reclaim disk space
  • ora-09936 : Open of ORACLE password file for write failed.
  • ora-01324 : cannot add file string due to DB_ID mismatch
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-35016 : (QFCHECK00) The analytic workspace and EIF file definitions of workspace object have a mismatched type.
  • ora-36910 : (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL workspace object can only edit the top level of its matching relation hierarchy.
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-00820 : Specified value of sga_max_size is too small, needs to be at least stringM
  • ora-00125 : connection refused; invalid presentation
  • ora-06136 : NETTCP: error during connection handshake
  • ora-16164 : LGWR network server host detach error
  • ora-16218 : This database is already preparing to switch over.
  • ora-31002 : Path name string is not a container
  • ora-07703 : error in archive text: need '/' after device type
  • ora-28012 : Manual commit not allowed here
  • ora-31064 : Cannot instantiate abstract element or property [string]
  • ora-22810 : cannot modify object attributes with REF dereferencing
  • ora-27472 : invalid metadata attribute string
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.