ORA-19903: test recovery not allowed when recovering to new incarnation

Cause : Either a new incarnation was set using RMAN's RESET DATABASE command for a control file that was CURRENT, or the control file is from a prior incarnation. As recovery to a new incarnation requires changing the control file, test recovery is not allowed.

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

Perform actual recovery or RESET DATABASE to incarnation that was last opened using the control file to do test recovery.

update : 22-08-2017

ORA-19903 - test recovery not allowed when recovering to new incarnation
ORA-19903 - test recovery not allowed when recovering to new incarnation

  • ora-00287 : specified change number string not found in thread string
  • ora-28046 : Password change for SYS disallowed
  • ora-06900 : CMX: cannot read tns directory
  • ora-09706 : slsget: get_process_stats error.
  • ora-16041 : Remote File Server fatal error
  • ora-02210 : no options specified for ALTER TABLE
  • ora-04053 : error occurred when validating remote object stringstringstringstringstring
  • ora-07484 : snlkput: cannot convert(put) lock.
  • ora-19658 : cannot inspect string - file is from different resetlogs
  • ora-29325 : SET COMPATIBILITY release number lower than string
  • ora-39026 : master table is inconsistent on validation string
  • ora-12060 : shape of prebuilt table does not match definition query
  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-16554 : translation not valid
  • ora-01620 : no public threads are available for mounting
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-15093 : buffer only contains string bytes, I/O requested is string bytes
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • ora-27301 : OS failure message: string
  • ora-06433 : ssaio: LSEEK error, unable to seek to requested block.
  • ora-22957 : NULL is an invalid input to powermultiset and COLLECT functions
  • ora-26714 : User error encountered while applying
  • ora-23383 : registration for materialized view repgroup "string"."string" failed at site string
  • ora-24391 : invalid fetch operation
  • ora-16657 : reinstatement of database in progress
  • ora-10841 : Default un-inintialized charact set form to SQLCS_IMPLICIT
  • ora-04004 : MINVALUE must be less than MAXVALUE
  • ora-12225 : TNS:destination host unreachable
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-07230 : slemcr: fopen error, unable to open error file.
  • 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.