Kbase P1908: Database shutdown with error 6091 with 'offset 2147475456'
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
FACT(s) (Environment):
UNIX
Progress 8.x
Progress 9.0x
Progress 9.1A
Progress 9.1B
SYMPTOM(s):
Database abnormal shutdown.
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (6091)
bkioWrite:Insufficient disk space during write, fd <file descriptor>, len 16384, offset 2147475456, file <file-name>. (6091)
bkxtn: write error, file <file-name> errno: 0. (3646)
SYSTEM ERROR: Unable to extend the database. (111)
<file-name> is a variable-length data extent and is the same for all errors above.
File specified by <file-name> is below 2,147,483,648 bytes.
Database crashes, but can be restarted with no problem.
CAUSE:
Progress tried to extend the variable-length extent beyond the limit supported by the operating system, which is slightly below 2GB.
Because the Operating System did not allow Progress to expand the extent to exactly 2GB, the database can be recovered.
Had the extent mentioned by <file-name> actually reached 2,147,483,648 bytes, the database would have been unrecoverable.
FIX:
Given that one of the extents has grown so near the 2GB limit, the best plan of action is to stop the database immediately, and restructure it to a multi-volume database where each extent is well below 2GB.
The easiest way to achieve that is to backup the database using probkup, then create a brand new void database using prostrct create and prorest into the new void database. Please see documentation for further details.