Unable to write archive log

From: fran keenan <fran.keenan_at_yac.com>
Date: 14 Jan 2002 04:04:26 -0800
Message-ID: <8b7972b3.0201140404.2a7389c6@posting.google.com>

Environment:

• oracle 8.1.7 (linux 6.2)
• Using MultiThreading

I got the following error in my archive log:
-------------------------------------------------------------->

  Thread 1 advanced to log sequence 12571   Current log# 7 seq# 12571 mem# 0: /u02/oradata/UKY2/redo07.log Mon Jan 7 19:40:28 2002
ARC6: Beginning to archive log# 6 seq# 12570 Mon Jan 7 21:02:27 2002

ARC7: Beginning to archive log# 6 seq# 12570
ARC7: Failed to archive log# 6 seq# 12570
ARC7: Beginning to archive log# 7 seq# 12571

Mon Jan 7 21:02:27 2002
Thread 1 advanced to log sequence 12572
  Current log# 8 seq# 12572 mem# 0: /u02/oradata/UKY2/redo08.log Mon Jan 7 21:02:34 2002
ARC7: Completed archiving log# 7 seq# 12571 Mon Jan 7 21:02:34 2002
ARC8: Beginning to archive log# 6 seq# 12570 ARC8: Failed to archive log# 6 seq# 12570 Mon Jan 7 21:05:04 2002
ARC9: Beginning to archive log# 6 seq# 12570 ARC9: Failed to archive log# 6 seq# 12570 Mon Jan 7 21:06:03 2002
ARC5: Beginning to archive log# 6 seq# 12570
-------------------------------------------------------------->

Now I know there is nothing wrong with oracle not being able to complete an archive log. However for sequence 12570, it took over 2.5 hours to complete the archive log. Normally when i've seen this it completes within a few minutes. Note however while trying to write 12570, it successfully wrote 12571. Is it unusual or cause issues, where the archive log 12571 is written before 12570 ? Note I had 5 redo logs, 4 of the same size and one of smaller size. I now have made all redo logs the same size. Maybe this may have added to the issue. My question is the archive logs getting out of synch have caused the db problems, as my db hung with the beginning of my hotbackup, and I have to bounce the db.

Thanks. Received on Mon Jan 14 2002 - 06:04:26 CST