RMAN-08119: skipping backup piece handle string; already exists
Cause: A BACKUP command does not need to backup controlfile autobackup pieces, because they already exist.
Action: This is an informational message. No action required.
RMAN-08119: skipping backup piece handle string; already exists
Cause: A BACKUP command does not need to backup controlfile autobackup pieces, because they already exist.
Action: This is an informational message. No action required.
RMAN-08118: WARNING: could not delete the following archived redo log
Cause: The routine deleteArchivedLog() could not delete an archived redo log on the target instance.
Action: Check the accompanying file specification and the associated error messages. The file specification indicates what archived redo log on the target instance RMAN was trying to delete and the error messages indicate why RMAN was unable to delete it. Resolve the problem by first confirming that the archived redo log in question has been backed up, do the deletion manually, and then do a crosscheck so that RMAN is aware of the deletion.
RMAN-08117: channel string: the autobackup does not contain SPFILE. Trying older autobackup...
Cause: The requested autobackup does not contain a SPFILE. This is because the instance was not started with a SPFILE when the autobackup was created.
Action: No Action Required. RMAN will try three older autobackups before signaling ORA-19687.
RMAN-08116: output filename is original SPFILE location
Cause: This is an informational message.
Action: No Action Required.
RMAN-08115: channel string: restoring SPFILE
Cause: This is an informational message.
Action: No Action Required.
RMAN-08114: channel string: restoring SPFILE to PFILE
Cause: This is an informational message.
Action: No Action Required.
RMAN-08113: including current SPFILE in backupset
Cause: This is an informational message.
Action: No Action Required.
RMAN-08112: archivelog failover was done on string, check alert log for more info
Cause: This is an informational message to indicate the server found a corrupted block in an archivelog and had to switch to another archivelog with same logseq in alternate archivelog destination to get corresponding un-corrupted block.
Action: If backup is done with delete input option, then nothing needs to be done. Otherwise, delete the archivelog that has corrupted blocks as recovery on applying this log would fail. alert log contains name of the log that has corrupted blocks.
RMAN-08111: some blocks not recovered: See trace file for details
Cause: Some blocks were not recovered due to errors.
Action: See trace file for details of the problem.
RMAN-08108: channel string: specifying block(s) to restore from backup set
Cause: This is an informational message.
Action: No Action Required.