View Incident Report

Serious

Reported By: Tom Martin
Reported On: 2/18/2007
For: Version 1.00 Build 1

# 2232 Unique Key Constraints Causing Index Corruption on Index Used for Constraint

I get the #601 error when I try to filter on a column that has a unique constraint. When I remove the constraint or create a regular index all is fine and no error occurs. As soon as I put a unique constraint on the column and try and filter by the same column, the #601 error reappears.

This seems to happen paticularly when I access tables created via the "Migrate Database from DBISAM." I did not seem to get this error when ceating new tables directly in EDB. Repair table does not fix the corrupt index.

Comments

The issue was that indexes used for unique keys performed extra index navigation during constraint checks, and this extra navigation was causing an index page buffer to get double-pinned in the buffer manager. The result was that the index was corrupted. If you have any unique keys defined on any table created with version 1.00 Build 1, you will need to repair them after installing 1.01 Build 1 or later in order to fix this issue.

Resolution

Fixed Problem on 2/20/2007 in version 1.01 build 1

Products Affected

ElevateDB Additional Software and Utilities
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