Oracle Index repair, ORA-00600: internal error code, arguments: [6200],
Background to the issue: incident log customer feedback DB generated a lot every day, you need to troubleshoot the cause
View alert logs found a large number of ORA-07445, ORA-00600 errors
Errors in file /data/oracle/diag/rdbms/bydata/bydata/trace/bydata_mmon_3667.trc (incident=111052):
ORA-00600: internal error code, arguments: [6200], [18446744073709551615], [], [], [], [], [], [], [], [], [], []
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0x2278EA1, kghstack_err()+85] [flags: 0x0, count: 1]
Errors in file /data/oracle/diag/rdbms/bydata/bydata/trace/bydata_mmon_3667.trc (incident=111053):
ORA-07445: exception encountered: core dump [kghstack_err()+85] [SIGSEGV] [ADDR:0x0] [PC:0x2278EA1] [SI_KERNEL(general_protection)] []
ORA-00600: internal error code, arguments: [6200], [18446744073709551615], [], [], [], [], [], [], [], [], [], []
Incident details in: /data/oracle/diag/rdbms/bydata/bydata/incident/incdir_111053/bydata_mmon_3667_i111053.trc
My 21 October 2019 9:50:30
In general, ORA-600 proved to be the oracle internal errors, typically caused by bad block data file or a bug oracle
First, see if there is a bad block data files
[oracle@OA_oracle ~]$ dbv file =/data/oracle/oradata/bydata/SYSAUX01.DBF
DBVERIFY: Release 11.2.0.1.0 - Production on Mon Oct 21 15:12:29 2019
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
DBVERIFY - Verification starting : FILE = /data/oracle/oradata/bydata/SYSAUX01.DBF
Block Checking: DBA = 8522163, Block Type = KTB-managed data block
**** row 0: row length 35 past end of block
**** row 0: row skipped so other stats may be wrong
**** row 1: row length 7641 past end of block
**** row 1: row skipped so other stats may be wrong
**** row 2: row length 1002 past end of block
**** row 2: row skipped so other stats may be wrong
**** row 3: row length 1951 past end of block
**** row 3: row skipped so other stats may be wrong
**** row 4: row length 441 past end of block
**** actual free space = -277001 < kdxcoavs = 29
**** key (begin=0x594, len=1438) overlaps with another
begin = 0x5ae len = 1428
---- end index block validation
Page 133555 failed with check code 6401
DBVERIFY - Verification complete
Total Pages Examined : 144640
Total Pages Processed (Data) : 47272
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 39600
Total Pages Failing (Index): 1 --- need to pay attention
Total Pages Processed (Lob) : 9592
Total Pages Failing (Lob) : 0
Total Pages Processed (Other): 26419
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 21757
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Total Pages Encrypted : 0
Highest block SCN : 296083261 (0.296083261)
It has this inspection possible corruption index data file is sysaux, for system files could not be processed by rebuilding the index, advise clients to restore a library
2> how to locate the corrupted index ORA-600 [6200] given in
description:
When accessing a particular table, you encounter ORA-600 [6200] error, the error means that the index is related to detect the presence of corruption.
The standard solution is to drop out of the index and rebuild all indexes for this table.
However, we can locate which index out of the question from the error trace file was generated.
E.g:
The display case is seen from the trace file indexing error message.
trace file error message:
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [6200], [260], [262], [], [], [], [], []
Block header dump: dba: 0x7b404757
Object id on Block? Y
seg/obj: 0x6190 csc: 0x00.4e537b5 itc: 2 flg: -typ: 2 - INDEX
fsl: 0 fnx: 0x0
Note that this seg / obj noted Hex values, we can convert it to a decimal value, which is the object id number.
0x6190 is 24976 Hex = 00006190 Octal = 00000060620
So that we can find an index object in DBA_OBJECTS view.
SVRMGR> SELECT OBJECT_ID, OBJECT_NAME FROM DBA_OBJECTS
WHERE DATA_OBJECT_ID = '24976';
DATA_OBJEC OBJECT_NAME
---------- ------------------------------------------------------
24976 tab1_index5
This index is that we should go to the reconstruction of that.