1826474 Members
3931 Online
109692 Solutions
New Discussion

%QMAN-W-LOWMEMORY

 
SOLVED
Go to solution
Volker Halle
Honored Contributor

Re: %QMAN-W-LOWMEMORY

Art,

you're NOT suffering from the bogus QMAN-I-LOWMEMORY problem addressed in those patches !

You seem to have a REAL virtual memory 'leak' in your QUEUE_MANAGER process.

The LOWMEMORY situation will be reported, if
PAGFILCNT (remaining pagefile quota) is less than 10% of PAGFILQUO (pagefile quota at start of process = same as for JOB_CONTROL).

The JIB data you've posted confirms this problem:

JIB$L_PGFLQUOTA 00009EB0
JIB$L_PGFLCNT 00000950

2384 < 10% of 40624

Based on the uptime of your system (328 days), this may be a slowly building memory leak, if we assume, that the QUEUE_MANAGER process had about the same uptime.

Maybe make a note in your calendar for 28-MAR-2011 to restart QUEUE_MANAGER, before you see this problem again...

Volker.
Volker Halle
Honored Contributor

Re: %QMAN-W-LOWMEMORY

Art,

QUEUE_MANAGER inherits it's pagefile quota from JOB_CONTROL. JOB_CONTROL is being started with a pagefile quota of 1/2 of the total available page file space in the system at the time JOB_CONTROL gets started (see SYS$STARTUP:VMS$CONFIG-050_JOBCTL.COM).

Your page files aren't 'large' enough to trigger the math overflow problem, so you must be experiencing a real LOWMEMORY problem.

Consider to watch PAGFILCNT of the QUEUE_MANAGER process over time. You'll start to get those %QMAN-W-LOWMEMORY messages, if remaining pagefile quota gets near 10% of the initial pagefile quota value for the QUEUE_MANAGER process.

Volker.