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 : 26-09-2017
ORA-39123

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

  • ora-13505 : SYSAUX tablespace can not be made read only
  • ora-16056 : backup control file archival requires proper syntax
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • ora-37158 : Bad clob or varray IN-args: (case string)
  • ora-10701 : Dump direct loader index keys
  • ora-09752 : pw_attachPorts: port_allocate failed.
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-36975 : (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.
  • ora-13443 : GeoRaster metadata SRS error
  • ora-24460 : Native Net Internal Error
  • ora-29547 : Java system class not available: string
  • ora-09754 : sppst: invalid process number passed to sppst.
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-07485 : scg_get_inst: cannot open instance number lock.
  • ora-38956 : Target platform string not cross platform compliant
  • ora-09985 : SGA definition file could not be read
  • ora-00479 : RVWR process terminated with error string
  • ora-12200 : TNS:could not allocate memory
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-39110 : error deleting worker processes
  • ora-13138 : could not determine name of object string
  • ora-07469 : sppst: mclear error, unable to clear semaphore.
  • ora-24397 : error occured while trying to free connections
  • ora-36200 : (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY clause, but ARGS variable workspace object did not specify one.
  • ora-29329 : Table not of type XMLType
  • ora-12672 : Database logon failure
  • ora-24314 : service handle not initialized
  • ora-03231 : the INITIAL extent may not be deallocated
  • ora-13060 : topology with the name string already exists
  • ora-32740 : The requested operation cannot be proceeded
  • 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.