ORA-29309: export dump file was generated by different version of DBMS_PITR package

Cause : The version of DBMS_PITR is different from the version of the cloned database.

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

Load the version of DBMS_PITR which matches the version of the cloned database.

update : 17-08-2017

ORA-29309 - export dump file was generated by different version of DBMS_PITR package
ORA-29309 - export dump file was generated by different version of DBMS_PITR package

  • ora-29274 : fixed-width multibyte character set not allowed for a URL
  • ora-21604 : property [string] is not a property of transient or value instances
  • ora-15104 : conflicting CONTENTS options
  • ora-07804 : slpdtb: number too large for supplied buffer
  • ora-14283 : UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-01866 : the datetime class is invalid
  • ora-02295 : found more than one enable/disable clause for constraint
  • ora-06802 : TLI Driver: could not open the /etc/netware/yellowpages file
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-38709 : Recovery Area is not enabled.
  • ora-09766 : osnmop: buffer allocation failure.
  • ora-01776 : cannot modify more than one base table through a join view
  • ora-19160 : XP0003 - syntax error: invalid variable name string
  • ora-31416 : invalid SOURCE_COLMAP value
  • ora-31507 : %s parameter value longer than maximum length string
  • ora-01524 : cannot create data file as 'string' - file already part of database
  • ora-32144 : Cannot perform operation on a null interval
  • ora-00119 : invalid specification for system parameter string
  • ora-36930 : Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed.
  • ora-39311 : call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal
  • ora-23292 : The constraint does not exist
  • ora-22893 : constraint can be specified only for REF columns
  • ora-33270 : (DBERR05) Analytic workspace string already exists.
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-32013 : failure in verifying parameters from the restored SPFILE
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-31486 : cannot support column string in this configuration
  • ora-24131 : table string has incorrect columns
  • ora-07570 : szrfc: $IDTOASC failure
  • ora-02313 : object type contains non-queryable type string attribute
  • 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.