Logmnr/capure error b'coz of corruption of redo log block

Hi,
We all know that capture process reads the REDO entries from redo log files or archived log files. Therefore we need to ahev db in ARCHIVELOG mode.
In alert log file, I found error saying :
Creating archive destination LOG_ARCHIVE_DEST_1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
ARC0: Log corruption near block 66922 change 0 time ?
ARC0: All Archive destinations made inactive due to error 354
Fri Apr 04 12:57:44 2003
Errors in file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
As a normal practice, we do have multiplexing of redo log files at diff location, but even that second copy of redo log is of no use to recover the redo log. This explains redo log could not be archived, since it can't be read. Same is true even for Logmnr process, it could not read the redo log file and it failed. Now, we have wae to recover from this situation (as far as DB is concern, not Stream Replication), since the shutdown after this error was IMMEDIATE causing checkpoing, and rollback/rollforward is not required during system startup. (No instance recovery) We can make db NOARCHIVELOG mode, drop that particular group, and create new one, and turn db to ARCHIVELOG mode This will certainly serve the purpose as far as consistency of DB is concern.
Here is a catch for Stream Replication. The redo log that got corrupted must be having few transaction which are not being archived, and each will be having corresponding SCN. Now, Capture Process read the info sequentially in order of SCN. Few transaction are now missed, and Capture process can't jump to next SCN skipping few SCN in between. So, we have to re-instantiate the objects on the another system which has no erros, and start working on it. My botheration is what will happen to those missed transaction on the another database. It's absolete loss of the data. In development I can manage that. But in real time Production stage, this is a critical situation. How to recover from this situation to get back the corrupted info from redo log ?
I have not dropped any of the log group yet. B'coz I would like to recover from this situation without LOSS of data.
Thanx, & regards,
Kamlesh Chaudhary
Content of trace files :
Dump file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc
Fri Apr 04 12:57:31 2003
ORACLE V9.2.0.2.1 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 2, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.2.0 - Production
Windows 2000 Version 5.0 Service Pack 2, CPU type 586
Instance name: trishul
Redo thread mounted by this instance: 1
Oracle process number: 16
Windows thread id: 1724, image: ORACLE.EXE
*** SESSION ID:(13.1) 2003-04-04 12:57:31.000
- Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION02\1_36.ARC'
- Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
*** 2003-04-04 12:57:44.000
ARC0: All Archive destinations made inactive due to error 354
*** 2003-04-04 12:57:44.000
kcrrfail: dest:2 err:354 force:0
*** 2003-04-04 12:57:44.000
kcrrfail: dest:1 err:354 force:0
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
*** 2003-04-04 12:57:44.000
ARC0: Archiving not possible: error count exceeded
ORA-16038: log 2 sequence# 36 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG
Dump file e:\oracle\admin\repf\udump\trishul_cp01_2048.trc
Fri Apr 04 12:57:27 2003
ORACLE V9.2.0.2.1 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 2, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.2.0 - Production
Windows 2000 Version 5.0 Service Pack 2, CPU type 586
Instance name: trishul
Redo thread mounted by this instance: 1
Oracle process number: 30
Windows thread id: 2048, image: ORACLE.EXE (CP01)
*** 2003-04-04 12:57:28.000
*** SESSION ID:(27.42) 2003-04-04 12:57:27.000
TLCR process death detected. Shutting down TLCR
error 1280 in STREAMS process
ORA-01280: Fatal LogMiner Error.
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01280: Fatal LogMiner Error
**********************

I have the similar problem - I am using Steams environment, and have got this
"ORA-00353: log corruption near block" errors in the alert.log file
during capture the changes on the primary database, and Capture
process became aborted after that.
Was that transactions lost, or after i've started the Capture process
again the were captured and send to the target database?
Have anyone solved that problem?
Can you help me with it?

Similar Messages

ORA-00354: corrupt redo log block header

