Kbase 17902: Finding Disk Space When BI File is Large - Crash Recovery
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/08/2003 |
|
Status: Technically Reviewed
GOAL:
Finding disk space when BI file is large - crash recovery.
FIX:
This Solution addresses how to recover when the bi file has taken up much of the available disk space and no room can be made by doing some house cleaning.
Normally, if the .bi file fills up all available disk space, room needs to be created by deleting unneeded files -- the bi file may grow to twice its size to go through crash recovery. If the bi file is already 1GB, then keep in mind also that there is a risk of bumping into the 2GB file size limitation during recovery.
NOTE: if attempting to go through crash recovery and there is not enough space to let the .bi file back out its incomplete transactions, (this can occupy up to twice the amount of space as the .bi file) bi file corruption is possible, at which point the only option is to go to backup. These are some possible ways to get around lack of diskspace. If there is space available on another file system, it may be possible to move the .bi file there and start up with the -g option, using the full pathname to the directory where you've put it.
If the database is single volume, physically move the .bi file to a place that is at least twice the size of the bi file. This will change the time/date stamp on the file, but Progress will be looking for this information in the header block of the database.
If the database is multi-volume, do the same thing as above, but before starting up, use PROSTRCT REPAIR to update the structure file to reflect the new location of the bi file. See the Progress System Administration Guide, page 7-32.
If the client is on the same file system as the .bi file and the temp files are very large, it may be possible to complete crash recovery by simply using the -T option to specify a full pathname to a temp file on a file system that has more space.