ORA-29340: export file appears to be corrupted: [string] [string] [string]

Cause : This is caused either by a corrupted export file or by an Oracle internal error.

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

Make sure the export file used for transportable tablespace is not corrupted. If the error still occurs, call Oracle support.

update : 20-09-2017
ORA-29340

ORA-29340 - export file appears to be corrupted: [string] [string] [string]
ORA-29340 - export file appears to be corrupted: [string] [string] [string]

  • ora-02450 : Invalid hash option - missing keyword IS
  • ora-25405 : transaction status unknown
  • ora-29344 : Owner validation failed - failed to match owner 'string'
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-14456 : cannot rebuild index on a temporary table
  • ora-09709 : soacon: failed to accept a connection.
  • ora-06750 : TLI Driver: sync failed
  • ora-16226 : DDL skipped due to lack of support
  • ora-30044 : 'Retention' can only specified for undo tablespace
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-00279 : change string generated at string needed for thread string
  • ora-32510 : cannot create watchpoint on unreadable memory
  • ora-12628 : TNS:no event callbacks
  • ora-07272 : spwat: invalid semaphore set id.
  • ora-09743 : smscre: could not attach shared memory.
  • ora-22343 : Compilation error for type invalidated by ALTER TYPE
  • ora-10865 : Control tracing of notification operations
  • ora-31648 : Timeout before master process string finished initialization.
  • ora-32142 : maximum number of iterations exceeded
  • ora-10266 : Trace OSD stack usage
  • ora-15031 : disk specification 'string' matches no disks
  • ora-13363 : no valid ETYPE in the geometry
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-30930 : NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn
  • ora-00365 : the specified log is not the correct next log
  • ora-19224 : XP0004 - XQuery static type mismatch: expected - string got - string
  • ora-32805 : identifier for string too long, maximum length is string characters
  • ora-28137 : Invalid FGA audit Handler
  • ora-13529 : Error occurred when flushing AWR table group
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • 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.