Skip Headers
Oracle® Database Reference
11g Release 2 (11.2)

E40402-14
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

V$BACKUP_CORRUPTION

V$BACKUP_CORRUPTION displays information about corrupt block ranges in datafile backups from the control file. Note that corruptions are not tolerated in the control file and archived redo log backups.

Column Datatype Description
RECID NUMBER Backup corruption record ID
STAMP NUMBER Backup corruption record stamp
SET_STAMP NUMBER Backup set stamp
SET_COUNT NUMBER Backup set count
PIECE# NUMBER backup piece that contains this corrupt block
FILE# NUMBER Absolute file number of the datafile that contains the corrupt blocks
BLOCK# NUMBER Block number of the first corrupt block in the range of corrupted blocks
BLOCKS NUMBER Number of corrupted blocks found starting with BLOCK#
CORRUPTION_CHANGE# NUMBER Change number at which the logical corruption was detected. Set to 0 to indicate media corruption.
MARKED_CORRUPT VARCHAR2(3) Indicates whether this corruption was not previously detected by the Oracle Database (YES) or the Oracle Database had already discovered this corrupt block and marked it as corrupt (NO). Note that when a corrupt block is encountered in a backup, and was not already marked corrupt by the Oracle Database, then the backup process does not mark the block as corrupt in the production datafile. Thus, this field may be YES for the same block in more than one backup set.
CORRUPTION_TYPE VARCHAR2(9) Type of block corruption in the datafile:
  • ALL ZERO - Block header on disk contained only zeros. The block may be valid if it was never filled and if it is in an Oracle7 file. The buffer will be reformatted to the Oracle8 standard for an empty block.

  • FRACTURED - Block header looks reasonable, but the front and back of the block are different versions.

  • CHECKSUM - optional check value shows that the block is not self-consistent. It is impossible to determine exactly why the check value fails, but it probably fails because sectors in the middle of the block are from different versions.

  • CORRUPT - Block is wrongly identified or is not a data block (for example, the data block address is missing)

  • LOGICAL - Block is logically corrupt

  • NOLOGGING - Block does not have redo log entries (for example, NOLOGGING operations on primary database can introduce this type of corruption on a physical standby)