Kbase P165889: Cannot go through crash recovery because not enough file system space to grow the bi file.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/05/2010 |
|
Status: Unverified
SYMPTOM(s):
Cannot extend the bi file because the file system has no space.
Cannot go through crash recovery because not enough file system space to grow the bi file.
FACT(s) (Environment):
Bi file has reached 20 GB
Variable length bi file.
All Supported Operating Systems
OpenEdge 10.1C
CAUSE:
File system does not have enough space to allow for the bi file to grow.
FIX:
A. You can add a new extent on a different file system that your database can use for growth associated with the database crash recovery:
1. Create an add.st file that contains a new extent on a different file system where there is space for bi growth.
2. Then issue the command: prostrct add dbname add.st (This command will result in having a new bi extent added to the other file system where there is room for growth. The original variable length bi file will become fixed at its current size.)
3. Now you can either start your database or truncate your bi file.
If interested in reorganization of your bi files (after completing the above steps), please see solution:
P125375, "How to go from having a variable before-image extent to having a fixed and variable length bi extent?"
OR
B. If largefiles are enabled, simply move the bi file to another file system that has space.
1. Then issue the command prostrct list to get latest copy of the structure file. Command: prostrct list dbname (this will update the dbname.st file)
2. Then update the structure file to point to the new location where the bi file resides.
3. Then prostrct repair to update the db with the new bi location information. Command: prostrct repair dbname dbname.st file
4. If you want to get the variable bi file back to something more manageable truncate the bi file. Command: proutil dbname -C truncate bi
If at this point you want to get the newly truncated bi file back to its original location, then go through steps 2 and 3 above.
Once the bi file is back where you want it to be, then start the database and we will initialize and start growing within the original 4 clusters.