LTAPEDEV to /dev/null from onmonitor

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

Kindly Ignore this as another thread is open with same content.

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) 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. --001636426ab515ef7904629139b5