I have an interesting/ scary scenario here. Take a look at the series of ORA-s this alert file.
What was going on?
How do I prevent this?
NB note that the log (48276) eventually succeeded to be archived. And followed by message "Archiver process freed from errors. No longer stopped."
Probably your archive drive might have been full and you could have cleared it later. When I was full, it gave that error. And and when you freed up, it said started archiving again.
04-12-2002, 01:25 AM
16014, 00000, "log %s sequence# %s not archived, no available destinations"
// *Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archivelog destinations specified or all destinations experienced debilitating errors.
// *Action: Verify that archivelog destinations are being specified and/or take the necessary step to correct any errors that may have occurred.
Looks like the archive destination was not availaible or it was full...as soon as Oracle saw it....ARC background process was freed from errors.
You need to make sure your archive destination directory has enough space to accomodate the archive files ..
In this scenario when your archiver is not able to write files...
ur database is in a hung state meaning nobody can login and no transactions can be processed.