Re: Error message

Hi Gordon,

I guess you are running your instance in ARCHIVELOG mode. Otherwise LGWR would just overwrite the last recently used redolog.

Check the following:

• Did you start your instance with log_archive_start = true? Just enter "show parameter" and look for this parameter. If it is set to FALSE you will have to archive to redolog manually - I cannot remember the command now as we use log_archive_start = true. Please look up the docs for server manager.
• If you started your instance with log_archive_start = true most likely the archiver cannot write to log_archive_dest (how to get this info - see item above). Check if the init.ora parameter log_archive_dest and log_archive_format are set properly - again please look up the docs.
• If the last two mentioned parameters are okay please check if there is sufficient space in log_archive_dest. If not please care for space - otherwise you will end up with an instance that is not allowing any change to the database as the LGWR cannot save these changes to the redolog. You end up with a hanging instance - no error message though. New connections will fail most likely with ORA-03113 or ORA-03114.

Martin

Gordon wrote:
>
> Hi
>
> I'm getting this error message on my Oracle 8 server several times a
> day:
>
> Warning - The following error occured during ORACLE redo log archival:
> ORACLE Instance orcl - Can not allocate log, archival required
> Press <ENTER> to acknowledge message.
>
> What does it mean? and how do I fix it?
>
> Thanks in advance,
>
> Gordon
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Sat Nov 27 1999 - 11:24:09 CST