ORACLE 8.1.7 Database ORA-600 4000 Recovery sample

There are many ORA-600 4000 errors encountered during the recovery of the database, but in Oracle 8i (8.1.7) This is the first time to make a memory for reference:
Database failure causes: The current redo is corrupted because of a storage exception, and the _allow_resetlogs_corruption parameter attempts to open the database
Media Recovery Log
Kcrrga:warning. Log sequence in archive filename wrapped
To fix length as indicated by%s in Log_archive_format.
The old log archive with same name might is overwritten.
ORA-279 signalled during:alter database RECOVER database using Backup cont ...
Wed Aug 20 23:01:43 2014
ALTER DATABASE RECOVER CANCEL
Media Recovery Cancelled
Completed:alter DATABASE RECOVER CANCEL
Wed Aug 20 23:01:50 2014
ALTER DATABASE open Resetlogs

Resetlogs is being done without consistancy checks. This could result
In a corrupted database. The database should be recreated.
Resetlogs after incomplete recovery UNTIL change 262618871
Wed Aug 20 23:01:50 2014
Thread 1 opened at log sequence 1
Current log# 3 seq# 1 mem# 0:f:redo01. LOG
Successful open of Redo thread 1.
Wed Aug 20 23:01:50 2014
Smon:enabling Cache Recovery
Wed Aug 20 23:01:50 2014
Errors in file c:oracleadminycfdudumpora00320.trc:
ORA-00600:??????????: [4000], [3], [], [], [], [], [], []

Smon:disabling Cache Recovery
Wed Aug 20 23:01:51 2014
ORA-704 signalled during:alter database open resetlogs
Database encountered ORA-600 4000 error, database could not be opened, parse corresponding trace log
Dump file C:oracleadminycfdudumpora00320.trc
Wed Aug 20 23:01:50 2014
ORACLE v8.1.7.0.0-production vsnsta=0
Vsnsql=e vsnxtr=3
Windows Version 5.2 Service Pack 2, CPU type 586
Oracle8i Release 8.1.7.0.0-production
Jserver Release 8.1.7.0.0-production
Windows Version 5.2 Service Pack 2, CPU type 586
Instance NAME:YCFD

Redo thread mounted by this instance:1

Oracle Process Number:8

Windows thread id:320, image:oracle. Exe


Session ID: (7.1) 2014-08-20 23:01:50.838
2014-08-20 23:01:50.838
Ksedmp:internal or fatal error
ORA-00600:??????????: [4000], [3], [], [], [], [], [], []
Current SQL statement for this session:
Select CTime, Mtime, stime from obj$ where obj# =: 1
-----Call Stack Trace-----
As can be seen here, because the database needs to execute select CTime at startup, Mtime, stime from obj$ where obj# = 1 statements, but for each reason ORA-600 4000 causes the database to not start properly, continue parsing the log
Lock Header dump:0x0040003e
Object ID on block? Y
seg/obj:0x12 csc:0x00.fb5c5c5 itc:1 FLG:-Typ:1-DATA
fsl:0 fnx:0x0 ver:0x01

Itl Xid Uba Flag Lck SCN/FSC
0x01 xid:0x0003.012.0002ae94 uba:0x00801f5b.5389.11--u-1 FSC 0x0000.0fb5c5c6


Sql> select checkpoint_change# from V$database;

263570122
It is obvious here that there is a problem with the corresponding transaction in the third # rollback segment through XID:
1. There is a transaction on the block for file 1 Bock 62,object_id (obj$)
2. The SCN for this transaction is 263,570,886>database SCN (263570122) that causes the fault to occur
3. When the database accesses file 1 Block 62, a transaction is found that has a SCN greater than the database SCN, resulting in ora-600[4000]
There are several ways to solve this problem
1. Modify block 62 To manually submit the transaction
2. Modify the database SCN to make the database SCN larger than ITL SCN
The following error occurred after resolving the Block 62 transaction problem
Wed Aug 20 23:03:55 2014
Smon:enabling Cache Recovery
Wed Aug 20 23:03:55 2014
Dictionary Check Beginning
Dictionary Check Complete
Wed Aug 20 23:03:55 2014
smon:enabling TX Recovery
Wed Aug 20 23:03:56 2014
Errors in file c:oracleadminycfdbdumpycfdsmon.trc:
Ora-00600:internal error code, arguments: [4193], [21173], [21181], [], [], [], [], []

Recovery of Online Redo log:thread 1 Group 1 Seq 2 Reading mem 0
mem# 0 errs 0:f:redo03. LOG
Smon:terminating instance due to error 600
Instance terminated by Smon, PID = 2468
The database appears ORA-600 4193, which is a common error because redo records and undo records do not match, and can be directly used _corrupted_rollback_segments/_offline_rollback_ Segments Shield rollback segment skipped
Wed Aug 20 23:08:10 2014
Smon:enabling Cache Recovery
smon:enabling TX Recovery
Smon:about to recover undo Segment 1
Smon:mark Undo Segment 1 as needs recovery
Smon:about to recover undo segment 2
Smon:mark Undo Segment 2 as needs recovery
Smon:about to recover undo segment 3
Smon:mark Undo Segment 3 as needs recovery
Smon:about to recover undo segment 4
Smon:mark Undo Segment 4 as needs recovery
Smon:about to recover undo segment 5
Smon:mark Undo Segment 5 as needs recovery
Smon:about to recover undo segment 6
Smon:mark Undo Segment 6 as needs recovery
Smon:about to recover undo segment 7
Smon:mark Undo Segment 7 as needs recovery
Smon:about to recover undo Segment 1
Smon:mark Undo Segment 1 as needs recovery
Smon:about to recover undo segment 2
Smon:mark Undo Segment 2 as needs recovery
Smon:about to recover undo segment 3
Smon:mark Undo Segment 3 as needs recovery
Smon:about to recover undo segment 4
Smon:mark Undo Segment 4 as needs recovery
Smon:about to recover undo segment 5
Smon:mark Undo Segment 5 as needs recovery
Smon:about to recover undo segment 6
Smon:mark Undo Segment 6 as needs recovery
Smon:about to recover undo segment 7
Smon:mark Undo Segment 7 as needs recovery
Wed Aug 20 23:08:15 2014
Completed:alter Database Open

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