Oracle Database ORA-600 kcrfr_update_nab_2 Failure recovery

The database startup report ORA-600 kcrfr_update_nab_2 error due to the Controller drop line, resulting in the failure of the normal open
Database version Information
ORACLE v10.2.0.4.0-64bit Production vsnsta=0
Vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition release 10.2.0.4.0-64bit Production
With the partitioning, OLAP, Data Mining and real application testing options
Windows Server 2003 Version V5.2 Service Pack 2
Cpu:12-type 8664, 2 physical cores
Process affinity:0x0000000000000000
Memory (avail/total): ph:22579m/32754m, ph+pgf:24594m/33845m
ORA-600 kcrfr_update_nab_2 Error
Mon OCT 24 17:42:57 2016
Database mounted in Exclusive Mode
Completed:alter DATABASE MOUNT
Mon OCT 24 17:42:58 2016
ALTER DATABASE OPEN
Mon OCT 24 17:43:14 2016
Beginning crash recovery of 1 threads
Parallel recovery started with one processes
Mon OCT 24 17:43:14 2016
Started Redo scan
Mon OCT 24 17:43:16 2016
Errors in file d:\oracle\product\10.2.0\admin\spcsjkdb\udump\spcsjkdb_ora_10108.trc:
Ora-00600:internal error code, arguments: [kcrfr_update_nab_2], [0x7ffc22a2150], [2], [], [], [], [], []

Mon OCT 24 17:43:18 2016
Aborting crash recovery due to error 600
Mon OCT 24 17:43:18 2016
Errors in file d:\oracle\product\10.2.0\admin\spcsjkdb\udump\spcsjkdb_ora_10108.trc:
Ora-00600:internal error code, arguments: [kcrfr_update_nab_2], [0x7ffc22a2150], [2], [], [], [], [], []

ORA-600 signalled During:alter DATABASE OPEN ...
Trace File Information
2016-10-24 17:43:14.515
ACTION NAME: () 2016-10-24 17:43:14.515
MODULE NAME: (sqlplus.exe) 2016-10-24 17:43:14.515
SERVICE NAME: () 2016-10-24 17:43:14.515
Session ID: (356.3) 2016-10-24 17:43:14.515
Successfully allocated recovery slaves
Using overflow buffers per recovery slave
Thread 1 checkpoint:logseq 33251, Block 2, SCN 14624215134369
Cache-low rba:logseq 33251, Block 2463324
On-disk rba:logseq 33251, Block 2803965, SCN 14624216078841
Start recovery at Logseq 33251, Block 2463324, SCN 0
2016-10-24 17:43:16.406
Ksedmp:internal or fatal error
Ora-00600:internal error code, arguments: [kcrfr_update_nab_2], [0x7ffc22a2150], [2], [], [], [], [], []
Current SQL statement for this session:
ALTER DATABASE OPEN
-----Call Stack Trace-----
Calling call entry argument values in hex
Location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp+663 Call??? ksedst+55 003c878b8 000000000 012b863e8
000000000
Ksfdmp+19 Call??? ksedmp+663 000000003 015572a70 007222698
003cacc80
kgerinv+158 Call??? ksfdmp+19 015572430 000000000 0FFFFFFFF
000000000
KGEASNMIERR+62 Call??? kgerinv+158 000000000 000000000 000000000
004fd788f
Kcrfr_update_nab+18 Call??? kgeasnmierr+62 00bda1170 000000000 000000000
6 000000002
kcrfr_read+1078 Call??? kcrfr_update_nab+18 007222698 00001E650 015572430
6 0072229b8
kcrfrgv+8134 Call??? kcrfr_read+1078 000000000 0051525d7 000000000
0051525d7
kcratr1+488 Call??? kcrfrgv+8134 007222698 000000000 000000000
000000000
kcratr+412 Call??? kcratr1+488 012b891c8 012b890a4 00727ffb8
00bea7ff0
kctrec+1910 Call??? kcratr+412 012b891c8 012b91e18 000000000
012b91e48
kcvcrv+3585 Call??? kctrec+1910 012b92c58 000000000 00726df00
00726bdb0
kcfopd+1007 Call??? kcvcrv+3585 012b93350 000000000 000000000
000000000
adbdrv+55820 Call??? kcfopd+1007 000000000 000000000 000000000
000000000
opiexe+13897 Call??? adbdrv+55820 000000023 000000003 000000102
000000000
opiosq0+3558 Call??? opiexe+13897 000000004 000000000 012b9b238
4155474e414c5f45
kpooprx+339 Call??? opiosq0+3558 000000003 00000000E 012b9b3c8
0000000a4
kpoal8+894 Call??? kpooprx+339 015587550 000000018 0041ae700
000000001
opiodr+1136 Call??? kpoal8+894 00000005E 000000017 012b9e868
0072f5100
ttcpip+5146 Call??? opiodr+1136 00000005E 000000017 012b9e868
2d8c00000000
opitsk+1818 Call??? ttcpip+5146 015587550 000000000 000000000
000000000
opiino+1129 Call??? opitsk+1818 00000001E 000000000 000000000
000000000
opiodr+1136 Call??? opiino+1129 00000003C 000000004 012b9fb20
000000000
opidrv+815 Call??? opiodr+1136 00000003C 000000004 012b9fb20
000000000
sou2o+52 Call??? opidrv+815 00000003C 000000004 012b9fb20
7ff7fc48580
opimai_real+131 Call??? sou2o+52 000000000 012B9FC40
7fffff7f258 077ef4d1c
opimai+96 Call??? opimai_real+131 7ff7fc48580 7fffff7e000
0001f0003 000000000
Oraclethreadstart+6 Call??? opimai+96 012B9FEF0 01289ff3c 012b9fcc0
7ff7fc48580
0000000077d6b6da Call??? Oraclethreadstart+6 01289ff3c 000000000 000000000
012b9ffa8
Official description
The Assert ORA-600: [kcrfr_update_nab_2] is a direct result of a lost write in the ' current ' line log that we are attempt ing to resolve. So, this confirms the theory of this is a os/hardware lost write issue not a internal Oracle bug. In fact the assert ORA-600: [kcrfr_update_nab_2] are how we detect a lost log write.
Bug 5692594
hdr:5692594 10.2.0.1 RDBMS 10.2.0.1 RECOVERY PRODID-5 PORTID-226
Abstract:after DATABASE crashed doesn ' T OPEN ORA-600 [kcrfr_update_nab_2]
status:95,closed, Vendor OS Problem
Bug 6655116
hdr:6655116 10.2.0.3 RDBMS 10.2.0.3 RECOVERY PRODID-5 PORTID-23
Abstract:instances CRASH with ORA-600 [kcrfr_update_nab_2] after DISK failure
According to the official description, combined with the fault situation, it is basically determined that the Oracle write is lost due to a hardware exception, so unless the Oracle-related bugs cause the database to not start properly
ORA-600 [kcrfr_update_nab_2] [A] [b]


Versions:
Versions 10.2 to 11.1

DESCRIPTION:

Failure of upgrade of recovery node (RN) Enqueue to SSX mode

ARGUMENTS:
ARG [A] state Object for redo NAB Enqueue for resilvering
Arg [b] Redo NAB enqueue mode

Functionality:
Kernel Cache Redo File Read

IMPACT:

INSTANCE failure
Processing methods
1. If there is a backup, use Backup for incomplete recovery, skip the last exception redo, the database resetlogs open
2. If there is no backup, try to use historical control files for incomplete recovery, or simply skip database consistency to open the library.

Original from: http://www.xifenfei.com/2016/10/ora-600-kcrfr_update_nab_2.html