Kbase P75673: 9971 when migrating from 9.1C to 9.1D
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/02/2005 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.1C
Progress 9.1D
Progress 9.1D 64-bit
OpenEdge 10.0A
OpenEdge 10.0A 64-bit
SYMPTOM(s):
Cannot start a Progress 9.1D database via proserve, pro or any utilities
Successfully started the database the first time after migration with 9.1D proserve command.
Can shutdown the database in 9.1D without errors.
Subsequent attempts to access the database via proserve, pro or any utility errors with 9971 and 9972 errors.
Getting errors 9971 and 9972 when trying to start the database.
Invalid before image version number found in bi file (9971)
This is a version bi file. (9972)
Database has multiple BI extents.
CHANGE:
Migrating from 9.1C to 9.1D
CAUSE:
Bug# 20040224-041
CAUSE:
We perform a version number check for all extents. The truncation of the BI file using (proutil dbname -C truncate bi) formats the first BI block of the first BI extent only. Because we did not format the first BI block for each subsequent BI extent, a version inconsistency is detected.
FIX:
1. Upgrade to 9.1D09 or later.
2. Upgrade to 10.0A01 or later.
Workarounds:
3. Procopy the 9.1C database into an existing empty Progress 9.1D database.
a. In 9.1C truncate the BI file.
Command: proutil dbname -C truncate bi
b. In 9.1D, either create a new structure file, or use previous <dbname>.st file to create a new version 9.1D database. Make sure database name and
extents are not the same.
Command: prostrct create dbname1 dbname1.st
c. Use 9.1D procopy command to copy 9.1C database into 9.1D empty database that was created in step 2.
Command: procopy dbname dbname1
4. Prior to migrating to 9.1D, configure the database so that there is a single BI file instead of multiple BI files. This will allow the truncation to format the first BI block in the first BI extent and the problem with multiple BI extents will be avoided.
a. Truncate BI file in version 9.1C:
Command: proutil dbname -C truncate bi
b. Remove extra BI extent in version 9.1C:
Command: prostrct remove dbname bi
c. Ensure environment variables are pointing to your 9.1D installation and proserve or access the database with a 9.1D utility. This will result in a successfully migrated 9.1D database.
Once the database has been migrated to 9.1D, a second BI extent can then be added back to the database if the DBA (Database Administrator) chooses.