Hi Guys,
Need your support to resolve one of the oracle issues,
Below are errors visible in alert.log in oracle,
ORA-16038: log 24 sequence# 660467 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 24 thread 1: '/oracle/PRD/origlogB/log_g24_m1.dbf'...
2010-10-03 07:26:12.835 20195 kcrr.c
ORA-16014: log 24 sequence# 660467 not archived, no available
destinations
Below is o/p of archive log list seems to be bit strange,
SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /oracle/PRD/saparch/PRDarch
Oldest online log sequence     660467
Next log sequence to archive   660467
Current log sequence           660576
And some more info,
SQL> SELECT GROUP#, STATUS, MEMBER FROM V$LOGFILE;
    GROUP# STATUS MEMBER
        28         /oracle/PRD/origlogB/log_g28_m1.dbf
        28         /oracle/PRD/mirrlogB/log_g28_m2.dbf
        27         /oracle/PRD/origlogA/log_g27_m1.dbf
        27         /oracle/PRD/mirrlogA/log_g27_m2.dbf
        26         /oracle/PRD/origlogB/log_g26_m1.dbf
        26         /oracle/PRD/mirrlogB/log_g26_m2.dbf
        25         /oracle/PRD/origlogA/log_g25_m1.dbf
        25         /oracle/PRD/mirrlogA/log_g25_m2.dbf
        24         /oracle/PRD/origlogB/log_g24_m1.dbf
        24         /oracle/PRD/mirrlogB/log_g24_m2.dbf
        23         /oracle/PRD/origlogA/log_g23_m1.dbf
        23         /oracle/PRD/mirrlogA/log_g23_m2.dbf
        22         /oracle/PRD/origlogB/log_g22_m1.dbf
        22         /oracle/PRD/mirrlogB/log_g22_m2.dbf
        21         /oracle/PRD/origlogA/log_g21_m1.dbf
        21         /oracle/PRD/mirrlogA/log_g21_m2.dbf
16 rows selected.
SQL> SELECT GROUP#, SEQUENCE#, MEMBERS, ARCHIVED, STATUS, FIRST_CHANGE# FROM V$LOG;
    GROUP# SEQUENCE#    MEMBERS ARC STATUS           FIRST_CHANGE#
        21     660571          2 NO INACTIVE            2.9116E+10
        22     660572          2 NO INACTIVE            2.9116E+10
        23     660570          2 NO INACTIVE            2.9116E+10
        24     660467          2 NO INACTIVE            2.9114E+10
        25     660573          2 NO ACTIVE              2.9116E+10
        26     660574          2 NO CURRENT             2.9116E+10
        27     660568          2 NO INACTIVE            2.9116E+10
        28     660569          2 NO INACTIVE            2.9116E+10
8 rows selected.
All file exists but still facing issue, no backup is running
Regards,
Yash

Hi,
Instead of the logfile name, try the command with the logfile integer as mentioned below.
alter database clear unarchived logfile group <integer>;
You can get the logfile integer using the view, v$log.
select GROUP#,MEMBERS,STATUS from v$log;
The value for the parameter GROUP# is the logfile integer.
Hope this helps.
Regards,
Varadharajan M

[DG Physical] ORA-00368: checksum error in redo log block

Hi all,
I'm building a DR solution with 1 primary & 2 DR site (Physical).
All DBs use Oracle 10.2.0.3.0 on Solaris 64bit.
The first one ran fine for some days (6), then I installed the 2nd. After restoring the DB (DUPLICATE TARGET DATABASE FOR STANDBY) & ready to apply redo. The DB fetched missing arc gaps & I got the following error:
==================
Media Recovery Log /global/u04/recovery/billhcm/archive/2_32544_653998293.dbf
Errors with log /global/u04/recovery/billhcm/archive/2_32544_653998293.dbf
MRP0: Detected read corruption! Retry recovery once log is re-fetched...
Wed Jan 27 21:46:25 2010
Errors in file /u01/oracle/admin/billhcm/bdump/billhcm1_mrp0_12606.trc:
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 1175553 change 8236247256146 time 01/27/2010 18:33:51
ORA-00334: archived log: '/global/u04/recovery/billhcm/archive/1_47258_653998293.dbf'
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Recovered data files to a consistent state at change 8236247255373
===================
I see that may be RFS get the file incorrectly so I ftp to get this file & continue the apply, it pass. Comparison the RFS file & ftp is difference. At that time, I think that something wrong with the RFS because the content of arc is not right. (I used BACKUP VALIDATE ARCHIVELOG SEQUENCE BETWEEN N1 AND N2 THREAD X to check all arcs the RFS fetched, there was corrupt in every file);
I restore the DR DB again & apply incremental backup from the primary, now it run well. I don't know what's happening as I did the same procedures for all DR DB.
Yesterday night, I have to stop & restart DR site 1. Today, I check and it got the same error as the 2nd site, with corrupted redo. I try to delete the arcs, & let RFS to reget it, but the files were corrupt too.
If this continue to happen with the 2nd site again, that'll be a big problem.
The DR site 1 & Primary is linked by a GB switch, site 2 by a 155Mbps connection (far enough for my db load at about 1.5MB/s avg apply rate).
I seach Oracle support (metalink) but no luck, there is a case but it mentions max_connection>1 (mine is default =1)
Can someone show me how to troubleshooting/debug/trace this problem.
That would be a great help!
Thank you very much.

