Kbase P4211: What happens to the variable-length extent of a database when prostrct add is performed?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
What happens to the variable-length extent of a database when prostrct add is performed?
FIX:
The rules applying to adding extent(s) to your database depends on which type of extents we are referring.
- There can be only one variable extent defined per Area, with the exception of After-Image extents (.ai) where by definition, more than one ai extent may be a variable extent.
- If the database has not grown into the variable-length bi extent, then the prostrct add operation will fail with error 8825. The given extent will first need to be removed with the "prostrct remove" utilitiy before adding a new extent.
"You must remove the variable length BI extent before adding additional BI extent(s). (8225)"
- Running the "prostrct add" utlity against a database that has grown into its variable-length extent, whether adding new fixed and/or a new variable extent, will cause the existing variable-length extent to be marked as a "fixed extent" before the new extent is added. (Please refer to Progress Solution 18874 below for a more detailed description) The file's current size will be rounded up to a multiple of: ( 16 * db_blocksize )
Please note, on systems where largefiles have not been enabled, with the "multiple of 16 x database blocksize" alogrithm restricts the absolute size of 2GB extents as per the table below:
Database blocksize "2 GB" defined in .st file (KB)
1 2,097,136
2 2,097,120
4 2,097,088
8 2,097,024