Kbase P12726: Database crashed with errors 9449 and 6072 in the log file.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
FACT(s) (Environment):
UNIX
Progress 9.1D
SYMPTOM(s):
Database crashed
Errors in the log file.
Progress executables have setuid root
Disk space is sufficient
<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)
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.
<bytes> in error 9449 is a positive number less than 2,147,483,648.
User <num> died with <num> buffers locked. (5027)
User <num> in error 5027 is the same user that caused errors 9449 and 6072.
User <num> died holding <num> shared memory locks. (5026)
User <num> in error 5026 is the same user that caused errors 9449 and 6072.
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:
For the short term, 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.
In the longer term, a better idea is to restructure the database so that all its extents are below the lowest ulimit of all users. For an idea on how to restructure your database, please see Solution P85237