Categories
Blog

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;

RECID      FILE# MARKED_CORRUPT MEDIA_CORRUPT LOGICALLY_CORRUPT COMPLETIO
---------- ---------- -------------- ------------- ----------------- ---------
20024          0           2015           308                 1 08-MAR-15
20081          0           2015           309                 1 09-MAR-15
20138          0           2015           310                 1 10-MAR-15
20195          0           2015           311                 1 11-MAR-15
20252          0           2015           312                 1 12-MAR-15

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;

RECID      FILE# MARKED_CORRUPT MEDIA_CORRUPT LOGICALLY_CORRUPT COMPLETIO
---------- ---------- -------------- ------------- ----------------- ---------
19967          0           2015           307                 0 07-MAR-15
20022          0           2015           308                 0 08-MAR-15
20023          0              0             0                 0 08-MAR-15
20024          0           2015           308                 1 08-MAR-15
20079          0           2015           309                 0 09-MAR-15
20080          0              0             0                 0 09-MAR-15
20081          0           2015           309                 1 09-MAR-15
20136          0           2015           310                 0 10-MAR-15
20137          0              0             0                 0 10-MAR-15
20138          0           2015           310                 1 10-MAR-15
20193          0           2015           311                 0 11-MAR-15
20194          0              0             0                 0 11-MAR-15
20195          0           2015           311                 1 11-MAR-15
20250          0           2015           312                 0 12-MAR-15
20251          0              0             0                 0 12-MAR-15
20252          0           2015           312                 1 12-MAR-15

 
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.

Categories
Blog

Gartner Magic Quadrant for Data Warehouse and Data Management Solutions for Analytics

Its good to see Oracle up there with the best 🙂
Magic Quadrant for Data Warehouse and Data Management Solutions for Analytics