IDS Forum

Re: Memory constraints for Workgroup edition

Posted By: Art Kagel
Date: Tuesday, 21 February 2012, at 12:53 p.m.

In Response To: RE: Memory constraints for Workgroup edition (LARRY SORENSEN)

First, there is no "workgroup edition" for 11.50. Likely you have Growth
Edition. Limits are 16 CPUs and 16GB of memory. Specific answers below:

Art

Art S. Kagel
Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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, Feb 21, 2012 at 12:15 PM, LARRY SORENSEN <lsorensen25@msn.com>wrote:

> I am running IDS 11.50.FC5 on a Solaris 64-bit server. I am starting to
> receive memory errors/warnings when running certain reports and backups.
>
> Question 1
>
> We have two different instances running on the same server. Do the memory
> constraints placed on the Workgroup edition apply per instance, or does it
> add
> up the memory from both instances together?
>

There are three different issues here. The licensing issue is that you
cannot have more than 16 GB of shared memory in use total for all Growth
Edition instances on the licensed machine taken together. The second issue
is practical. To my knowledge the engines do not monitor they memory usage
of other instances, only its own. Third is error messages. Those messages
would be specific to the single instance issuing them. What error messages
are you seeing?

>
> Question 2
>
> What are some good methods for monitoring the memory usage and for setting
> up
> the instance to operate within the memory constraints of Workgroup
> editions so
> that memory allocation errors do not occur?
>

Monitoring memory usage can be as simple as running "onstat - "
periodically, say from a cron, and checking the total memory usage reported
at the end of the header line. Or you could query sysmaster:syssegments:

> select (sum(seg_size)/(1024))::INT||" Kbytes" from syssegments;

(expression)

508080 Kbytes

1 row(s) retrieved.

>

IB that OAT has a report of the memory usage as well.

As to restricting memory, be sure to configure SHMVIRTSIZE, SHMTOTAL and
the BUFFERPOOL settings so that the total shared memory used by all
instances does not exceed 16GB. Only the virtual segment will grow.
SHMVIRTSIZE sets the initial size and SHMTOTAL will limit the growth for an
instance (of set to a positive value).

> Thanks.
>
> Larry
>
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>

--e89a8f22c68138df7b04b97d1725

Messages In This Thread

• RE: Memory constraints for Workgroup edition
  LARRY SORENSEN -- Tuesday, 21 February 2012, at 12:15 p.m.
  • Re: Memory constraints for Workgroup edition
    Art Kagel -- Tuesday, 21 February 2012, at 12:53 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.