Problem: Archiver is unable to archive a redo log because the output device is full or unavailable

Problem: Archiver is unable to archive a redo log because the output device is full or unavailable

Hey,

My Oracle 10.1.0 database is in a “hung” state due to the fact that the archiver is unable to archive a redo log because the output device is full or unavailable. Here is an excerpt from the alert log content:

Wed Dec 20 10:31:31 2006
Errors in file f:\oracle\admin\realtid\bdump\realtid_arc0_4104.trc:
ORA-00333: redo log read error block 1 count 2048

ARC0: All Archive destinations made inactive due to error 333
Committing creation of archivelog ‘E:\BACKUP\REALTID\ARCH\ARCH47191601231474.ARC’ (error 333)
ARC0: All standby destinations failed; successful archival assumed
ARC0: Failed to archive thread 1 sequence 4719 (333)
Wed Dec 20 10:31:31 2006
Errors in file f:\oracle\admin\realtid\bdump\realtid_arc0_4104.trc:
ORA-16038: log 3 sequence# 4719 cannot be archived
ORA-00333: redo log read error block  count
ORA-00312: online log 3 thread 1: ‘F:\ORADATA\REALTID\REDO03.LOG’

Wed Dec 20 10:31:40 2006
ARC1: Evaluating archive thread 1 sequence 4719
Wed Dec 20 10:32:45 2006
Errors in file f:\oracle\admin\realtid\bdump\realtid_arc1_4860.trc:
ORA-00333: redo log read error block 2049 count 2048
ORA-00312: online log 3 thread 1: ‘F:\ORADATA\REALTID\REDO03.LOG’
ORA-27091: unable to queue I/O
OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 1117) The request could not be performed because of an I/O device error.

Is it a hardware failure?


Solution: Archiver is unable to archive a redo log because the output device is full or unavailable

Hi,
You can clear the logfile and continue.
ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 3;

You may need to take a full database backup immediately and your past backups are not useful for a complete recovery.