Message-Id: <10660.120239@fatcity.com> From: Satar Naghshineh Date: Wed, 25 Oct 2000 15:29:59 -0700 Subject: Waits on archiving This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C03ED3.20856D60 Content-Type: text/plain > Ohh Proactive... Gotcha. There's not much to be proactive about. Once you > have set it up properly, it runs smoothly. The archiving process comes to > play in two ways (maybe I'm missing something, forgive me): > > 1. Not enough room on device to write an archived redo log. > System will freeze in this situation. Writing scripts/commands in Cron to > control this is advisable. For me, I have to also look at it daily due to > some Rambo developers who like to do a million Inserts/updates/deletes > time to time. > > 2. Competition for I/O on the CPU, system bus, controller, disk bus, disk > spindle. > Ideally you want to have your archive dest set to a device that has it's > own I/O path. > > By the way, am I understanding your question right? > > Regards, > Satar > > -----Original Message----- > From: David Turner [SMTP:turner@tellme.com] > Sent: Wednesday, October 25, 2000 9:56 PM > To: Multiple recipients of list ORACLE-L > Subject: Re: Waits on archiving > > Hehe. I like that but I'd like to be a bit more proactive. I am switching > logs about > every 6 minutes and will be setting it up to switch between 30 and 45 min. > I still > would like to know the waiting due to archiving though. > > Dave Turner > On Wed, Oct 25, 2000 at 11:30:41AM -0800, Satar Naghshineh wrote: > > Don't worry about knowing if you have problems, the users will let you > know. > > The whole Database freezes until the ARCH process can write again. > > > > Regards, > > Satar > > > > > > > ------_=_NextPart_001_01C03ED3.20856D60 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Waits on archiving

Ohh Proactive... = Gotcha. There's not much to be proactive about. Once you have set it up = properly, it runs smoothly. The archiving process comes to play in two = ways (maybe I'm missing something, forgive me):

1. Not enough room = on device to write an archived redo log.
System will freeze = in this situation. Writing scripts/commands in Cron to control this is = advisable. For me, I have to also look at it daily due to some Rambo = developers who like to do a million Inserts/updates/deletes time to = time.

2. Competition for = I/O on the CPU, system bus,  controller, disk bus, disk spindle. =
Ideally you want to = have your archive dest set to a device that has it's own I/O = path.

By the way, am I = understanding your question right?

Regards,
Satar