Home » RDBMS Server » Backup & Recovery » alert.log > Bad header found during deleting archived log (Oracle 10g on RHEL-4)
alert.log > Bad header found during deleting archived log [message #351400] Tue, 30 September 2008 11:42 Go to next message
ORA_UMAIR
Messages: 3
Registered: August 2008
Junior Member
Hi,

How do I correct the following? Thanks in advance!


***
Corrupt block seq: 2629 blocknum=1.
Bad header found during deleting archived log
Data in bad block - seq:0. bno:0. time:0
beg:0 cks:0
calculated check value: 0
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
***
Corrupt block seq: 2630 blocknum=1.
Bad header found during deleting archived log
Data in bad block - seq:0. bno:0. time:0
beg:0 cks:0
calculated check value: 0
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
***
Corrupt block seq: 2629 blocknum=1.
Bad header found during deleting archived log
Data in bad block - seq:0. bno:0. time:0
beg:0 cks:0
calculated check value: 0
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
***
Corrupt block seq: 2630 blocknum=1.
Bad header found during deleting archived log
Data in bad block - seq:0. bno:0. time:0
beg:0 cks:0
calculated check value: 0
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
***
Corrupt block seq: 2629 blocknum=1.
Bad header found during deleting archived log
Data in bad block - seq:0. bno:0. time:0
beg:0 cks:0
calculated check value: 0
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
Reread of seq=2629, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2629_1_578136984.log, found same corrupt data
***
Corrupt block seq: 2630 blocknum=1.
Bad header found during deleting archived log
Data in bad block - seq:0. bno:0. time:0
beg:0 cks:0
calculated check value: 0
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Reread of seq=2630, blocknum=1, file=/prdmtx1/oradata/PRDMTX1/arch/arch_PRDMTX1_2630_1_578136984.log, found same corrupt data
Re: alert.log > Bad header found during deleting archived log [message #351414 is a reply to message #351400] Tue, 30 September 2008 14:28 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
I assume these messages are being produced in your alert log?

Are these old archive logs? Are there other files on the same file system as these files?

Have you performed a backup recently?
Re: alert.log > Bad header found during deleting archived log [message #351426 is a reply to message #351414] Tue, 30 September 2008 15:34 Go to previous messageGo to next message
ORA_UMAIR
Messages: 3
Registered: August 2008
Junior Member
1) These messages are being produced in the alert log.

2) These are new archive logs. Yes there are other files on the same file system as these files.

3) Yes, a RMAN backup was performed and completed successfully.

Any advice?
Re: alert.log > Bad header found during deleting archived log [message #351429 is a reply to message #351426] Tue, 30 September 2008 16:21 Go to previous message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
What is producing these messages? Are you running an RMAN job to delete the archivelogs?
Previous Topic: Corrupted redo log
Next Topic: Recovery - NOARCHIVELOG
Goto Forum:
  


Current Time: Mon Dec 05 06:34:31 CST 2016

Total time taken to generate the page: 0.13822 seconds