RMAN-06430: recovery catalog userid cannot be SYS

RMAN-06430: recovery catalog userid cannot be SYS

Cause: A recovery catalog connection was made to userid SYS. The recovery catalog must be created in a userid other than SYS.

Action: Specify a different userid in the CATALOG connect string.

RMAN-06429: %s database is not compatible with this version of RMAN

RMAN-06429: %s database is not compatible with this version of RMAN

Cause: The indicated database is not compatible with this version of the Recovery Manager (RMAN). Other messages have also been issued which detail the cause of the error.

Action: See the other messages. If the database is CATALOG, then you may be able to use the CREATE CATALOG or UPGRADE CATALOG commands to correct the problem. If the database is TARGET or AUXILIARY, then you must either upgrade the target database or use a newer version of the RMAN executable.

RMAN-06428: recovery catalog is not installed

RMAN-06428: recovery catalog is not installed

Cause: A recovery catalog database connection has been made, but the recovery catalog tables and views have not been installed.

Action: If you mis-typed the recovery catalog owner userid, then correct the userid and reconnect to the recovery catalog. If this is the first time that you have signed on to Recovery Manager with this recovery catalog owner userid, then use the CREATE CATALOG command to create the recovery catalog schema. Alternatively, exit RMAN and connect without specifying a recovery catalog connection.

RMAN-06427: recovery catalog already exists

RMAN-06427: recovery catalog already exists

Cause: The CREATE CATALOG command cannot be used when the recovery catalog already exists.

Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog to the most current release without losing any existing backup data. Use the DROP CATALOG command to remove an existing recovery catalog.

RMAN-06426: RECOVERY_CATALOG_OWNER role must be granted to user string

RMAN-06426: RECOVERY_CATALOG_OWNER role must be granted to user string

Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the userid that was supplied in the CATALOG connect string does not have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role.

Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog owner.

RMAN-06425: lamp;lt;lamp;nbsp;datafile pathname not availablelamp;gt;

RMAN-06425: lamp;lt;lamp;nbsp;datafile pathname not availablelamp;gt;

Cause: This is an informational message only.

Action: No action is required.

RMAN-06424: error while looking up proxy copy

RMAN-06424: error while looking up proxy copy

Cause: An error occurred while looking up the specified proxy copy in the recovery catalog or target database control file.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the proxy copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06746: backup cancelled because all files were skipped

RMAN-06746: backup cancelled because all files were skipped

Cause: All files for this backup set were skipped, therefore no backup no backup set was created.

Action: This message is informational only.

RMAN-06745: skipping datafile copy string; already backed up string time(s)

RMAN-06745: skipping datafile copy string; already backed up string time(s)

Cause: The indicated datafile copy was not included in the backup set because it was already backed up on the device requested.

Action: Use FORCE option to override backup optimization.

RMAN-06744: specification does not match any datafile copy in the repository

RMAN-06744: specification does not match any datafile copy in the repository

Cause: The specified datafilecopies are not found in the repository.

Action: Verify datafile copy existence and retry the command.

RMAN-06743: specification does not match any backupset in the repository

RMAN-06743: specification does not match any backupset in the repository

Cause: The specified backupsets are not found in the repository.

Action: Verify backupset existence and retry the command.

RMAN-06742: platform name string longer than number

RMAN-06742: platform name string longer than number

Cause: The specified platform name exceeds the maximum allowable platform name.

Action: Correct the platform name.

RMAN-06741: database name is string and DBID is string

RMAN-06741: database name is string and DBID is string

Cause: This is an informational message only.

Action: No action is required.

RMAN-06740: database name is not specified

RMAN-06740: database name is not specified

Cause: The UNREGISTER DATABASE command failed because of the following: o RMAN is not connected to the target database o The database name is not specified in the command o DBID is not set with the SET DBID command

Action: Any one of the following actions will fix the problem: o Connect to the target database o Specify database name o Set DBID with SET DBID command

RMAN-06739: database string is not found in the recovery catalog

RMAN-06739: database string is not found in the recovery catalog

Cause: The UNREGISTER DATABASE command was used with a database name that was not found in the recovery catalog.

Action: Make sure the database name specified in the DROP DATABASE command syntax is correct.

RMAN-06738: database name string is not unique in the recovery catalog

RMAN-06738: database name string is not unique in the recovery catalog

Cause: The UNREGISTER DATABASE command was used with a database name that is ambiguous.

Action: Use the SET DBID command to specify the database id and resolve the ambiguity.

RMAN-06737: database name string does not match target database name string

RMAN-06737: database name string does not match target database name string

Cause: The UNREGISTER DATABASE command was used with a database name that does not match the name of the database to which RMAN is connected.

Action: Specify the correct database name or avoid specifying the database name when connected to the target database.

RMAN-06736: Do you really want to unregister the database (enter YES or NO)?

