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

ORA-01256: error in locking database file string

1 Answers  

---

ORA-09364: Windows 3.1 Two-Task driver unable to create hidden window

1 Answers  

---

ORA-06434: ssaio: read error, unable to read requested block from database file.

1 Answers  

---

NNL-00893: Similar requests received: number

1 Answers  

---

IMP-00083: dump file does not contain an incremental export

1 Answers  

---

TNS-00125: Failed to get number of Interchanges in TNSNET.ORA

1 Answers  

---

ORA-00303: cannot process Parallel Redo

1 Answers  

---

ORA-07257: spdcr: translation error expanding program name.

2 Answers  

---

ORA-14311: Expecting VALUES LESS THAN or AT clause

1 Answers  

---

ORA-01573: shutting down instance, no further change allowed

1 Answers  

---

NID-00503: DBNAME New database name (NONE)

1 Answers  

---

ORA-25463: table alias not specified

1 Answers  

---