View Incident Report

Serious

Reported By: Ralf Mimoun
Reported On: 11/23/2011
For: Version 4.31 Build 2

# 3518 Deleting an Index When the Number of Indexes is at the Maximum Number Can Cause Header Corruption

I am preparing an update of one of my software projects. I have to drop an index of one of the tables because I am running out of index counts - 31 indexes max.

After you run the following SQL against the table, you get an error #8961, header information corrupt, when you open the table.

DROP INDEX IF EXISTS "Artikel"."NegativerBestandErlaubtIndex";

Resolution

Fixed Problem on 12/14/2011 in version 4.31 build 3

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