笔记：DG未开启Force Logging导致的坏块

在一次检查过程中，备库出现了坏块的信息：

ORA-01578: ORACLE 数据块损坏 (文件号 20, 块号 60212)
ORA-01110: 数据文件 20: '+DATADG/*****DB/DATAFILE/******.350.1016917327'
ORA-26040: 数据块是使用 NOLOGGING 选项加载的

问题原因很简单，在搭建DG的时候，为开启Force Logging

处理也很简单，开启主库Force Logging

ADG会自动进行恢复

使用RMAN检测数据库坏块

rman target /
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
backup validate check logical database;
}

select * from V$DATABASE_BLOCK_CORRUPTION ;

如果V$DATABASE_BLOCK_CORRUPTION有数据显示，使用下面的sql进行查询

SELECT e.owner,
       e.segment_type,
       e.segment_name,
       e.partition_name,
       c.file#,
       greatest(e.block_id, c.block#) corr_start_block#,
       least(e.block_id + e.blocks - 1, c.block# + c.blocks - 1) corr_end_block#,
       least(e.block_id + e.blocks - 1, c.block# + c.blocks - 1) -
       greatest(e.block_id, c.block#) + 1 blocks_corrupted,
       null description
  FROM dba_extents e, v$database_block_corruption c
 WHERE e.file_id = c.file#
   AND e.block_id <= c.block# + c.blocks - 1
   AND e.block_id + e.blocks - 1 >= c.block#
UNION
SELECT s.owner,
       s.segment_type,
       s.segment_name,
       s.partition_name,
       c.file#,
       header_block corr_start_block#,
       header_block corr_end_block#,
       1 blocks_corrupted,
       'Segment Header' description
  FROM dba_segments s, v$database_block_corruption c
 WHERE s.header_file = c.file#
   AND s.header_block between c.block# and c.block# + c.blocks - 1
UNION
SELECT null owner,
       null segment_type,
       null segment_name,
       null partition_name,
       c.file#,
       greatest(f.block_id, c.block#) corr_start_block#,
       least(f.block_id + f.blocks - 1, c.block# + c.blocks - 1) corr_end_block#,
       least(f.block_id + f.blocks - 1, c.block# + c.blocks - 1) -
       greatest(f.block_id, c.block#) + 1 blocks_corrupted,
       'Free Block' description
  FROM dba_free_space f, v$database_block_corruption c
 WHERE f.file_id = c.file#
   AND f.block_id <= c.block# + c.blocks - 1
   AND f.block_id + f.blocks - 1 >= c.block#
 order by file#, corr_start_block#;
 
SELECT tablespace_name, segment_type, owner, segment_name
FROM dba_extents
WHERE file_id = &fileid
and &blockid between block_id AND block_id + blocks - 1;

使用DBV检测坏块

dbv file=+DATADG/*******db/datafile/*****.dbf blocksize=8192;

我家大婶儿给的参考：
MOS Doc 290161.1 - The Gains and Pains of Nologging Operations
MOS Doc 794505.1 - ORA-1578, ORA-26040 Corrupt blocks by NOLOGGING - Error explanation and solution