Hi Andrew, I tried that and took it out.
See the comment in the blog.
" There was a twitter discussion about this today :
https://twitter.com/SteveHarville/status/466269935199453185
I modified the code like this:
execute immediate ‘ALTER SYSTEM ARCHIVE LOG CURRENT’ ;
execute immediate ‘ALTER SYSTEM CHECKPOINT GLOBAL’ ;
I ran the old version and the new version on a test database and the new
version took almost double the time!
So I won’t make the change in the original code."
On 5:39pm, Thu, Aug 6, 2015 Andrew Kerber <andrew.kerber@xxxxxxxxx> wrote:
That's nice. Just add an alter system checkpoint prior to the first wait
before the drop and it will be even nicer.
Sent from my iPad
On Aug 6, 2015, at 3:32 PM, Steve Harville <steve.harville@xxxxxxxxx>
wrote:
I wrote a PL/SQL package to do this :
https://steveharville.wordpress.com/2014/03/20/automating-redo-log-maintenance/
On Thu, Aug 6, 2015 at 1:31 PM Andrew Kerber <andrew.kerber@xxxxxxxxx>
wrote:
Pro tip: 'alter system checkpoint' after a log switch will put the
previous log into the inactive state faster than just waiting.
Sent from my iPad
On Aug 6, 2015, at 12:18 PM, Don Seiler <don@xxxxxxxxx> wrote:
Best way to move them without downtime is to add new logfile groups on
the new location, then perform logfile switches and as the old logfiles are
archived and status is INACTIVE then you can drop the old groups. Ideally
new and old groups would have the same size logs, etc.
Don.
On Thu, Aug 6, 2015 at 12:12 PM, Michael Calisi <oracle455@xxxxxxxxx>
wrote:
I am new to oracle-l and posting my first question.
I currently have 6 redo logs and we would like to move them with out
taken the database down. We are creating a new lun/pool on the top shelf
and wondering what's the best way to move my redo logs.
Thanks,
--
Don Seiler
http://www.seiler.us
