Answer / guest

Cause: The UPGRADE CATALOG command alters the recovery
catalog schema. Although the recovery catalog is designed to
be compatible with older versions of the Recovery Manager
(RMAN), it is possible that an upgrade will remove support
for older versions of RMAN.

Action: If you really want to upgrade the recovery catalog,
then enter the UPGRADE CATALOG command again. If you are not
going to use an older version of RMAN with this recovery
catalog, then compatibility is not an issue. If you plan to
also continue using an older version of RMAN with this
recovery catalog then, before upgrading, consult the
Migration Guide for the current Oracle release to determine
if upgrading to the current version of the recovery catalog
will remove support for older versions of RMAN.

Please add more information about this Error

LPX-00201: unknown encoding "~s"

1 Answers  

---

NZE-28839: no persona descriptor

1 Answers  

---

ORA-29809: cannot drop an operator with dependent objects

1 Answers  

---

ORA-30933: Element 'string' may not appear at this point within parent 'string'

1 Answers  

---

ORA-13013: the specified topology was not INTERIOR or BOUNDARY

1 Answers  

---

ORA-25405: transaction status unknown

1 Answers  

---

DRG-11510: encountered unrecoverable error on line string

1 Answers  

---

QSM-02122: compatibility mode must be 8.1 or higher

1 Answers  

---

ORA-02851: Request list is empty when it should not be

1 Answers  

---

PLS-00408: duplicate column 'string' not permitted in INSERT or UPDATE

1 Answers  

---

ORA-24028: cannot create a reciever non-repudiable single consumer queue

1 Answers  

---

ORA-15021: parameter "string" is not valid in string instance

1 Answers  

---