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

RMAN-06121: uncataloged controlfile copy

1 Answers  

---

NZE-28853: Initialization failure

1 Answers  

---

RMAN-06491: controlfile autobackup format "string" contains more than one "string" format specifier

1 Answers  

---

NNF-03003: Format error parsing server response

1 Answers  

---

ORA-28152: proxy user 'string' may not specify initial role 'string' on behalf of client 'string'

1 Answers  

---

ORA-14098: index mismatch for tables in ALTER TABLE EXCHANGE PARTITION

1 Answers  

---

NCR-03007: NCRO: Context is busy

1 Answers  

---

NNL-01003: NON LEAF responses received: number

1 Answers  

---

TNS-00143: Illegal PREFERRED_CMANAGERS entry in TNSNAV.ORA

1 Answers  

---

NNL-00559: Shows, sets, or cancels the time for the next cache dump to the trace file

1 Answers  

---

ORA-01149: cannot shutdown - file string has online backup set

2 Answers  

---

TNS-12234: TNS:Redirect to destination

1 Answers  

---