Re: Changing size of redo logs
From: Eugene Freydenzon <efreydenzon_at_corpinfo.com>
Date: 1996/09/11
Message-ID: <32374C44.6EA_at_corpinfo.com>#1/1
6. Repeat steps 1 to 5 for all groups.
Note: Sometimes change sequence is different from naming sequience. To be shure: issue 4, and after that 1. and find out. Basicaly, you need to use not second in sequience because of the switch log risk during your operations. In most cases you can ignore that (if you have more that 10 minutes between normal log switches). Just issue 4 first, and after that replace all groups as above. After that another switch(the same step 4), and the last one.
Note 2: In case of archivelog, do not worry about wasting diskspace with archived logs - they will be small.
Note 3: In case you are going to change your files name, you can do everything, without deleting physical files, you can delete them afterwards.
Note 4: You do not need to logout users for this task. Note 5: All canges will not affect to rolling forvard using archived logs, but you need to back up because of controlfiles entries problem. In fact, you can recover database using your "backup controlfile to trace", but it will be an additional headache. If I missed something, please forgive me. If I was too detailed, --------""-------. Hope it helps,
Eugene.
Date: 1996/09/11
Message-ID: <32374C44.6EA_at_corpinfo.com>#1/1
B. Yim wrote:
>
> I have a database with rather small redo logs. Now the number of
> transactions are tripled and I need to increase the size of the redo
> logs so as not to generate so many archive logs.
>
> Is there any way to do this, especially without shutting down the
> database.
>
> TIA
B. Yim wrote:
>
> I have a database with rather small redo logs. Now the number of
> transactions are tripled and I need to increase the size of the redo
> logs so as not to generate so many archive logs.
>
> Is there any way to do this, especially without shutting down the
> database.
>
> TIA
You can do it like this:
1. Check in v$log which log is active (STATUS) 2. Drop last group in that sequence (if active is 1, drop 3). 3. using OS command remove old group files.4 Issue "alter system switch logfile" to switch to another group. 5. add new group with nessesary parameters (location, size, amount of members. etc.)
6. Repeat steps 1 to 5 for all groups.
Note: Sometimes change sequence is different from naming sequience. To be shure: issue 4, and after that 1. and find out. Basicaly, you need to use not second in sequience because of the switch log risk during your operations. In most cases you can ignore that (if you have more that 10 minutes between normal log switches). Just issue 4 first, and after that replace all groups as above. After that another switch(the same step 4), and the last one.
Note 2: In case of archivelog, do not worry about wasting diskspace with archived logs - they will be small.
Note 3: In case you are going to change your files name, you can do everything, without deleting physical files, you can delete them afterwards.
Note 4: You do not need to logout users for this task. Note 5: All canges will not affect to rolling forvard using archived logs, but you need to back up because of controlfiles entries problem. In fact, you can recover database using your "backup controlfile to trace", but it will be an additional headache. If I missed something, please forgive me. If I was too detailed, --------""-------. Hope it helps,
Eugene.
-- ******************************************************** * Everything above is only my opinion * ******************************************************** * * * If you see a lion in a cage and sign says "elephant" * * , * * DO not belive your eyes ! * * (Kozma Prutkov. (informal translation)) * * * ********************************************************Received on Wed Sep 11 1996 - 00:00:00 CEST