Re: Redo log entry

Hi

Your redo logs look like they are way too small. I would look at making them much bigger to stop them switching every second. This current activity will have a detrimental affect on performance.

Alistair

"mammoth.usenet-access.com" <bgt_0990_at_msn.com> wrote in message news:3c56a820$1_2_at_corp-goliath.newsgroups.com...
> As I go back in the alert log for one of our customers I find numerous
> entries such as:
>
>
> ARC0: Beginning to archive log# 1 seq# 3481
> ARC0: Completed archiving log# 1 seq# 3481
> Thu Dec 06 09:08:21 2001
> Thread 1 cannot allocate new log, sequence 3483
> Checkpoint not complete
> Current log# 2 seq# 3482 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO02.LOG
> Thread 1 advanced to log sequence 3483
> Current log# 3 seq# 3483 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO03.LOG
> Thu Dec 06 09:08:22 2001
> ARC0: Beginning to archive log# 2 seq# 3482
> ARC0: Completed archiving log# 2 seq# 3482
> Thu Dec 06 09:08:24 2001
> Thread 1 advanced to log sequence 3484
> Current log# 1 seq# 3484 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO01.LOG
> Thu Dec 06 09:08:24 2001
> ARC0: Beginning to archive log# 3 seq# 3483
> ARC0: Completed archiving log# 3 seq# 3483
>
> What am I looking at here? What is the impact on the system and what
should
> I do about it?
>
> Thanks
> Barry
>
>
>
>