RE: changing archivelog mode in 10g

Alter archive log stop was part of a nice way to rotate destination targets for the archive location.

In older disk technology it was sweet indeed to have arch completely own a single disk drive at a time and turn loose the tape drive on the "one less than a log file full" drive (or time driven) previous destination with absolutely nothing referencing that drive.

It had absolutely nothing to do with whether you were running in "noarchivelog" mode, which frequently resulted in human to human communication errors.

With multiple archive log destinations to guards and the like, my GUESS would be the effect of the command was removed to avoid hanging the system without inherently generating an error to the then existing rotation systems.

What is the context in which it would make your life easier? Perhaps someone has an idea for a work-around for your particular situation. As a dinosaur, I'm quite sympathetic to laments of the form "I wish xxx still worked" but that doesn't help us help you.

OT: Is Ted going to survive the smear and charges to get re-elected? Will he get his trial before the election so he can clear himself?

Regards,

mwf

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Maureen English
Sent: Tuesday, August 12, 2008 6:47 PM
To: oracle-l_at_freelists.org
Subject: Re: changing archivelog mode in 10g

Maybe it's me who missed something. The 10g SQL Reference shows the alter system
command to have an archive_log_clause. One option for the syntax of this clause
is 'archive log stop', making the command 'alter system archive log stop'.

The description of the stop clause, however, says:

> STOP Clause
> In earlier releases, this clause disabled automatic archiving of redo log
file groups for
> the thread assigned to your instance. This clause has been deprecated. It
has no effect,
> and if you specify it, Oracle Database writes a message to the alert log.

Doesn't that mean the same thing as turning off archiving - or is that word 'automatic'
what's got me confused?
We never did this with a 9i database, but a user was loading so much data into one of our
10g databases today that we kept running out of space for archive logs. It would have been
nice to be able to turn off archive logging without shutting down the database.

• Maureen

Bradd Piontek wrote:
> Maybe I'm missing something. I thought all 'alter system archive log
> stop' did was stop the archiver processes. This didn't turn off
> archiving for the database. That has to be done in MOUNT mode. I believe
> the reason it isn't used anymore, is that log_archive_start has been
> deprecated (the archiver processes are automatically stopped/started
> when needed). My assumption was that they did this since
> log_archive_start had a tendency of being missed by dba's when enabling
> archivelog mode.
> I could be mistaken.
>
> Bradd Piontek
> Oracle Blog: http://piontekdd.blogspot.com
> Linked In: http://www.linkedin.com/in/piontekdd
>
>
> On Tue, Aug 12, 2008 at 12:45 PM, Maureen English
> <sxmte_at_email.alaska.edu <mailto:sxmte_at_email.alaska.edu>> wrote:
>
> Why did Oracle decide that stopping archive logging when
> the database was up and available is no longer a desired
> option?
>
> In 9i, we could do an 'alter system archive log stop;',
> but in 10g, this is not supported.
>
> It sure would make my life easier right about now....
>
> - Maureen
> University of Alaska
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l




--
http://www.freelists.org/webpage/oracle-l