Oracle Database ORA-00354 ORA-00353 ORA-00312 exception handling

Database starts error

Win platform Oracle 9.2.0.6 version Database redo log block header corrupted, ORA-00354 ORA-00353 ORA-00312 error causing database to fail to start
SQL >alter database open;
*
ERROR at line 1:

Ora-00354:corrupt Redo Log Block header
Ora-00353:log corruption near block 1892904 change 281470950178815
Ora-00312:online Log 3 thread 1: ' D:\ORACLE\ORADATA\ZOYO\REDO03. LOG '
Sun 24 15:44:05 2016
Database mounted in Exclusive Mode.
Completed:alter Database Mount Exclusive
Sun 24 15:44:05 2016
ALTER DATABASE Open
Sun 24 15:44:05 2016
Beginning crash recovery of 1 threads
Sun 24 15:44:05 2016
Started Redo scan
ORA-354 signalled during:alter database open ...
Shutting down Instance:further logons disabled
Shutting down instance (immediate)
License High Water mark = 3
Sun 24 15:44:32 2016
ALTER DATABASE Close NORMAL
ORA-1109 signalled During:alter DATABASE close NORMAL ...

Through analysis, determine that the damaged redo03 is the current redo, can not be opened using the normal method, plus the _allow_resetlogs_corruption parameters, try to open the library, still fail

Database report ORA-600 2662 error

Sun 24 16:26:30 2016
Smon:enabling Cache Recovery
Sun 24 16:26:30 2016
Errors in file d:\oracle\admin\zoyo\udump\zoyo_ora_640.trc:
ORA-00600: Internal error code, parameters: [2662], [0], [31563641], [0], [31563654], [4194721], [], []

Sun 24 16:26:31 2016
Errors in file d:\oracle\admin\zoyo\udump\zoyo_ora_640.trc:
ORA-00704: Bootstrapper process failed
ORA-00600: Internal error code, parameters: [2662], [0], [31563641], [0], [31563654], [4194721], [], []

Sun 24 16:26:31 2016
Error 704 happened during DB Open, shutting down database
User:terminating instance due to error 704
Instance terminated by USER, PID = 640
ORA-1092 signalled during:alter database open resetlogs ...
Error handling for ORA 600 2662

According to experience, this error only needs to push the SCN, you can through bbed, hidden parameters, Event,oradebug, modify control files and other methods, push the SCN, the database reported familiar ORA-00604 ORA-00607 ORA-600 4194 errors, The block we met before was mostly 128, this time the exception block is 9. In fact, it has to do with the version, in Oracle 9.2.0.6 the error is file 1 Block 9. Most versions are 128
Sun before 24 16:29:39 2016
smon:enabling Cache Recovery
Sun 16:29:39 2016
Errors in file d:\oracle\admin\zoyo\udump\zoyo_ora_343 2.TRC:
ORA-00600: Internal error code, parameters: [4194], [n], [5], [], [], [], [], []
 
Sun: 16:29:39 2016
doing B Lock recovery for fno:1 blk:401
Sun 16:29:39 2016
Recovery of Online Redo log:thread 1 Group 1 Seq 2 Rea Ding mem 0
  mem# 0 errs 0:d:\oracle\oradata\zoyo\redo01. LOG
doing block recovery for fno:1 blk:9
Sun 16:29:40 2016
Recovery of Online Redo Log:thread 1 Grou P 1 Seq 2 Reading mem 0
  mem# 0 errs 0:d:\oracle\oradata\zoyo\redo01. LOG
Sun 16:29:40 2016
Errors in file d:\oracle\admin\zoyo\udump\zoyo_ora_3432.trc:

ORA-00604: Recursive SQL Layer 1 error occurred
ORA-00607: An internal error occurred while changing the data block
ORA-00600: Internal error code, parameters: [4194], [14], [5], [], [], [], [], []

Error 604 happened during DB Open, shutting down database
User:terminating instance due to error 604
Instance terminated by USER, PID = 3432
ORA-00604 ORA-00607 ORA-600 4194 Analysis trace file
2016-01-24 16:29:40.031
Recovery of Online Redo log:thread 1 Group 1 Seq 2 Reading mem 0

Block image after block recovery:
Buffer tsn:0 rdba:0x00400009 (1/9)
Scn:0x0000.01e112e1 seq:0x01 flg:0x04 tail:0x12e10e01
frmt:0x02 chkval:0xba76 type:0x0e=ktu UNDO HEADER w/unlimited extents
Extent Control Header
-----------------------------------------------------------------
Extent Header:: spare1:0 spare2:0 #extents: 6 #blocks: 47
Last map 0x00000000 #maps: 0 offset:4128
Highwater:: 0x00400191 ext#: 4 blk#: 0 ext Size:8
#blocks in SEG. HDR ' s freelists:0
#blocks below:0
MAPBLK 0x00000000 Offset:4
Unlocked
Map Header:: Next 0x00000000 #extents: 6 obj#: 0 flag:0x40000000
Extent Map
-----------------------------------------------------------------
0x0040000a Length:7
0x00400011 Length:8
0x00400181 Length:8
0x00400189 Length:8
0x00400191 Length:8
0x00400199 Length:8

