Oracle教程 2023-02-24

Oracle 视图 V$BACKUP_CORRUPTION 官方解释，作用，如何使用详细说明

本站中文解释

V$BACKUP_CORRUPTION 是Oracle 9i以给出的一个视图，用于检测RMAN备份引起的任何损坏。该视图会显示每个备份文件块中发现的所有已损坏数据文件块。

使用该视图，可以查看备份过程发生的任何问题。通过检查V$BACKUP_CORRUPTION，可以确定是否存在破坏性备份错误。如果有，可以用备份中存在的正常文件块来恢复坏的文件块。

使用V$BACKUP_CORRUPTION的方法：

1. 使用V$BACKUP_CORRUPTION视图查询损坏的备份数据文件块：

SELECT * FROM V$BACKUP_CORRUPTION;

2. 如果有损坏的备份数据文件块，可以用备份中的正常文件块来恢复，可以使用recover from scn功能来恢复：

recover from scn buffer ;

3. 如果使用recover from scn恢复失败，可以尝试使用recover database datafile 功能恢复文件：

recover database datafile ;

官方英文解释

V$BACKUP_CORRUPTION displays information about corrupt block ranges in data file 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 data file 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 data file. 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 data file: `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)
`CON_ID`	`NUMBER`	The ID of the container to which the data pertains. Possible values include: `0`: This value is used for rows containing data that pertain to the entire CDB. This value is also used for rows in non-CDBs. `1`: This value is used for rows containing data that pertain to only the root n: Where n is the applicable container ID for the rows containing data