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.