Kbase P15186: Error 6091 and no additional space is available
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/2/2004 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
Error 6091 when restarting DB and no additional space is available
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (6091)
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file dbX_N.dM. (6091)
no way to add physical space where non fixed dbX_N.dM extent resides
CAUSE:
Crash recovery is expanding the non fixed dbX_N.dM extent.
The new option for V9 probkup, "norecover", will skip crash recovery for the backup. It is on restore ("prorest") that crash recovery will occur.
FIX:
1. Make a backup of the database as it is
probkup dbX <file/device-name> -norecover
2. Restore the backup where you have enough space. If a database area is larger than 2Gig and LargeFile is not enabled, then a dbX.st file for the structure of the database will be needed.
prorest dbX <file/device-name>