ORA-00600 kclchkblk_4 Error Recovery Method Introduction (1/2)

The article summarizes the ORA-00600 kclchkblk_4 error recovery methods, there is a need to learn friends can refer.

Recently the customer encountered a ORA-600 kclchkblk_4 error while restoring the database, which has official explanations and solutions on MOS.

The following error message is displayed:

The Code is as follows:

Copy code

Errors in file/u01/app/oracle/admin/orcl/bdump/orcl_smon_7493.trc: ORA-600: internal error code, arguments: [kclchkblk_4], [1904], [18446744073431179384], [1904], 18446744073403569507], [], [], [] Starting background process QMNC QMNC started with pid = 24, OS id = 8329 Errors in file/u01/app/oracle/admin/orcl/bdump/orcl_smon_7493.trc: ORA-600: internal error code, arguments: [2662], [1904], [3988985522], [1904], [4016595064], [8388610], [], [] Errors in file/u01/app/oracle/admin/orcl/bdump/orcl_smon_7493.trc: ORA-600: internal error code, arguments: [2662], [1904], [3988985525], [1904], [4016595064], [8388610], [], [] SMON: terminating instance due to error 474 Instance terminated by SMON, pid = 7493

The problem may be caused by the SCN problem of the temporary tablespace. You can try to delete all the temporary files and start the database, which may usually start normally.
The possible steps are to determine and delete the temporary file in the Mount state:

The Code is as follows:	Copy code
SQL> select file_name, file_id from dba_temp_files; SQL> alter database tempfile_name drop; SQL> alter tablespace add tempfile size N;

If the database can be started successfully, you can recreate a temporary file.

Problem description:
The server suddenly fails and crashes, causing the database to fail to drive and the CURRENT redo group to be damaged. Oracle 10g rac environment, asm disk group, redhat linux system. One member in each group is the key to failure to repair the group.
No archive and no backup. You cannot use ASM to cold back up data files.

The Code is as follows:	Copy code
ORA-00368: checksum error in redo log block. ORA-00353: log uption near block 254606 change 12131176305969 time 03/08/2011 01:03:00 ORA-00312: online log 2 thread 1: '+ DG1/police/onlinelog/group_2.258.657430669'

View the log group file information. The error log group is in CURRENT mode.

The Code is as follows:	Copy code
SQL> select group #, sequence #, archived, status from v $ log; GROUP # SEQUENCE # ARC STATUS --------------------------------------- 1 17495 NO INACTIVE 2 17496 NO CURRENT 3 17365 NO INACTIVE 4 17366 NO CURRENT

There is only one group member.

 

The Code is as follows:	Copy code
SQL> Group Instance Member STATUS Size (MB) ---------------------------------------------------------------------------- 1 1 + DG1/police/onlinelog/group_1. INACTIVE 500 257.657430665 2 1 + DG1/police/onlinelog/group_2. CURRENT 500 258.657430669 3 2 + DG1/police/onlinelog/group_3. INACTIVE 500 265.657431819 4 2 + DG1/police/onlinelog/group_4. CURRENT 500 266.657431825

You cannot use the clear command to clear redo information.

The Code is as follows:

Copy code

SQL> alter database clear unarchived logfile group 2 2; Alter database clear unarchived logfile group 2 * ERROR at line 1: ORA-01624: log 2 needed for crash recovery of instance found E1 (thread 1) ORA-00312: online log 2 thread 1: '+ DG1/police/onlinelog/group_2.258.657430669' SQL> alter database clear logfile group 2; Alter database clear logfile group 2 * ERROR at line 1: ORA-01624: log 2 needed for crash recovery of instance found E1 (thread 1) ORA-00312: online log 2 thread 1: '+ DG1/police/onlinelog/group_2.258.657430669'

Procedure

Drop the database

The Code is as follows:	Copy code
SQL> shutdown immediate

5. Add the following parameters to init <sid>. ora:

The Code is as follows:	Copy code
_ Allow_resetlogs_upload uption = TRUE

6. Restart the database and use until cancel to restore the database.

SQL> recover database until cancel;
Cancel

If an error occurs, ignore it and send it.

The Code is as follows:	Copy code
SQL> alter database open resetlogs;

If you are lucky, you can start the database and export the data. However, it is a bit unexpected. I don't know whether it is a special back-to-back or rac environment recovery. The following error is reported in alert. log:

The Code is as follows:

Copy code

Errors in file/u01/app/oracle/admin/police/bdump/export e2_j003_1771_trc: ORA-00600: internal error code, arguments: [4194], [9], [8], [], [], [], [], [], [] Wed Mar 9 18:08:06 2011 Errors in file/u01/app/oracle/admin/police/bdump/export e2_j004_17722.trc: ORA-00600: internal error code, arguments: [4193], [55749], [55753], [], [], [], [], [], [] Wed Mar 9 18:08:08 2011 Errors in file/u01/app/oracle/admin/police/bdump/export e2_mmon_11328.trc: ORA-00600: internal error code, arguments: [4194], [12], [17], [], [], [], [], [], [] Wed Mar 9 18:08:08 2011 Errors in file/u01/app/oracle/admin/police/bdump/export e2_j002_17718.trc: ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_3], [0], [0], [1], [], [], [], [], []

1 2