This (Replication) is the wrong forum for your posting.
Please post to the "Database - General" forum at
General Database Discussions
But, first, log an SR with Oracle Support.
Hemant K Chitale

Ora-00368 checksum error in redo log block

We are running small database in oracle 9i in non archive mode .Database is not opening up with following error ora-00368 checksum error in redo log block.
How to do the incomplete database recovery and open the database.
Regards
Arun

For more details
Here is what I am Doing.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'M:\ORACLE\ORADATA\mail\SYSTEM01.DBF'
SQL> alter database recover datafile
'M:\ORACLE\ORADATA\mail\SYSTEM01.DBF';
alter database recover datafile 'M:\ORACLE\ORADATA\mail\SYSTEM01.DBF'
ERROR at line 1:
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 103414 change 5082448355423 time
04/22/2003 04:30:11
ORA-00312: online log 3 thread 1: 'M:\ORACLE\ORADATA\mail\REDO03.LOG'
What can be done to start the database??
Regards
Arun

Checksum error in redo log block

I received ORA-00368 in my database and to resolve it I tried following steps:-
1) recover database until cancel;
2) alter database open resetlogs;
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/oracle/data/system01.dbf'
3) recover database;
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 12018 change 5983381348672 time 05/18/2010
16:08:24
ORA-00312: online log 10 thread 1: '/u02/oracle/data/log10b.dbf'
ORA-00312: online log 10 thread 1: '/u01/oracle/data/log10a.dbf'
There are 4 log groups with 2 members each and the database is in archive mode. Log group# 10 is current and all others are inactive.
Could you please let me know how should I proceed further either with or without losing transaction in group# 10 redo log?
Thanks
Rajkum

How can I drop the CURRENT log group# 10 and start the database with remaining 3 log groups? Database is in archive mode.Short answer: You cant. It is the CURRENT redo log... most probably your database wasnt shut down cleanly hence requiring a recovery. This recovery cannot be done because you have a corruption in your redo log needed to roll-forward the changes.
Without a valid backup and a restore/recovery until time there is no chance of opening the database without the help of Oracle. I strongly suggest you open a SR and prepare your management for some costs because you are running a unsupported database version on a unsupported (at least today) operating system. I also doubt you have a valid support contract for a 9i database...
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

Get ORA-00368: checksum error in redo log block

Hi all,
I get an error ORA-00368: checksum error in redo log block when connecting to database and here is the error:
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 430757 change 1236507302 time 11/12/2009
09:55:35
ORA-00312: online log 4 thread 1: '/oradata02/tchad/redo4.log'
Note that we are in noarchive log mode.
Could you help on how to recover my database please or a doc if there is interesting somewhere.
Thank you
Lucienot

Hi I don't have redo log duplex and here are the things i've done:
1.     shutdown abort
2.     ALTER DATABASE CLEAR UNARCHIVED LOGFILE '/oradata/.../redo3.log';
3.     startup nomount;
4.     alter database mount;
5.     ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 4;
SQL> SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
GROUP# ARC STATUS
3 NO ACTIVE
4 NO CURRENT
5 NO UNUSED
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata00/tchad/system01.dbf'
Thanks

ORA-00354: corrupt redo log block header..urgent

Hi All,
i am running into an issue when trying to recover a datafile.
1). Logs are being applied to the datafile to recover but RMAN is throwing this error:
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver logfile 'H:\ORACLE_ARCHIVE_LOGS\RBS\ARCHIVELOG\2012_04_23\O1_MF_1_13174_7SC4
P56W_.ARC'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 32768 change 6715041179 time 04/23/2012 13:
33:51
ORA-00334: archived log: 'H:\ORACLE_ARCHIVE_LOGS\RBS\ARCHIVELOG\2012_04_23\O1_MF
_1_13174_7SC4P56W_.ARC'
thanks in advance

