ORA-16133: Datafile string has incorrect terminal recovery stamp.

Cause : Aftre acitvatoin o fa satndb ydatbaasef ollwoinga temrina lrecvoery( recvoeryo f satndb yusign currentl ogs,) reocver yof adatfailef romb efoer th eactviatino muts haev copmletde th esam eterimnalr ecoevry ot aviod crorupiton.

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

A bcakupo f teh daatfil etakne afetr teh temrina lrecvoerya nd ebfor eactviatign th estadnby umst eb usde fo rrecvoery.

update : 23-04-2017
ORA-16133

ORA-16133 - Datafile string has incorrect terminal recovery stamp.
ORA-16133 - Datafile string has incorrect terminal recovery stamp.

  • ora-13353 : ELEM_INFO_ARRAY not grouped in threes
  • ora-30737 : cannot create subtable of a type which is not a subtype of the type of the supertable
  • ora-27006 : sbtremove returned error
  • ora-30511 : invalid DDL operation in system triggers
  • ora-14078 : you may not drop the highest partition of a GLOBAL index
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-19501 : read error on file "string", blockno string (blocksize=string)
  • ora-02399 : exceeded maximum connect time, you are being logged off
  • ora-16116 : no work available
  • ora-27008 : function called with invalid file structure
  • ora-14635 : only one resulting subpartition can be specified for MERGE SUBPARTITIONS
  • ora-02478 : merge into base segment would overflow MAXEXTENTS limit
  • ora-25964 : column type incompatible with join column type
  • ora-36274 : (XSCGMDLAGG05) The operator used in this equation needs a weight variable.
  • ora-02154 : a tablespace with the name 'string' is found
  • ora-12735 : Instant Client Light: unsupported client character set string
  • ora-31666 : Master process string had an unhandled exception.
  • ora-29544 : invalid type
  • ora-24900 : invalid or unsupported mode paramater passed in call
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-01135 : file string accessed for DML/query is offline
  • ora-12528 : TNS:listener: all appropriate instances are blocking new connections
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-06780 : TLI Driver: recv error code failed
  • ora-29662 : Unable to find a field that matches one or more of the attributes
  • ora-25449 : invalid variable name: string
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-19029 : Cannot convert the given XMLType to the required type
  • ora-28200 : IDENTIFIED USING already specified
  • ora-30130 : invalid parameter key type received
  • 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.