Kbase P22898: Do the after-image notes record the mkschema update of the S
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/17/2003 |
|
Status: Unverified
GOAL:
Do the after-image notes record the mkschema update of the SQL tables?
GOAL:
Are mkschema updates transferred to the hotspare through ai files?
GOAL:
When roll forward ai notes onto a hotspare database are schema changes recorded
GOAL:
When applying the mkschema to a converted 8-9 database after AI is enabled, if those ai files are used to roll forward into another database, would the new SQL tables be present in the new database?
FIX:
The conv89 utility runs mkschema as the final step in a conversion and failed to put SQL-92 definitions into the fully converted database in Progress 9.1D02
The mkschema executable, amongst other things, undertakes the following actions:
- place SQL92 definitions into the fully converted database
- make sure that all the V9 VST's are updated and inplace
- add CRC level checking at both the table and index level
When no SQL schema found in database after a conv89 database migration, the new mkschema exectuable, provided in Progress 9.1D03 corrects a problem with post conversion SQL access to the database.
If after-imaging (AI) has already been enabled on the database, the mkschema update will be recorded in the after-image notes so that when it is appied against the hotspare, the SQL schema will also be populated.
When undertaking such business critical operations, best practice is to have the hotspare better baselined by re-baselining in line with the live database.