What's the difference?

[BUFF]

Hi Everyone!
What's the difference among adding more redo log groups, adding more members on the log groups and making each redo log file bigger?
I'm confused on this because I'm having problem with my archiving on my Oracle (8.15) on NT. I'm getting a stop error on the Event Viewer telling me that "Archive process error: ORACLE Instance newdb - Can not allocate log, archival required."
I've searched on this site and I have added more log groups but I am still seeing the stop error.
Can anyone enlighten me on this? Thanks in advance.

[birdax1]

Doing an 'Archive log list;' when connected as SYS or INTERNAL shows ????

What?

Database log mode Archive Mode
Automatic archival Disabled

If this is the case then that is the reason why. Try :
ALTER SYSTEM ARCHIVE LOG ALL;

Have you got enought disk space?

What does the alter log say?

[BUFF]

Here's the result. Also I have a lot of disk space.
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\Archivelog\newdb
Oldest online log sequence 43139
Next log sequence to archive 43142
Current log sequence 43142

[ramaral]

have you doubled checked the archive destination including read and write permissions?

[Edited by ramaral on 02-21-2002 at 10:32 AM]

[BUFF]

Permissions are set properly. In fact, it's creating archive logs but it's the stop error on the event viewer that is worrying me.

[sambavan]

Does your alert log say anything? If so could you pass the information of the error with the error#

Sam

[BUFF]

The whole is too big but here is an excerpt from it. Thanks!
========================
=======================
ARC3: Beginning to archive log# 4 seq# 42380
ARC3: Failed to archive log# 4 seq# 42380
ARC3: Beginning to archive log# 1 seq# 42381
Thu Feb 21 03:52:27 2002
LGWR: prodding the archiver
Thu Feb 21 03:52:27 2002
ARC4: received prod
Thu Feb 21 03:52:27 2002
ARC2: Completed archiving log# 4 seq# 42380
ARC2: re-scanning for new log files
ARC2: prodding the archiver
Thu Feb 21 03:52:27 2002
ARC4: Beginning to archive log# 1 seq# 42381
Thu Feb 21 03:52:28 2002
ARC4: Failed to archive log# 1 seq# 42381
ARC4: Beginning to archive log# 3 seq# 42382
Thu Feb 21 03:52:28 2002
ARC3: Completed archiving log# 1 seq# 42381
ARC3: re-scanning for new log files
ARC3: prodding the archiver
Thu Feb 21 03:52:28 2002
ARC1: received prod
Thread 1 advanced to log sequence 42383
Thu Feb 21 03:52:28 2002
Current log# 2 seq# 42383 mem# 0: D:\ORACLE\ORADATA\newdb\REDO02.LOG
Thu Feb 21 03:52:29 2002
ARC0: received prod
ARC1: Beginning to archive log# 3 seq# 42382
Thu Feb 21 03:52:29 2002
ARC1: Failed to archive log# 3 seq# 42382
Thu Feb 21 03:52:30 2002
LGWR: prodding the archiver
Thu Feb 21 03:52:30 2002
ARC0: Beginning to archive log# 3 seq# 42382
Thu Feb 21 03:52:30 2002
ARC2: received prod
Thu Feb 21 03:52:30 2002
ARC0: Failed to archive log# 3 seq# 42382
ARC0: Beginning to archive log# 2 seq# 42383
Thu Feb 21 03:52:30 2002
ARC4: Completed archiving log# 3 seq# 42382
ARC4: re-scanning for new log files
ARC4: prodding the archiver
Thu Feb 21 03:52:30 2002
ARC2: Beginning to archive log# 2 seq# 42383
Thu Feb 21 03:52:30 2002
ARC3: received prod
ARC3: Beginning to archive log# 2 seq# 42383
Thu Feb 21 03:52:31 2002
ARC2: Failed to archive log# 2 seq# 42383
Thu Feb 21 03:52:31 2002
ARC3: Failed to archive log# 2 seq# 42383
Thu Feb 21 03:52:31 2002
Thread 1 advanced to log sequence 42384
Thu Feb 21 03:52:31 2002
Current log# 4 seq# 42384 mem# 0: D:\ORACLE\ORADATA\newdb\REDO04.LOG
LGWR: prodding the archiver
Thread 1 advanced to log sequence 42385
Thu Feb 21 03:52:31 2002
ARC4: received prod
Thu Feb 21 03:52:31 2002
Current log# 1 seq# 42385 mem# 0: D:\ORACLE\ORADATA\newdb\REDO01.LOG
Thu Feb 21 03:52:31 2002
ARC0: Completed archiving log# 2 seq# 42383
ARC0: re-scanning for new log files
ARC0: prodding the archiver
ARC0: received prod
Thu Feb 21 03:52:31 2002
ARC4: Beginning to archive log# 4 seq# 42384
Thu Feb 21 03:52:32 2002
Thread 1 cannot allocate new log, sequence 42386
Thu Feb 21 03:52:32 2002

[sambavan]

Looks like a v.active database. You are falling short of redologs. Add more redologs and also make sure the check point had been set correctly.

Its either the database is filling up the redologs where your archive log processes are falling behind or such that you are making a v.frequent checkpoint causing the backlog. In general, i would see that the log swith takes for every 30min. If your check point had been set correct, then you need to increase the redolog size and add more logs to the group or create more groups.

Sam

[BUFF]

Ok, it really has something to do with my redo logs. Just need some clarifications here.
Is there any difference among adding more redo log groups, adding more members into a log groups and making the redo logs size bigger? Is there any advantages, especially performance wise when using any of these?

Thanks again.

[sambavan]

http://technet.oracle.com/docs/produ...linere.htm#273

Sam