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-09-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-25957 : join index where clause cannot contain cycles
  • ora-24084 : DBLINK name in address field of agent string is not unique within the first 24 bytes
  • ora-30340 : illegal dimension name
  • ora-21609 : memory being resized without being allocated first
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-27230 : OS system call failure
  • ora-14310 : VALUES LESS THAN or AT clause cannot be used with List partitioned tables
  • ora-07446 : sdnfy: bad value 'string' for parameter string.
  • ora-01555 : snapshot too old: rollback segment number string with name "string" too small
  • ora-16643 : unable to determine location of broker configuration files
  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-24814 : operation not allowed for temporary LOBs
  • ora-00983 : cannot audit or noaudit SYS user actions
  • ora-10567 : Redo is inconsistent with data block (file# string, block# string)
  • ora-07281 : slsget: times error, unable to get cpu time.
  • ora-29974 : Internal event for PL/SQL debugging
  • ora-12326 : database string is closing immediately; no operations are permitted
  • ora-24031 : invalid value, string should be non-NULL
  • ora-01080 : error in shutting down ORACLE
  • ora-13464 : error loading GeoRaster data: string
  • ora-22313 : cannot use two versions of the same type "string"
  • ora-07233 : slemcw: invalid file handle, seals do not match.
  • ora-07577 : no such user in authorization file
  • ora-25221 : enqueue failed, signature specified queue not supporting non-repudiation
  • ora-32131 : bind data type cannot be changed
  • ora-30658 : attempt was made to create a temporary table with EXTERNAL organization
  • ora-07665 : ssrexhd: recursive exception encountered string string string string string string
  • ora-07280 : slsget: unable to get process information.
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • 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.