Oracle power off causes database ORA-600 kccpb_sanity_check_2 failure recovery

Today, someone is looking for me in Taobao, need Oracle Database recovery support

Remote login to see the database mount when the report Ora-600[kccpb_sanity_check_2] Error

C:\Documents and Settings\administrator>sqlplus/as Sysdba

Sql*plus:release 10.2.0.3.0-production on Wed June 29 16:23:18 2015

Copyright (c) 1982, 2006, Oracle. All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-production
With the partitioning, OLAP and Data Mining options

Sql> ALTER DATABASE Mount;
ALTER DATABASE Mount
*
ERROR at line 1:
Ora-00600:internal error code, arguments: [Kccpb_sanity_check_2], [14169],
[14160], [0x0], [], [], [], []

Try to rebuild the control file

sql> shutdown immediate;
Ora-01507:database not mounted


ORACLE instance shut down.
sql> startup pfile= ' D:\database\m104\pfile\init.ora ' Nomount
ORACLE instance started.

Total System Global area 444596224 bytes
Fixed Size 1291072 bytes
Variable Size 155192512 bytes
Database buffers 281018368 bytes
Redo buffers 7094272 bytes

Sql> show PARAMETER CONT;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
Control_file_record_keep_time Integer 7
Control_files string D:\DATABASE\M104\CTRL\CONTROL0
2.CTL
Global_context_pool_size string
sql> ALTER DATABASE MOUNT;
ALTER DATABASE MOUNT
*
ERROR at line 1:
Ora-00600:internal error code, arguments: [Kccpb_sanity_check_2], [14169],
[14160], [0x0], [], [], [], []


Sql>
Sql> CREATE controlfile Reuse DATABASE "m104_db" Noresetlogs FORCE LOGGING Noar
Chivelog
2 Maxlogfiles 16
3 Maxlogmembers 3
4 Maxdatafiles 100
5 Maxinstances 8
6 Maxloghistory 2921
7 LOGFILE
8 GROUP 1 ' D:\database\m104\log\redo01.log ' SIZE 51200K,
9 GROUP 2 ' D:\database\m104\log\redo02.log ' SIZE 51200K,
GROUP 3 ' D:\database\m104\log\redo03.log ' SIZE 51200K
One datafile
' D:\database\m104\data\system01.dbf ',
' D:\database\m104\data\sysaux01.dbf ',
' D:\database\m104\data\USERS01. DBF ',
' D:\database\m104\data\UNDOTBS01. DBF ',
' D:\database\m104\data\INDX01. DBF '
CHARACTER SET WE8ISO8859P1
18;
CREATE controlfile Reuse DATABASE "m104_db" Noresetlogs FORCE LOGGING noarchive
LOG
*
ERROR at line 1:
Ora-01503:create Controlfile failed
Ora-00600:internal error code, arguments: [Kccsga_update_ckpt_4], [1], [8],
[], [], [], [], []

Sql>
Sql> CREATE controlfile Reuse DATABASE "m104_db" Resetlogs FORCE LOGGING Noarch
Ivelog
2 Maxlogfiles 16
3 Maxlogmembers 3
4 Maxdatafiles 100
5 Maxinstances 8
6 Maxloghistory 2921
7 LOGFILE
8 GROUP 1 ' D:\database\m104\log\redo01.log ' SIZE 51200K,
9 GROUP 2 ' D:\database\m104\log\redo02.log ' SIZE 51200K,
GROUP 3 ' D:\database\m104\log\redo03.log ' SIZE 51200K
One datafile
' D:\database\m104\data\system01.dbf ',
' D:\database\m104\data\sysaux01.dbf ',
' D:\database\m104\data\USERS01. DBF ',
' D:\database\m104\data\UNDOTBS01. DBF ',
' D:\database\m104\data\INDX01. DBF '
CHARACTER SET WE8ISO8859P1
18;
CREATE controlfile Reuse DATABASE "m104_db" Resetlogs FORCE LOGGING Noarchivelo
G
*
ERROR at line 1:
Ora-01503:create Controlfile failed
Ora-00600:internal error code, arguments: [Kccsga_update_ckpt_4], [1], [8],
[], [], [], [], []

