SEO

It looks like the archiver failed to archive a log in an 8.1.7
database. Here's a snip of the alert log:

ARC0: Beginning to archive log# 1 seq# 3501
ARC0: Failed to archive log# 1 seq# 3501
Thu Sep 02 10:28:01 2004
ARCH: Completed archiving log# 1 seq# 3501
Thu Sep 02 11:28:00 2004
Thread 1 advanced to log sequence 3503
Current log# 6 seq# 3503 mem# 0:
D:\HLTHPNT\DATABASE\REDOLOGS\EMR6A.LOG
Current log# 6 seq# 3503 mem# 1:
D:\HLTHPNT\DATABASE\REDOLOGS\EMR6B.LOG
Thu Sep 02 11:28:00 2004
ARCH: Beginning to archive log# 2 seq# 3502
Thu Sep 02 11:28:00 2004
ARC0: Beginning to archive log# 2 seq# 3502
ARC0: Failed to archive log# 2 seq# 3502
Thu Sep 02 11:28:01 2004
ARCH: Completed archiving log# 2 seq# 3502
Dump file D:\Hlthpnt\Database\Trace\emrALRT.LOG
Thu Sep 02 12:48:48 2004
....

Log #6 advanced to seq# 3503. At this point there was a crash, and
when the database came back up it went through crash recovery

....
Beginning crash recovery of 1 threads
Thu Sep 02 12:49:01 2004
Thread recovery: start rolling forward thread 1
Recovery of Online Redo Log: Thread 1 Group 6 Seq 3503 Reading mem 0
Mem# 0 errs 0: D:\HLTHPNT\DATABASE\REDOLOGS\EMR6A.LOG
Mem# 1 errs 0: D:\HLTHPNT\DATABASE\REDOLOGS\EMR6B.LOG
....

Processing continued, but seq# 3503 was never archived. Later on,
Group 6 advanced to seq# 3513, so 3503 was lost.

Is anyone aware of any issues with failure to archive a log? If we
hadn't been running a standby database, we probably never would have
caught this unless there was a failure that required a recovery.

Thanks,

Tommy