Kbase 19138: What to check when code generates error 303?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/06/2009 |
|
Status: Verified
GOAL:
What to check when code generates error 303?
GOAL:
How manage error 303 when files are invisible
GOAL:
What to check when code generates error "** UNIX maximum file size exceeded. <program>. (303)" ?
FACT(s) (Environment):
OpenEdge Category: Language (4GL/ABL)
Progress/OpenEdge Product Family
UNIX
FIX:
Error 303 occurs when a file being created by Progress is exceeding the maximum file size limit for the user.
Option #1
A sample ulimit -a produces the following result:
$ulimit -a
time(seconds) unlimited
file(blocks) 2097151
data(kbytes) 131072
stack(kbytes) 32768
memory(kbytes) 32768
coredump(blocks) 2097151
nofiles(descriptors) 2000
In the example above, 'blocks' are 512-byte blocks.
If the file being created is greater than the maximum size allowed by 'file(blocks)', this is the problem. In the example above, the maximum size allowed is 2097151 * 512 bytes, which is slightly less than 1Gb.
Option #2
Sometimes the problem is unclear because it is produced by very large transactions (in a batch, for example) and files greater than 2 GB are not found.
Start the session with the Save Temp Files (-t) startup parameter.
Check the files with the extensions .srt, .bi, .dbi, .pge, and .trp.
These temporary files are normally invisible but the Save Temp Files (-t) startup parameter will make the temporary files visible during a session.