The rebuild control files are reported to be ora-600[kccsga_update_ckpt_4 by using either Noresetlogs or Resetlogs. Strange, no solution specifies the new name reconstruction of the control file try it.

Modify the control file path

Sql> SHUTDOWN ABORT
ORACLE instance shut down.
sql> startup pfile= ' D:\database\m104\pfile\init.ora ' Nomount
ORACLE instance started.

Total System Global area 444596224 bytes
Fixed Size 1291072 bytes
Variable Size 155192512 bytes
Database buffers 281018368 bytes
Redo buffers 7094272 bytes
Sql> show PARAMETER CONT;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
Control_file_record_keep_time Integer 7
Control_files string D:\DATABASE\M104\CTRL\CONTROL0
4.CTL
Global_context_pool_size string
Sql> CREATE controlfile Reuse DATABASE "m104_db" Resetlogs FORCE LOGGING Noarch
Ivelog
2 Maxlogfiles 16
3 Maxlogmembers 3
4 Maxdatafiles 100
5 Maxinstances 8
6 Maxloghistory 2921
7 LOGFILE
8 GROUP 1 ' D:\database\m104\log\redo01.log ' SIZE 51200K,
9 GROUP 2 ' D:\database\m104\log\redo02.log ' SIZE 51200K,
GROUP 3 ' D:\database\m104\log\redo03.log ' SIZE 51200K
One datafile
' D:\database\m104\data\system01.dbf ',
' D:\database\m104\data\sysaux01.dbf ',
' D:\database\m104\data\USERS01. DBF ',
' D:\database\m104\data\UNDOTBS01. DBF ',
' D:\database\m104\data\INDX01. DBF '
CHARACTER SET WE8ISO8859P1
18;

Control file created.

Using the new control file location, this time finally the database rebuild control file succeeded
Attempt to specify redo for recovery, database open normally

sql> RECOVER DATABASE USING BACKUP controlfile UNTIL CANCEL;
Ora-00279:change 3643108240801 generated at 07/26/2015 20:15:22 for
Thread 1
Ora-00289:suggestion:
D:\ORACLE\PRODUCT\10.2.0\DB_1\RDBMS\ARC00567_0866390669.001
Ora-00280:change 3643108240801 for thread 1 was in sequence #567


Specify log: {<ret>=suggested | AUTO | CANCEL}
D:\database\m104\log\redo01.log
Ora-00310:archived log contains sequence 566; Sequence 567 Required
ora-00334:archived log: ' D:\DATABASE\M104\LOG\REDO01. LOG '


Ora-01547:warning:recover succeeded but OPEN Resetlogs would get error below
Ora-01194:file 1 needs more recovery to be consistent
Ora-01110:data file 1: ' D:\DATABASE\M104\DATA\SYSTEM01. DBF '


sql> RECOVER DATABASE USING BACKUP controlfile UNTIL CANCEL;
Ora-00279:change 3643108240801 generated at 07/26/2015 20:15:22 for
Thread 1
Ora-00289:suggestion:
D:\ORACLE\PRODUCT\10.2.0\DB_1\RDBMS\ARC00567_0866390669.001
Ora-00280:change 3643108240801 for thread 1 was in sequence #567


Specify log: {<ret>=suggested | AUTO | CANCEL}
D:\database\m104\log\redo02.log
Log applied.
Media recovery complete.
sql> ALTER DATABASE OPEN resetlogs;

Database altered.

Database recovery complete. The entire database recovery is relatively simple, but note here Ora-600[kccsga_update_ckpt_4] through the modification of the control file path evasion, specific reasons.

Knowledge points added: ORA-600 [kccpb_sanity_check_2] [A] [b] {C}
Versions:
Versions 10.2 to 11.2

DESCRIPTION:

This internal error was raised when the sequence number (seq#) of the
The controlfile is greater than the seq# in the Controlfile header.

The header value should always is equal to, or greater than the value
Held in the control file block (s).

This extra check is introduced in Oracle 10GR2 to detect lost writes
or stale reads to the header.

ARGUMENTS:
Arg [A] seq# in the control block header.
Arg [b] seq# in the control file header.
ARG {C}

Contact: Mobile Phone (13429648788) QQ (107644445)
Link: http://www.xifenfei.com/6001.html