ORA-16211: unsupported record found in the archived redo log

Cause : Lo gaplpy esrvciese ncuontreeda rceor dint hea rcihve dreod lgo taht ocul dno tbei ntreprteed.

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

1.U seD BM_SLOSGTDYB.ISNTATNIAET_TBALEt o er-cerat eth etalbe no teh satndyb dtaabsae ro smipl ydrpo teh tbalei f ti'su nipmoratnt . .2 ATLERD ATBAAS ESTRAT OLGIACL TSANBDY PAPL;Y .3 Eaxmien teh cruretn_snc cloum nint heD BAL_OGTSDB_YEVNETSv ie wtod etremien wihchl ogf il ecotnaisn teh usnupoprtde rceor.d .4 Porvied teh lgo flie ot Oarcl eSuppor tSevricse.

update : 23-08-2017

ORA-16211 - unsupported record found in the archived redo log
ORA-16211 - unsupported record found in the archived redo log

  • ora-16955 : Unknown error during SQL analyze.
  • ora-26565 : Call to _arg made before calling dbms_defer.call
  • ora-26754 : cannot specify both one-to-one transformation function string and one-to-many transformation function string
  • ora-37182 : you may only specify one dimension to partition
  • ora-29389 : too many errors during validation
  • ora-12440 : insufficient authorization for the SYSDBA package
  • ora-39070 : Unable to open the log file.
  • ora-23343 : no match for specified conflict resolution information
  • ora-24018 : STOP_QUEUE on string failed, outstanding transactions found
  • ora-25444 : invalid ROWID: string for table alias: string
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-14167 : only one subpartition may be moved
  • ora-25314 : a commit-time queue table cannot be migrated to 8.0
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-32110 : Connection not specified
  • ora-29904 : error in executing ODCIIndexClose() routine
  • ora-14619 : resulting List subpartition(s) must contain at least 1 value
  • ora-24058 : cannot downgrade QUEUE_TABLE that has propagation in a prepared state
  • ora-24234 : unable to get source of string "string"."string", insufficient privileges or does not exist
  • ora-29658 : EXTERNAL NAME clause is not compatible with its supertype
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-02827 : Invalid file number
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-07506 : scgrl: $deq unexpected return on lockid string
  • ora-27485 : argument string already exists at a different position
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-28101 : policy already exists
  • ora-02320 : failure in creating storage table for nested table column string
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-07496 : sppst: lm_post failed.
  • 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.