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 : 27-06-2017

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

  • ora-24316 : illegal handle type
  • ora-01938 : IDENTIFIED BY must be specified for CREATE USER
  • ora-23457 : invalid flavor ID string
  • ora-02344 : cannot revoke execute on a type with table dependents
  • ora-01761 : DML operation does not map to a unique table in the join
  • ora-26668 : STREAMS process string exists
  • ora-01266 : Unable to create unique file name
  • ora-33006 : (XSAGDNGL02) The relation workspace object is not related to itself.
  • ora-31019 : Recursive deletion snapshot too old for string/string
  • ora-15176 : file 'string' already has an alias associated with it
  • ora-09215 : sfqio: error detected in IOCompletionRoutine
  • ora-19017 : Attributes can only be simple scalars
  • ora-14054 : invalid ALTER TABLE TRUNCATE PARTITION option
  • ora-24405 : error occured while trying to create connections in the pool
  • ora-09854 : snyPortInfo: bad return code from request.
  • ora-09853 : snyRemovePort: bad return code from request.
  • ora-29705 : ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
  • ora-36181 : A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.
  • ora-07534 : scginq: $getlki unexpected return on lockid string
  • ora-32059 : deadlock detected on mapping structures
  • ora-36862 : (XSTFRC02) Column number for this SQL Cache must be between 1 and number. Specified column number number is invalid.
  • ora-09851 : soacon: Archmon unable to lock named pipe.
  • ora-06924 : CMX: wrong break message length
  • ora-12611 : TNS:operation is not portable
  • ora-33425 : (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
  • ora-22997 : VARRAY | OPAQUE stored as LOB is not specified at the table level
  • ora-02095 : specified initialization parameter cannot be modified
  • ora-09855 : removeCallback: bad message format.
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • 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.