Icon View Incident Report

Serious Serious
Reported By: Terry Swiers
Reported On: 9/21/2011
For: Version 2.05 Build 11
# 3507 REPAIR TABLE Not Handling Fatal Errors During Index Repair Properly

I have a database (catalog with single table) that is giving me some problems. This database started throwing 601 errors yesterday indicating that there are duplicate keys in the altcode index on the code table. Since the altcode index is not a unique index, I wouldn't expect this error to be displayed.

Attempting to run a repair on the table does show that there are some problems with the code table, including a recursive next index page error. At the end of the repair, it throws a AV, and leaves the table in the same state that it was before the repair.

Comments Comments
Normally, the type of error would have to be an AV or range check error due to corruption.

Resolution Resolution
Fixed Problem on 10/14/2011 in version 2.06 build 1

Products Affected 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