If you cannot recover the data by yourself, ask Parnassusdata, the professional ORACLE database recovery team for help.
Parnassusdata Software Database Recovery Team
Service Hotline: +86 13764045638 E-mail: service@parnassusdata.com
Applies to:
Oracle Server - Enterprise Edition - Version 11.2.0.1.0 and later
Information in this document applies to any platform.
***Checked for relevance on 23-Nov-2012***
Symptoms
Database fails to open after crash with
ORA-00600: intern felkod, argument: [kcrf_resilver_log_1], [0x3B0E7AA68], [2]
From the trace file generated:
----- Current SQL Statement for this session (sql_id=1h50ks4ncswfn) -----
ALTER DATABASE OPEN
----- Call Stack Trace -----
kgeasnmierr
kcrf_write_zeroblks
kcrfis
kcrfais
kcrfr_read_disk
kcrfr_read
kcrfrgv
kcratr_scan
kcratr
kctrec
kcvcrv
Cause
Unpblished Bug 9056657: BOX REBOOT DURING UPGRADE CAUSED ORA-600 [KCRF_RESILVER_LOG_1]
There has been a lost write to the online redolog as a result of the crash.
The fix for this bug will raise a more meaning log corruption error rather than an ORa-00600 error.
Instance recovery is not possible - restore the database and do point in time recovery to the most recent archivelog.
Solution
Unpublished Bug 9056657 is included in 11.2.0.2 Patch Set Release.
Backports may be requested.