Kbase P121920: Prostrct repair fails on database copied from split mirror of production database.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/09/2009 |
|
Status: Verified
SYMPTOM(s):
Prostrct repair fails on database copied from split mirror of production database.
Database Repair: attempt to update non-existent extent. Area: 7 Extent: 1
Database is down when copied.
Disabled after-imaging
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.0x
OpenEdge 10.1A
OpenEdge 10.1B
CHANGE:
Added new areas to the production database during dump and load process. Moved tables and indexes to new areas before loading the data and then removed the old areas. All done with after imaging added to this database but not necessarily enabled.
CAUSE:
Bug# OE00161163
FIX:
Upgrade to 10.1C. If if is not possible to do so at this time use the work around given below.
Work around used to resolve this issue:
After moving desired tables, truncating the old areas and then removing the old empty areas:
1. Shut down database
proshut dbname -by
2. Refresh structure file to reflect the changes
prostrct list dbname
3. Truncate bi
proutil dbname -C truncate bi
4. Disable AI
rfutil dbname -C aimage end
5. cp -p <dbname>.db file to backup name
6. Delete current .db file
7. Build new .db file
prostrct builddb dbname
8. Backup database
probkup dbname dbname.bak
9. Enable AI
rfutil dbname -C aimage begin
10. Start database
proserve dbname -S <port> -H <hostname>
11. When a database is copied from the split mirror of the production database at this point, edit the st file of the copy to reflect the new locations and run prostrct repair
Secondary work around:
Remove the after image areas
*** when running the builddb and prostrct repair make sure you are using the refreshed .st file wiht the most recent changes.