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 : 28-06-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-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-06102 : NETTCP: cannot allocate context area
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-00112 : value of string is null
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-39776 : fatal Direct Path API error loading table string
  • ora-13187 : subdivision failed
  • ora-19013 : Cannot create VARRAY columns containing XMLType
  • ora-27484 : Argument names are not supported for jobs without a program.
  • ora-01528 : EOF while processing SQL statement
  • ora-01250 : Error string occurred during termination of file header access
  • ora-18010 : command missing mandatory CATEGORY keyword
  • ora-31470 : asynchronous change tables must contain the RSID$ column
  • ora-24344 : success with compilation error
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-03208 : partitioned type must be specified for a non-composite object
  • ora-28154 : Proxy user may not act as client 'string'
  • ora-40287 : invalid data for model - cosine distance out of bounds
  • ora-28335 : referenced or referencing FK constraint column cannot be encrypted
  • ora-24776 : cannot start a new transaction
  • ora-19500 : device block size string is invalid
  • ora-32824 : schedule exists for source string and destination string
  • ora-36838 : (XSLMGEN08) Dimension string.string!string attribute string is missing a COLUMNNAME property value
  • ora-30345 : circular dimension hierarchy
  • ora-30566 : Index maintainence clause not allowed for this command
  • ora-30006 : resource busy; acquire with WAIT timeout expired
  • ora-00271 : there are no logs that need archiving
  • ora-24367 : user handle has not been set in service handle
  • ora-22309 : attribute with name "string" already exists
  • ora-29705 : ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
  • 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.