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-04-2017

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

  • ora-12821 : invalid value for INSTANCES
  • ora-31231 : DBMS_LDAP: invalid PROPERTY_SET
  • ora-37144 : (MDQUERY01) string is not a valid metadata object type for MDQUERY.
  • ora-14103 : LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
  • ora-29906 : indextype string.string does not exist
  • ora-29555 : Java source, class or resource is not allowed here
  • ora-16783 : instance string not open for read and write access
  • ora-22331 : cannot alter an incomplete type
  • ora-12841 : Cannot alter the session parallel DML state within a transaction
  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-12444 : policy already applied to table
  • ora-02754 : osnfsmmap: cannot change shared memory inheritence
  • ora-26695 : error on call to string: return code string
  • ora-12802 : parallel query server lost contact with coordinator
  • ora-29335 : tablespace 'string' is not read only
  • ora-24021 : queue table definition not imported for string.string
  • ora-03112 : a server linked as single-task cannot use SQL*Net
  • ora-14286 : cannot COALESCE the only subpartition of this table partition
  • ora-10900 : extent manager fault insertion event #string
  • ora-01905 : STORAGE keyword expected
  • ora-01529 : error closing file 'string'
  • ora-04054 : database link string does not exist
  • ora-19606 : Cannot copy or restore to snapshot control file
  • ora-12008 : error in materialized view refresh path
  • ora-40206 : invalid setting value for setting name string
  • ora-02298 : cannot validate (string.string) - parent keys not found
  • ora-02788 : Unable to find kernel process pointer in async process array
  • ora-10583 : Can not recovery file string renamed as missing during test recovery
  • ora-12824 : INSTANCES DEFAULT may not be specified here
  • ora-28012 : Manual commit not allowed here
  • 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.