Kbase P7529: Prosrct add used to enable multi volume after-imaging: errors 756 752
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/01/2005 |
|
Status: Verified
FACT(s) (Environment):
Progress 8.2C
SYMPTOM(s):
Prosrct add used to add more ai extents
Errors on startup of database
Invalid after image version number found in ai file header (752)
This is not a Progress ai file (756)
ai areas below area number 256
CAUSE:
To date, this issue has only been found to occur in the Progress 8.2C product. The exact cause is unknown.
FIX:
To work around this issue, turn off ai before adding new extents as follows:
1.) Disable after-imaging:
$ rfutil dbname -C aimage end -G 0
2.) Truncate the bi:
$ proutil dbname -C trunc bi -G 0
3.) Remove existing ai extents, the following cmd will remove these sequentailly from dbname.an .. dbname.a1
$ prostrct remove dbname ai
4.) Re-add the ai extents needed, where "dbname.st" describes the structure of the ai files needed:
$ prostrct add dbname dbname.st
5.) Backup the database to create the baseline for recovery database to roll forward ai files created from now on:
$ probkup dbname <dir>/dbname.bak
6.) Start after-imaging:
rfutil dbname -C aimage begin -G 0
7.) Start the database and cron jobs for archiving and switching ai files.