Icon View Incident Report

Serious Serious
Reported By: Andrew Vaz
Reported On: 4/1/2003
For: Version 3.24 Build 1
# 1385 Repairing Tables with Modified Buffering Parameters Causes Index Corruption

When attempting to repair tables, if your in local mode and if the session buffer parameters are altered:

MaxTableDataBufferSize:=(MaxTableDataBufferSize*2);
MaxTableDataBufferCount:=(MaxTableDataBufferCount*2);
MaxTableIndexBufferSize:=(MaxTableIndexBufferSize*2);
MaxTableBlobBufferSize:=(MaxTableBlobBufferSize*2);
MaxTableBlobBufferCount:=(MaxTableBlobBufferCount*2);

the table goes out with a big bang if "force index rebuild" is used. The indexes get heavily corrupted. I don't know if this is normal, but I have some small apps that are for peer2peer only and I'm using the parameters above to make the thing faster, but when the user had a problem and had to use the repair option of my app, everything went bezerk.


Resolution Resolution
Fixed Problem on 4/3/2003 in version 3.25 build 1
Image