RMAN-06736: Do you really want to unregister the database (enter YES or NO)?

Cause: This is a user prompt.

Action: Answer the question to proceed.

RMAN-06735: Do you really want to drop the database (enter YES or NO)?

RMAN-06735: Do you really want to drop the database (enter YES or NO)?

Cause: This is a user prompt.

Action: Answer the question to proceed.

RMAN-06734: Do you really want to drop all backups and the database (enter YES or NO)?

RMAN-06734: Do you really want to drop all backups and the database (enter YES or NO)?

Cause: This is a user prompt.

Action: Answer the question to proceed.

RMAN-06733: database unregistered from the recovery catalog

RMAN-06733: database unregistered from the recovery catalog

Cause: This is an informational message only.

Action: No action is required.

RMAN-06732: database dropped

RMAN-06732: database dropped

Cause: This is an informational message only.

Action: No action is required.

RMAN-06731: command string:string%% complete, time left number:number:number

RMAN-06731: command string:string%% complete, time left number:number:number

Cause: This is an informational message only.

Action: No action is required.

RMAN-06730: no channel to restore a backup of the SPFILE

RMAN-06730: no channel to restore a backup of the SPFILE

Cause: A SPFILE restore could not proceed because the backup on a device type that was not allocated for restore.

Action: No action required, this is an informational message only. See message 6026 for further details.

RMAN-06729: no backup of the SPFILE found to restore

RMAN-06729: no backup of the SPFILE found to restore

Cause: A SPFILE restore could not proceed because no backup of the SPFILE was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user s restore operands.

Action: Modify options for the SPFILE restore.

RMAN-06728: could not locate control file copy string

RMAN-06728: could not locate control file copy string

Cause: The specified control file copy could not be found on any allocated channel.

Action: Allocate additional channels on other nodes of the cluster, or if the control file copy have been deleted, use the CROSSCHECK CONTROLFILECOPY command to correct the recovery catalog entries.

RMAN-06727: could not locate datafile copy string

RMAN-06727: could not locate datafile copy string

Cause: The specified datafile copy could not be found on any allocated channel.

Action: Allocate additional channels on other nodes of the cluster, or if the datafile copy have been deleted, use the CROSSCHECK DATAFILECOPY command to correct the recovery catalog entries.

RMAN-06726: could not locate archivelog string

RMAN-06726: could not locate archivelog string

Cause: The specified archivelog could not be found on any allocated channel.

Action: Allocate additional channels on other nodes of the cluster, or, if the archived logs have been deleted, use the CROSSCHECK ARCHIVELOG command to correct the recovery catalog entries.

RMAN-06725: database not open: sort area size too small

RMAN-06725: database not open: sort area size too small

Cause: sort area size too small to execute RMAN commands.

Action: open the database or increase sort_area_size.

RMAN-06724: backup not done; all files already backed up

RMAN-06724: backup not done; all files already backed up

Cause: A BACKUP command does not need to backup any files, because all of the files to backup are already backed up.

Action: No action required, this is an informational message only.

RMAN-06723: file string (string bytes) updated in catalog

RMAN-06723: file string (string bytes) updated in catalog

Cause: This is an informational message only.

Action: No action is required.

RMAN-06722: unable to remove file string from catalog

RMAN-06722: unable to remove file string from catalog

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Follow actions for other messages.

RMAN-06721: could not normalize path for file: string

RMAN-06721: could not normalize path for file: string

Cause: An error was encountered when trying to normalize the pathname for the specified file.

Action: Ensure that the path is correct.

RMAN-06720: file string removed from catalog

RMAN-06720: file string removed from catalog

Cause: This is an informational message only.

Action: No action is required.

RMAN-06719: file string (string bytes) restrieved from catalog

RMAN-06719: file string (string bytes) restrieved from catalog

Cause: This is an informational message only.

Action: No action is required.

RMAN-06718: could not find file string in catalog

RMAN-06718: could not find file string in catalog

Cause: The filename provided was not found in the catalog.

Action: The specified file is not stored in the catalog, or it is stored with a different path than the one provided. Specify the filename as stored in the catalog.

RMAN-06717: number of source files (string) and destination files (string) does not match

RMAN-06717: number of source files (string) and destination files (string) does not match

Cause: The number of files to retrieve from the catalog does not match the number of destinations specified.

Action: Ensure that the number of files to be retrieved matches the number of destinations specified.

RMAN-06716: skipping datafile number; already restored to file string

RMAN-06716: skipping datafile number; already restored to file string

Cause: Recovery Manager determined that this file is already restored. Use FORCE option to override this optimization.

Action: No action required, this is an informational message only.

RMAN-06711: global scripts require a target connection

RMAN-06711: global scripts require a target connection

Cause: Connection to a target database was not specified.

Action: Provide a target connection and retry the command.

