RMAN-06451: proxy copy handle=string recid=string stamp=string
Cause: This is an informational message.
Action: No action required.
Category Archives: RMAN Database Error Messages
RMAN-06450: crosschecked proxy copy: found to be ‘string’
RMAN-06450: crosschecked proxy copy: found to be 'string'
Cause: This is an informational message.
Action: No action required.
RMAN-06449: deleted proxy copy
RMAN-06449: deleted proxy copy
Cause: This is an informational message.
Action: No action required.
RMAN-06448: uncataloged proxy copy
RMAN-06448: uncataloged proxy copy
Cause: This is an informational message.
Action: No action required.
RMAN-06447: changed proxy copy available
RMAN-06447: changed proxy copy available
Cause: This is an informational message.
Action: No action required.
RMAN-06446: changed proxy copy unavailable
RMAN-06446: changed proxy copy unavailable
Cause: This is an informational message.
Action: No action required.
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used
Cause: The CONNECT CATALOG command was used after the user had already specified the NOCATALOG option.
Action: Re-start RMAN if you wish to use a recovery catalog.
RMAN-06444: string created with compilation errors
RMAN-06444: string created with compilation errors
Cause: During the CREATE CATALOG or UPGRADE CATALOG command, the indicated PL/SQL package specification or body could not be created because of PL/SQL compilation errors.
Action: The PL/SQL packages used by the recovery catalog are located in the RECOVER.BSQ library file, and should never be modified. Make sure that the RECOVER.BSQ file has not been modified or damaged, and then if this error persists, contact Oracle Support Services. Connect to the recovery catalog owner and query the USER_ERRORS view to find out the details of the compilation errors.
RMAN-06443: error upgrading recovery catalog
RMAN-06443: error upgrading recovery catalog
Cause: An error was received from the recovery catalog database while upgrading the recovery catalog.
Action: Correct the error and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'column already exists,' which can happen if the recovery catalog has already been partially upgraded. Only serious errors will be displayed while upgrading the recovery catalog.
RMAN-06442: enter UPGRADE CATALOG command again to confirm catalog upgrade
RMAN-06442: enter UPGRADE CATALOG command again to confirm catalog upgrade
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 Oracle9i Database Migration or 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.