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.

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 is quite possible that a user may connect in multi-user mode to a database where
the extents are bigger than the users's own ulimit value for file size.
The ulimit value for the user permits them full ability to read data from that database extent, however, when it comes to writing data the ulimit limit for file size takes effect and error 9449 is generated.