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 : 28-05-2017

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

  • ora-32146 : Cannot perform operation on a null date
  • ora-10588 : Can only allow 1 corruption for normal media/standby recovery
  • ora-34019 : (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.
  • ora-02372 : data for row: string
  • ora-36674 : (XSDPART12) Invalid dimension value starting at string.
  • ora-29851 : cannot build a domain index on more than one column
  • ora-31508 : invalid parameter value for synchronous change set
  • ora-14117 : partition resides in offlined tablespace
  • ora-13437 : GeoRaster metadata blocking error
  • ora-16635 : NetSlave connection was broken in the middle of a transmission session
  • ora-13272 : geometric object string in table string is invalid
  • ora-24812 : character set conversion to or from UCS2 failed
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-23335 : priority group string already exists
  • ora-16238 : attempt to use version 9 log
  • ora-36974 : (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
  • ora-38725 : specified name "string" does not match actual "string"
  • ora-13278 : failure to convert SRID to native format
  • ora-29361 : value string is outside valid range of 0 to 100
  • ora-13842 : no SELECT privilege on DBA_SQL_PROFILES
  • ora-12661 : Protocol authentication to be used
  • ora-16013 : log string sequence# string does not need archiving
  • ora-01412 : zero length not allowed for this datatype
  • ora-29504 : invalid or missing schema name
  • ora-07239 : slemrd: invalid file handle, seals do not match.
  • ora-01724 : floating point precision is out of range (1 to 126)
  • ora-22298 : length of directory alias name or file name too long
  • ora-12436 : no policy options specified
  • ora-36847 : (XSLMGEN17) AW name is blank
  • ora-03134 : Connections to this server version are no longer supported.
  • 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.