Hi

Thanks for the reply.

My problem is not because of disk becoming full !

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

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 ...
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]