Kbase 34428: Manually set the local buffer size (-l) startup parameter to avoid error 5408
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Solution ID: P4428
SYMPTOM(s):
WARNING: -l exceeded. Automatically increasing from <old value> to <new value>. (5408)
CAUSE:
The (5408) message refers to the -l (local buffer size) startup parameter that administers how much memory Progress will use for the client's local buffer pool. It is merely indicating that this limit has been exceeded and Progress is automatically increasing the -l setting.
FIX:
To avoid seeing this error, start the Progress session with a larger -l setting.
The default is 200KB, hence messages will start from 200KB+.
The maximum settable value is 2097151K in Progress 8.x; 4GB in 9.x.
The -l parameter is dynamic; that is, Progress will automatically increase the value but will record that event in the log file every time it does so.
If adjusting -l does not eliminate the errors, check to see if some portion of the program being run is consuming large amounts of memory. In checking your application, consider that:
"-l (local buffer size) is used for variables, work files, and records that are in use at a particular moment in time by the user. 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) will therefore also affect the -l memory usage."