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

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

  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-22809 : nonexistent attribute
  • ora-16543 : invalid request made to broker
  • ora-12599 : TNS:cryptographic checksum mismatch
  • ora-10852 : Enable tracing for Enqueue Dequeue Operations
  • ora-08238 : smsfre: cannot detach from SGA
  • ora-29298 : Character set mismatch
  • ora-28274 : No ORACLE password attribute corresponding to user nickname exists.
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-01597 : cannot alter system rollback segment online or offline
  • ora-02479 : error while translating file name for parallel load
  • ora-07860 : osnsoi: error setting up interrupt handler
  • ora-14056 : partition number string: sum of PCTUSED and PCTFREE may not exceed 100
  • ora-00110 : invalid value string for attribute string, must be between string and string
  • ora-16619 : health check timed out
  • ora-22880 : invalid REF
  • ora-00386 : use_indirect_data_buffers not supported
  • ora-22606 : pickler image handle [string] is not well-formed
  • ora-27543 : Failed to cancel outstanding IPC request
  • ora-01071 : cannot perform operation without starting up ORACLE
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-02878 : sou2o: Variable smpdidini overwritten
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-12047 : PCT FAST REFRESH cannot be used for materialized view "string"."string"
  • ora-02264 : name already used by an existing constraint
  • ora-39021 : Database compatibility version string is not supported.
  • ora-37117 : olapi history retention has been disabled
  • ora-12069 : invalid object for offline instantiation
  • ora-10619 : Avoid assertions when possible
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • 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.