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 : 24-06-2017
ORA-19903

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

  • ora-34359 : (MXDSS11) string appears twice in the alias list.
  • ora-25195 : invalid option for index on an index-organized table
  • ora-12982 : cannot drop column from a nested table
  • ora-28140 : Invalid column specified
  • ora-24077 : cannot create propagation schedule for EXCEPTION queue string.string
  • ora-28551 : pass-through SQL: SQL parse error
  • ora-24265 : Insufficient privileges for SQL profile operation
  • ora-19723 : Cannot recreate plugged in read-only datafile string
  • ora-38604 : FI including & excluding cursor item-id type must match input cursor item-id type
  • ora-07281 : slsget: times error, unable to get cpu time.
  • ora-30176 : invalid format code used in the format string
  • ora-07229 : slcpuc: error in getting number of CPUs.
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • ora-03201 : the group number specification is invalid
  • ora-24275 : function 'string' parameter 'string' missing or invalid
  • ora-16570 : operation requires restart of database "string"
  • ora-32101 : cannot create OCI Environment
  • ora-22881 : dangling REF
  • ora-13363 : no valid ETYPE in the geometry
  • ora-25004 : WHEN clause is not allowed in INSTEAD OF triggers
  • ora-30110 : syntax error at 'string'
  • ora-01585 : error identifying backup file string
  • ora-31196 : XML nodes over string in size cannot be printed
  • ora-37042 : (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object since doing so would cause a deadlock.
  • ora-06515 : PL/SQL: unhandled exception string
  • ora-01631 : max # extents (string) reached in table string.string
  • ora-23378 : connection qualifier "string" is not valid for object group "string"."string"
  • ora-38441 : System could not derive the list of STORED and INDEXED attributes.
  • ora-38720 : Missing log file number.
  • 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.