ORA-01578坏块处理
收到报错:
ORA-01578: ORACLE 数据块损坏 (文件号 4, 块号 293465)
ORA-01110: 数据文件 1: ‘xxxx’
坏块处理有3种通用的办法:
一、解决方法:
备份好用情况:
1.blockrecover
备份不可用情况:
2.dbms_repair.SKIP_CORRUPT_BLOCKS标记跳过坏块,将数据块标为坏块,不访问
3.Oracle 10231内部事件跳过坏块 exp导出数据
二、记一次生产不境故障处理:
1.查询确定文件号和块号
select * from v$database_block_corruption;
2.查看坏块所在的表空间,段类型
select tablespace_name,segment_name,segment_type from dba_extents where file_id='25' and 3063907 between block_id and block_id+blocks-1;
3.如果怀疑还有其它坏块
dbv file=D:\APP\ADMINISTRATOR\ORADATA\ORCL\USERS01.DBF blocksize=8192 logfile='D:\dbv.log'
4.对坏块进行处理
1)如果是索引,重建索引即可
2)如果没有备份,也不是索引,可使用跳块的方法
alter table V7QY.KFAB_ZNGZCP MOVE;
execute DBMS_REPAIR.SKIP_CORRUPT_BLOCKS('V7QY','KFAB_ZNGZCP',flags=>dbms_repair.noskip_flag);
select OWNER,INDEX_NAME,INDEX_TYPE,TABLE_NAME,STATUS,LAST_ANALYZED,PARTITIONED from dba_indexes
where owner = 'V7QY' AND STATUS <> 'VALID';
三、介建演示环境
--当前环境
SYS@gg> select * from v$version where rownum<2;
BANNER CON_ID
------------------------------------------------------------------------------------------ ----------
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production 0
--创建表空间
sys@gg> create tablespace gg_tbs datafile '/u01/app/oracle/oradata/gg/pdb1/gg.dbf' size 10m autoextend on;
--创建表对象test1及其索引
sys@gg> create table test1 tablespace gg_tbs as select * from dba_objects;
sys@gg> create index i_test1 on test1(object_id);
--表段上的相关信息
sys@gg> select segment_name , header_file , header_block,blocks
2 from dba_segments where segment_name ='TEST1';
SEGMENT_NAME HEADER_FILE HEADER_BLOCK BLOCKS
---------------------------------------- ----------- ------------ ----------
TEST1 14 130 1536
--使用linux自带的dd命令来损坏数据块
[oracle@dddg ~]$ dd if=/dev/zero of=/u01/app/oracle/oradata/gg/pdb1/gg.dbf bs=8192 conv=notrunc seek=212 count=1
1+0 records in
1+0 records out
8192 bytes (8.2 kB) copied, 0.000113115 s, 72.4 MB/s
[oracle@dddg ~]$ dd if=/dev/zero of=/u01/app/oracle/oradata/gg/pdb1/gg.dbf bs=8192 conv=notrunc seek=213 count=1
1+0 records in
1+0 records out
8192 bytes (8.2 kB) copied, 0.000219159 s, 37.4 MB/s
[oracle@dddg ~]$ dd if=/dev/zero of=/u01/app/oracle/oradata/gg/pdb1/gg.dbf bs=8192 conv=notrunc seek=312 count=1
sys@gg> alter system flush buffer_cache;
--下面的查询收到了错误提示
sys@gg> select count(*) from test1;
select count(*) from test1
*
ERROR at line 1:
ORA-01578: ORACLE data block corrupted (file # 15, block # 212)
ORA-01110: data file 15: '/u01/app/oracle/oradata/gg/pdb1/gg.dbf'
##### 4、使用DBMS_REPAIR修复坏块
Step 1) 创建相应的表对象
--使用DBMS_REPAIR.ADMIN_TABLES过程创建一个表对象,用于记录需要被修复的表
sys@gg> BEGIN
DBMS_REPAIR.ADMIN_TABLES (
TABLE_NAME => 'REPAIR_TABLE',
TABLE_TYPE => dbms_repair.repair_table,
ACTION => dbms_repair.create_action,
TABLESPACE => 'USERS');
END;
/
PL/SQL procedure successfully completed.
--使用DBMS_REPAIR.ADMIN_TABLES过程创建一个表对象,用于记录在表块损坏后那些孤立索引,也就是指向坏块的那些索引
sys@gg> BEGIN
DBMS_REPAIR.ADMIN_TABLES
(
TABLE_NAME => 'ORPHAN_KEY_TABLE',
TABLE_TYPE => DBMS_REPAIR.ORPHAN_TABLE,
ACTION => DBMS_REPAIR.CREATE_ACTION,
TABLESPACE => 'USERS'
);
END;
/
PL/SQL procedure successfully completed.
Step 2) 校验受损的对象
--使用DBMS_REPAIR.CHECK_OBJECT来检测对象上受损的情形,并返回受损块数
sys@gg> SET SERVEROUTPUT ON
sys@gg> DECLARE num_corrupt INT;
BEGIN
num_corrupt := 0;
DBMS_REPAIR.CHECK_OBJECT (
SCHEMA_NAME => 'HR',
OBJECT_NAME => 'TEST1',
REPAIR_TABLE_NAME => 'REPAIR_TABLE',
CORRUPT_COUNT => num_corrupt);
DBMS_OUTPUT.PUT_LINE('number corrupt: ' || TO_CHAR (num_corrupt));
END;
/
number corrupt: 3
PL/SQL procedure successfully completed.
--下面我们可以从repair_table查询到受损的块
--从下面的查询中可以看出列marked_corrupt全部为true,表明我们在CHECK_OBJECT已经标注了坏块
sys@gg> COLUMN object_name FORMAT a10
sys@gg> COLUMN repair_description FORMAT a28
sys@gg> SET LINES 10000
sys@gg> SELECT object_name, block_id, corrupt_type,marked_corrupt,repair_description FROM repair_table;
OBJECT_NAME BLOCK_ID CORRUPT_TYPE MARKED_CORRUPT REPAIR_DESCRIPTION
------------------------------ ---------- ------------ -------------------- ----------------------------------------
TEST1 212 6148 TRUE mark block software corrupt
TEST1 213 6148 TRUE mark block software corrupt
TEST1 312 6148 TRUE mark block software corrupt
Step 3) 标记坏块
--过程FIX_CORRUPT_BLOCKS用于标记坏块,在这个演示中,我们在CHECK_OBJECT已经被标注了,如没有执行下面的过程
--由于上一步已经标注,所以下面的输出为0
sys@gg> SET SERVEROUTPUT ON
sys@gg> DECLARE num_fix INT;
2 BEGIN
3 num_fix := 0;
4 DBMS_REPAIR.FIX_CORRUPT_BLOCKS (
5 SCHEMA_NAME => 'HR',
6 OBJECT_NAME=> 'TEST1',
7 OBJECT_TYPE => dbms_repair.table_object,
8 REPAIR_TABLE_NAME => 'REPAIR_TABLE',
9 FIX_COUNT=> num_fix);
10 DBMS_OUTPUT.PUT_LINE('num fix: ' || TO_CHAR(num_fix));
11 END;
12 /
num fix: 0
PL/SQL procedure successfully completed.
Step 4) DUMP孤立的索引键值
--使用DUMP_ORPHAN_KEYS过程将那些指向坏块的索引键值填充到ORPHAN_KEY_TABLE
sys@gg> SET SERVEROUTPUT ON
sys@gg> DECLARE num_orphans INT;
2 BEGIN
3 num_orphans := 0;
4 DBMS_REPAIR.DUMP_ORPHAN_KEYS (
5 SCHEMA_NAME => 'HR',
6 OBJECT_NAME => 'I_TEST1',
7 OBJECT_TYPE => dbms_repair.index_object,
8 REPAIR_TABLE_NAME => 'REPAIR_TABLE',
9 ORPHAN_TABLE_NAME=> 'ORPHAN_KEY_TABLE',
10 KEY_COUNT => num_orphans);
11 DBMS_OUTPUT.PUT_LINE('orphan key count: ' || TO_CHAR(num_orphans));
12 END;
13 /
orphan key count: 177
PL/SQL procedure successfully completed.
--下面的查询可以看到正好等于上面返回的数量也就是177条记录
sys@gg> select count(*) from orphan_key_table;
COUNT(*)
----------
177
--验证对象是否可以查询,下面的结果显示依旧无法查询
sys@gg> select count(*) from test1;
select count(*) from test1
*
ERROR at line 1:
ORA-01578: ORACLE data block corrupted (file # 15, block # 212)
ORA-01110: data file 15: '/u01/app/oracle/oradata/gg/pdb1/gg.dbf'
Step e 跳过坏块
--使用SKIP_CORRUPT_BLOCKS来告知Oracle哪些坏块需要被跳过
sys@gg> BEGIN
2 DBMS_REPAIR.SKIP_CORRUPT_BLOCKS (
3 SCHEMA_NAME => 'HR',
4 OBJECT_NAME => 'TEST1',
5 OBJECT_TYPE => dbms_repair.table_object,
6 FLAGS => dbms_repair.skip_flag);
7 END;
8 /
PL/SQL procedure successfully completed.
--由于索引键上存在孤立索引,因此我们重建索引
sys@gg> alter index i_test1 rebuild;
Index altered.
--验证结果
sys@gg> select count(*) from test1;
COUNT(*)
----------
73112
##### 5、后记
a、再次提醒,备份重于一切,因此无论何时应保留可用的备份。
b、DBMS_REPAIR包并不是真正意思上的坏块修复,而是标记坏块,损坏的这部分数据被丢失。
c、DBMS_REPAIR包的几个步骤,先创建相应的表用于存储修复表及孤立索引,其次CHECK_OBJECT,FIX_CORRUPT_BLOCKS,DUMP_ORPHAN_KEYS,SKIP_CORRUPT_BLOCKS。
d、完整DBMS_REPAIR上面提到的几个步骤后,建议重建索引。
e、注,如果受损表对象被其他对象参照,建议先disable这些约束,那些在子表上孤立的记录可根据情形决定后再enable约束。
————————————————
参考链接:https://blog.csdn.net/leshami/article/details/10616687