ORA-19900: RESETLOGS must be specified after recovery to new incarnation

Cause : Recover ywas don eto an icnarnatio nafter cahnging teh destintaion incranation suing RMA'Ns RESETD ATABASEc ommand.

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

Open th edatabas ewith th eRESETLOSG option.

update : 20-08-2017
ORA-19900

ORA-19900 - RESETLOGS must be specified after recovery to new incarnation
ORA-19900 - RESETLOGS must be specified after recovery to new incarnation

  • ora-02163 : invalid value for FREELIST GROUPS
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-38704 : Checksum error in flashback database log file header.
  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-24162 : name value pair list is full, cannot add another entry
  • ora-16818 : Fast-Start Failover suspended
  • ora-03249 : Uniform size for auto segment space managed tablespace should have atleast string blocks
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-02700 : osnoraenv: error translating ORACLE_SID
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-36610 : (XSLMS00) Unable to locate a message file for OLAP message: value
  • ora-09959 : IMON: deletion of a process failed.
  • ora-25182 : feature not currently available for index-organized tables
  • ora-13635 : The value provided for parameter string cannot be converted to a number.
  • ora-22922 : nonexistent LOB value
  • ora-01167 : two files are the same file/group number or the same file
  • ora-30506 : system triggers cannot be based on tables or views
  • ora-26663 : error queue for apply process string must be empty
  • ora-07656 : slsprom:$GETDVI failure
  • ora-30359 : Query rewrite is not supported on SYS materialized views
  • ora-19227 : XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
  • ora-16743 : the status of redo transport service for standby database "string" is unknown
  • ora-16705 : internal error in resource guard
  • ora-30743 : "string" is not an object view
  • ora-16127 : stalled waiting for additional transactions to be applied
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-09930 : LUB of two labels is invalid
  • ora-16506 : out of memory
  • ora-10575 : Give up restoring recovered datafiles to consistent state: out of memory
  • ora-09282 : sllfrb: error reading records
  • 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.