Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Use "onstat -g mem" when it happens again. It should show some very
large pool. If the pool name in column 1 is a number than this is the
session number (use onstat -g ses <num>). But it's possible that the
memory was not allocated for a particular session. If you can send me
the output I will try and tell you more.
Michael
Zev Berezin wrote:
> Hi All,
>
>
>
> Version: IDS 7.31.UD5 - Tools 7.30.UC5 - Solaris 2.6
>
> Yesterday a process dynamically allocated as much virtual memory as
> allowed by SHMTOTAL - 48 new allocations in less than a minute!
> I ran onmode -F and it worked as advertised, almost all segmetns were
> freed.
>
> I tried to track the session that caused this.
> onstat -u didn't return any users with large reads or writes.> I suppose since onmode -F was able to free so many segments, the
> offending session was probably not active anyway.
>
> My question is how could I map a session to virtual memory usage.
> I could use the ALARMPROGRAM to run onstat's if alarm event = 6.
> the ran out of virtual shared memory code.
>
> I'm not sure however, how to specifically map virtual memory usage to a
> specific session.
>
> Any help is appreciated.
>
>
> TIA,
> Zev Berezin
> IBM Informix DBA
>
> sending to informix-list
--
=== Michael Mueller ==================
Tel. + 49 8171 63600
Fax. + 49 8171 63615
Web: http://www.mm.kay-mueller.dehttp://www.planets.kay-mueller.de
======================================
sending to informix-list
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.