track session of memory segment
Hello,
i have informix 11.50FC8GE server in there there are some memory segments so i
want to track particulate user session or process for those memory segment.
what is the best way to track them.
memory segment like follows.
IBM Informix Dynamic Server Version 11.50.FC8GE -- On-Line (Prim) -- Up 140
days 13:37:16 -- 9902464 Kbytes
Segment Summary:
id key addr size ovhd class blkused blkfree
3145734 52564801 c000000005f00000 8993243136 105827216 R 2195614 2
7 52564802 c00000021e000000 1048576000 12289744 V 241224 14776
8 52564803 c00000025c800000 32768000 385504 V 7770 230
9 52564804 c00000025ed00000 32768000 385504 V 3845 4155
32778 52564805 c000000260d00000 32768000 385504 V 111 7889
Total: - - 10140123136 - - 2448564 27052
(* segment locked in memory)
You have 5 memory segments in use by server number 0 on your system. (The
52564801 is a hex number that encodes that information the 01 at the end
indicates segment 1, and your segments go up to 05. The digits 525648
encode the initials RVH, for Roy V Harrington, one of the people who worked
for Informix in the very early days.). Those shared memory segments are
all used by your main server; they're shared between all the processes that
make up that server. There may be session data in any of them. You can't
simply eliminate any of them, especially not with 11.50. You could restart
your server; that would probably reduce the number of segments if your
system has grown over the 20 weeks it has been running.
What is your real concern?
On Mon, Nov 23, 2015 at 9:16 PM, PUSHPA KUMARA <pushpa@cybersoft.lk> wrote:
> Hello,
>
> i have informix 11.50FC8GE server in there there are some memory segments
> so i
> want to track particulate user session or process for those memory segment.
> what is the best way to track them.
>
> memory segment like follows.
> IBM Informix Dynamic Server Version 11.50.FC8GE -- On-Line (Prim) -- Up 140
> days 13:37:16 -- 9902464 Kbytes>
> Segment Summary:
> id key addr size ovhd class blkused blkfree
> 3145734 52564801 c000000005f00000 8993243136 105827216 R 2195614 2
> 7 52564802 c00000021e000000 1048576000 12289744 V 241224 14776
> 8 52564803 c00000025c800000 32768000 385504 V 7770 230
> 9 52564804 c00000025ed00000 32768000 385504 V 3845 4155
> 32778 52564805 c000000260d00000 32768000 385504 V 111 7889
> Total: - - 10140123136 - - 2448564 27052
>
> (* segment locked in memory)
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Jonathan Leffler <jonathan.leffler@gmail.com> #include <disclaimer.h>
Guardian of DBD::Informix - v2015.1101 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."
--089e013a06bc68c436052542fa31
Hi,
as Jonathan already wrote, individual shared memory segments of
the Informix server are not directly associated with (individual) client
sessions.
You track sessions with the command "onstat -g ses". From there you
can obtain the session ID of individual sessions. By specifying such a
session ID, as in "onstat -g ses <session=5FID>" you can get more
specific information on individual sessions. This then also contains
info on how much memory a session has in use. This memory is
'allocated' (internally in the Informix server) from those shared
memory segments that you see with the command "onstat -g seg".
Regards, Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland Research & Development GmbH
Chairman of the Supervisory Board: Martina Koederitz
Board of Management: Dirk Wittkopp
Corporate Seat: Boeblingen, Germany
Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
From: "Jonathan Leffler" <jonathan.leffler@gmail.com>
To: ids@iiug.org
Date: 11/24/2015 06:55
Subject: Re: track session of memory segment [36106]
Sent by: ids-bounces@iiug.org
You have 5 memory segments in use by server number 0 on your system. (The=20
52564801 is a hex number that encodes that information the 01 at the end=20
indicates segment 1, and your segments go up to 05. The digits 525648=20
encode the initials RVH, for Roy V Harrington, one of the people who=20
worked=20
for Informix in the very early days.). Those shared memory segments are=20
all used by your main server; they're shared between all the processes=20
that=20
make up that server. There may be session data in any of them. You can't=20
simply eliminate any of them, especially not with 11.50. You could restart =
your server; that would probably reduce the number of segments if your=20
system has grown over the 20 weeks it has been running.=20
What is your real concern?=20
On Mon, Nov 23, 2015 at 9:16 PM, PUSHPA KUMARA <pushpa@cybersoft.lk>=20
wrote:=20
> Hello,=20
>=20
> i have informix 11.50FC8GE server in there there are some memory=20
segments=20
> so i=20
> want to track particulate user session or process for those memory=20
segment.=20
> what is the best way to track them.=20
>=20
> memory segment like follows.=20
> IBM Informix Dynamic Server Version 11.50.FC8GE -- On-Line (Prim) -- Up=20
140=20
> days 13:37:16 -- 9902464 Kbytes=20
>=20
> Segment Summary:=20> id key addr size ovhd class blkused blkfree=20
> 3145734 52564801 c000000005f00000 8993243136 105827216 R 2195614 2=20
> 7 52564802 c00000021e000000 1048576000 12289744 V 241224 14776=20
> 8 52564803 c00000025c800000 32768000 385504 V 7770 230=20
> 9 52564804 c00000025ed00000 32768000 385504 V 3845 4155=20
> 32778 52564805 c000000260d00000 32768000 385504 V 111 7889=20
> Total: - - 10140123136 - - 2448564 27052=20
>=20
> (* segment locked in memory)=20
>=20
>=20
>=20
>=20
***************************************************************************=
****=20
> Forum Note: Use "Reply" to post a response in the discussion forum.=20
>=20
>=20
--=20
Jonathan Leffler <jonathan.leffler@gmail.com> #include <disclaimer.h>=20
Guardian of DBD::Informix - v2015.1101 - http://dbi.perl.org=20
"Blessed are we who can laugh at ourselves, for we shall never cease to be =
amused."=20
--089e013a06bc68c436052542fa31=20
***************************************************************************=
****=20
Forum Note: Use "Reply" to post a response in the discussion forum.=20
Pushpa:
If you run "onstat -g ses 0" you can see how much memory each session has
allocated and used. The same information is available in
sysmaster:sysscblst so you can select from there order by memtotal or
memused to see the worst offender sessions. Keep in mind that any session
that is no longer connected will not show up.
To catch short lived sessions consuming memory you would have to have
SQLTRACE turned on and be capturing that data periodically using onstat -g
his or enabling the task manager task that's installed for that purpose.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.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 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 Tue, Nov 24, 2015 at 12:16 AM, PUSHPA KUMARA <pushpa@cybersoft.lk> wrote:
> Hello,
>
> i have informix 11.50FC8GE server in there there are some memory segments
> so i
> want to track particulate user session or process for those memory segment.
> what is the best way to track them.
>
> memory segment like follows.
> IBM Informix Dynamic Server Version 11.50.FC8GE -- On-Line (Prim) -- Up 140
> days 13:37:16 -- 9902464 Kbytes>
> Segment Summary:
> id key addr size ovhd class blkused blkfree
> 3145734 52564801 c000000005f00000 8993243136 105827216 R 2195614 2
> 7 52564802 c00000021e000000 1048576000 12289744 V 241224 14776
> 8 52564803 c00000025c800000 32768000 385504 V 7770 230
> 9 52564804 c00000025ed00000 32768000 385504 V 3845 4155
> 32778 52564805 c000000260d00000 32768000 385504 V 111 7889
> Total: - - 10140123136 - - 2448564 27052
>
> (* segment locked in memory)
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a113fe84e7f586b052547adea