Re: onmode -F

I've never seen aproblem using onmode -F. Note that if you run onstat -g seg you can identify which and if any segments will actually befreed by onmode -F. These will be 95% or more unused meaning only overhead pages have been allocated. If a segment is not unused onmode -F will not help anyway. If you are seeing more than one class V, virtual, segment in the onstat -g seg report increase SHMVIRTSIZE to include their size so that you will again only have one after restarting. This is critical on HP/PA. Art S. Kagel "J. Mäki" wrote: > > Of course, it's a question of onmode -F....not onstat -F > > J. Mäki <jukka.maki@tieto.com> wrote in message > news:4aQo5.264$_03.12419@read2.inet.fi... > > Has anybody been facing a problem when running onstat -F > > We had problems with logical logs, they didn't got backed up. > > We are using onbar. After rebooting Informix everything has been always ok > > !. > > Now I tried onstat -F, because I think it's a kind of memory fragmentation > > problem. > > After pressing enter database got stucked. Nothing in Online.log. Dbaccess > > didn't work. > > Sessions from Baan didn't work. I had to give onmode -ky. It took 30 > minutes > > to bring instance down. > > This is very big instance with 3-4 gig memory consumption (onstat -g seg). > > Lot of tables, not so much data. > > Application is baan in 3-tier setup. Version of IDS is 7.31.FC2 on HP/UX > 11 > > N-class, 6 processors and 12g memory. > > I have onstat -p from that situation ( yes, onstat-commands were working > !). > > > > Thank you ! > > > >