bcm@bcm-laptop:~$ oerr ora 353
00353, 00000, "log corruption near block %s change %s time %s"
// *Cause: Some type of redo log corruption has been discovered. This error
//          describes the location of the corruption. Accompanying errors
//          describe the type of corruption.
// *Action: Do recovery with a good version of the log or do incomplete
//          recovery up to the indicated change or time.
bcm@bcm-laptop:~$ oerr ora 354
00354, 00000, "corrupt redo log block header"
// *Cause: The block header on the redo block indicated by the accompanying
//          error, is not reasonable.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time. If this happens when archiving,
//          archiving of the problem log can be skipped by clearing the log
//          with the UNARCHIVED option. This must be followed by a backup of
//          every datafile to insure recoverability of the database.

How to overcome corrupt redo log block header

friends, can you tell me any utilities or packages using which i can clean my redo log . Iam encountering this error during recovery of my database
Nand

Jafar,
SQL> recover database using backup controlfile;
ORA-00279: change 166327733 generated at 04/03/2008 12:06:36 needed for thread
1
ORA-00289: suggestion : C:\COLD\ARCHIVES\ARC17966_0616830416.001
ORA-00280: change 166327733 for thread 1 is in sequence #17966
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\STREDO09.LOG
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 4044 change 166329643 time 04/03/2008
12:46:45
ORA-00334: archived log: 'C:\STREDO09.LOG'
ORA-01112: media recovery not started
The stredo09.log is the standby redo log. My production server crashed.....Unfortunately the physical standby was also down..before main crashed..(power failure). Iam not able to open the production server.

How to corrupt a redo log ... :) ?

Hi Could anybody tell me how could (if it is possible) to corrupt a redo log ? I should like to make a test and I need such a thing to do ... So, any suggestions ?
Thanks, Paul T.

open the file in any editor add some entries
if you want o coirrupt data,control anything is possible :)
But this is not a question which should not be posted.
the files in use means the database files of the running instnace cannot be edited only after shutting down you can sabotage the DB

Corruption in redo log

Hi,
We are using Oracle 7.3 and we had a system crash. After i boot up the system and tried to open the database, i got a message that one of the redo log(current) was corrupted and hence the database cannot opened. We are in nonarchived mode and since we are using raid5, we haven't multiplexed the files. I cannot drop the log (As i cannot open the database,i cannot switch the logfile, drop and rebuild again). Now is there any methord to drop the log, and rebuild the log again? (The final option is to restore the whole system through "UFSRESTORE" since total storage of all HDD is only 16gb and then take a import of the schema).
thanks
Arun

