ORA-39141: dump file "string" is a duplicate of dump file "string"

Cause : When a dump file set consists of multiple files, all files in the set must be specified for an import operation. One of the files provided to import was found to be a duplicate of another dump file in the set. This can occur if the files in the dump set were copied or renamed using operating system utilities and the same dump file was inadvertently copied more than once with different destination names.

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

Remove the dump file indicated in the message and retry the import operation providing only the complete set of dump files created by a specific export job.

update : 24-08-2017

ORA-39141 - dump file "string" is a duplicate of dump file "string"
ORA-39141 - dump file "string" is a duplicate of dump file "string"

  • ora-15203 : diskgroup string contains disks from an incompatible version of ASM
  • ora-02877 : smpini: Unable to initialize memory protection
  • ora-24146 : rule string.string already exists
  • ora-29521 : referenced name string could not be found
  • ora-25306 : Cannot connect to buffered queue's owner instance
  • ora-10564 : tablespace string
  • ora-24153 : rule set string.string already exists
  • ora-06813 : TLI Driver: the configured ethernet address is incorrect
  • ora-14107 : partition specification is required for a partitioned object
  • ora-25127 : RELY not allowed in NOT NULL constraint
  • ora-16163 : LGWR network server host attach error
  • ora-00953 : missing or invalid index name
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-22335 : The client cannot work with an altered type
  • ora-14171 : cannot specify clause in CREATE|ALTER TABLE
  • ora-38609 : FI Not enough memory for tree counting, requires at least stringKB
  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • ora-29523 : authorization error for unknown referenced name
  • ora-39019 : invalid operation type string
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-30930 : NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-30082 : datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
  • ora-32301 : object-relational materialized views must be primary key based
  • ora-06596 : unsupported LOB operation in RPC call
  • ora-19681 : block media recovery on control file not possible
  • ora-22317 : typecode number is not legal as a number type
  • ora-14503 : only one partition name can be specified
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • ora-12088 : cannot online redefine table "string"."string" with unsupported datatype
  • 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.