Kbase P122921: Type II database storage areas grow very large after loading schema definitions
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/4/2009 |
|
Status: Verified
SYMPTOM(s):
Database structure containing type II storage areas grows very large after loading schema definitions
FACT(s) (Environment):
512 blocks per cluster and 8kb database blocksize used
Database areas are defined as variable
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
Each schema object will allocate it's own cluster of database blocks, as defined in the database structure file that was used when creating the structure.
Tables and indexes are examples of schema objects. So if you have a table that contains 5 indexes, then that counts as 6 objects (1 table, 5 indexes).
So as a minimum for such a table:
6 objects (and therefore clusters) * 512 blocks per cluster = 3072 database blocks.
3072 blocks * 8kb blocksize = 24mb of allocated database space.
You can see that if this table only had a few records, it may not make sense to place this table's objects into a structure that allocates 512 blocks to each object, unless of course you expect it to grow.
FIX:
Allocate schema objects to database areas that have appropriate sized clusters. The size of the table & indexes, and also the average record size of each table should be considered when defining the database structure.
For assistance please review the referenced solutions.