In some exceptional cases, when querying the database's Dba_extents dictionary table, you may experience a ORA-600 kcfrbd_3 error that is caused by a file size that is incompatible with the control file, and may be triggered by a database write exception, which can usually be eliminated by rebuilding the control file.
However, if the data file header information logging error, and the data file itself does not conform to, you need to modify the data file header file size information to be able to solve the problem.
This issue is extremely rare and the following reference information is recorded in MOS note 601798.1:
The code is as follows |
Copy Code |
Oracle reports the ORA-00600: [Kcfrbd_3] on a particular query. The same exception is encountered if your try to select dba_extents using a file#/block#.
|
Here are some of the key parameters to this 600 error description:
The code is as follows |
Copy Code |
Ksedmp:internal or fatal error Ora-00600:internal error code, arguments: [Kcfrbd_3], [13], [64011], [1], [64000], [64000], [], [] Arg [A] File number Arg [b] block number ARG [C] Nro of blocks Arg [d] Logical File Size ARG [E] File Size
|
The first parameter is the file number, and the following 13 is the file number:
The code is as follows |
Copy Code |
SELECT Segment_name, Segment_type, owner, Tablespace_name from sys.dba_extents WHERE file_id = and 64011 betwee N block_id and block_id + blocks-1; Error at line 2: ora-00600:internal ERROR Code, arguments: [Kcfrbd_3], [13], [66499], [1], [64000], [64000], [], [] cause There is a corruption on the extent allocation table to tablespace this the file# Belongs to. For example, in the case, DataFile # is +data/orcl/datafile/mgmt_tablespace.340.655388135 (FOB) flags= fib=0x1629c8f68 incno=0 pending I/O cnt=0 fname=+data/orcl/datafile/mgmt_ tablespace.340.655388135 fno=13 lblksz=8192 fsiz=64000 We are trying to access the bloc K 64011 This is beyond the number of blocks 6400. |
The simplest case of
can be eliminated by resize files.