View Incident Report

Serious

Reported By: Kevin Koehne
Reported On: 8/14/2019
For: Version 2.31 Build 7

# 4758 Global File I/O Buffering Can Cause Index Corruption During Repair Operations

When we try to restore a database, one of the tables is corrupt. In looking at the source database, the table is fine; but when it's restored it's so corrupt, any attempt at repairing it wipes out all of the data.

Comments and Workarounds

The data rows weren't gone, but the indexes were corrupted in a way that made them appear to be gone. The workaround is to run the repair with the global file I/O buffering turned off.

Resolution

Fixed Problem on 9/12/2019 in version 2.31 build 8

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