TRN CTL:: seq:0x008e chd:0x0060 ctl:0x0024 inc:0x00000000 nfb:0x0001
mgc:0x8002 xts:0x0068 flg:0x0001 opt:2147483646 (0x7ffffffe)
uba:0x00400191.008e.04 scn:0x0000.01ded29c
version:0x01
Free Block POOL::
uba:0x00400191.008e.04 ext:0x4 spc:0x1c3e
uba:0x00000000.002f.21 ext:0x5 spc:0x1334
uba:0x00000000.002e.37 ext:0x4 spc:0x788
uba:0x00000000.0000.00 ext:0x0 spc:0x0
uba:0x00000000.0000.00 ext:0x0 spc:0x0
TRN TBL::

From here you can determine that there is a problem with the allocation block record in the Undo segment header, clear KTUXC.FBP.FBP[N].KUBA.KDBA related records, and open the database normally

. struct KTUXC kernel transaction undo Xaction Table Control
. {
. struct KSCN SCN with 3 members
. {
04148 UB4 bas = 0x9cd2de01 = 31380124
04152 ub2 WRP = 0X0000 = 0
04154 Cc32 pad = 0X0000 = 0
. }
. struct Kuba uba with 4 members
. {
04156 Kdba dba = 0x91014000 = 0x00400191 file 1 Block 401
04160 ub2 seq = 0x8e00 = 142
04162 Ub1 rec = 0X04 = 4
04163 CC16 pad = 0X00 = 0
. }
04164 SB2 FLG = 0X0100 = 1
04166 ub2 seq = 0x8e00 = 142
04168 SB2 NFB = 0X0100 = 1
04170 Cc32 pad1 = 0X0000 = 0
04172 UB4 inc = 0X00000000 = 0
04176 SB2 CHD = 0x6000 = 96
04178 SB2 ctl = 0x2400 = 36
04180 ub2x MGC = 0x0280 = 0x8002
04182 UB2 ver = 0X0100 = 1
04184 ub2 xts = 0x6800 = 104
04186 Cc32 pad2 = 0X0000 = 0
04188 ub4 opt = 0xfeffff7f = 2147483646
. KTUFB fbp[5] (array with 5 elements)
. struct FBP [0] with 3 members
. {
. struct Kuba uba with 4 members
. {
04192 Kdba dba = 0x91014000 = 0x00400191 file 1 Block 401
04196 ub2 seq = 0x8e00 = 142
04198 Ub1 rec = 0X04 = 4
04199 CC16 pad = 0X00 = 0
. }
04200 SB2 ext = 0x0400 = 4
04202 SB2 spc = 0X3E1C = 7230
. }
. struct FBP [1] with 3 members
. {
. struct Kuba uba with 4 members
. {
04204 Kdba dba = 0X00000000 = 0X00000000 file 0 Block 0
04208 ub2 seq = 0x2f00 = 47
04210 Ub1 rec = 0x21 = 33
04211 CC16 pad = 0X00 = 0
. }
04212 SB2 ext = 0x0500 = 5
04214 SB2 spc = 0x3413 = 4916
. }
. struct FBP [2] with 3 members
. {
. struct Kuba uba with 4 members
. {
04216 Kdba dba = 0X00000000 = 0X00000000 file 0 Block 0
04220 ub2 seq = 0x2e00 = 46
04222 Ub1 rec = 0x37 = 55
04223 CC16 pad = 0X00 = 0
. }
04224 SB2 ext = 0x0400 = 4
04226 SB2 spc = 0x8807 = 1928
. }
. struct FBP [3] with 3 members
. {
. struct Kuba uba with 4 members
. {
04228 Kdba dba = 0X00000000 = 0X00000000 file 0 Block 0
04232 ub2 seq = 0X0000 = 0
04234 Ub1 rec = 0X00 = 0
04235 CC16 pad = 0X00 = 0
. }
04236 SB2 ext = 0X0000 = 0
04238 SB2 spc = 0X0000 = 0
. }
. struct FBP [4] with 3 members
. {
. struct Kuba uba with 4 members
. {
04240 Kdba dba = 0X00000000 = 0X00000000 file 0 Block 0
04244 ub2 seq = 0X0000 = 0
04246 Ub1 rec = 0X00 = 0
04247 CC16 pad = 0X00 = 0
. }
04248 SB2 ext = 0X0000 = 0
04250 SB2 spc = 0X0000 = 0
. }
. }
Sun 24 16:44:52 2016
smon:enabling TX Recovery
Sun 24 16:44:52 2016
Database Characterset is ZHS16GBK
Replication_dependency_tracking turned off (no async multimaster replication found)
Completed:alter DATABASE OPEN