Citizen_2 wrote:
How can i force the archiving of a redo log group 2?How could you archive a log group when you have lost all members of that group?
Have you checked out this documentation: [Recovering After the Loss of Online Redo Log Files|file://///castle/1862/Home%20Directories/Vaillancourt/Oracle%2010gR2%20Doc/backup.102/b14191/recoscen008.htm#sthref1872]
More specifically:
If the group is . . . Current
Then . . .
It is the log that the database is currently writing to.
And you should . . .
Attempt to clear the log; if impossible, then you must restore a backup and perform incomplete recovery up to the most recent available redo log.
>
HTH!

Corruption in a log file

Problem Description: alter database open
ERROR at line 1:
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 75 change 898387731 time 11/07/2009 17:15:29
ORA-00312: online log 2 thread 1: '/opt/oracle/archivelogs/online_logs/redo02.log'
Elapsed: 00:00:01.71
SQL> select CONTROLFILE_CHANGE#, ARCHIVELOG_CHANGE# from v$database;
CONTROLFILE_CHANGE# ARCHIVELOG_CHANGE#
898387746 898387674
Elapsed: 00:00:00.00
SQL> select distinct checkpoint_change# from v$datafile_header;
CHECKPOINT_CHANGE#
898385334
Elapsed: 00:00:00.01I'm wondering if I should clear the logfile, or restore and recover control file to change# 898385334 or a higher number. Please advise. I filled out a severity 1 request, but I haven't heard back. It has been nearly 3 hours. I'm thinking I need to restore and recover the control file, but I would like some expert advice.
If it matters:
Oracle 11.1.0.6.0
the corruption was caused by a full disk (Oracle completely filled one archivelog destination while another had 600GB+ free)
the backups were done with RMAN
a full restore and recover will take considerable time (probably a week or more by the time I get the data off of tape)
I have all the archivelogs
I have a recent control file backup
and I'd be happy to post any other information.

Flashback is not enabled. I think it was enabled when we were running this on a win32 platform, but it's not anymore.
I thought the logfiles were duplexed when the database was set up, but Unfortunately, logfiles aren't duplexed. It also turns out that the datafiles are fuzzy. They need recovery from the corrupted online redo log, probably past the corruption point. Once the database is online again, I'll duplex or multiplex the logfiles before letting the customer use it again.
The database is about 1.3TB. A full backup normally takes two days to complete, plus it would a few days to free up the space on the backup server. However, I have some much faster disk space now.
Oracle support has gotten back to me, but their support system is suffering from partial outages. We tried applying all the logfiles, then an open resetlogs, but it didn't work, due to datafiles being fuzzy. His recommendation was to do a full restore and recover, but that will probably take more than a week. Most of the data has been archived to tape, and I've been generating 100's of GB (in their bzip2 compressed backup form) of archivelogs working on restoring the database from a previous crash.
He said we could also try to force the database open, do a full export, create the database again, then import the data, and said it had a pretty good chance of working. Unless I come across some other option, we'll try that first, since by morning, I'll have somewhere around 1.8TB of extra disk space to hold the data.

How to recover from one corrupted redo log file in NOARCHIVE mode?

Oracle 10.2.1.
The redo log file was corrupted and Oracle can't work.
When I use STARTUP mount, I got no error msg.
SQL> startup mount
ORACLE instance started.
Total System Global Area 1652555776 bytes
Fixed Size 1251680 bytes
Variable Size 301991584 bytes
Database Buffers 1342177280 bytes
Redo Buffers 7135232 bytes
Database mounted.
But I have some applications which are depended on Oracle can't be started.
So, I tried STARTUP open. But I got error msg.
SQL> startup open
ORACLE instance started.
Total System Global Area 1652555776 bytes
Fixed Size 1251680 bytes
Variable Size 301991584 bytes
Database Buffers 1342177280 bytes
Redo Buffers 7135232 bytes
Database mounted.
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 497019 change 42069302 time 11/07/2007
23:43:09
ORA-00312: online log 4 thread 1:
'G:\ORACLE\PRODUCT\10.2.0\ORADATA\NMDATA\REDO04.LOG'
So, how can I restore and recover my database?
If use RMAN, how to do that?
Any help will be appreciated.
Thanks.

Hi, Yingkuan,
Thanks for the helps.
Actually, I have 10 redo log files exists. All of them are here.
I tried your suggestion:
alter database clear unarchived logfile group 4;
The error msg I got is the same as before:
SQL> alter database clear unarchived logfile group 4;
alter database clear unarchived logfile group 4
ERROR at line 1:
ORA-01624: log 4 needed for crash recovery of instance nmdata (thread 1)
ORA-00312: online log 4 thread 1:
'G:\ORACLE\PRODUCT\10.2.0\ORADATA\NMDATA\REDO04.LOG'
Compared to losing all the data, it is OK for me lose some of them.
I have more than 1 TB data stored and 99.9% of them are raster images.
The loading of these data were the headache. If I can save them, I can bear the lost.
I want to grasp the last straw.
But I don't know how set the parameter: allowresetlogs_corruption
I got the error msg:
SQL> set allowresetlogs_corruption=true;
SP2-0735: unknown SET option beginning "_allow_res..."
I have run the command:
Recover database until cancel
Alter database open resetlogs
The error msg I got is the following:
SQL> recover database until cancel
ORA-00279: change 41902930 generated at 11/05/2007 22:01:48 needed for thread 1
ORA-00289: suggestion :
D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\NMDATA\ARCHIVELOG\2007_11_09\O1_MF_
1_1274_%U_.ARC
ORA-00280: change 41902930 for thread 1 is in sequence #1274
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\NMDATA\SYSTEM01.DBF'
ORA-01112: media recovery not started
SQL>
From the log file, I got the following:
ALTER DATABASE RECOVER database until cancel
Fri Nov 09 00:12:48 2007
Media Recovery Start
parallel recovery started with 2 processes
ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel ...
Fri Nov 09 00:13:20 2007
ALTER DATABASE RECOVER CANCEL
Fri Nov 09 00:13:21 2007
ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ...
Fri Nov 09 00:13:21 2007
ALTER DATABASE RECOVER CANCEL
ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
Thank you very much. and I am looking forward to your followup input.

ORA-00333: redo log read error block

ORA-01033: ORACLE initialization or shutdown in progress ...
/ as sysdba
SQL> shutdown immediate;
SQL> startup nomount;
SQL> alter database mount;
SQL> alter database open;
ORA-00333: redo log read error block 8299 count 8192
SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL> select group#,members,THREAD, STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE# from v$log;
GROUP# MEMBERS,THREAD,STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE#
1 1 1 CURRENT NO 52428800 29-FEB-12 1597643 57
2 1 1 INACTIVE NO 52428800 29-FEB-12 1573462 56
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Feb 29 19:46:38 2012
Recovery of Online Redo Log: Thread 1 Group 1 Seq 56 Reading mem 0
Mem# 0 errs 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_7LZYZK8S_.LOG
Wed Feb 29 19:46:40 2012
Completed redo application
Wed Feb 29 19:46:40 2012
Completed crash recovery at
Thread 1: logseq 56, block 6568, scn 1597642
270 data blocks read, 270 data blocks written, 1460 redo blocks read
Wed Feb 29 19:46:43 2012
Thread 1 advanced to log sequence 57
Thread 1 opened at log sequence 57
Current log# 2 seq# 57 mem# 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
Successful open of redo thread 1
Wed Feb 29 19:46:43 2012
SMON: enabling cache recovery
Wed Feb 29 19:46:55 2012
Successfully onlined Undo Tablespace 1.
Wed Feb 29 19:46:55 2012
SMON: enabling tx recovery
Wed Feb 29 19:46:56 2012
Database Characterset is AL32UTF8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=19, OS id=3024
Wed Feb 29 19:47:09 2012
Completed: alter database open
Wed Feb 29 19:47:14 2012
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Wed Feb 29 20:33:30 2012
MMNL absent for 1537 secs; Foregrounds taking over
Wed Feb 29 20:33:31 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:31 2012
MMNL absent for 1540 secs; Foregrounds taking over
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:32 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:33 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 21:45:24 2012
MMNL absent for 4318 secs; Foregrounds taking over
MMNL absent for 4318 secs; Foregrounds taking over
MMNL absent for 4322 secs; Foregrounds taking over
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Feb 29 22:30:01 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 3, v.3244
CPU : 2 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:3097M/3546M, Ph+PgF:5143M/5429M, VA:1943M/2047M
Wed Feb 29 22:30:01 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
__shared_pool_size = 201326592
__large_pool_size = 8388608
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
sga_target = 805306368
control_files = C:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 587202560
compatible = 10.2.0.1.0
db_recovery_file_dest = C:\oraclexe\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=winsp3ue)(PORT=1522))
job_queue_processes = 4
audit_file_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 268435456
PMON started with pid=2, OS id=2176
PSP0 started with pid=3, OS id=2204
MMAN started with pid=4, OS id=2208
DBW0 started with pid=5, OS id=2212
LGWR started with pid=6, OS id=2220
CKPT started with pid=7, OS id=2240
SMON started with pid=8, OS id=2460
RECO started with pid=9, OS id=2464
CJQ0 started with pid=10, OS id=2480
MMON started with pid=11, OS id=2484
Wed Feb 29 22:30:02 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=2492
Wed Feb 29 22:30:02 2012
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Wed Feb 29 22:30:02 2012
alter database mount exclusive
Wed Feb 29 22:30:06 2012
Setting recovery target incarnation to 2
Wed Feb 29 22:30:06 2012
Successful mount of redo thread 1, with mount id 2657657770
Wed Feb 29 22:30:06 2012
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Wed Feb 29 22:30:07 2012
alter database open
Wed Feb 29 22:30:07 2012
Beginning crash recovery of 1 threads
Wed Feb 29 22:30:07 2012
Started redo scan
Wed Feb 29 22:30:15 2012
Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
ORA-00333: redo log read error block 10347 count 6144
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).
Waiting for Help
Regards

Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
ORA-00333: redo log read error block 10347 count 6144
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).Might your redo log file is corrupted or not exist, check physically. -> C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
is it archivelog mode?
perform fake recovery and open resetlogs.

