View Incident Report

Serious

Reported By: Greg Hallam
Reported On: 7/18/2018
For: Version 2.28 Build 4

# 4672 VERIFY TABLE/REPAIR TABLE Statements Not Detecting Leaf Index Page Row Corruption

I have noticed some corruption in one of our tables. If I search for 21725168 in the search column OrdNo, it will be successful. If I set the order in browsing to 'OrderNo', I can see the record twice and with the same ID. Changing one record changes the other. What is worse is that VERIFY and REPAIR don't find the problem or fix it.

Comments and Workarounds

The verify/repair functionality was not verifying that there weren't duplicate physical row #'s in the leaf pages for indexes, which it now does. The workaround was to use the OPTIMIZE TABLE statement to rebuild the indexes.

Resolution

Fixed Problem on 7/19/2018 in version 2.28 build 5

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