Kbase P149307: Getting error 9450 when truncating a bi file on Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/9/2009 |
|
Status: Unverified
SYMPTOM(s):
Getting error 9450 when truncating a bi file on Windows
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9450)
bkioWrite:Insufficient disk space during write, fd 1844, len 16384, offset 535384, file <pathname>/dbname.bX (x represents bi extent #)
The bi file in the 9450 error is a variable length bi extent.
Database had originally crashed when variable length bi extent filled up file system space where the extent resided.
FACT(s) (Environment):
File system where the bi file is located only contains the bi files and therefore there are not extra files that can be deleted to free up some space for additional bi growth.
Windows
OpenEdge 10.1B03 Service Pack
OpenEdge Category: Database
OpenEdge Database Category: Repair
CAUSE:
File system / disk where the variable length bi file resides is full. Therefore the truncation of the bi file cannot continue due to the utility needing to extend / grow the extent even further when going through the truncation process.
FIX:
Copy or Move the variable extent bi file to a disk that has additional space for growth.
Modify the path name for where the variable length bi extent now resides within the dbname.st file.
From the directory where the dbname.db and .st file are, issue the command: prostrct repair dbname
Then truncate the bi file to have the variable length bi file shrink back to it's original size. Command: proutil dbname -C truncate bi
Can then use the bigrow option to proutil to preformat bi clusters so you do not experience performance issues while bi file gets back to it's relative sweet spot. See solution: P2676, "Grow the before image file (.bi) with bigrow to improve performance" for additional information on bigrow.