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.
Posted in Blog

Affiliations

Engagements

  • Oracle OpenWorld 2014
  • Gartner BI Summit 9/3/15-10/3/15
  • UKOUG Business Analytics SIG 12/3/15
  • UKOUG Conference 7/12/15-9/12/15
  • Oracle Ireland Conference 2016 3/3/16-4/3/16
  • UKOUG Systems 2016 12/5/16
  • Oracle OpenWorld 2016
  • POUG 2016 7/10/16
  • DOAG 2016 15/11/16
  • UKOUG 2016 5/12/16

Videos

Posts

  • 2017 (8)
  • 2016 (22)
  • 2015 (22)
  • 2014 (8)
  • 2013 (2)