Kbase P105382: Error (210) with block number approximately 2147472480.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
SYMPTOM(s):
Error (210) with block number approximately 2147472480.
Error (210) is shown in database log.
SYSTEM ERROR: Attempt to read block 2147472480 which does not exist. (210)
One of the areas is approximately 64GB with a blocksize of 8k and a records per block setting of 256.
CAUSE:
One of your areas has hit the maximum area size, and that has subsequently corrupted your database.
FIX:
You need to create a new larger database structure and re-arrange your tables into new areas so that no area will hit the maximum area size.
It may be possible to move a small subset of data initially to a new area by the following process:
1) Dump a data definition for the table(s) or indices in question.
2) Create a new add.st wherein an area with a lower value for the records per block is defined to hold the tables / indices from the area which has hit the limit.
3) Use prostrct add to add the new area to the database.
4) Modify the .df file and redefine the area names which relate to the old area.
5) Dump whatever is considered the current set of working data from the table in the old area. (proutil -C dumpspecified may be a good tool for this purpose)
6) Purge this set of data after it is dumped.
7) Rename the table(s) and indices or move them to the new area (this may take too long for all the data).
8) Load the .df made in step 1 which was modified to refer to the new area with the smaller records per block.
9) Load the subset of data dumped in step 5.
Over time the remaining data from the old, renamed table may be migrated programmatically online or offline to the new table in the new area.