How to recover from corrupt redo log file in non-archived 10g db

Hello Friends,
I don't know much about recovering databases. I have a 10.2.0.2 database with corrupt redo file and I am getting following error on startup. (db is non archived and no backup) Thanks very much for any help.
Database mounted.
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 6464 change 9979452011066 time 06/27/2009
15:46:47
ORA-00312: online log 1 thread 1: '/dbfiles/data_files/log3.dbf'
====
SQL> select Group#,members,status from v$log;
GROUP# MEMBERS STATUS
1 1 CURRENT
3 1 UNUSED
2 1 INACTIVE
==
I have tried this so far but no luck
I have tried following commands but no help.
SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 3;
Database altered.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 6464 change 9979452011066 time 06/27/2009
15:46:47
ORA-00312: online log 1 thread 1: '/dbfiles/data_files/log3.dbf'

user652965 wrote:
Thanks very much for your help guys. I appreciate it. unfortunately none of these commands worked for me. I kept getting error on clearing logs that redo log is needed to perform recovery so it can't be cleared. So I ended up restoring from earlier snapshot of my db volume. Database is now open.
Thanks again for your input.And now, as a follow-up, at a minimum you should make sure that all redo log groups have at least 3 members. Then, if you lose a single redo log file, all you have to do is shutdown the db and copy one of the good members (of the same group as the lost member) over the lost member.
And as an additional follow-up, if you value your data you will run in archivelog mode and take regular backups of the database and archivelogs. If you fail to do this you are saying that your data is not worth saving.

