RMAN-06197: Total System Global Area string bytes
Cause: This is an informational message only.
Action: No action is required.
Cause: This is an informational message only.
Action: No action is required.
RMAN-06196: Oracle instance started
RMAN-06196: Oracle instance started
Cause: A STARTUP command completed successfully.
Action: None, this is an informational message.
Cause: A STARTUP command completed successfully.
Action: None, this is an informational message.
RMAN-06195: auxiliary database not started
RMAN-06195: auxiliary database not started
Cause: A command was issued that requires the auxiliary database instance be started.
Action: Issue a STARTUP AUXILIARY command.
Cause: A command was issued that requires the auxiliary database instance be started.
Action: Issue a STARTUP AUXILIARY command.
RMAN-06194: target database instance not started
RMAN-06194: target database instance not started
Cause: A command was issued that requires the target database instance be started.
Action: Issue a STARTUP command to start the instance.
Cause: A command was issued that requires the target database instance be started.
Action: Issue a STARTUP command to start the instance.
RMAN-06193: connected to target database (not started)
RMAN-06193: connected to target database (not started)
Cause: This is an informational message only.
Action: The database must be started before any other RMAN commands are issued.
Cause: This is an informational message only.
Action: The database must be started before any other RMAN commands are issued.
RMAN-06192: maximum value for MAXPIECESIZE or MAXSETSIZE must be between 1 Kb and 2048 Gb
RMAN-06192: maximum value for MAXPIECESIZE or MAXSETSIZE must be between 1 Kb and 2048 Gb
Cause: Input size for MAXPIECESIZE or MAXSETSIZE was out of range.
Action: Specify a valid size and retry the command.
Cause: Input size for MAXPIECESIZE or MAXSETSIZE was out of range.
Action: Specify a valid size and retry the command.
RMAN-06191: PL or SQL package string.string version string in string database is too new
RMAN-06191: PL or SQL package string.string version string in string database is too new
Cause: RMAN detected an incompatible version of the specified package.
Action: Use a newer version of recovery manager. Message 6439 indicates the minimum required version of recovery manager.
Cause: RMAN detected an incompatible version of the specified package.
Action: Use a newer version of recovery manager. Message 6439 indicates the minimum required version of recovery manager.
RMAN-06190: PL or SQL package string.string version string in string database is not current
RMAN-06190: PL or SQL package string.string version string in string database is not current
Cause: RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode.
Action: No action is required, but certain features and bug-fixes may not be available when RMAN runs in backwards-compatible mode. If the database is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are dbmsrman.sql and prvtrman.plb.
Cause: RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode.
Action: No action is required, but certain features and bug-fixes may not be available when RMAN runs in backwards-compatible mode. If the database is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are dbmsrman.sql and prvtrman.plb.
RMAN-06189: current DBID number does not match target mounted database (number)
RMAN-06189: current DBID number does not match target mounted database (number)
Cause: SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected.
Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN.
Cause: SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected.
Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN.
RMAN-06188: cannot use command when connected to a mounted target database
RMAN-06188: cannot use command when connected to a mounted target database
Cause: An attempt was made to issue a command that can be used only when there is no connection to the target database or when the target database is not mounted.
Action: Dismount the database or restart RMAN and use the command before connecting to the target database.
Cause: An attempt was made to issue a command that can be used only when there is no connection to the target database or when the target database is not mounted.
Action: Dismount the database or restart RMAN and use the command before connecting to the target database.
RMAN-06187: control file copy string not found or out of sync with catalog
RMAN-06187: control file copy string not found or out of sync with catalog
Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.
Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.
RMAN-06186: PL or SQL package string.string version string in string database is too old
RMAN-06186: PL or SQL package string.string version string in string database is too old
Cause: The specified PL or SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN).
Action: If the database indicated is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN.
Cause: The specified PL or SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN).
Action: If the database indicated is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN.
RMAN-06185: Recovery Manager incompatible with string database: RMAN number.number.number.number to number.number.number.number required
RMAN-06185: Recovery Manager incompatible with string database: RMAN number.number.number.number to number.number.number.number required
Cause: This version of recovery manager was incompatible with the indicated database or the dbms_backup_restore package installed in the indicated database.
Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary. Otherwise, use a version of RMAN within the range specified in the error message.
Cause: This version of recovery manager was incompatible with the indicated database or the dbms_backup_restore package installed in the indicated database.
Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary. Otherwise, use a version of RMAN within the range specified in the error message.
RMAN-06184: duplicate object in backup specifier: string string
RMAN-06184: duplicate object in backup specifier: string string
Cause: A backup command specifies the same datafile or copy of a datafile multiple times.
Action: Eliminate the duplicates.
Cause: A backup command specifies the same datafile or copy of a datafile multiple times.
Action: Eliminate the duplicates.
RMAN-06183: datafile or datafile copy larger than MAXSETSIZE: file# string string
RMAN-06183: datafile or datafile copy larger than MAXSETSIZE: file# string string
Cause: A BACKUP DATAFILE(copy) command specified the MAXSETSIZE operand too low. The specified datafile is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.
Cause: A BACKUP DATAFILE(copy) command specified the MAXSETSIZE operand too low. The specified datafile is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.
RMAN-06182: archive log larger than MAXSETSIZE: thread string seq string string
RMAN-06182: archive log larger than MAXSETSIZE: thread string seq string string
Cause: A BACKUP ARCHIVELOG command specified the MAXSETSIZE operand too low. The specified archive log is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.
Cause: A BACKUP ARCHIVELOG command specified the MAXSETSIZE operand too low. The specified archive log is larger than MAXSETSIZE will allow.
Action: Increase MAXSETSIZE limit.
RMAN-06181: multiple channels require Enterprise Edition
RMAN-06181: multiple channels require Enterprise Edition
Cause: Attempt to allocate more than 1 channel in a job.
Action: Remove all except one ALLOCATE CHANNEL command.
Cause: Attempt to allocate more than 1 channel in a job.
Action: Remove all except one ALLOCATE CHANNEL command.
RMAN-06180: incremental backups require Enterprise Edition
RMAN-06180: incremental backups require Enterprise Edition
Cause: A BACKUP command with INCREMENTAL LEVEL lamp;gt; 0 was specified.
Action: Use FULL, or INCREMENTAL LEVEL 0.
Cause: A BACKUP command with INCREMENTAL LEVEL lamp;gt; 0 was specified.
Action: Use FULL, or INCREMENTAL LEVEL 0.
RMAN-06179: datafile number not processed because file is read-only
RMAN-06179: datafile number not processed because file is read-only
Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point in time.
Action: None, informational message only
Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point in time.
Action: None, informational message only
RMAN-06178: datafile number not processed because file is offline
RMAN-06178: datafile number not processed because file is offline
Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point in time.
Action: None, informational message only
Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point in time.
Action: None, informational message only
RMAN-06177: restore not done; all files readonly, offline, or already restored
RMAN-06177: restore not done; all files readonly, offline, or already restored
Cause: A RESTORE command does not need to restore any files, because all of the files to be restored are offline, read-only, or are already restored to their correct destinations.
Action: None, informational message only
Cause: A RESTORE command does not need to restore any files, because all of the files to be restored are offline, read-only, or are already restored to their correct destinations.
Action: None, informational message only
RMAN-06176: no recovery required; all files are readonly or offline
RMAN-06176: no recovery required; all files are readonly or offline
Cause: A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the system tablespace.
Action: None, informational message only
Cause: A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the system tablespace.
Action: None, informational message only
RMAN-06175: deleted script: string
RMAN-06175: deleted script: string
Cause: A DELETE SCRIPT command was executed.
Action: None, informational message only.
Cause: A DELETE SCRIPT command was executed.
Action: None, informational message only.
RMAN-06174: not connected to auxiliary database
RMAN-06174: not connected to auxiliary database
Cause: An auxiliary command was issued but no connection to a auxiliary database has been established.
Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database.
Cause: An auxiliary command was issued but no connection to a auxiliary database has been established.
Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database.
RMAN-06173: no set newname command has been issued for datafile string when restore auxiliary
RMAN-06173: no set newname command has been issued for datafile string when restore auxiliary
Cause: Auxiliary type was specified for the control file, but no SET NEWNAME command has been previously issued for a datafile.
Action: Issue SET NEWNAME command for every datafile in the recovery set.
Cause: Auxiliary type was specified for the control file, but no SET NEWNAME command has been previously issued for a datafile.
Action: Issue SET NEWNAME command for every datafile in the recovery set.
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
Cause: A restore could not proceed because no autobackup was found or specified handle is not a valid copy or backup piece. In case of restore from autobackup, it may be the case that a backup exists, but it does not satisfy the criteria specified in the user s restore operands. In case of restore from handle, it may be the handle is not a backup piece or controflile copy. In may be that it does not exist.
Action: Modify autobackup search criteria or verify the handle.
Cause: A restore could not proceed because no autobackup was found or specified handle is not a valid copy or backup piece. In case of restore from autobackup, it may be the case that a backup exists, but it does not satisfy the criteria specified in the user s restore operands. In case of restore from handle, it may be the handle is not a backup piece or controflile copy. In may be that it does not exist.
Action: Modify autobackup search criteria or verify the handle.
RMAN-06171: not connected to target database
RMAN-06171: not connected to target database
Cause: A command was issued but no connection to the target database has been established.
Action: Issue a CONNECT TARGET command to connect to the target database.
Cause: A command was issued but no connection to the target database has been established.
Action: Issue a CONNECT TARGET command to connect to the target database.
RMAN-06170: no control file copy found with offline range recid string stamp string datafile string
RMAN-06170: no control file copy found with offline range recid string stamp string datafile string
Cause: This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current control file and no control file copy with the record could be accessed. At least 1 control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.
Action: Query the rc_controlfile_copy view for the names of all control file copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command.
Cause: This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current control file and no control file copy with the record could be accessed. At least 1 control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.
Action: Query the rc_controlfile_copy view for the names of all control file copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command.
RMAN-06168: no backup pieces with this tag found: string
RMAN-06168: no backup pieces with this tag found: string
Cause: A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found.
Action: Make sure the tag is specified correctly.
Cause: A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found.
Action: Make sure the tag is specified correctly.
RMAN-06167: already connected
RMAN-06167: already connected
Cause: a CONNECT command was issued, but RMAN is already connected to the specified database.
Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.
Cause: a CONNECT command was issued, but RMAN is already connected to the specified database.
Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.
RMAN-06166: datafile string cannot be recovered
RMAN-06166: datafile string cannot be recovered
Cause: Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists.
Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a point-in-time recovery may be possible.
Cause: Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists.
Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a point-in-time recovery may be possible.
RMAN-06165: datafile string is too old to recover, restore a more recent copy
RMAN-06165: datafile string is too old to recover, restore a more recent copy
Cause: The archived logs and or or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered.
Action: Issue a RESTORE for the datafile, then reissue the RECOVER command.
Cause: The archived logs and or or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered.
Action: Issue a RESTORE for the datafile, then reissue the RECOVER command.
RMAN-06164: WARNING: no channel of required type allocated to recover datafile number
RMAN-06164: WARNING: no channel of required type allocated to recover datafile number
Cause: A RECOVER command could not proceed because incremental backup sets or archive log backup sets exist on a device type that has not been allocated.
Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.
Cause: A RECOVER command could not proceed because incremental backup sets or archive log backup sets exist on a device type that has not been allocated.
Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.
RMAN-06163: some datafiles cannot be recovered, aborting the RECOVER command
RMAN-06163: some datafiles cannot be recovered, aborting the RECOVER command
Cause: This message should be followed by one or more 6162 or 6164 messages.
Action: Check the accompanying errors.
Cause: This message should be followed by one or more 6162 or 6164 messages.
Action: Check the accompanying errors.
RMAN-06162: sql statement: string
RMAN-06162: sql statement: string
Cause: This is the sql statement about to be executed for a SQL command.
Action: None, informational message only.
Cause: This is the sql statement about to be executed for a SQL command.
Action: None, informational message only.
RMAN-06161: error when inspecting auxiliary filename: string
RMAN-06161: error when inspecting auxiliary filename: string
Cause: This error is accompanied by other errors explaining the cause.
Action: Correct the auxiliary filename if it is wrong via the CONFIGURE AUXNAME command.
Cause: This error is accompanied by other errors explaining the cause.
Action: Correct the auxiliary filename if it is wrong via the CONFIGURE AUXNAME command.
RMAN-06160: no backup pieces found for backup set key: number
RMAN-06160: no backup pieces found for backup set key: number
Cause: No backup pieces for the requested backup set were found in the recovery catalog, or the target database control file.
Action: Specify an existing backup set.
Cause: No backup pieces for the requested backup set were found in the recovery catalog, or the target database control file.
Action: Specify an existing backup set.
RMAN-06159: error while looking up backup set
RMAN-06159: error while looking up backup set
Cause: An error occurred while looking up the specified backup set 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 key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: An error occurred while looking up the specified backup set 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 key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.
RMAN-06158: validation succeeded for archived log
RMAN-06158: validation succeeded for archived log
Cause: The CROSSCHECK ARCHIVELOG command determined that the archived log still matches its data.
Action: None -this is an informational message.
Cause: The CROSSCHECK ARCHIVELOG command determined that the archived log still matches its data.
Action: None -this is an informational message.
RMAN-06157: validation failed for archived log
RMAN-06157: validation failed for archived log
Cause: The CROSSCHECK ARCHIVELOG command determined that the archived log could not be found or no longer contained the same data, so its record was marked expired.
Action: None -this is an informational message.
Cause: The CROSSCHECK ARCHIVELOG command determined that the archived log could not be found or no longer contained the same data, so its record was marked expired.
Action: None -this is an informational message.
RMAN-06156: validation succeeded for control file copy
RMAN-06156: validation succeeded for control file copy
Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy still matches its data in the recovery catalog.
Action: None -this is an informational message.
Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy still matches its data in the recovery catalog.
Action: None -this is an informational message.
RMAN-06155: validation failed for control file copy
RMAN-06155: validation failed for control file copy
Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None -this is an informational message.
Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None -this is an informational message.
RMAN-06154: validation succeeded for datafile copy
RMAN-06154: validation succeeded for datafile copy
Cause: The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy still matches its data in the recovery catalog.
Action: None -this is an informational message.
Cause: The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy still matches its data in the recovery catalog.
Action: None -this is an informational message.
RMAN-06153: validation failed for datafile copy
RMAN-06153: validation failed for datafile copy
Cause: The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None -this is an informational message.
Cause: The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog.
Action: None -this is an informational message.
RMAN-06151: datafile string creation scn string
RMAN-06151: datafile string creation scn string
Cause: This is an informational message. It should be accompanied by other messages.
Action: none
Cause: This is an informational message. It should be accompanied by other messages.
Action: none
RMAN-06150: auxiliary name for datafile number set to: string
RMAN-06150: auxiliary name for datafile number set to: string
Cause: This message is issued in response to a CONFIGURE AUXNAME command.
Action: None -this is an informational message.
Cause: This message is issued in response to a CONFIGURE AUXNAME command.
Action: None -this is an informational message.
RMAN-06148: redundancy count must be greater than zero
RMAN-06148: redundancy count must be greater than zero
Cause: The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.
Cause: The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.
RMAN-06147: no obsolete backups found
RMAN-06147: no obsolete backups found
Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness.
Action: None -this is an informational message.
Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness.
Action: None -this is an informational message.
RMAN-06146: changes found for file number beyond offline SCN
RMAN-06146: changes found for file number beyond offline SCN
Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database control file, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database control file is not really current, but is a restored copy of an older control file.
Action: Mount a current control file or a backup control file.
Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database control file, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database control file is not really current, but is a restored copy of an older control file.
Action: Mount a current control file or a backup control file.
RMAN-06145: control file is not current - obsolete file list may be incomplete
RMAN-06145: control file is not current - obsolete file list may be incomplete
Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted control file is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS.
Action: No action need be taken - this is an informational message only. To ensure a complete report of obsolete backups, mount a current control file.
Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted control file is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS.
Action: No action need be taken - this is an informational message only. To ensure a complete report of obsolete backups, mount a current control file.
RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION
RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION
Cause: The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation.
Action: Remove the FROM or UNTIL option and re-run the LIST command.
Cause: The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation.
Action: Remove the FROM or UNTIL option and re-run the LIST command.
RMAN-06143: LIKE may only be specified with COPY
RMAN-06143: LIKE may only be specified with COPY
Cause: The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, control files or archive logs have file names that may be tested with a LIKE operand.
Action: Remove the LIKE option and re-run the RMAN command.
Cause: The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, control files or archive logs have file names that may be tested with a LIKE operand.
Action: Remove the LIKE option and re-run the RMAN command.
RMAN-06142: DEVICE TYPE cannot be specified with this command
RMAN-06142: DEVICE TYPE cannot be specified with this command
Cause: The DEVICE TYPE option was specified with a command that does not support it.
Action: Remove the DEVICE TYPE option and re-run the command.
Cause: The DEVICE TYPE option was specified with a command that does not support it.
Action: Remove the DEVICE TYPE option and re-run the command.
RMAN-06141: cannot specify ARCHIVELOG LIKE option with RESTORE
RMAN-06141: cannot specify ARCHIVELOG LIKE option with RESTORE
Cause: The ARCHIVELOG LIKE option was specified with RESTORE. This is not permitted because recovery catalog contains only those records that are not deleted from disk.
Action: Remove the ARCHIVELOG LIKE option and re-run the command.
Cause: The ARCHIVELOG LIKE option was specified with RESTORE. This is not permitted because recovery catalog contains only those records that are not deleted from disk.
Action: Remove the ARCHIVELOG LIKE option and re-run the command.
RMAN-06140: cannot specify TAG option with LIST INCARNATION
RMAN-06140: cannot specify TAG option with LIST INCARNATION
Cause: The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation.
Action: Remove the TAG option and re-run the LIST command.
Cause: The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation.
Action: Remove the TAG option and re-run the LIST command.
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Cause: A REPORT SCHEMA with no at_clause was issued, and there is no recovery catalog, and the control file mounted by the target instance is not current, so the information about the current list of datafiles may not be current.
Action: Use a recovery catalog or mount a current control file.
Cause: A REPORT SCHEMA with no at_clause was issued, and there is no recovery catalog, and the control file mounted by the target instance is not current, so the information about the current list of datafiles may not be current.
Action: Use a recovery catalog or mount a current control file.
RMAN-06138: control file not mounted - must specify AT clause with REPORT command
RMAN-06138: control file not mounted - must specify AT clause with REPORT command
Cause: A REPORT SCHEMA with no at_clause was issued, and there is no recovery catalog, and there is also no control file mounted at the target database, so there is no place to get the information about the current list of files comprising the database.
Action: Use a recovery catalog or mount a control file at the target database.
Cause: A REPORT SCHEMA with no at_clause was issued, and there is no recovery catalog, and there is also no control file mounted at the target database, so there is no place to get the information about the current list of files comprising the database.
Action: Use a recovery catalog or mount a control file at the target database.
RMAN-06137: must have recovery catalog for REPORT SCHEMA AT TIME
RMAN-06137: must have recovery catalog for REPORT SCHEMA AT TIME
Cause: A REPORT SCHEMA at_clause command was issued, but there is no recovery catalog database.
Action: If you are not using a recovery catalog, then you may only issue the REPORT SCHEMA command with no at_clause.
Cause: A REPORT SCHEMA at_clause command was issued, but there is no recovery catalog database.
Action: If you are not using a recovery catalog, then you may only issue the REPORT SCHEMA command with no at_clause.
RMAN-06136: ORACLE error from auxiliary database: string
RMAN-06136: ORACLE error from auxiliary database: string
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
RMAN-06105: duplicate qualifier found in LIST command: string
RMAN-06105: duplicate qualifier found in LIST command: string
Cause: The indicated qualifier appears more than once in a LIST qualifier list.
Action: delete the duplicate qualifier
Cause: The indicated qualifier appears more than once in a LIST qualifier list.
Action: delete the duplicate qualifier
Subscribe to:
Posts (Atom)