LGWR: prodding the archiver

Oracle 8.1.5 EE
OS: Windows NT 4.0

I'm running the database in archivelog mode. The alert log has the following of and on...

LGWR: prodding the archiver

... but yesterday afternoon onwards, this kept repeating in the alert log and the server could not allocate new log as the online logs needed archiving...

Sorted this out, by acknowleging message on console and then giving ...

Code:

---


archive log all;

---

Trying to investigate why this happened ?? All applications using this database were affected! Everyone one was trouble-shooting the other tiers of the application but the database. Any pointers??

Thanks & Regards.



====================alert log ==============================
============================================================

Wed Sep 11 08:41:16 2002
LGWR: prodding the archiver
Thread 1 advanced to log sequence 1886
Current log# 2 seq# 1886 mem# 0: D:\ORACLE\ORADATA\BLAZE\REDO02.LOG
Wed Sep 11 08:41:16 2002
ARCH: Beginning to archive log# 1 seq# 1885
ARCH: Completed archiving log# 1 seq# 1885
Wed Sep 11 10:54:56 2002
LGWR: prodding the archiver
Thread 1 advanced to log sequence 1887
Current log# 3 seq# 1887 mem# 0: D:\ORACLE\ORADATA\BLAZE\REDO03.LOG
Wed Sep 11 11:24:02 2002
LGWR: prodding the archiver
Thread 1 advanced to log sequence 1888
Current log# 1 seq# 1888 mem# 0: D:\ORACLE\ORADATA\BLAZE\REDO01.LOG
Wed Sep 11 14:42:29 2002
LGWR: prodding the archiver
Thread 1 cannot allocate new log, sequence 1889
All online logs needed archiving
Current log# 1 seq# 1888 mem# 0: D:\ORACLE\ORADATA\BLAZE\REDO01.LOG
LGWR: prodding the archiver
LGWR: prodding the archiver
...
...
LGWR: prodding the archiver
LGWR: prodding the archiver
Thu Sep 12 09:45:47 2002
Archive Log All
ARCH: Beginning to archive log# 2 seq# 1886
Thu Sep 12 09:45:47 2002
LGWR: prodding the archiver
LGWR: prodding the archiver
LGWR: prodding the archiver
LGWR: prodding the archiver
Thu Sep 12 09:45:51 2002
ARCH: Completed archiving log# 2 seq# 1886
ARCH: Beginning to archive log# 3 seq# 1887
Thu Sep 12 09:45:51 2002
LGWR: prodding the archiver
Thread 1 advanced to log sequence 1889
Current log# 2 seq# 1889 mem# 0: D:\ORACLE\ORADATA\BLAZE\REDO02.LOG

======================= end of alert log ===================

[Edited by ggnanaraj on 09-12-2002 at 03:07 AM]

Is this the situation..

http://members.cox.net/djackson99/no...up_failed.html

It might help thought its given for unix env..



Sameer

Hi

Thanks for the reply.

My problem is not because of disk becoming full !

BTW, the following info was also in the event viewer...

Quote:

---

Archive process error: ORACLE Instance blaze - Can not allocate log, archival required.

---

I suppose the problem was with the archive process not waking up inspite of being prodded by the log writer.

The error ...

Quote:

---

LGWR: prodding the archiver

---

... comes continously in the alert log for more than 2000 times, one line for every second or so it seems! (the alert log file increased from 1.7 mb to 5.5 mb).

Maybe I need to also mention that this is the first time I'm getting this problem after configuring for archivelog mode 6 months back. The database has 3 log groups of 5MB each.

Any one has faced this problem ??




[Edited by ggnanaraj on 09-12-2002 at 04:47 AM]

Quote:

---

BTW, the following info was also in the event viewer...

Archive process error: ORACLE Instance blaze - Can not allocate log, archival required.

---

This is a typical error when all log files get full and no arhiving is enable..

1. Oracle tries to write new transactions to logfile
2. Old logs (which are already full) aren't got archived automatically
3. Doesn't able to allocate new log

check what it shows???

SQL> show parameter log_archive_start

Hi Sameer

If you read my post carefully, you will notice that the db is in archivelog mode...so obviously log_archive_start is true!

I repeat, that the link you posted speaks about a situation where a unix file system is full and the logs are diverted to another file system. I like to distinguish between 'logs being full' and 'disk being full'. Ofcouse, in my situation, 3 redo log groups are full and not archived because of the archiver not responding (it seems!) inspite of the efforts of the log writer to awaken them.

I hope I make myself clear.

Metalink, speaks about such errors ocurring because of OS or hardware problems. Not much similar situations where you have... LGWR: prodding the archiver ... repeating continously in the alert log.

I wonder why the guru's are silent ?

Thanks & Regards.

Or check whether automatic archieving enabled.

connect as sys
then try this
SQL > archive log list

You should get something like this...

Database log mode Archive Mode
Automatic archival Enabled
Archive destination /arch
Oldest online log sequence 1165
Next log sequence to archive 1169
Current log sequence 1169

If you dont see your automatic archival enabled, then do it by starting up the database in mount state and giving the following command

SQL > archive log start

then open the database.

nagarjuna, thank you for your reply... but listen to what I have to say...

the db is in archivelog mode with automatic archiving for the past 6 months. ...got this error all of a sudden...only now..

Yes, it looks like there is a problem with ARC0 process. Raise a TAR with metalink. Bounce the database for temporary solutions. Before that do take a trace of all the error msgs.

Semi dumb question:

How busy was your system? IE, if your process list was too long (connections, other jobs, other apps, etc),the archiver process may be too far down to start?

I am not 100% sure, but I believe I have run into this once or twice in Unix over the years.