Kbase P61980: Truncation of Database Fails. _proutil.exe has encountered a problem and needs to close.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/23/2004 |
|
Status: Unverified
FACT(s) (Environment):
Windows 32 Intel
SYMPTOM(s):
Cannot connect to database.
Truncate of BI File fails.
_proutil.exe has encountered a problem and needs to close
Log file Contains Garbage characters
Log File shows the proutil command being executed and nothing after it
<proutil> session begin for <user> on <ttyxxx>. (451)
CAUSE:
Corruption in the before image file
FIX:
Restore the database from backup and roll forward the after image files (if after imaging is being used).
If for some reason this is not a feasible resolution (i.e. the backup quality is suspect), the before image file can be force truncated. This action can cause logical corruption in the database and requires that the database be dumped and loaded afterwards. Database access is allowed after the truncate.
The syntax to force truncating your before image file is:
proutil dbname -C truncate -F
The following messages will then appear:
** The FORCE option was given, database recovery will be skipped. (33)
After-imaging disabled by the FORCE parameter. (4790)
** Your database was damaged. Dump its data and reload it. (37)
Error 37 will appear until the repair of the database is completed. It is recommended that the database be dumped and loaded as soon as possible after forcing in.