How does changing the name of a storage area affect after-imaging?

How does changing the name of a Storage Area affect after-imaging?
Does rebuilding the dbname.db with the builddb utility affect roll forward on the hotspare database?
Can ai files roll forward after Storage Areas have been renamed?

This Article only refers to database enabled for After-Imaging. If the database is enabled for Replication, refer to Article:

• What effect does builddb have on a replication enabled database?   

When running the builddb utility, the dbname.db is rebuilt according to the information in the referenced dbname.st file. It is therefore imperative that the ai extents that already exist in the database structure are also included in the "dbname.st" used to run the prostrct builddb utility in order to not break after-imaging on the database. For further instruction, refer to Article

• How to change Storage Area names?  

If the ai files are missing in the structure file used, then the database will fail to startup as the ai files are no longer part of the structure but after-imaging is still enabled.

The only reliable way to recover from this situation is to:

• Disable after-imaging with 'rfutil -C aimage end'
• The existing ai files on disk will have to be backed up for reference for the pre Area-Name's change baseline,
• AI files re-added to the database structure with 'prostrct add'
• After-imaging re-initialised with 'rfutil -C aimage begin for the new hotspare baseline which then needs to be re-instated.

There is a specific issue in Progress 9.1D07 and prior in that although the ai files will be recognized in the new_dbname.db (when included in the dbname.st used to run buildb), the after-imaging and last-backed-up flags are reset in the master block (dbname.d1) by the builddb utility.  As a consequence, the next-sequence set for roll forward on the production database will be 1,where the next-sequence for roll forward on the hotspare will be whatever the last roll forward operation was prior to running builddb. As a result, the roll-forward recovery baseline will have to be re-set by a prorest of a backup taken after the builddb operation.

In order to initiate after-imaging on the live database:

• Existing ai notes will have to be archived for future prosperity.
• The database will need to be backed up, and
• The rfutil aimage begin qualifier will need to be run, to set the ai flag in the master block to re-instate after-imaging.

Otherwise apply Progress 9.1D08 Service Pack where this issue has been addressed.