Kbase P30870: How does changing the name of a storage area affect after-imaging
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/04/2008 |
|
Status: Verified
GOAL:
How does changing the name of a storage area affect after-imaging
GOAL:
Does rebuilding the dbname.db with the builddb utility affect roll forward on the hotspare database?
GOAL:
Can ai files roll forward after storage areas have been renamed?
FACT(s) (Environment):
Progress 9.1D
All Supported Operating Systems
All Supported Operating Systems
FIX:
When running the builddb utility, the dbname.db is rebuilt according to the information in the referenced dbname.st file, it is important that the ai extents are included in the dbname.st used to run the prostrct builddb utility.
Although the ai files will be recognized in the new_dbname.db (if included in the dbname.st used to run buildb), there is an issue with Progress 9.1D in that 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 prorest the backup taken after the builddb operation.
In order to initiate after-imaging on the live database:
- the 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.