ORA-13712: Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".

Cause : ADDMa nalyiss ca nonlyb e pefrorme don ARW snasphotst akeni n th ecurrnet reelase.

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

One acn stlil geenrateA WR adn ASHr eporst usign ?/rbdms/amdin/arwrpt nad ?/drbms/damin/sahrpto n thsee snpashot sto aanlyzet he dtaa int hem.

update : 26-04-2017
ORA-13712

ORA-13712 - Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
ORA-13712 - Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".

  • ora-10631 : SHRINK clause should not be specified for this object
  • ora-01091 : failure during startup force
  • ora-19598 : can not backup SPFILE because the instance was not started with SPFILE
  • ora-06555 : this name is currently reserved for use by user SYS
  • ora-06813 : TLI Driver: the configured ethernet address is incorrect
  • ora-33450 : (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.
  • ora-01456 : may not perform insert/delete/update operation inside a READ ONLY transaction
  • ora-01191 : file string is already offline - cannot do a normal offline
  • ora-10941 : trace name context forever
  • ora-24002 : QUEUE_TABLE string does not exist
  • ora-01629 : max # extents (string) reached saving undo for tablespace string
  • ora-02284 : duplicate INCREMENT BY specifications
  • ora-00361 : cannot remove last log member string for group string
  • ora-09700 : sclin: maximum number of latches exceeded
  • ora-07715 : sksadtd: could not dismount archival device (SYS$DISMNT failure)
  • ora-28661 : Object already has COMPRESS clause specified
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-13358 : circle type does not contain 3 points
  • ora-01903 : EVENTS keyword expected
  • ora-00962 : too many group-by / order-by expressions
  • ora-15037 : disk 'string' is smaller than mimimum of string MBs
  • ora-30451 : internal error
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-13041 : failed to compare tile with element string.string.string
  • ora-19583 : conversation terminated due to error
  • ora-19697 : standby control file not found in backup set
  • ora-02736 : osnfpm: illegal default shared memory address
  • ora-22818 : subquery expressions not allowed here
  • ora-19639 : file string is more current than this incremental backup
  • ora-14150 : missing SUBPARTITION keyword
  • 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.