RMAN-06710: script string not found in catalog

RMAN-06710: script string not found in catalog

Cause: An attempt was made to call a script that could not be found in the target database or as a global script in the specified catalog.

Action: Verify the script name and retry the command.

RMAN-06709: No scripts in recovery catalog

RMAN-06709: No scripts in recovery catalog

Cause: An attempt was made to list the scripts in the catalog, but no scripts could be found in the specified recovery catalog.

Action: No action required, this is an informational message only.

RMAN-06708: short write while writing file string . Wrote string bytes instead of string bytes

RMAN-06708: short write while writing file string . Wrote string bytes instead of string bytes

Cause: An attempt was made to write to a file system that was full.

Action: Ensure that the file system has room for the file. Check system logs.

RMAN-06707: could not initialize for output file: string

RMAN-06707: could not initialize for output file: string

Cause: An error was encountered when trying to initialize the specified file for output.

Action: Ensure that the file exists.

RMAN-06706: could not close file: string (reason=string)

RMAN-06706: could not close file: string (reason=string)

Cause: An error was encountered when trying to close the specified file.

Action: Ensure that the file has correct permissions and still exists.

RMAN-06705: text script line is too long (lamp;gt;1024)

RMAN-06705: text script line is too long (lamp;gt;1024)

Cause: A text script contained a line longer than the permitted maximum length.

Action: Split the line in smaller lines an retry the operation.

RMAN-06703: could not open file: string (reason=string)

RMAN-06703: could not open file: string (reason=string)

Cause: An error was encountered when trying to open the specified file.

Action: Ensure that the file has correct permissions.

RMAN-06702: could not initialize for input file: string

RMAN-06702: could not initialize for input file: string

Cause: An error was encountered when trying to initialize the specified file for input.

Action: Ensure that the file exists.

RMAN-06701: could not construct path for file: string

RMAN-06701: could not construct path for file: string

Cause: An error was encountered when trying to construct the full pathname for the specified file.

Action: Ensure that the path is correct.

RMAN-06700: error parsing text script in file string

RMAN-06700: error parsing text script in file string

Cause: Incorrect syntax or invalid commands were found.

Action: Fix text script and retry the command.

RMAN-06610: For record type string recids from number to number are re-used before resync

RMAN-06610: For record type string recids from number to number are re-used before resync

Cause: This messages is issued when the control file records were re-used before resyncing to catalog database.

Action: Increase control_file_keep_record_time setting or issue BACKUP command that it will generate fewer control file records, e.g., backup few tablespaces instead of the complete database in one BACKUP command.

RMAN-06609: AS COPY can be configured only for disk device

RMAN-06609: AS COPY can be configured only for disk device

Cause: The AS COPY option was specified for non disk device.

Action: Remove the AS COPY option and resubmit the command.

RMAN-06608: RMAN configuration has no stored or default parameters

RMAN-06608: RMAN configuration has no stored or default parameters

Cause: This message is issued in response to a SHOW command.

Action: No action is required, this is an informational message only.

RMAN-06607: RMAN configuration parameters are:

RMAN-06607: RMAN configuration parameters are:

Cause: This message is issued in response to a SHOW command.

Action: No action is required, this is an informational message only.

RMAN-06606: RMAN configuration parameters are successfully reset to default value

RMAN-06606: RMAN configuration parameters are successfully reset to default value

Cause: This message is issued in response to a CONFIGURE command.

Action: No action is required, this is an informational message only.

RMAN-06605: old RMAN configuration parameters are successfully deleted

RMAN-06605: old RMAN configuration parameters are successfully deleted

Cause: This message is issued in response to a CONFIGURE command.

Action: No action is required, this is an informational message only.

RMAN-06604: new RMAN configuration parameters are successfully stored

RMAN-06604: new RMAN configuration parameters are successfully stored

Cause: This message is issued in response to a CONFIGURE command.

Action: No action is required, this is an informational message only.

RMAN-06601: new RMAN configuration parameters:

RMAN-06601: new RMAN configuration parameters:

Cause: This message is issued in response to a CONFIGURE command.

Action: No action is required, this is an informational message only.

RMAN-06600: old RMAN configuration parameters:

RMAN-06600: old RMAN configuration parameters:

Cause: This message is issued in response to a CONFIGURE command.

Action: No action is required, this is an informational message only.

RMAN-06599: tablespace string is not read-only

RMAN-06599: tablespace string is not read-only

Cause: A conversion was attempted on a tablespace which is not read-only.

Action: Change the tablespace to read-only and retry the operation.

RMAN-06598: conversion between platforms string and string is not needed

RMAN-06598: conversion between platforms string and string is not needed

Cause: Conversion of Oracle data files between the specified platforms was not necessary because the Oracle data file format is already the same on both platforms.

Action: Do not do the conversion.