ORA -16014 - Error in archiving, no available destination

From: Prem K Mehrotra <premmehrotra_at_hotmail.com>
Date: 22 Mar 2004 18:57:46 -0800
Message-ID: <43441e77.0403221857.6754e407@posting.google.com>

I have started getting following error in my database. ORA-16014: log 2 sequence# 18315 not archived, no available destinations
ORA-00312: online log 2 thread 1: '/local8/oradata/fdc/redo02a.log' ORA-00312: online log 2 thread 1: '/local1/oradata/fdc/redo02b.log' This error occurred 3 months ago and then went away after database was restarted. Problem has started happening again. It has happened twice sinec
yesterday.
Following ae init.ora parameters:

log_archive_start = TRUE
log_archive_dest_1="location=/local2/ora_arch/bdc/archive mandatory"
log_archive_dest_2="location=/local2/ora_arch/bdc/rman mandatory"
log_archive_format = bdc%S.arc

Need help right away.
File systems are not 100% full.
I can write to those file systmes.

---

I have alert.log for more than one year. Before Jan 2004, I used to use single archive log destination. Error will show up in alert.log once every 3 months, but it will correct after a few tries, i.e., redo log will be archived.

Since Jan 2004, I have started using multiple destinations:

og_archive_start = TRUE

log_archive_dest_1="location=/local2/ora_arch/bdc/archive mandatory"
log_archive_dest_2="location=/local2/ora_arch/bdc/rman mandatory"
log_archive_format = bdc%S.arc

Now when the problem happens, it does not correct after a few tries and one
is forced to restart the database which is unacceptale in production environment.
We do want to make sure logs are archived to both destinations, that's why
mandatory.
I am looking for a way as not to shutdown the database because I anticipate
problem may happen again

any ideas will be appreciated. Received on Mon Mar 22 2004 - 20:57:46 CST