Kbase P113948: What to do if you reach the database area size limit.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/30/2009 |
|
Status: Verified
GOAL:
What to do if you reach the database area size limit.
GOAL:
How to handle if you reach the database area size limit.
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
If more than one table exists in the area which is approaching or has reached the maximum size possible for an area:
1) Migrate many smaller tables from the area to another area which has more space or has a lower setting for records per block.
2) Move a single table of significant size to another area which has more space or has a lower setting for records per block.The above steps will slow down the growth of the area approaching the limits but there may still be some growth of any data which exists in the area. This growth can be due to updates to existing records. Updates to records which can not fit within the existing block the record lives in may attempt to allocate a new block if no other blocks with space exist. Any creation of new records can under some circumstances (usually due to the size of the new records) try to allocate new blocks for the creation of the new records. If the size of the new record is greater than the space in the existing blocks the database engine may allocate a new block for the new record rather than fragment the record.
There are several methods to migrate the data.
1) Perform a tablemove of the data from areaX to areaY.
2) Perform a dump of data, a delete of the data, and a load of data to a new area.
3)
a) Create a new area with a smaller records per block.
b) Create a new table in the new area with a different name.
c) Programmatically copy records from the old table to the new table.
d) Remove the records from the old table.
If the version of the product is 10.0A or later , create a Type II storage area to house the table(s).