Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: arch directory filled; restart ARCH process?
This is a multi-part message in MIME format.
------=_NextPart_000_0041_01BFECAC.58CC0940 Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
RE: arch directory filled; restart ARCH process?The size of the archive log
it has to produce is a lot bigger then anything it needs to write into the
alert.log. In my experience the archive log directory has never filled up
to the point where there
are no bytes left at all. It may show 100% but there is still a tiny amount
of space left.
-----Original Message-----
From: root_at_fatcity.com [mailto:root_at_fatcity.com]On Behalf Of Alex Hillman
Sent: Thursday, July 13, 2000 8:26 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: arch directory filled; restart ARCH process?
Would be interesting to know what would happen if archive logs were in the same file system as alert.log. On NT it is often the situation for small boxes - let say they have 1 disk. Anybody knows the answer?
Alex Hillman
-----Original Message-----
From: James Bullard [mailto:jbullard_at_onvia.com]
Sent: Wednesday, July 12, 2000 7:48 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: arch directory filled; restart ARCH process?
There was also a bug in 8.0.5 on HP/UNIX and archiver would not restart
after the destination had been cleared, however, they do have a patch.
Apparently it is eliminated in 8.0.6. Another interesting side note, on
our
live site, we had the same problem occur and Oracle will spawn other
archiver processes in the event after some prodding the first one does not
respond. It shows up in the alert log.
James
-----Original Message-----
Sent: Wednesday, July 12, 2000 2:23 PM
To: Multiple recipients of list ORACLE-L
Once the archive destination has free space the arch process should
restart
automatically by itself. I've had this happen every so often. The DB
does
not
crash although arch gets wrapped up around the flag pole pretty bad till
it
gets
fixed. The DB will continue to run normally until the last of the online
redo
logs gets filled at which time it ceases to run additional transactions,
freezes
anybody currently logged on and refuses to accept any new connections.
Mostly
folks will get an ORA-00257 error and that's all. Once Arch is freed up
and
has
had time to archive one online redo log successfully things will return to
normal by themselves. BTW: If arch was writing to a file when the
directory
filled, it will hold that file open & try to finish when it can.
Dick Goulet
____________________Reply Separator____________________ Author: "Sandy Ocheltree" <ora_dba_at_hotmail.com> Date: 7/12/00 10:45 AM
Help. I have just started working with a database in archivelog mode. The process that writes our archived logs to tape failed yesterday and eventually the directory that holds the logs filled. The database did not crash though! (I thought that's how it worked?) The alert log has entries showing ARCH trying to write to the filled directory, and failing, but no db
crash. I have copied the archived files off for now and freed up space--is it safe to just restart the ARCH process? Once the process is restarted will
it continue to write to the file that it was archiving to when it failed? Or
will it write to a new file? Am I missing something crucial here?
Thanks,
Sandy
--
Author: Sandy Ocheltree
INET: ora_dba_at_hotmail.com
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists --------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists --------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists --------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L
------=_NextPart_000_0041_01BFECAC.58CC0940 Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =charset=3Diso-8859-1">
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR></HEAD> <BODY> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =class=3D493552316-13072000>The=20
<BR><FONT size=3D2>Sent: Wednesday, July 12, 2000 7:48 PM</FONT> =
<BR><FONT=20
size=3D2>To: Multiple recipients of list ORACLE-L</FONT> <BR><FONT=20
size=3D2>Subject: RE: arch directory filled; restart ARCH =
process?</FONT>=20
</P><BR>
<P><FONT size=3D2>There was also a bug in 8.0.5 on HP/UNIX and =
archiver would=20
not restart</FONT> <BR><FONT size=3D2>after the destination had been =
cleared,=20
however, they do have a patch.</FONT> <BR><FONT size=3D2>Apparently it =
is=20
eliminated in 8.0.6. Another interesting side note, on =
our</FONT>=20
<BR><FONT size=3D2>live site, we had the same problem occur and Oracle =
will=20
spawn other</FONT> <BR><FONT size=3D2>archiver processes in the event =
after some=20
prodding the first one does not</FONT> <BR><FONT size=3D2>respond. It =
shows up=20
in the alert log.</FONT> </P><BR>
<P><FONT size=3D2>James </FONT></P>
<P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>Sent:=20
Wednesday, July 12, 2000 2:23 PM</FONT> <BR><FONT size=3D2>To: =
Multiple=20
recipients of list ORACLE-L</FONT> </P><BR>
<P><FONT size=3D2>Once the archive destination has free space the arch =
process=20
should restart</FONT> <BR><FONT size=3D2>automatically by =
itself. I've had=20
this happen every so often. The DB does</FONT> <BR><FONT=20
size=3D2>not</FONT> <BR><FONT size=3D2>crash although arch gets =
wrapped up around=20
the flag pole pretty bad till it</FONT> <BR><FONT size=3D2>gets</FONT> =
<BR><FONT=20
size=3D2>fixed. The DB will continue to run normally until the =
last of the=20
online</FONT> <BR><FONT size=3D2>redo</FONT> <BR><FONT size=3D2>logs =
gets filled=20
at which time it ceases to run additional transactions,</FONT> =
<BR><FONT=20
size=3D2>freezes</FONT> <BR><FONT size=3D2>anybody currently logged on =
and refuses=20
to accept any new connections.</FONT> <BR><FONT size=3D2>Mostly</FONT> =
<BR><FONT=20
size=3D2>folks will get an ORA-00257 error and that's all. Once =
Arch is=20
freed up and</FONT> <BR><FONT size=3D2>has</FONT> <BR><FONT =
size=3D2>had time to=20
archive one online redo log successfully things will return to</FONT>=20
<BR><FONT size=3D2>normal by themselves. BTW: If arch was =
writing to a=20
file when the directory</FONT> <BR><FONT size=3D2>filled, it will hold =
that file=20
open & try to finish when it can.</FONT> </P>
<P><FONT size=3D2>Dick Goulet</FONT> </P>
<P><FONT size=3D2>____________________Reply = Separator____________________</FONT>=20
archivelog mode. The </FONT><BR><FONT size=3D2>process that writes our =
archived=20
logs to tape failed yesterday and </FONT><BR><FONT size=3D2>eventually =
the=20
directory that holds the logs filled. The database did not =
</FONT><BR><FONT=20
size=3D2>crash though! (I thought that's how it worked?) The alert log =
has=20
entries </FONT><BR><FONT size=3D2>showing ARCH trying to write to the =
filled=20
directory, and failing, but no db</FONT> </P>
<P><FONT size=3D2>crash. I have copied the archived files off for now =
and freed=20
up space--is </FONT><BR><FONT size=3D2>it safe to just restart the =
ARCH process?=20
Once the process is restarted will</FONT> </P>
<P><FONT size=3D2>it continue to write to the file that it was =
archiving to when=20
it failed? Or</FONT> </P>
<P><FONT size=3D2>will it write to a new file? Am I missing something =
crucial=20
here?</FONT> <BR><FONT size=3D2>Thanks,</FONT> <BR><FONT =
size=3D2>Sandy</FONT>=20
<BR><FONT=20
=
size=3D2>________________________________________________________________=________</FONT>=20
538-5051 FAX: (858) 538-5051</FONT> <BR><FONT size=3D2>San =
Diego,=20
California -- Public =
Internet access=20
/ Mailing Lists</FONT> <BR><FONT=20
=
size=3D2>----------------------------------------------------------------=----</FONT>=20
<BR><FONT size=3D2>-- </FONT><BR><FONT size=3D2>Author: =
</FONT><BR><FONT=20
size=3D2> INET: dgoulet_at_vicr.com</FONT> </P>
<P><FONT size=3D2>Fat City Network Services -- (858) =
538-5051 FAX: (858) 538-5051</FONT> <BR><FONT size=3D2>San =
Diego,=20
California -- Public =
Internet access=20
/ Mailing Lists</FONT> <BR><FONT=20
=
size=3D2>----------------------------------------------------------------=----</FONT>=20
538-5051 FAX: (858) 538-5051</FONT> <BR><FONT size=3D2>San =
Diego,=20
California -- Public =
Internet access=20
/ Mailing Lists</FONT> <BR><FONT=20
=
size=3D2>----------------------------------------------------------------=----</FONT>=20
![]() |
![]() |