View Incident Report

Minor

Reported By: Brian Clingan
Reported On: 2/13/2017
For: Version 2.24 Build 3

# 4492 REPAIR TABLE Statement Not Fixing Cross-Linked Index Corruption

A customer is trying to repair a table, but the repair keeps detecting/repairing the same index corruption. The repair log message is:

Invalid recursive index page 237574 key page pointer (335381)

Deleting the .edbidx file and then executing the REPAIR TABLE statement fixes the issue permanently.

Comments and Workarounds

There was corruption in the indexes whereby one index was cross-linked to another index, and ElevateDB's verification/repair functionality didn't cover this condition adequately. That was why deleting the .edbidx file fixed the issue.

Resolution

Fixed Problem on 2/14/2017 in version 2.25 build 1

Products Affected

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap