ORA-01555 ORA-600 kdiulk: kcbz_objdchk ORA-600 kdBlkCheckError and so on error recovery

Database startup ORA-00704, 0RA-00604, ORA-01555 causes database cannot start

Tue May 31 17:32:42 2016
SMON: enabling cache recovery
SUCCESS: diskgroup RECOVERY was mounted
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ORA-01555 caused by SQL statement below (SQL ID: 4krwuz0ctqxdt, SCN: 0x0004. 3af84bee ):
Select ctime, mtime, stime from obj $ where obj # =: 1
Archived Log entry 5 added for thread 1 sequence 10 ID 0x86a261e7 dest 1:
Errors in file/opt/app/oracle/diag/rdbms/xifenfei/trace/xifenfei_ora_12779.trc:
ORA-00704: bootstrap process failure.
ORA-00704: bootstrap process failure.
ORA-00604: error occurred at recursive SQL level 1
ORA-01555: snapshot too old: rollback segment number 7 with name "_ SYSSMU7_1592079335 $" too small
Errors in file/opt/app/oracle/diag/rdbms/xifenfei/trace/xifenfei_ora_12779.trc:
ORA-00704: bootstrap process failure.
ORA-00704: bootstrap process failure.
ORA-00604: error occurred at recursive SQL level 1
ORA-01555: snapshot too old: rollback segment number 7 with name "_ SYSSMU7_1592079335 $" too small
Error 704 happened during db open, shutting down database
USER (ospid: 12779): terminating the instance due to error 704
Start the database after modifying the transaction through bbed
Tue May 31 17:35:49 2016
SMON: enabling tx recovery
**************************************** *****************************
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
Been restored. It may be necessary to add files to these
Tablespaces. That can be done using the SQL statement:
 
Alter tablespace <tablespace_name> ADD TEMPFILE
 
Alternatively, if these temporary tablespaces are no longer
Needed, then they can be dropped.
Empty temporary tablespace: TEMP
**************************************** *****************************
Updating character set in controlfile to AL32UTF8
Tue May 31 17:35:50 2016
Errors in file/opt/app/oracle/diag/rdbms/xifenfei/trace/xifenfei_p021_13862.trc (incident = 166002 ):
ORA-00600: Internal error code, parameter: [kdiulk: kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [], []
Tue May 31 17:35:50 2016
Errors in file/opt/app/oracle/diag/rdbms/xifenfei/trace/xifenfei_p010_13818.trc (incident = 165914 ):
ORA-00600: Internal error code, parameter: [kdiulk: kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [], []
Tue May 31 17:35:50 2016
Errors in file/opt/app/oracle/diag/rdbms/xifenfei/trace/xifenfei_p004_13794.trc (incident = 165866 ):
ORA-00600: Internal error code, parameter: [kdiulk: kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [], []
Tue May 31 17:35:50 2016
Errors in file/opt/app/oracle/diag/rdbms/xifenfei/trace/xifenfei_p011_13822.trc (incident = 165922 ):
ORA-00600: Internal error code, parameter: [kdiulk: kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [], []
Tue May 31 17:35:50 2016
Errors in file/opt/app/oracle/diag/rdbms/xifenfei/trace/xifenfei_p016_13842.trc (incident = 165962 ):
ORA-00600: Internal error code, parameter: [kdiulk: kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [], []
ORA-600 [kdiulk: kcbz_objdchk] trace file
* ** Session id: (3.5) 17:35:50. 068
Objd mismatch typ = 6, seg. obj =-2, diskobj = 222225, dsflg = 0, dsobj = 285890, tid = 285890, cls = 1
ORA-00600: Internal error code, parameter: [kdiulk: kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], [], []
 
Parallel Transaction recovery server caught exception 600
Begin Parallel Recovery Context Dump
Nsi: 48, nsactive: 48
, Nirsi: 1, nidti: 1, ndt: 1, rescan: 0, ptrs: 48
[Ktprsi] wdone: 50
[Ktprpri 2017651b8] ktprsi:
37903b60 37903b78 37903b90 37903ba8 37903bc0 37903bd8 37903bf0 37903c08 37903c20 37903c38 37903c50
37903c68 37903c80 37903c98 37903cb0 37903cc8 37903ce0 37903cf8 37903d10 37903d28 37903d40 37903d58
37903d70 37903d88 37903da0 37903db8 37903dd0 37903de8 37903e00 37903e18 37903e30 37903e48 37903e60
37903e78 37903e90 37903ea8 37903ec0 37903ed8 37903ef0 37903f08 37903f20 37903f38 37903f50 37903f68
37903f80 37903f98 37903fb0 37903fc8
[Ktprht] nhb: 47, nfl: 20247, flg: 2
 
* ** 17:36:08. 584
[Ktprhb] nfl: 1, nelem: 97, flg: 0, sqn: 1
Flist: 37698940.
Nhe: [ktprhe 32] sqn:-1297235803.
[Kturur] uoff:-1797708320, sqn: 4
Uba: 0x098004cd. 07e4. 0b
*-----------------------------
* Rec # 0xb slt: 0x07 objn: 123986 (0x0001e452) objd: 285891 tblspc: 10 (0x0000000a)
* Layer: 10 (Index) opc: 22 rci 0x0a
Undo type: Regular undo Last buffer split: No
Temp Object: No
Tablespace Undo: No
Rdba: 0x00000000

It can be basically determined that the dataobj # In the undo index does not match the dataobj # in the block. this error occurs during Database undo rollback. you can skip undo rollback and recreate the object.

Tue May 31 17:36:06 2016
Simulated error on redo application.
Block recovery from logseq 12, block 959 to scn 20401094719
Recovery of Online Redo Log: Thread 1 Group 3 Seq 12 Reading mem 0
Mem #0: + DATA/xifenfei/onlinelog/group_3.263.802446627
Block recovery completed at rba 12.1012.16, scn 4.3221225536
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Simulated error for redo application done.
Errors in file/opt/app/oracle/diag/rdbms/xifenfei/trace/xifenfei_p009_13814.trc (incident = 165906 ):
ORA-00600: Internal error code, parameter: [kdBlkCheckError], [26], [950417], [18025], [], [], [], [], [], [], [], []

These errors are caused by an exception in the database block logic and the parameter meaning is missing.

ORA-600 kddummy_blkchk in 10g ORA-600 kdBlkCheckError in 11g
ARGUMENTS:
Arg [a] Absolute file number
Arg [B] Bock number
Arg 1 Internal error code returned from kcbchk () which indicates the problem encountered.
See Note 46389.1 for details of block check codes.
Analysis based on QREF kddummy_blkchk/kdBlkCheckError Check Codes Listing (Full) (Doc ID 1264040.1)
Here, 18025 is part of the code KCBTEMAP_EC_START + KTS4_EC_SBFREE exception, mainly manifested in Incorrect firstfree or nfree which can be blocked by setting some parameters.

There are other errors during recovery

ORA-600 encountered when generating server alert SMG-4128
ORA-00600: internal error code, arguments: [ktcpoptx :! Cmt top lvl], [], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4406], [0x1026B65348], [0x000000000], [2], [6215], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [ktcpoptx :! Cmt top lvl], [], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
ORACLE Instance xifenfei (pid = 15)-Error 600 encountered while recovering transaction (10, 7) on object 123986.
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [kturbleurec1], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [kewrose _1], [600],
[ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Non-fatal internal error happenned while SMON was doing logging scn-> time mapping.

The overall analysis error is mainly caused by an undo exception. You can set db_block_checking and other relevant parameters by setting _ uploupted_rollback_segments to clear SMON_SCN_TIME and other database operation errors. Then, you can rebuild the database logically.

Original article from: Workshop