Kbase P75589: 9971 when migrating from 9.1C to 9.1D - Use Single bi extent
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/10/2004 |
|
Status: Unverified
SYMPTOM(s):
Truncated the database with 9.1C and then started database with 9.1D.
Can successfully start the database first time after migrating to 9.1D
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.
Invalid before image version number found in bi file (9971)
This is a version <version-number> bi file. (9972)
Database has multiple bi extents.
CHANGE:
Migrating from 9.1C to 9.1D
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 bi extent, a version inconsistency is detected.
FIX:
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. Because the problem is associated with multiple bi files during the truncation, the problem will be avoided.
1. Truncate bi file in version 9.1C:
Command: proutil dbname -C truncate bi
2. Remove extra bi extent in version 9.1C:
Command: prostrct remove dbname bi
3. Ensure environment variables are pointing to your 9.1D installation and
proserve or access the database with a 9.1D utility.
To add second bi extent back to the database after migration to 9.1D:
4. Create a file called add.st. In this file, enter a line for where
you would like the second bi file added. Example:
b /tmp
5. Use prostrct add command to add extent back to the database.
Command: prostrct add dbname add.st