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 : 21-07-2017

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

  • ora-21600 : path expression too long
  • ora-24072 : cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
  • ora-01049 : Bind by name is not spupportted in streamed RPC
  • ora-09746 : smscre: shared memory attach address incorrect.
  • ora-00112 : value of string is null
  • ora-29910 : invalid callback operation
  • ora-02431 : cannot disable constraint (string) - no such constraint
  • ora-28584 : heterogeneous apply internal error
  • ora-01371 : Complete LogMiner dictionary not found
  • ora-25104 : UNRECOVERABLE option can only be used with ALTER INDEX REBUILD
  • ora-13379 : invalid index for sub-element to be extracted
  • ora-39102 : Timeout before master process string finished initialization. Master error:
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-28116 : insufficient privileges to do direct path access
  • ora-13201 : invalid parameters supplied in CREATE INDEX statement
  • ora-14194 : only one subpartition may be rebuilt
  • ora-06953 : Not enough virtual memory
  • ora-23465 : flavor already includes column string of "string"."string"
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-16560 : unable to convert document, syntax error at "string"
  • ora-07759 : slemtr: invalid destination
  • ora-03222 : average row size and row count must be greater than zero
  • ora-28512 : cannot get data dictionary translations from string
  • ora-13013 : the specified topology was not INTERIOR or BOUNDARY
  • ora-30401 : JOIN KEY columns must be non-null
  • ora-22819 : scope of input value does not correspond to the scope of the target
  • ora-22814 : attribute or element value is larger than specified in type
  • ora-07404 : sfareq: Timeout occurred waiting for request to complete.
  • ora-13011 : value is out of range
  • ora-01075 : you are currently logged on
  • 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.