Kbase P25874: How to recover from errors 2329 and 612 after 2 Gig limit violation?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/02/2010 |
|
Status: Unverified
SYMPTOM(s):
Truncate bi fails
Starting the database fails with errors 2329,612
SYSTEM ERROR: Invalid block <block> for file <file-name>, max is <max-block> (2329)
SYSTEM ERROR: Possible file truncation, <block-offset> too big for database. (612)
** Any incomplete transactions are being backed out. (459)
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
CHANGE:
Prostrct repair set back the size of the data extent that exceeded 2 Gig before.
CAUSE:
There might be data/index corruption due to 2 Gig limit violation on the data extent.
FIX:
1.Force into db with 'proutil db-name -C truncate bi -F' and dump/reload as much data as possible (+ index rebuild). This has the potential for
data inconsistencies.
2.Restore from backup.