Answer / guest

Cause: the database incarnation that matches the resetlogs
change# and time of the mounted target database controlfile
is not the current incarnation of the database

Action: If 'reset database to incarnation <key>' was used to
make an old incarnation current then restore the target
database from a backup that matches the incarnation and
mount it. You will need to do 'startup nomount' before you
can restore the controlfile using RMAN. Otherwise use 'reset
database to incarnation <key>' make the intended incarnation
current in the recovery catalog.

Please add more information about this Error

TNS-03505: Failed to resolve name

1 Answers  

---

TNS-12590: TNS:no I/O buffer

1 Answers  

---

ORA-00235: controlfile fixed table inconsistent due to concurrent update

1 Answers  

---

ORA-19860: piece validation cannot be performed more than once

1 Answers  

---

ORA-32165: Cannot get XA environment

1 Answers  

---

PCC-02417: Illegal type conversion between attribute and host variable

1 Answers  

---

ORA-13117: [string]_RELATION$ table does not exist

1 Answers  

---

AUD-00802: name of index is limited to 22 characters

1 Answers  

---

SQL*Loader-00287: No control file name specified.

1 Answers  

---

ORA-36806: (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string.

1 Answers  

---

RMAN-06078: the controlfile is older than datafile string

1 Answers  

---

ORA-22627: tc [string] must be that of object/varray/nested table

1 Answers  

---