Kbase 42726: Database crashed with errors 9449 and 6072 in the log file.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Solution ID: P12726
FACT(s) (Environment):
UNIX
SYMPTOM(s):
Database crashed
Errors in the log file:
<function>:Maximum file size exceeded during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9449)
bkioWrite:Maximum file size exceeded during write, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9449)
<bytes> in error 9449 is a positive number less than 2,147,483,648.
SYSTEM ERROR: error writing, file = <file-name>, ret = <return-value> (6072)
SYSTEM ERROR: error writing, file = <file-name>, ret = -1 (6072)
<file-name> in error 9449 and <file-name> in error 6072 are the same.
User <num> died with <num> buffers locked. (5027)
User <num> in error 5027 is the same user that caused errors 9449 and 6072.
Begin ABNORMAL shutdown code (2249)
CAUSE:
The ulimit for the user who triggered error 9449 is too low.
Ulimit limits the file size for writing to a file but it does not pose any restrictions for reading from a file.
As consequence, it's quite possible that a user connects in multi-user mode to a database where the extents are bigger than their own ulimit; the user can also read data from that database.
However, when it comes to writing data the ulimit kicks in and error 9449 is generated.
FIX:
Increase the ulimit for the user who triggered error 9449 so that they can write to any of the database files.
How you increase the ulimit depends on your UNIX implementation, so please refer to your UNIX Administration manuals for further details.