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@xxxxxxxxxxxxxxxx>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 > -- > //www.freelists.org/webpage/oracle-l > > >