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 : 26-05-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-30397 : multiple JOIN KEY clauses specified for the same child level
  • ora-29289 : directory access denied
  • ora-25134 : keyword TABLE expected
  • ora-06423 : NETCMN: Error in receiving data
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-13198 : Spatial error: string
  • ora-02845 : Invalid value for the timing wanted flag
  • ora-33092 : (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-27193 : sbtinfo2 did not return volume label
  • ora-01244 : unnamed datafile(s) added to control file by media recovery
  • ora-12828 : Can't start parallel transaction at a remote site
  • ora-29275 : partial multibyte character
  • ora-12020 : materialized view string is not registered
  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-24795 : Illegal string attempt made
  • ora-24086 : cannot create a 8.0 compatible string queue
  • ora-22974 : missing WITH OBJECT OID clause
  • ora-28593 : agent control utility: command terminated with error
  • ora-25266 : didnt try to dequeue by message id. with the signature
  • ora-00090 : failed to allocate memory for cluster database ORADEBUG command
  • ora-02244 : invalid ALTER ROLLBACK SEGMENT option
  • ora-16602 : object must be disabled to perform this operation
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-09881 : sstasfre/sstasdel: shmdt error, unable to detach tas read page
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-36208 : (XSAGOP05N) In AGGMAP workspace object, you can only specify NAOPERATOR string with the PROPORTIONAL or EVEN operators, not string.
  • ora-38499 : expression set already configured for stored/indexed attributes
  • 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.