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

E40402-15
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$COPY_CORRUPTION

V$COPY_CORRUPTION displays information about datafile copy corruptions from the control file.

Column Datatype Description
RECID NUMBER Copy corruption record ID
STAMP NUMBER Copy corruption record stamp
COPY_RECID NUMBER Datafile copy record ID
COPY_STAMP NUMBER Datafile copy record stamp
FILE# NUMBER Datafile number
BLOCK# NUMBER First block of the corrupted range
BLOCKS NUMBER Number of contiguous blocks in the corrupted range
CORRUPTION_CHANGE# NUMBER Change number at which the logical corruption was detected. Set to 0 to indicate media corruption.
MARKED_CORRUPT VARCHAR2(3) (YES | NO) If set to YES the blocks were not marked corrupted in the datafile, but were detected and marked as corrupted while making the datafile copy
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)