Kbase P125310: Errors 9971 and 9972 version 1 trying to start a database using 10.1A or previous version after migr
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/03/2008 |
|
Status: Unverified
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
OpenEdge 10.1A
OpenEdge 10.1B
SYMPTOM(s):
Errors 9971 and 9972 version 1 trying to start a database using 10.1A or previous version after migrating it to 10.1B
Errors 9971 and 9972 version 1 trying to open a database using 10.1A or previous version after migrating it to 10.1B
Invalid before image version number found in bi file . (9971)
This is a version 1 bi file. (9972)
This is a version <version-number> bi file. (9972)
Error 11727 and 11810 after truncating the bi using 10.1A or 10.0x
An invalid feature <num> has been encountered in the database's Enabled feature list. (11727)
An invalid feature 9 has been encountered in the database's Enabled feature list. (11727)
The list of enabled features in database <database> contains features that are not recognized by this codebase (11810)
CAUSE:
The error message 9971 happens because the database manager, while opening the database, checks for the version number of the bi file in the block header of the bi file.
In 10.1B, due to the implementation of the 64-bits DB-keys the bi file version must be changed. This change happens when you first open the database.
If then you try to open the database again on 10.1A or 10.0x, the errors 9971 and 9972 with bi version 7 will appear.
If you then truncate the bi using 10.1A or 10.0x then the error 11727 and 11810 will happen if you try to connect or open the database using 10.1A or 10.0x.
but also, if you try to use revert utility on 10.1B you will get errors 9971 and 9972 with bi version 1.
FIX:
Restore a backup of the database from the moment before the bi was truncated using 10.1A or 10.0x and always use revert utility in 10.1B before opening it using a previous version.
See solution P123167 on instructions on how to use revert utility.
If a backup of the database is not available, you may use as a workaround a truncate bi with -F option. Please, take in considaration that using -F option with truncate bi does reviewng the following information P24330, "Consequences of using the -F startup option"