Kbase P158553: Cannot start database due to errors 2329 and 612 on an after image file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/10/2010 |
|
Status: Verified
SYMPTOM(s):
Cannot start database without generating 2329 errors
SYSTEM ERROR: Invalid block <block> for file <filename.tl>, max is <max-block> (2329)
SYSTEM ERROR: Invalid block 0 for file db-name.an, max is <max-block> (2329)
(612) SYSTEM ERROR: Possible file truncation, 0 too big for database
All errors relate to an after image file (extent)
Power failure prior to error messages
Cannot truncate bi file: proutil dbname -C truncate bi
Cannot end after imaging: rfutil dbname -C aimage end
FACT(s) (Environment):
OpenEdge 10.2x
All Supported Operating Systems
CAUSE:
The after image file generating the error messages is corrupted.
FIX:
The following steps allowed the database to be restarted after the power outage:
1. Copy the database using an OS copy
2. Run prostrct list dbname <somenewname.st> and compare this new st file to the dbname.st file. (should be the same)
3. Create a copy of the current .st file.
4. Remove ai extent entries in the current database-name.st file and save it.
5. Rename the current .db file to old.db
6. Run prostrct builddb db-name
7. Move all of the after image files to another location
8. Run rfutil db-name -C aimage end
9. Create an addai.st file with the same number and structure of after image extents as originally found in the dbname.st file prior to any issue.
10. Run prostrct add db-name addai.st
11. Run prostrct list dbname to get the current structure information from the .db file to the dbname.st file
12. Run probkup
13. Start after imaging
14. start the database