View Incident Report

Serious

Reported By: Kai Peters
Reported On: 6/8/2009
For: Version 4.28 Build 1

# 3005 Altering a Table and Adding Two Unique Indexes Can Cause Index Corruption If Duplicate Keys Exist

I just caught an 8965 in the current DBIsam manager 4.28 Build 1:

After restructuring (adding a few indices) the table n question, DBIsam rightfully piped up about key violations and asked whether I wanted to continue.

After I confirmed, I received said error (which was easily repaired afterwards)

I had a few records in table with identical phone # - I then added a unique index on phone number.

Comments

The circumstances were:

1) Two unique indexes must be added during the alter, or at least one unique index and then one non-unique index (in that order).

2) The record that causes the duplicate key for the first unique index must also include a value that is present in another record for the second index.

Resolution

Fixed Problem on 6/8/2009 in version 4.28 build 2

Products Affected

DBISAM Additional Software and Utilities
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard
DBISAM ODBC Standard with Source
DBISAM ODBC Trial
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap