V$BACKUP_DATAFILE Shows Corruptions for File #0

Just saw the following in some database backups: SQL> select recid, file#, MARKED_CORRUPT, MEDIA_CORRUPT,LOGICALLY_CORRUPT,COMPLETION_TIME from v$backup_datafile where logically_corrupt = 1; File# 0 is the control file. As you can see some of the backups are OK for the file: SQL> select recid, file#, MARKED_CORRUPT, MEDIA_CORRUPT,LOGICALLY_CORRUPT,COMPLETION_TIME from v$backup_datafile where file#=0;   The actual backup logs have no error, Also no errors in the Alert log file. Apparently this is safe if you see this. The non-zero values do not indicate a corruption in the controlfile(s) - instead it is a result of the underlying fields being used by RMAN for timestamp and sequence information for autobackups, ie. this is intended behavior.