PROSTRCT builddb fails after conv1011 with errors 44 6070

PROSTRCT builddb fails after conv1011 with errors 44 6070
Re-creating the Control Area (.db) fails with errors 44 6070

Database converted from 10 to 11 using conv1011 without error
After conversion, database files were moved to new directories
The Control Area (.db file) was deleted and regenerated with BUILDDB to reflect current directories and update the Control Area

 

PROUTIL -C conv1011 does not update the dbVersion number for all extent blocks for all areas. Instead, conv1011 updates the version for only the Master Block in the .d1 extent and the Control Area (.db) extent block.

This only impacts builddb. 

When PROSTRCT builddb runs, it recreates the .db file using information from the .st file and the dbVersion in the .d1 extent block.
However the .d1 extent block is not updated by conv1011 from the old version number leading to these errors. 

Upgrade to OpenEdge 11.6.0 or later where PROSTRCT builddb reads the version number out of the master block which was always updated correctly from conv1011, instead of the old dbversion in the .d1 extent block. .

Instead of using PROSTRCT BUILDDB to update the Control Area after moving database extents to different directories,
Use PROSTRCT REPAIR instead:
 
Whenever using the PROSTRCT utility to update the Database Control Area structure:

1. Always ensure that fully qualified paths to every database extent are used, don't rely on relative paths
2. Explicitly refer to the the structure file, don't rely on the default dbname.st

 

Progress Article:   

What is the difference between PROSTRCT REPAIR and BUILDDB?