Kbase P20103: Getting around SYSTEM ERROR: rlrdnxt: note prefix and suffix lengths don't match
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/09/2008 |
|
Status: Verified
SYMPTOM(s):
rlrdnxt: note prefix and suffix lengths don't match <prefix length> <suffix length> (9383)
rlrdnxt: note prefix and suffix lengths don't match (5112)
rlrdnxt: note prefix and suffix lengths don't match . (7167)
FACT(s) (Environment):
All Supported Operating Systems
Progress 6.x
Progress 7.x
Progress 8.x
Progress 9.x
OpenEdge 10.x
CAUSE:
This is a non-recoverable corruption error of the notes in the before image file. These notes are kept in order with transaction numbers and keep track of all changes to your database. The before image file is used at database startup and during crash recovery to reconcile any changes to the database. This is a necessary file to ensure the integrity of your data.
Corruption to the before-image file may be caused by user error, hardware errors or errors at the operating system level. Please try to find and address these problems or they will reoccur
FIX:
When going to backup and rolling forward is not a feasible resolution (i.e. your backup quality is suspect), you can force truncate the before image file. This action may cause logical corruption in your database and your database must be repaired (dump and load of database is the recommended repair tool), but it will allow access to the database 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 you repair your database as soon as possible after forcing in by dumping and loading.