Today the database encountered this error at startup: ORA-00283: Recovery session canceled due to errors ORA-00368: redo checksum in log Block Error ORA-00353: log corruption close to block 138240 change 925634142 time 1216201311: 39: 30ORA-00334: archive log: D: ORACLEORADATAONLINELOGREDO01.LOG is originally r
Today the database encountered this error at startup: ORA-00283: resume session cancel ORA-00368 due to errors: redo checksum errors in the log block ORA-00353: log corruption close to block 138240 change 925634142 time 12/16/2013 11:39:30 ORA-00334: archive log: D: \ ORACLE \ ORADATA \ ONLINELOG \ REDO01.LOG originally r
This error occurs when the database is started today:
ORA-00283: resume session canceled due to an error
ORA-00368: redo checksum errors in the log Block
ORA-00353: log corruption close to block 138240 change 925634142 time 11:39:30
ORA-00334: archiving logs: 'd: \ ORACLE \ ORADATA \ ONLINELOG \ REDO01.LOG'
It turns out that the redo file is damaged. Because it is test data and there is no archive or backup, the data is not very important.
The solution is as follows:
1. Set the initialization parameter _ allow_resetlogs_uption = true
NOTE: If spfile is used, modify the spfile.
2. startup mount
Recover database using backup controlfile until cancel;
Execute "Restore" and then press "cancel ".
3. alter database open resetlogs;
Open Database
4. If the database can be opened normally, it will be OK.
It may not be opened, so try shutdown immediate and start up again
5. Modify the parameter file to remove the _ allow_resetlogs_uption parameter.
I thought it was okay, but the development team tried again and said it could not be connected.
I can see that the database can be up, But I can execute a query at will and it will be down again. What is going on?
Alert Log discovery:
ORA-00600: internal error code, arguments: [4194], [62], [53], [], [], [], [], [], []
This error indicates that the undo tablespace is faulty.
So rebuilding undo:
Create undo tablespace undotbs2 datafile 'd: \ oracle \ product \ 10.2.0 \ oradata \ hyd \ undotbs02.dbf 'size 625 M;
Alter system set undo_tablespace = undotbs2
Drop tablespace "undotbs1" INCLUDING CONTENTS AND DATAFILES
Show parameter undo
OK!
No wonder the data can be used up, but the operation fails once it is executed.
This is because redo and undo are broken together. Fortunately, the data file is intact.