ORACLE 如何检查找出损坏索引 ( Corrupt Indexes )
ORACLE 如何检查找出损坏索引 ( Corrupt Indexes )
在Oracle数据库中如何找出损坏索引呢? 下面我们人为构造一个案例,将索引块损坏。如下案例所示:123456789101112131415161718192021222324252627SQL> create tablespace test_data2 datafile'/u01/app/oracle/oradata/gsp/test_data_01.dbf'3 size 200M autoextend off4 logging5 segment space management auto6 extent management local; Tablespace created. SQL> create tablespace test_index2 datafile'/u01/app/oracle/oradata/gsp/test_idx_01.dbf'3 size 200M autoextend off4 logging5 segment space management auto6 extent management local; Tablespace created. SQL> create user kerry2 identified by1234563 default tablespace test_data; User created. SQL> grant connect to kerry;SQL> grant resource to kerry;
上述脚本是创建表空间,创建用户kerry并授权,然后使用kerry账号登录数据库,构造测试数据,在TEST表上创建索引IX_TEST12345678910111213141516171819202122SQL> show user;USER is"KERRY"SQL>SQL> CREATE TABLE TEST(ID NUMBER(10), NAME VARCHAR2(64)); Table created. SQL> DECLARE I NUMBER;2 BEGIN3 FOR I IN1..1000 LOOP4 INSERT INTO TEST VALUES(I, LPAD('T',60));5 END LOOP;6 COMMIT;7 END;8 / PL/SQL procedure successfully completed. SQL> CREATE INDEX IX_TEST ON KERRY.TEST(NAME) TABLESPACE TEST_INDEX; Index created.
然后使用下面脚本找到索引段数据库文件ID,以及索引段的第一个块的块号。1234567891011121314151617SQL> show user;USER is"SYS"SQL> col segment_namefor a32;SQL> col header_filefor 9999;SQL> col header_blockfor 9999;SQL> select segment_name2 ,header_file3 ,header_block4 ,blocks5 from dba_segments ds6 where ds.owner='KERRY' and ds.segment_name='IX_TEST'; SEGMENT_NAME HEADER_FILE HEADER_BLOCK BLOCKS-------------------------------- ----------- ------------ ----------IX_TEST8 130 16 SQL>
构造坏块的方法有不少(例如BBED等),这里我们使用RMAN下面的命令clear,可以标记数据块为corrupt,标记数据文件8中130号数据块为坏块。1234567891011121314151617[oracle@DB-Server ~]$ rman target / Recovery Manager: Release11.2.0.1.0 - Production on Thu Sep13 17:41:05 2018 Copyright (c)1982,2009, Oracle and/or its affiliates. All rights reserved. connected to target database: GSP (DBID=644393201) RMAN> recover datafile8 block130 clear; Starting recover at13-SEP-18using target database control file instead of recovery catalogallocated channel: ORA_DISK_1channel ORA_DISK_1: SID=12 device type=DISKFinished recover at13-SEP-18 RMAN>
那么我们先来看看使用那些方法验证索引损坏了,测试验证一下看看是否可行。
1:使用ANALYZE分析验证索引结构1234567891011121314151617[oracle@DB-Server ~]$ sqlplus / as sysdba SQL*Plus: Release11.2.0.1.0 Production on Thu Sep13 17:42:03 2018 Copyright (c)1982,2009, Oracle. All rights reserved. Connected to:Oracle Database 11g Enterprise Edition Release11.2.0.1.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> analyze index kerry.ix_test validate structure;analyze index kerry.ix_test validate structure*ERROR at line1:ORA-01578: ORACLE data block corrupted (file #8, block #130)ORA-01110: data file8:'/u01/app/oracle/oradata/gsp/test_idx_01.dbf'
如上截图所示,如果索引损坏(Corrupt Index),那么使用analyze index validate structure就会报错。要检查整个数据库所有的损坏索引(Corrupt Indexes)的话,就可以借助下面脚本:12345678spool analy_index.sqlSET PAGESIZE50000;SELECT'ANALYZE INDEX ' || OWNER ||'.' || INDEX_NAME||' VALIDATE STRUCTURE;' FROM DBA_INDEXES; spool off; @analy_index.sql
2:使用系统视图v$database_block_corruption查看损坏索引
如下所示,我们使用这个脚本来查看出现坏块的索引,发现这个脚本无法找出坏块索引。12345678910111213set pagesize50 linesize170col segment_name format a30col partition_name format a30SELECT DISTINCT file#,segment_name,segment_type,tablespace_name,partition_nameFROM dba_extents a,v$database_block_corruption bWHERE a.file_id = b.file#AND a.block_id <= b.block#AND a.block_id + a.blocks >= b.block#;
原因分析如下,视图v$database_block_corruption中有坏块记录,但是我们将索引段的第一个块标记为坏块后,在dba_extents中没有该索引段的记录了。所以这种情况下的索引损坏,这个SQL语句根本无法找出坏块索引。1234567891011121314151617181920SQL> SELECT file_id,2 segment_name,3 segment_type4 FROM dba_extents5 WHERE file_id =8 ; no rows selected SQL> SELECT file_id,2 segment_name,3 segment_type4 FROM dba_extents5 WHERE owner ='KERRY'; FILE_ID SEGMENT_NAME SEGMENT_TYPE---------- -------------------------------- ------------------7 TEST TABLE7 TEST TABLE SQL>
因为一个段的第一个区的第一个块是FIRST LEVEL BITMAP BLOCK,第二个块是SECOND LEVEL BITMAP BLOCK,这两个块是用来管理free block的,第三个块是PAGETABLE SEGMENT HEADER,这个块才是segment里的HEADER_BLOCK,再后面的块就是用来记录数据的。关于这些知识,可以参考我博客ORACLE关于段的HEADER_BLOCK的一点浅析。而我们最上面的例子,是将第一个块构造为坏块,所以导致上面SQL无法查出。 我们重新构造案例,如我们将索引段的数据块构造为坏块,例如下面,将块号148人为构造坏块。那么此时这个脚本就能找出坏块索引了。所以综上述实验可以看出,这个脚本查找坏块索引是有条件的,要看索引段损坏的块是什么类型1234567891011121314151617181920212223242526272829303132333435SQL> SELECT FILE_ID,2 BLOCK_ID,3 BLOCKSFROM DBA_EXTENTS4 5 WHERE OWNER ='&OWNER'6 AND SEGMENT_NAME ='&TABLE_NAME';Enter valuefor owner: KERRYold5: WHERE OWNER ='&OWNER'new 5: WHERE OWNER ='KERRY'Enter valuefor table_name: IX_TESTold6: AND SEGMENT_NAME ='&TABLE_NAME'new 6: AND SEGMENT_NAME ='IX_TEST' FILE_ID BLOCK_ID BLOCKS---------- ---------- ----------8 144 88 152 8 SQL> SELECT HEADER_FILE2 , HEADER_BLOCK3 , BYTES4 , BLOCKS5 , EXTENTSFROM DBA_SEGMENTS6 7 WHERE OWNER='&OWNER' AND SEGMENT_NAME='&SEGMENT_NAME';Enter valuefor owner: KERRYEnter valuefor segment_name: IX_TESTold7: WHERE OWNER='&OWNER' AND SEGMENT_NAME='&SEGMENT_NAME'new 7: WHERE OWNER='KERRY' AND SEGMENT_NAME='IX_TEST' HEADER_FILE HEADER_BLOCK BYTES BLOCKS EXTENTS----------- ------------ ---------- ---------- ----------8 146 131072 16 2 SQL>
RMAN> recover datafile 8 block 148 clear;
原文出处:潇湘隐者
ORACLE 如何检查找出损坏索引 ( Corrupt Indexes )相关教程