ORA-00333: redo log read error block 65538 count 8192

Hi,
I wanted to alter user hr's password, but I couldn't open the database first. What should I do? Here is my demo: Thank you for your response.
C:\>sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Sun May 16 12:12:43 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect sys/oracle as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> select * from v$controlfile;
STATUS
NAME
C:\ORACLE\ORADATA\SARAH\CONTROL01.CTL
C:\ORACLE\ORADATA\SARAH\CONTROL02.CTL
C:\ORACLE\ORADATA\SARAH\CONTROL03.CTL
SQL> select * from dba_users;
select * from dba_users
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00333: redo log read error block 65538 count 8192
SQL> desc v$instance
Name Null? Type
INSTANCE_NUMBER NUMBER
INSTANCE_NAME VARCHAR2(16)
HOST_NAME VARCHAR2(64)
VERSION VARCHAR2(17)
STARTUP_TIME DATE
STATUS VARCHAR2(12)
PARALLEL VARCHAR2(3)
THREAD# NUMBER
ARCHIVER VARCHAR2(7)
LOG_SWITCH_WAIT VARCHAR2(11)
LOGINS VARCHAR2(10)
SHUTDOWN_PENDING VARCHAR2(3)
DATABASE_STATUS VARCHAR2(17)
INSTANCE_ROLE VARCHAR2(18)
ACTIVE_STATE VARCHAR2(9)
SQL> select instance_name, status from v$instance;
INSTANCE_NAME STATUS
sarah MOUNTED
SQL>
*******************************

I did what Prabhu told me..But i recovered using backup controlfile and when i was asked to apply logs..i applied my oldest logs and it worked
Like i have two groups with two members each
I applied log1a.dbf and it said media recovery completee
I opened the database But then it started giving me errors for undo tablespace
I made another undo tablespace..tried dropping the old one but it did not permitted as it had some segments with status "needs recovery"
Than i added this parameter in pfile with the correupted segment and than tried to drop the segment but it still did not permit
corruptedrollback_segments =(corrupted_undo segment_name)
Next what i did was I mounted the database, ran another session of media recovery and opened the databse using resetlogs
Than i dropped the old undo and it went through successfully..
If you think anything i did wrong than please advice..
I hope this action plans helps you in case you come across same errors some day
I would be very thankful if you can refer me a document of recovery which covers all kinds of recoveries and scenarios and commands too
Thanks alot

Logmnr/capure error b'coz of corruption of redo log block

Similar Messages

Maybe you are looking for