Kbase P123403: What to do when the bi hits 2 gig on version 9 or later and the OS file size limit is 2 gig?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/01/2009 |
|
Status: Verified
GOAL:
What to do when the bi hits 2 gig on version 9 or later and the OS file size limit is 2 gig?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
To handle the situation where the BI has grown to 2 gigabytes and hits the maximum OS file size.
1) Create an add.st file or any other temporary .st file.
2) Define at least double the current size of the BI broken down into whatever the operating system maximum file size is.
Normally when choosing extent sizes they must be multiples of 16 times the database blocksize.
3) Make sure there is also a variable BI extent defined in the .st file
4) Perform an operating system backup of the database (all files)
5) prostrct add <database name> <st file name>
Although there is functionality in version 9 to support large files, if the operating system and file system are not large file compliant, enabling the database for large files will not help.
If the operating system and file system can easily be converted to large file support then another simpler way to handle this situation would be to enable large file support for the database with the following command:
proutil <database name > -C enablelargefiles