Some strategy to resize logical-logs in HDR
Posted in 2013
User asked about resizing logical logs in an 11.50 HDR two-node setup without rebuilding the secondary. Multiple experts confirmed HDR automatically replicates logical log changes: use onparams to add new larger logs, take a fake backup to /dev/null, use onmode -l and onmode -c to move current log into new logs, then drop old ones. Secondary automatically stays in sync without needing reconstruction.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: High Availability & Replication
Hello my friends. Happy new year for all! I have a two node HDR, based in 11.50 version, needing to resize my logical-logs. My doubt is: is there some good strategy to do it, with less time spending? My idea is: stop hdr, letting just site A online (in standard mode), resize everything, but then it would require me to rebuild my HDR (site B reconstruction, resync) of course.... Is there any easier way to do it, maybe without the need to rebuild the HDR environment? Thanks a lot for your attention. Regards.
ALEXANDRE
Admin Guide Chapter 20 :
"
*Managing the Logical Log*
The size of the logical log must be the same on both database servers. You
can add or drop a logical-log file with the onparams utility, as described
in Chapter 14, Managing Logical-Log Files, on page 14-1. Dynamic Server
replicates this change on the secondary database server; however, the
LOGFILES parameter on the secondary database server is not updated. After
you issue the onparams command from the primary database server, therefore,
you must manually change the LOGFILES parameter to the desired value on the
secondary database server. Finally, for the change to take effect, you must
perform a level-0 backup of the root dbspace on the primary database server.
If you add a logical-log file to the primary database server, this file is
available for use and flagged F as soon as you perform the level-0 backup.
The new logical-log file on the secondary database server is still flagged
A. However, this condition does not prevent the secondary database server
from writing to the file.
"
Therefore, just do what you want to do on the Primary and the Secondary is
kept in step auto-magically, no need to break the HDR at all, and because
IDS is so good, your users won't even know this is happening (unlike M$$QL
which locks the database to build an index Grrrr!!)
Keith
On 3 January 2013 12:48, *ALEXANDRE *MARINI <alexandre@briug.org> wrote:
> Hello my friends.
> Happy new year for all!
>
> I have a two node HDR, based in 11.50 version, needing to resize my
> logical-logs.
> My doubt is: is there some good strategy to do it, with less time spending?
>
> My idea is: stop hdr, letting just site A online (in standard mode), resize
> everything, but then it would require me to rebuild my HDR (site B
> reconstruction, resync) of course....
>
> Is there any easier way to do it, maybe without the need to rebuild the HDR
> environment?
>
> Thanks a lot for your attention.
> Regards.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--20cf307d04d227e0c204d26208b2
Thanks a lot, I am even more impressed about Informix HDR features now. Regards, Keith!
Just use onparams to add new logical logs with the new size, then use
onparams to drop the older smaller ones. The secondary will follow along
and add and drop the logs at the same time as the log records recording
those changes are propagated to it. You will need to use onmode -l and
onmode -c to move the 'current' log and the checkpoint record into the newlogs and wait for the secondary to catch up with those changes before
dropping the 'current' log, otherwise this is not complex.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
On Thu, Jan 3, 2013 at 6:48 AM, ALEXANDRE MARINI <alexandre@briug.org>wrote:
> Hello my friends.
> Happy new year for all!
>
> I have a two node HDR, based in 11.50 version, needing to resize my
> logical-logs.
> My doubt is: is there some good strategy to do it, with less time spending?
>
> My idea is: stop hdr, letting just site A online (in standard mode), resize
> everything, but then it would require me to rebuild my HDR (site B
> reconstruction, resync) of course....
>
> Is there any easier way to do it, maybe without the need to rebuild the HDR
> environment?
>
> Thanks a lot for your attention.
> Regards.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--f46d0447882dde01b904d262ee50
On 3 Jan 2013, at 12:48, ALEXANDRE MARINI <alexandre@briug.org> wrote:
> Hello my friends.
> Happy new year for all!
>
> I have a two node HDR, based in 11.50 version, needing to resize my
> logical-logs.
> My doubt is: is there some good strategy to do it, with less time spending?
>
> My idea is: stop hdr, letting just site A online (in standard mode), resize
> everything, but then it would require me to rebuild my HDR (site B
> reconstruction, resync) of course....
>
> Is there any easier way to do it, maybe without the need to rebuild the HDR
> environment?
Why not just add the new logs, take a fake backup and use onmode -l and onmode
to move into the new logs and drop the old ones?
I agree with Spokey's strategy. Just make sure you have space in the dbspaces
on both the primary and secondary servers. Add the new, larger logical logs.
Take an archive to /dev/null. Move to the new logical logs. Delete the old
undersized logical logs. As long as you have space on both servers, all the
work will be done on your primary server.
Larry
> To: ids@iiug.org
> From: spokey.wheeler@gmail.com
> Subject: Re: Some strategy to resize logical-logs in HDR [29182]
> Date: Thu, 3 Jan 2013 23:10:54 -0500
>
> On 3 Jan 2013, at 12:48, ALEXANDRE MARINI <alexandre@briug.org> wrote:
>
> > Hello my friends.
> > Happy new year for all!
> >
> > I have a two node HDR, based in 11.50 version, needing to resize my
> > logical-logs.
> > My doubt is: is there some good strategy to do it, with less time spending?
> >
> > My idea is: stop hdr, letting just site A online (in standard mode), resize
> > everything, but then it would require me to rebuild my HDR (site B
> > reconstruction, resync) of course....
> >
> > Is there any easier way to do it, maybe without the need to rebuild the HDR
> > environment?
>
> Why not just add the new logs, take a fake backup and use onmode -l and
onmode> to move into the new logs and drop the old ones?
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>