Answer / guest

Cause: While a media recovery was active, a new incarnation
was detected by the server due to inspection or cataloging
of archived logs or backup files.

Action: If you want recovery to use the new incarnation,
restart recovery. This is the most common action on a
standby database when resetlogs is done in primary. If you
do not want recovery to use the new incarnation, change the
recovery destination using RMAN's RESET DATABASE TO
INCARNATION <incarnation#> command. To see which
incarnations are available for this target database, query
V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.

Please add more information about this Error

PCB-00400: %s

1 Answers  

---

PLS-01415: Use of aggregate value here

1 Answers  

---

TNS-12210: TNS:error in finding Navigator data

1 Answers  

---

KUP-04005: file operation successful

1 Answers  

---

DRG-50904: weight string outside valid range 0.1 to 10.0

1 Answers  

---

ORA-19566: exceeded limit of string corrupt blocks for file string

1 Answers  

---

ORA-14327: Some index [sub]partitions could not be rebuilt

1 Answers  

---

ORA-13454: GeoRaster metadata is invalid

1 Answers  

---

ORA-15048: ASM internal files cannot be deleted

1 Answers  

---

RMAN-06561: available space must be larger than number kb

1 Answers  

---

ORA-36716: (XSMXALLOC04) You can only use the ACROSS phrase when allocation BASIS workspace object is a FORMULA.

1 Answers  

---

DRG-50301: server error reading request queue

1 Answers  

---