Kbase P4426: How to clear: Your database was damaged. Dump its data and reload it. (37)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/16/2008 |
|
Status: Verified
GOAL:
How to clear: Your database was damaged. Dump its data and reload it. (37)
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
** Your database was damaged. Dump its data and reload it. (37)
CAUSE:
You WILL continue to get the:
"** Your database was damaged. Dump its data and reload it. (37)"
every time the database is accessed single-user or started multi-user after forcing into the database with "proutil db-name -C truncate bi -F" to recover from when the 2GB limit was reached on .bi for example.
Forcing into the database skips crash recovery and because there may well be data inconsistencies, the database is marked as damaged. Please refer to Progress Solution P24330 for further details on the consequences of using -F.
FIX:
You must dump and load your database at the next convenient time to clear the damaged flag. Running idxbuild will also clear the damaged flag if it suceeds.