Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: can not allocate log, archival required..

Re: can not allocate log, archival required..

From: Sean M <smckeownNO_at_BACKSIESearthlink.net>
Date: Tue, 26 Mar 2002 02:43:30 GMT
Message-ID: <3C9FE065.10FD1527@BACKSIESearthlink.net>


Dusan Bolek wrote:
>
> While you're arguing about deleting/not-deleting of ARC files, one
> question has came to my mind. What is the correct sequence of tasks
> while this problem occurs on NTs ? The only one I know, is to delete
> ARC files, do shutdown abort and startup of dabase. That's not very
> good, because all uncomitted transactions are gonne and must be rerun.
> However just deleting of ARC files (like on Unix) doesn't work,
> because ARCH will not resume its work. And killin' ARCH is impossible,
> because of NT's process management.

I'm not sure I understand the question - are you asking how to unhang an Archiver process that was hung because the log_archive_dest filled up? If so, then it probably depends a bit, but a shutdown abort seems drastic. Haven't used Oracle on NT in a while, but if you're using log_archive_dest and not log_archive_dest_n, then the archiver ought to pick back up on its own after you free up space. If you're using log_archive_dest_n and the destination fills or if the archiver doesn't pick back up on its own on your OS, you can still manually archive the log file. In other words, just because *automatic* archiving stopped/failed for a particular file, doesn't mean you can't do it on your own via "alter system archive log logfile 'filename' to 'location';". Also, you could "trick" the achiver and dynamically change log_archive_dest to a new directory, let ARCH succeed there once, then change it back. But maybe I misunderstood the question?

Regards,
Sean Received on Mon Mar 25 2002 - 20:43:30 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US