Kbase P59946: Error (132) in database log, scan shows Bad Frag errors with Err:4, no Bad Blocks found.
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  23/02/2010 |
|
Status: Verified
SYMPTOM(s):
Error (132) in database log, scan shows Bad Frag errors with Err:4, no Bad Blocks found.
SYSTEM ERROR: Record continuation not found, fragment recid <recid>. (137)
Errors occur in the database log file after a certain amount of time. No other errors.
Many Bad Frag errors in the dbrpr scan output all with Err:4. No bad blocks found.
** Bad Frag 130475234 for rec 182161600 Err:4
FACT(s) (Environment):
Hardware checks out to be fine.
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
The exact cause is unknown at the time of this writing.
Err:4 means that the target fragment was not correct/found.
FIX:
Workaround:
Delete the bad records using dbrpr, option 5 under the Scan menu.
Rebuild the database indexes.