Kbase P86803: Shared memory batch client fails with stget and memory errors
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/1/2004 |
|
Status: Unverified
FACT(s) (Environment):
AIX 4.3.3
FACT(s) (Environment):
Progress 9.1C
SYMPTOM(s):
Shared memory batch client fails with stget and memory errors
** stget: out of storage. (6498)
** stget: out of storage. (1450)
SYSTEM ERROR: Memory violation. (49)
Memory errors always preceded by 5408 messages
WARNING: -l exceeded. Automatically increasing from <old value> to <new value>. (5408)
CAUSE:
The -l startup parameter governs how much memory Progress will use for the client local buffer pool. You have exceeded this limit and Progress automatically increases the -l setting. You may have to start Progress up with a larger -l setting or you may have an application bug that is consuming large amounts of memory. Note that Progress workfiles (not temp-tables) are entirely stored in -l memory. All other program variable records and database/temp-table records take space in -l only when the record is in an active 4GL buffer. Any record cache (used with a query) also affects the -l memory usage.
Trying to allocate memory dynamically for -l resulted in the memory errors.
FIX:
In the startup parameters for the batch client set a value for -l.
Ensure that this value is higher than the <new value> reported in the last 5408 message.