Kbase P34794: Why the DB record occupation amount could be different form one system to another?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/05/2010 |
|
Status: Unverified
GOAL:
Why the DB record occupation amount could be different form one system to another?
GOAL:
Why the amount of extents used could be different from one system to another?
CHANGE:
If you create a new Database structure based in your current DB .st file, adding a new variable extent. Dump the data from the old DB and loading in the new DB the old data. You may notice that after a huge activity (creation of records) into the DB, your last variable extent will not have data.
FIX:
This is the normal behavior.
Since your New DB after the Load of Data will only unfracmented, possibly less unscatered records (depending on the blocksize of the new DB), you may experience that after a huge creation of records, that the last variable extent you added will remain free for a period of time.
This is the purpose of a variable extent, to fill only if the fixed extents are full.
This is only true if the blocksize of the old and new DB have the same size and within the same OS Platform, since different platforms can have different block sizes.