Kbase P105361: Can after-image files be rolled forward against a hotspare database of a different minor version?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/22/2008 |
|
Status: Verified
GOAL:
Can after-image files be rolled forward against a hotspare database of a different minor version?
GOAL:
Can a 9.1E AI file be applied to a 9.1D Standby database?
GOAL:
Can Progress 9.1E after-image files be rolled forward against the Progress 9.1D hotspare database?
FACT(s) (Environment):
All Supported Operating Systems
FIX:
In principle, if this were just a matter of serving the production database on the same machine under 9.1E instead of 9.1D (having truncated using 9.1D and ensuring that we're starting with a new ai file),
there would be no issue in roll forward the ai files created under the 9.1E against the 9.1D hotspare database using either a 9.1D or a 9.1E rfutil -C roll forward client session (it's a single user connection).
For example; when the production database is proserved under a 9.1E session:
9.1C rfutil session will fail with error (1178)
9.1E rfutil session will be okay
when the database is not running (in otherwords, no shared memory involved):
9.1C rfutil session will work
9.1E rfutil session will work
because the rfutil session is being run as a single-user connection.
So in the case of "rfutil -C roll forward" you will be able to roll forward the ai notes created under the 9.1E session against the existing hotspare database.
NOTE: all of the above assumes that between versions there has been
- no platform change
- no restoring of the production database into the 9.1E environment, this voids the replication baseline
- the major version is the same