Re: Resize redo log without making DB in restricted mode

From: Mark Bole <makbo_at_pacbell.net>
Date: Mon, 25 Apr 2005 14:26:39 GMT
Message-ID: <z67be.361$Gd7.127@newssvr21.news.prodigy.com>

lambu999_at_yahoo.com wrote:

>>>Hi All,
>>>
>>>I have a question.
>>>
>>>I need to resize my redo log file [...]
>>>
>>>This is a development machine with NO ARCHIVE LOG on.
>>>I plan to do it at night time, where , not much transaction going

>

[...]
>
> alter
>

>>the database and switch log files until it is using the new ones.

>
> Then drop
>

>>the small ones.
>>Jim

>
> -------------------------------------------------------------------------
>
> Hi,
>
> - Alter system switch logfile - I presume we have to wait till
> oracle starts using the bigger logfiles in this case, as there are no
> commands to make Oracle switch to a specific logfile. correct?
>
> - In case if the logs are being archived, before dropping the old
> ones we need to make sure they have been archived. I think we can find
> out if the smaller logs have been archived or not from SEQUENCE# column
> of v$archived_log. Is there any command to force archiver to start
> archiving a particular log file or does it start archiving a log
> autmoatically once a log switch happens. (and to prevent from oracle
> using the smaller log, drop the smaller logfile as soon as the
> archiving completes?). Any holes in my assumptions?
>
> Thanks.
>

The database of the OP is in NOARCHIVELOG mode, so the above does not apply specifically.

However if it were in ARCHIVELOG mode, a more useful command than "switch logfile" would be ALTER SYSTEM ARCHIVE LOG CURRENT (or other syntax variations as shown in the docs). Yes, you can archive specific log groups, in 10g at least.

-Mark Bole Received on Mon Apr 25 2005 - 09:26:39 CDT