Kbase P6126: What to do if a lot of changes to the database need to be ma
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/21/2003 |
|
Status: Unverified
GOAL:
What to do if a lot of changes to the database need to be made and after imaging is enabled.
CAUSE:
If you are planning to make a massive change to data or the schema of the database you may want to temporarily disable after-imaging. It is possible due to the volume of data during some schema changes or batch update tasks that the currently defined number of after image files you have allocated for this database may fill too quickly for your AI copying scripts to keep up with the flow of data..
FIX:
1) shutdown the database
2) back up the database and all after image files
3) disable after imaging
rfutil <dbname> -C aimage end
4) make your changes to the database
5) backup your database
(NOTE if you do not use a progress database then you must mark the database as having been backed up by issuing the following command:
rfutil <dbname> -C mark backedup
6) rfutil <dbname> -C aimage begin