RMAN-06442: enter UPGRADE CATALOG command again to confirm
catalog upgrade
- 1 Answers
- 2340 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-01615: instance string (thread string) is mounted - cannot disable
QSM-02017: subquery present in the HAVING clause
PCC-02200: found unrecognized punctuation sequence
PCC-00120: File I/O error during code generation
ORA-13190: recursive SQL fetch failed
ORA-00084: global area must be PGA, SGA, or UGA
AMD-00100: not found: string "string"
RMAN-06083: error when loading stored script string
ORA-10631: SHRINK clause should not be specified for this object
SQL*Loader-00401: End field position number must be greater than or equal to start number
ORA-01526: error in opening file 'string'
KUP-04082: error converting field string for LOBFILE column string
Oracle Errors 
