Re: Excess V-segment allocation - who's responsible?

onstat -g mem will give you the session (first column) along with theaddress that can be related to onstat -g seg malc_p@btinternet. com (Malc P) To: informix-list@iiug.org Sent by: cc: owner-informix-lis Subject: Re: Excess V-segment allocation - who's t@iiug.org responsible? 03/12/2004 03:48 AM Please respond to malc_p Yup, we've got monitoring (hourly) looking at total shared memory allocated to informix, so I've put alarms on this so that we can have a look at the 'hot' times. I'm pretty convinced it's the JDBC connections, but the point I really want to clear up is whether there's any way of investigating the extra segments (e.g. with onstat -g stk, and knowing the address of the segment in memory) to find out what process (or owner) caused the engine to allocate it. Thanks Malc sending to informix-list