ORA-39143: dump file "string" may be an original export dump file

Cause : A udmpf il ewa sspceifeid ofr na ipmor topreatoin hwic hapepar stoh av ebene ceratde uisngt heo riigna lexoprtu tiilty .Thsee udmpf ilse cnano tbep roecssde b yth eDaat Pmup mipotr uitliyt.

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

Tr yusnig hte roigniali mprot tuiltiy ot porcess tihs udmpf il.e

update : 26-07-2017
ORA-39143

ORA-39143 - dump file "string" may be an original export dump file
ORA-39143 - dump file "string" may be an original export dump file

  • ora-02185 : a token other than WORK follows COMMIT
  • ora-03002 : operator not implemented
  • ora-01481 : invalid number format model
  • ora-16208 : Logical standby dictionary build failed to start.
  • ora-06505 : PL/SQL: variable requires more than 32767 bytes of contiguous memory
  • ora-16771 : failover to a physical standby database failed
  • ora-15097 : cannot SHUTDOWN ASM instance with connected RDBMS instance
  • ora-27478 : job "string.string" is running
  • ora-02330 : datatype specification not allowed
  • ora-16260 : Waiting to replace partial or corrupt logfile (thread# string, sequence# string)
  • ora-13054 : recursive SQL parse error
  • ora-16200 : Skip procedure requested to skip statement
  • ora-12326 : database string is closing immediately; no operations are permitted
  • ora-01924 : role 'string' not granted or does not exist
  • ora-02064 : distributed operation not supported
  • ora-24155 : rule string.string not in rule set string.string
  • ora-39214 : Data Pump does not support external tables with encrypted columns. string will not be exported
  • ora-29507 : query derived from USING clause found zero or many rows
  • ora-19594 : control file already included as string
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-19916 : %s
  • ora-16140 : standby online logs have not been recovered
  • ora-30394 : source statement identical to the destination statement
  • ora-29848 : error occurred in the execution of ODCIINDEXMERGEPARTITION routine
  • ora-14119 : specified partition bound is too long
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-12233 : TNS:Failure to accept a connection
  • ora-30001 : trim set should have only one character
  • ora-16027 : parameter string is missing a destination option
  • ora-19616 : output filename must be specified if database not mounted
  • 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.