Incident details in: d: \ oracle \ diag \ rdbms \ yccy \ yccy \ incident \ incdir_131022 \ yccy_pr04_3980_i131022.trc
Errors in file d: \ oracle \ diag \ rdbms \ yccy \ yccy \ trace \ yccy_pr0e_3260.trc (incident = 131142):
ORA-07445: exception encountered: core dump [kcbzpnd () + 299] [ACCESS_VIOLATION] [ADDR: 0xFFFFFFFFFFFFFFFF] [PC: 0x12EC13B] [UNABLE_TO_READ] []
ORA-00600: internal error code, arguments: [3020], [5], [163457], [21134977], [], [], [], [], [], [], [], [],
ORA-10567: Redo is inconsistent with data block (file # 5, block # 163457, file offset is 1339039744 bytes)
ORA-10564: tablespace DT_SYS_DAT
ORA-01110: data file 5: 'E: \ ORACLE_DATA \ YCCY \ DT_SYS_DAT.ORA'
ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK'
Incident details in: d: \ oracle \ diag \ rdbms \ yccy \ yccy \ incident \ incdir_131142 \ yccy_pr0e_3260_i131142.trc
Mon Mar 28 10:20:41 2016
Trace dumping is performing id = [cdmp_20160328102041]
Errors in file d: \ oracle \ diag \ rdbms \ yccy \ yccy \ trace \ yccy_pr0i_2132.trc (incident = 131174):
ORA-07445: exception encountered: core dump [kcbzpnd () + 299] [ACCESS_VIOLATION] [ADDR: 0xFFFFFFFFFFFFFFFF] [PC: 0x12EC13B] [UNABLE_TO_READ] []
ORA-00600: internal error code, arguments: [3020], [5], [154240], [21125760], [], [], [], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file # 5, block # 154240, file offset is 1263534080 bytes)
ORA-10564: tablespace DT_SYS_DAT
ORA-01110: data file 5: 'E: \ ORACLE_DATA \ YCCY \ DT_SYS_DAT.ORA'
ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK'
Incident details in: d: \ oracle \ diag \ rdbms \ yccy \ yccy \ incident \ incdir_131174 \ yccy_pr0i_2132_i131174.trc
Mon Mar 28 10:20:41 2016
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR: 0x2E7FFFFFE] [PC: 0x74CAE3F0, 0000000074CAE3F0]
Errors in file d: \ oracle \ diag \ rdbms \ yccy \ yccy \ trace \ yccy_pr06_2684.trc (incident = 131077):
ORA-07445: exception encountered: core dump [PC: 0x74CAE3F0] [ACCESS_VIOLATION] [ADDR: 0x2E7FFFFFE] [PC: 0x74CAE3F0] [UNABLE_TO_READ] []
Incident details in: d: \ oracle \ diag \ rdbms \ yccy \ yccy \ incident \ incdir_131077 \ yccy_pr06_2684_i131077.trc
Mon Mar 28 10:20:42 2016
Exception [type: ACCESS_VIOLATION, UNABLE_TO_WRITE] [ADDR: 0x0] [PC: 0x4D20D2, kslgetl () + 54]
Mon Mar 28 10:20:42 2016
Errors in file d: \ oracle \ diag \ rdbms \ yccy \ yccy \ trace \ yccy_pmon_3856.trc (incident = 130853):
ORA-07445: exception encountered: core dump [kslgetl () + 54] [ACCESS_VIOLATION] [ADDR: 0x0] [PC: 0x4D20D2] [UNABLE_TO_WRITE] []
Incident details in: d: \ oracle \ diag \ rdbms \ yccy \ yccy \ incident \ incdir_130853 \ yccy_pmon_3856_i130853.trc
Trace dumping is performing id = [cdmp_20160328102042]
Errors in file d: \ oracle \ diag \ rdbms \ yccy \ yccy \ incident \ incdir_131077 \ yccy_pr06_2684_i131077.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [PC: 0x74CAE3F0] [ACCESS_VIOLATION] [ADDR: 0x2E7FFFFFE] [PC: 0x74CAE3F0] [UNABLE_TO_READ] []
Process debug not enabled via parameter _debug_enable
Trace dumping is performing id = [cdmp_20160328102043]
Mon Mar 28 10:21:01 2016
RECO (ospid: 3524): terminating the instance due to error 472
Instance terminated by RECO, pid = 3524
By observing this log, you can basically find that it is mainly FILE 45. Although a bad block is prompted, the final verification is determined to be a normal block (similar to: Reread (file 45, block 7836) found valid data). Here is mainly file 5, which is reported. A lot of ORA-600 [3020].
Perform recovery operations on the data files one by one
SQL> startup mount;
The ORACLE routine has started.
Total System Global Area 1.7103E + 10 bytes
Fixed Size 2192864 bytes
Variable Size 9059699232 bytes
Database Buffers 8019509248 bytes
Redo Buffers 21762048 bytes
The database is loaded.
SQL> recover datafile 1;
Complete media recovery.
SQL> recover datafile 2;
ORA-03113: end of file for communication channel
Process ID: 1652
Session ID: 551 Serial Number: 55
SQL> recover datafile 3;
Complete media recovery.
SQL> recover datafile 4;
Complete media recovery.
SQL> recover datafile 5;
ORA-03113: end of file for communication channel
Process ID: 4900
Session ID: 551 Serial Number: 56131
SQL> recover datafile 6;
Complete media recovery.
…………
SQL> recover datafile 63;
Complete media recovery.
SQL> recover datafile 64;
Complete media recovery.
Except for datafiles 2, 5, all other files were successfully recovered.
For file 2 try to process
Can't succeed through recover, you can only give up temporarily, and then consider offline opening the library first, and then force this file online
SQL> recover datafile 2;
ORA-03113: end of file for communication channel
Process ID: 5020
Session ID: 551 Serial Number: 3
Mon Mar 28 10:47:12 2016
ALTER DATABASE RECOVER datafile 2
Media Recovery Start
Serial Media Recovery started
Recovery of Online Redo Log: Thread 1 Group 1 Seq 18688 Reading mem 0
Mem # 0: E: \ ORACLE_DATA \ YCCY \ REDO01.LOG
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR: 0x2E7FFFFFE] [PC: 0x74CAE3F0, 0000000074CAE3F0]
Errors in file d: \ oracle \ diag \ rdbms \ yccy \ yccy \ trace \ yccy_ora_3508.trc (incident = 143022):
ORA-07445: exception occurred: core dump [PC: 0x74CAE3F0] [ACCESS_VIOLATION] [ADDR: 0x2E7FFFFFE] [PC: 0x74CAE3F0] [UNABLE_TO_READ] []
Incident details in: d: \ oracle \ diag \ rdbms \ yccy \ yccy \ incident \ incdir_143022 \ yccy_ora_3508_i143022.trc
Errors in file d: \ oracle \ diag \ rdbms \ yccy \ yccy \ incident \ incdir_143022 \ yccy_ora_3508_i143022.trc:
ORA-00607: internal error while changing data block
ORA-00602: internal programming exception error
ORA-07445: exception occurred: core dump [PC: 0x74CAE3F0] [ACCESS_VIOLATION] [ADDR: 0x2E7FFFFFE] [PC: 0x74CAE3F0] [UNABLE_TO_READ] []
For file 5 processing
SQL> recover datafile 5;
ORA-00283: recovery session cancelled due to error
ORA-00600: internal error code, parameters: [3020], [5],
[163457], [21134977], [], [], [],
[], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file # 5, block # 163457, file
offset is 1339039744 bytes)
ORA-10564: tablespace DT_SYS_DAT
ORA-01110: data file 5: 'E: \ ORACLE_DATA \ YCCY \ DT_SYS_DAT.ORA'
ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK'
SQL> recover datafile 5 allow 1 corruption;
ORA-00283: recovery session cancelled due to error
ORA-00600: internal error code, parameters: [3020], [5], [162433], [21133953], [], [], [],
[], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file # 5, block # 162433, file
offset is 1330651136 bytes)
ORA-10564: tablespace DT_SYS_DAT
ORA-01110: data file 5: 'E: \ ORACLE_DATA \ YCCY \ DT_SYS_DAT.ORA'
ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK'
SQL> recover datafile 5 allow 1 corruption;
ORA-00283: recovery session cancelled due to error
ORA-00600: internal error code, parameters: [3020], [5], [166272], [21137792], [], [], [],
[], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file # 5, block # 166272, file
offset is 1362100224 bytes)
ORA-10564: tablespace DT_SYS_DAT
ORA-01110: data file 5: 'E: \ ORACLE_DATA \ YCCY \ DT_SYS_DAT.ORA'
ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK'
SQL> recover datafile 5 allow 1 corruption;
ORA-00283: recovery session cancelled due to error
ORA-00600: internal error code, parameters: [3020], [5], [169346], [21140866], [], [], [],
[], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file # 5, block # 169346, file
offset is 1387282432 bytes)
ORA-10564: tablespace DT_SYS_DAT
ORA-01110: data file 5: 'E: \ ORACLE_DATA \ YCCY \ DT_SYS_DAT.ORA'
ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK'
SQL> recover datafile 5 allow 1 corruption;
Complete media recovery.
open database and online datafile 2
SQL> startup pfile = 'd: /pfile.txt' mount;
The ORACLE routine has started.
Total System Global Area 1.7103E + 10 bytes
Fixed Size 2192864 bytes
Variable Size 9059699232 bytes
Database Buffers 8019509248 bytes
Redo Buffers 21762048 bytes
The database is loaded.
SQL> alter database datafile 2 offline;
The database has changed.
SQL> alter database open;
The database has changed.
SQL> shutdown immediate;
ORA-03113: end of file for communication channel
SQL> conn / as sysdba
Connected to an idle routine.
SQL> startup pfile = 'd: /pfile.txt' mount;
The ORACLE routine has started.
Total System Global Area 1.7103E + 10 bytes
Fixed Size 2192864 bytes
Variable Size 9059699232 bytes
Database Buffers 8019509248 bytes
Redo Buffers 21762048 bytes
The database is loaded.
SQL> select group #, status from v $ log;
GROUP # STATUS
---------- ----------------
1 INACTIVE
3 INACTIVE
2 CURRENT
SQL> recover database until cancel;
ORA-00279: change 1226478477 (generated on 03/28/2016 20:23:37) is required for thread 1
ORA-00289: suggestion:
D: \ ORACLE \ FLASH_RECOVERY_AREA \ YCCY \ ARCHIVELOG \ 2016_03_28 \ O1_MF_1_18689_% U_.ARC
ORA-00280: change 1226478477 (for thread 1) in sequence # 18689
Specified logs: {<RET> = suggested | filename | AUTO | CANCEL}
E: \ ORACLE_DATA \ YCCY \ REDO02.LOG
Applied logs.
Complete media recovery.
SQL> alter database datafile 2 online;
The database has changed.
SQL> alter database open resetlogs;
The database has changed.
The database is basically opened normally, and the 3020 part of the bad blocks are basically processed.
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
1 on 1 presale consultation
24/7 Technical Support 6 Free Tickets per Quarter Faster Response
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.
A comprehensive suite of global cloud computing services to power your business
Payment Methods We Support
