Kbase P104719: Error 210 when starting or connecting to newly created database
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  19/03/2008 |
|
Status: Unverified
FACT(s) (Environment):
Windows 2000
OpenEdge 10.0B
SYMPTOM(s):
Error 210 when starting or connecting to newly created database
Newly created database cannot be accessed, returns error 210
SYSTEM ERROR: Attempt to read block 0 which does not exist. (210)
(2356) when creating database
Open failed, Database test requires rebuild of all indexes. (2356)
Errors 8405, 8404, 8406 appear before 210
Client/database minor version mismatch. Expected <version>. Found <version>. (8405)
WARNING: updates to this database are not recommended. (8404)
Database minor version mismatch. Expected <version>. Found <version>. (8406)
CAUSE:
The st file with which the database was created contained a definition of blocks per cluster for the schema area.
This is incorrect - blocks per cluster should not be defined for the schema area.
In OE10 docs OpenEdge Data Management: Database Administration (Dec 2003), p.1-5, Table 1-1 contains a definition of the blocks per cluster token. There is the following note -
Note: The blocks per cluster token applies only to data areas.
The OpenEdge Data Management: Database Design (Dec 2003), p.1-5, notes that -
In Release 10 of OpenEdge, existing storage areas use ASA I architecture, as do schema.
In the ASA I architecture, data is maintained at the block level, and not at the cluster level as in ASA II. The schema area, since it uses ASA I, cannot make use of blocks per cluster.
FIX:
1. Correct the st file - do not define blocks per cluster for the Schema Area. The Schema Area cannot be a Type II storage area (ASA II)
For example:
d "Schema Area":6,32;1 .
not:
d "Schema Area":6,32;8 .
2. Recreate the database using the corrected st file.