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 : 28-06-2017
ORA-29309

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-16013 : log string sequence# string does not need archiving
  • ora-28044 : unsupported directory type
  • ora-12211 : TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA
  • ora-24401 : cannot open further connections
  • ora-23330 : column group string already exists
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-03215 : File Size specified for resize is too small
  • ora-31463 : logfile location string is an empty directory
  • ora-24191 : the property name string has existed
  • ora-39121 : Table string can't be replaced, data will be skipped. Failing error is: string
  • ora-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-12585 : TNS:data truncation
  • ora-19703 : device command string exceeds maximum length of string
  • ora-09312 : slspool: error spooling file to printer
  • ora-19037 : XMLType result can not be a fragment
  • ora-19205 : Attribute 'string' qualifies a non-scalar value in the select list
  • ora-39055 : The string feature is not supported in version string.
  • ora-38497 : Expression Filter index does not exist
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • ora-01426 : numeric overflow
  • ora-19705 : tag value exceeds maximum length of string characters
  • ora-07277 : spdde: illegal pid passed as argument.
  • ora-28504 : ROWID not found in ROWID cache for heterogeneous database link
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-39023 : Version string is not supported.
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-01255 : cannot shutdown - file string in recovery manager backup
  • ora-23363 : mismatch of mview base table "string" at master and mview site
  • ora-32812 : subscriber string does not exist
  • 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.