LTAPEDEV /dev/null from ON-Monitor
On IDS 11.10 FC3 (Solaris 10), the poster changed LTAPEDEV to /dev/null via ON-Monitor so logical logs would be auto-marked backed up without restarting the instance. The onconfig showed the change, but filled logs stayed unflagged (no 'B'), even after forcing log switches with onmode -l. Art Kagel suggested the next log switch should do it; Malcolm Perrior said the already-full logs must be cleared manually with 'ontape -a' (or 'ontape -c'), since auto-backup only kicks in when the engine starts with /dev/null. The poster disputed this per IBM docs and no definitive resolution was reached, with Malcolm speculating a version inconsistency.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hello, IDS 11.10 FC3 on solaris 10. Simple question~ when i set the LTAPEDEV parameter to /dev/null from ON-Monitor utility to make this change effective while the database server is online. The onconfig file shows LTAPEDEV set to /dev/null and previous entry for LTAPEDEV is commented(also the path is changed to /dev/null). It means that IDS engine has proccessed the change effectively but the logical log files shows 317465e60 509 U-B---- 39185 5:5020053 10000 10000 100.00 317465ec8 510 U-B---- 39186 5:5030053 10000 10000 100.00 317465f30 511 U------ 39187 5:5040053 10000 10000 100.00 317465f98 512 U------ 39188 5:5050053 10000 10000 100.00 317466028 513 U------ 39189 5:5060053 10000 10000 100.00 317466090 514 U------ 39190 5:5070053 10000 10000 100.00 3174661c8 517 U------ 39193 5:5100053 10000 10000 100.00 I have read in some doc/article, that even though the logs are not marked as backed up Immediately by the engine still they are available for writing. When would the logs be marked with "B" as in backedup. Is there some event that will trigger this or some condition has to satisfy? Last time when i changed LTAPEDEV to /dev/null from ON-Monitor i could see all the logs showing status as backed-up after few days (not immediately though)and ofcourse with out rebooting the instance. Regards Vikas
Hello Art!
There were couple of log switches since i changed LTAPEDEV to /dev/null from
ON-Monitor.
Now i have issued a onmode -l and forced a log switch at log id 519 and then
did some transaction to fill few more logs but:
317465e60 509 U-B---- 39185 5:5020053 10000 10000 100.00
317465ec8 510 U-B---- 39186 5:5030053 10000 10000 100.00
317465f30 511 U------ 39187 5:5040053 10000 10000 100.00
317465f98 512 U------ 39188 5:5050053 10000 10000 100.00
317466028 513 U------ 39189 5:5060053 10000 10000 100.00
317466090 514 U------ 39190 5:5070053 10000 10000 100.00
3174660f8 515 U------ 39191 5:5080053 10000 10000 100.00
317466160 516 U------ 39192 5:5090053 10000 10000 100.00
3174661c8 517 U------ 39193 5:5100053 10000 10000 100.00
317466230 518 U------ 39194 5:5110053 10000 10000 100.00
317466298 519 U-----L 39195 5:5120053 10000 6420 64.20
317466300 520 U------ 39196 5:5130053 10000 10000 100.00
317466368 521 U------ 39197 5:5140053 10000 10000 100.00
3174663d0 522 U------ 39198 5:5150053 10000 10000 100.00
317466438 523 U------ 39199 5:5160053 10000 10000 100.00
3174664a0 524 U------ 39200 5:5170053 10000 10000 100.00
317466508 525 U------ 39201 5:5180053 10000 10000 100.00
317466570 526 U------ 39202 5:5190053 10000 10000 100.00
3174665d8 527 U------ 39203 5:5200053 10000 10000 100.00
317466640 528 U------ 39204 5:5210053 10000 10000 100.00
3174666a8 529 U------ 39205 5:5220053 10000 10000 100.00
317466710 530 U------ 39206 5:5230053 10000 10000 100.00
317466778 531 U------ 39207 5:5240053 10000 10000 100.00
3174667e0 532 U------ 39208 5:5250053 10000 10000 100.00
317466848 533 U---C-- 39209 5:5260053 10000 7276 72.76
3174668b0 534 U-B---- 38624 5:5270053 10000 10000 100.00
317466918 535 U-B---- 38625 5:5280053 10000 10000 100.00
What am i missing here?
Vikas.
--------------------------------------------------------------------------
It should happen at the next log change. You can force that with onmode -l
Art
On Tue, Feb 10, 2009 at 7:44 AM, VIKAS HIVARKAR
<vikas.hivarkar@gmail.com>wrote:
> Hello,
>
> IDS 11.10 FC3 on solaris 10.
>
> Simple question~
>
> when i set the LTAPEDEV parameter to /dev/null from ON-Monitor utility to
> make
> this change effective while the database server is online.
>
> The onconfig file shows LTAPEDEV set to /dev/null and previous entry for
> LTAPEDEV is commented(also the path is changed to /dev/null).
>
> It means that IDS engine has proccessed the change effectively but the
> logical
> log files shows
>
> 317465e60 509 U-B---- 39185 5:5020053 10000 10000 100.00
> 317465ec8 510 U-B---- 39186 5:5030053 10000 10000 100.00
> 317465f30 511 U------ 39187 5:5040053 10000 10000 100.00
> 317465f98 512 U------ 39188 5:5050053 10000 10000 100.00
> 317466028 513 U------ 39189 5:5060053 10000 10000 100.00
> 317466090 514 U------ 39190 5:5070053 10000 10000 100.00
> 3174661c8 517 U------ 39193 5:5100053 10000 10000 100.00
>
> I have read in some doc/article, that even though the logs are not marked
> as
> backed up Immediately by the engine still they are available for writing.
>
> When would the logs be marked with "B" as in backedup. Is there some event
> that will trigger this or some condition has to satisfy?
>
> Last time when i changed LTAPEDEV to /dev/null from ON-Monitor i could see
> all
> the logs showing status as backed-up after few days (not immediately
> though)and ofcourse with out rebooting the instance.
>
> Regards
> Vikas
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Dunno. It's been a long time since I ran a server with logs to /dev/null,
even development servers. I'm not that brave.
Art
On Tue, Feb 10, 2009 at 10:41 AM, VIKAS HIVARKAR
<vikas.hivarkar@gmail.com>wrote:
> Hello Art!
>
> There were couple of log switches since i changed LTAPEDEV to /dev/null
> from
> ON-Monitor.
>
> Now i have issued a onmode -l and forced a log switch at log id 519 and
> then
> did some transaction to fill few more logs but:
>
> 317465e60 509 U-B---- 39185 5:5020053 10000 10000 100.00
> 317465ec8 510 U-B---- 39186 5:5030053 10000 10000 100.00
> 317465f30 511 U------ 39187 5:5040053 10000 10000 100.00
> 317465f98 512 U------ 39188 5:5050053 10000 10000 100.00
> 317466028 513 U------ 39189 5:5060053 10000 10000 100.00
> 317466090 514 U------ 39190 5:5070053 10000 10000 100.00
> 3174660f8 515 U------ 39191 5:5080053 10000 10000 100.00
> 317466160 516 U------ 39192 5:5090053 10000 10000 100.00
> 3174661c8 517 U------ 39193 5:5100053 10000 10000 100.00
> 317466230 518 U------ 39194 5:5110053 10000 10000 100.00
> 317466298 519 U-----L 39195 5:5120053 10000 6420 64.20
> 317466300 520 U------ 39196 5:5130053 10000 10000 100.00
> 317466368 521 U------ 39197 5:5140053 10000 10000 100.00
> 3174663d0 522 U------ 39198 5:5150053 10000 10000 100.00
> 317466438 523 U------ 39199 5:5160053 10000 10000 100.00
> 3174664a0 524 U------ 39200 5:5170053 10000 10000 100.00
> 317466508 525 U------ 39201 5:5180053 10000 10000 100.00
> 317466570 526 U------ 39202 5:5190053 10000 10000 100.00
> 3174665d8 527 U------ 39203 5:5200053 10000 10000 100.00
> 317466640 528 U------ 39204 5:5210053 10000 10000 100.00
> 3174666a8 529 U------ 39205 5:5220053 10000 10000 100.00
> 317466710 530 U------ 39206 5:5230053 10000 10000 100.00
> 317466778 531 U------ 39207 5:5240053 10000 10000 100.00
> 3174667e0 532 U------ 39208 5:5250053 10000 10000 100.00
> 317466848 533 U---C-- 39209 5:5260053 10000 7276 72.76
> 3174668b0 534 U-B---- 38624 5:5270053 10000 10000 100.00
> 317466918 535 U-B---- 38625 5:5280053 10000 10000 100.00
>
> What am i missing here?
>
> Vikas.
> --------------------------------------------------------------------------
> It should happen at the next log change. You can force that with onmode -l
>
> Art
>
> On Tue, Feb 10, 2009 at 7:44 AM, VIKAS HIVARKAR
> <vikas.hivarkar@gmail.com>wrote:
>
> > Hello,
> >
> > IDS 11.10 FC3 on solaris 10.
> >
> > Simple question~
> >
> > when i set the LTAPEDEV parameter to /dev/null from ON-Monitor utility to
> > make
> > this change effective while the database server is online.
> >
> > The onconfig file shows LTAPEDEV set to /dev/null and previous entry for
> > LTAPEDEV is commented(also the path is changed to /dev/null).
> >
> > It means that IDS engine has proccessed the change effectively but the
> > logical
> > log files shows
> >
> > 317465e60 509 U-B---- 39185 5:5020053 10000 10000 100.00
> > 317465ec8 510 U-B---- 39186 5:5030053 10000 10000 100.00
> > 317465f30 511 U------ 39187 5:5040053 10000 10000 100.00
> > 317465f98 512 U------ 39188 5:5050053 10000 10000 100.00
> > 317466028 513 U------ 39189 5:5060053 10000 10000 100.00
> > 317466090 514 U------ 39190 5:5070053 10000 10000 100.00
> > 3174661c8 517 U------ 39193 5:5100053 10000 10000 100.00
> >
> > I have read in some doc/article, that even though the logs are not marked
> > as
> > backed up Immediately by the engine still they are available for writing.
> >
> > When would the logs be marked with "B" as in backedup. Is there some
> event
> > that will trigger this or some condition has to satisfy?
> >
> > Last time when i changed LTAPEDEV to /dev/null from ON-Monitor i could
> see
> > all
> > the logs showing status as backed-up after few days (not immediately
> > though)and ofcourse with out rebooting the instance.
> >
> > Regards
> > Vikas
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --
> Art S. Kagel
> Oninit (www.oninit.com)
> IIUG Board of Directors (art@iiug.org)
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do
those opinions reflect those of other individuals affiliated with any entity
with which I am affiliated nor those of the entities themselves.
--001636163eb543dad50462927b7d
Your log logs are filling but IDS won't back them up until you tell it to; use
'ontape -a'.
This happens if you change the LTAPEDEV parameter while the server is online.
If you start the engine with it set to /dev/null, it backs them up
automatically.
Even am i NOT that brave to run any of my important servers with /dev/null.
But yes i set my test instance to /dev/null as there is nothing imp to loose
and not much space to save log files.
For some testing i've changed LTAPEDEV pointing to directory so that i can get
some log files and now wanting /dev/null to be effective, ofcourse with out a
reboot.
Thanks for the Help!
Regards
Vikas
------------------------------------------------------------------------------
Dunno. It's been a long time since I ran a server with logs to /dev/null,
even development servers. I'm not that brave.
Art
On Tue, Feb 10, 2009 at 10:41 AM, VIKAS HIVARKAR
<vikas.hivarkar@gmail.com>wrote:
> Hello Art!
>
> There were couple of log switches since i changed LTAPEDEV to /dev/null
> from
> ON-Monitor.
>
> Now i have issued a onmode -l and forced a log switch at log id 519 and
> then
> did some transaction to fill few more logs but:
>
> 317465e60 509 U-B---- 39185 5:5020053 10000 10000 100.00
> 317465ec8 510 U-B---- 39186 5:5030053 10000 10000 100.00
> 317465f30 511 U------ 39187 5:5040053 10000 10000 100.00
> 317465f98 512 U------ 39188 5:5050053 10000 10000 100.00
> 317466028 513 U------ 39189 5:5060053 10000 10000 100.00
> 317466090 514 U------ 39190 5:5070053 10000 10000 100.00
> 3174660f8 515 U------ 39191 5:5080053 10000 10000 100.00
> 317466160 516 U------ 39192 5:5090053 10000 10000 100.00
> 3174661c8 517 U------ 39193 5:5100053 10000 10000 100.00
> 317466230 518 U------ 39194 5:5110053 10000 10000 100.00
> 317466298 519 U-----L 39195 5:5120053 10000 6420 64.20
> 317466300 520 U------ 39196 5:5130053 10000 10000 100.00
> 317466368 521 U------ 39197 5:5140053 10000 10000 100.00
> 3174663d0 522 U------ 39198 5:5150053 10000 10000 100.00
> 317466438 523 U------ 39199 5:5160053 10000 10000 100.00
> 3174664a0 524 U------ 39200 5:5170053 10000 10000 100.00
> 317466508 525 U------ 39201 5:5180053 10000 10000 100.00
> 317466570 526 U------ 39202 5:5190053 10000 10000 100.00
> 3174665d8 527 U------ 39203 5:5200053 10000 10000 100.00
> 317466640 528 U------ 39204 5:5210053 10000 10000 100.00
> 3174666a8 529 U------ 39205 5:5220053 10000 10000 100.00
> 317466710 530 U------ 39206 5:5230053 10000 10000 100.00
> 317466778 531 U------ 39207 5:5240053 10000 10000 100.00
> 3174667e0 532 U------ 39208 5:5250053 10000 10000 100.00
> 317466848 533 U---C-- 39209 5:5260053 10000 7276 72.76
> 3174668b0 534 U-B---- 38624 5:5270053 10000 10000 100.00
> 317466918 535 U-B---- 38625 5:5280053 10000 10000 100.00
>
> What am i missing here?
>
> Vikas.
> --------------------------------------------------------------------------
> It should happen at the next log change. You can force that with onmode -l
>
> Art
>
> On Tue, Feb 10, 2009 at 7:44 AM, VIKAS HIVARKAR
> <vikas.hivarkar@gmail.com>wrote:
>
> > Hello,
> >
> > IDS 11.10 FC3 on solaris 10.
> >
> > Simple question~
> >
> > when i set the LTAPEDEV parameter to /dev/null from ON-Monitor utility to
> > make
> > this change effective while the database server is online.
> >
> > The onconfig file shows LTAPEDEV set to /dev/null and previous entry for
> > LTAPEDEV is commented(also the path is changed to /dev/null).
> >
> > It means that IDS engine has proccessed the change effectively but the
> > logical
> > log files shows
> >
> > 317465e60 509 U-B---- 39185 5:5020053 10000 10000 100.00
> > 317465ec8 510 U-B---- 39186 5:5030053 10000 10000 100.00
> > 317465f30 511 U------ 39187 5:5040053 10000 10000 100.00
> > 317465f98 512 U------ 39188 5:5050053 10000 10000 100.00
> > 317466028 513 U------ 39189 5:5060053 10000 10000 100.00
> > 317466090 514 U------ 39190 5:5070053 10000 10000 100.00
> > 3174661c8 517 U------ 39193 5:5100053 10000 10000 100.00
> >
> > I have read in some doc/article, that even though the logs are not marked
> > as
> > backed up Immediately by the engine still they are available for writing.
> >
> > When would the logs be marked with "B" as in backedup. Is there some
> event
> > that will trigger this or some condition has to satisfy?
> >
> > Last time when i changed LTAPEDEV to /dev/null from ON-Monitor i could
> see
> > all
> > the logs showing status as backed-up after few days (not immediately
> > though)and ofcourse with out rebooting the instance.
> >
> > Regards
> > Vikas
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --
> Art S. Kagel
> Oninit (www.oninit.com)
> IIUG Board of Directors (art@iiug.org)
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
...or you could run 'ontape -c' for continuous log log backups; do it in a
spare terminal session or use 'at now' or similar.
Vikas Did you try my suggestions? Is it working? regards Malc
Hello Malcolm !
-----Your log logs are filling but IDS won't back them up until you tell it
to; use 'ontape -a'.
This happens if you change the LTAPEDEV parameter while the server is online.
If you start the engine with it set to /dev/null, it backs them up
automatically.-------
Your solution is perfectly ok in case i wish to backup my logs but thats not
what i want to do.
Please read the following from IBM site:
"You can specify /dev/null as a tape device for logical-log backups when you
decide that you do not need to recover transactions from the logical log. When
you specify the tape device as /dev/null, block size and tape size are
ignored. If you set LTAPEDEV either to or from /dev/null, you must use
ON-Monitor or restart the database server for the new setting to take effect."
See, it says that eighter i have to set /dev/null in onconfig and reboot the
instance for the change to be effective OR set the LTAPEDEV to /dev/null from
ON-Monitor and the change should be effective with out a reboot.
After changing the LTAPEDEV to /dev/null from ON-Monitor, there is single
uncommented LTAPEDEV entry in onconfig and is set to /dev/null which confirms
that the engine has processes the change from ON-Monitor.
I've worked with this just couple of months back with IDS 11.10 FC2W4 and
every thing was ok.
As you mentioned: I can backup the logs using "ontape -a" OR reboot the
instance for /dev/null to be effective. BUT before that trying to figure out
what exactly have I missed? may be some thing very obvious or may be..
Regards
Vikas
P.S: I can afford to wait for some time with logs not backed up ( or not
showing as backed up) as it is my TEST instance, not much logging activity
except when i do some and i have enough logs to avoid any instance hanging
because of no log free scenario.
Hmmmm - you're on a later version to me so I hadn't noticed that one could now change LTAPEDEV to /dev/null with OnMonitor and have it instantly recognised.....if you've had it work on an earlier sub-version then I can only suspect that there's an inconsistency in behaviour with your current one. Good luck!
That's always worked that way. Art On Wed, Feb 11, 2009 at 11:49 AM, MALCOLM PERRIOR <iiug@perrior.net> wrote: > Hmmmm - you're on a later version to me so I hadn't noticed that one could > now > change LTAPEDEV to /dev/null with OnMonitor and have it instantly > recognised.....if you've had it work on an earlier sub-version then I can > only > suspect that there's an inconsistency in behaviour with your current one. > > Good luck! > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. --0016364ee39e2cb4460462a9321b