Re: ORA -16014 - Error in archiving, no available destination

srivenu_at_hotmail.com (srivenu) wrote in message news:<1a68177.0403230526.5f566f8d_at_posting.google.com>...
> Prem,
> You may get the reason for failure in V$ARCHIVE_DEST and
> V$ARCHIVE_DEST_STATUS.
> You need not bounce the database to restart archiving.
> you can
> 1) issue the command alter system archive log start to '<[current
> destination]>';
> 2) Stop and restart the archiver process.
> 3) give the REOPEN parameter in log_archive_dest_n
> If the REOPEN clause is not specified, it is automatically set to 0.
> This means that if an error of archiving occurs, the database still
> operates until it tries to overrite the corresponding log at which
> time, the database hangs.
> If a destination is MANDATORY, Oracle Corporation recommends that you
> specify REOPEN. If you do not specify seconds, the default value is
> 300 seconds.
>
> regards
> Srivenu

HJR & Veenu:

Thanks a lot. I will try to add REOPEN=60. Right now when REOPEN is not set. Oracle tries to archive the failed log right away several times. With REOPEN it will wait.

I have another queston:

I picked up some code which does:

alter system switch logfile;
mv archived_file dir1

I think when switching is done, Oracle switches the file to a new file and leaves archiver to achive previous log file. I think what I should do is:

alter system archive log current;
mv

this way I will ensure that previous log has been archived before switch is
made?

Prem Received on Tue Mar 23 2004 - 13:47:43 CST