ORA-00600: internal error code, arguments: [kdsgrp1] 逻辑坏块

处理过程
日志：
ue Jun 18 22:28:00 2013
Archived Log entry 63360 added for thread 3 sequence 7246 ID 0x8251a1b6 dest 1:
Tue Jun 18 22:57:25 2013
Errors in file /oracle/app/oracle/diag/rdbms/prodb/prodb3/trace/prodb3_ora_4389.trc  (incident=484169):
ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/prodb/prodb3/incident/incdir_484169/prodb3_ora_4389_i484169.trc

vi /oracle/app/oracle/diag/rdbms/prodb/prodb3/incident/incdir_484169/prodb3_ora_4389_i484169.trc
......

* kdsgrp1-1: *************************************************
            row 0x0b4e713a.d0 continuation at
            0x0b4e7159.5b file# 45 block# 946521 slot 91 not found
......            

找到有讹误的块所在对象            
select owner,file_id,segment_name, segment_type, block_id, blocks
from dba_extents
where file_id=13 and block_id<=946521 and (block_id + blocks- 1) >= 946521;  

OWNER           FILE_ID SEGMENT_NAME            SEGMENT_TYPE     BLOCK_ID     BLOCKS
------------- --------- ----------------------- ------------------ ---------- ----------
USER                         13 TBL_STATUS_HISTORY_P   INDEX              945536        1792

找到索引所在表
SQL> select table_name,index_name,owner from dba_indexes where index_name='GOME_STATUS_HISTORY_P';

TABLE_NAME                     INDEX_NAME                     OWNER
------------------------------ ------------------------------ ------------------------------
TBL_STATUS_HISTORY            TBL_STATUS_HISTORY_P          USER
            

SQL> select count(STATUS_HISTORY_ID) from USER.TBL_STATUS_HISTORY;

COUNT(STATUS_HISTORY_ID)
------------------------
                76516771


Execution Plan
----------------------------------------------------------
Plan hash value: 1925894911

---------------------------------------------------------------------------------------
| Id  | Operation             | Name                  | Rows  | Cost (%CPU)| Time     |
---------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT      |                       |     1 |   192K  (1)| 00:38:36 |
|   1 |  SORT AGGREGATE       |                       |     1 |            |          |
|   2 |   INDEX FAST FULL SCAN| TBL_STATUS_HISTORY_P |    75M|   192K  (1)| 00:38:36 |
---------------------------------------------------------------------------------------

           

借用惜分飞的总结：

总结：很明显这次出现这个问题，因为内存中出现坏块导致，经过一段时间buffer cache中的坏块内容已经被老化，所以现在不能重现(甚至不用做任何操作)。如果内存中出现了坏块，而且还没有被老化掉，可以刷新data buffer;如果是数据块出现坏块，根据实际情况决定处理