Kbase P118396: Error (210) when adding data extents or records to a database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/01/2009 |
|
Status: Verified
SYMPTOM(s):
SYSTEM ERROR: Attempt to read block <number> which does not exist. (210)
Getting error 210 when adding extents to an area
Error (210) when adding data extents
prostrct add fails with error (210)
Client is getting 210 error when trying to update a record in the database.
SYSTEM ERROR: Attempt to read block 2147468288 which does not exist. (210)
FACT(s) (Environment):
8 KB database blocksize
Area is comprised of a single table.
Area has 256 records per block
Area is close to 64 GB
OpenEdge Category: Database
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
CAUSE:
Error: SYSTEM ERROR: Attempt to read block <number> which does not exist. (210)
Is associated with hitting the limit for the maximum area size. Correlating database blocksize, records-per-block and the current database size shows that the area to which space is being added or records being added has reached or will reach the maximum addressable size for a data area.
Example: 1KB blocksize and 256 records-per-block, the maximum area size is 8GB.
FIX:
To recover from this error, the database is going to have to be reorganized in one of the following ways:
1. It may be the case that you can archive data and delete records, and thus free up space in the tables in that area, but this will depend on your business requirements.
2. If you wish to keep records-per-block the same, then you can add new areas to the database and move tables into them. This would free up space in the area that is currently experiencing the problem. The tablemove utility can be used with the database online to move these tables into the new areas. Please note that there is a performance hit for doing this online.
3. Create a new database structure file for the database with new areas that have a different records-per-block settings for the existing tables. Then dump and load the database to make use of this new structure.
4. Create a new database structure with a lower number of records-per-block and then dump and load into this new database and locate tables to the new areas with the more appropriate records-per-block settings.