Re: Dynamically adding shared memory segs

Bill Weaver schrieb: > > Today for some reason we've added 5 shared memory segments dynamically. It almost never happens > that we even have 1 added since I've worked to size our initial segment to avoid this. How can > I tell what is causing us to add so many all of a sudden? [snip] Run 'onstat -g ses' and have a look at the 'total memory' column. This may indicate who is using the additional memory. Remember, sessions don't free memory by themselves: So if there is a big difference between 'total memory' and 'used memory' you should think about running 'onmode -F' every x minutes/hours by cron. Another problem may be the use of stored-procedures. The context of a SP is stored in the memory-area of the executing session for reuse. If you have longrunning sessions which occasionally use big SP's, which aren't rerun several times, it may be usefull to set the environment-variable DBMAXPROC=1 in your client-environment. This limits each session to hold only one SP-context. As far as i know, the value 0 for DBMAXPROC does not work. hth martin