Tim

DBISAM 4.24 Build 1

I have a corrupted table. After repairing it, DBSYS says "TABLE... was successfully repaired". Then, if I try to open the table, DBSYS just closes with
no error message. Why repair doesn't fix the problem? Can you help me, please? I can send you the table if you want. Thanks,

Mauricio Campana Nonino
Nonino Software

Mauricio

<<
I have a corrupted table. After repairing it, DBSYS says "TABLE... was
successfully repaired". Then, if I try to open the table, DBSYS just closes
with no error message. Why repair doesn't fix the problem? Can you help me,
please? I can send you the table if you want. Thanks,
>>

Sometimes, there are much garbage stored in the fields and repair is not
able to *clean* this garbage.
You can use a SQL statement to try solving the problem using where condition
that filter all records and remove indesirable records.

For example:
select * into newtable where keyfields <> null

If the table is not so big then you could put it at binary NG and I can see
what I can help you.

Eduardo

Eduardo,

Thanks for your help. I have already solved the problem in the follow way:

1) Repair "CorruptedTable";
2) CopyTable "CorruptedTable" to "TempTable";
3) Now I can open "TempTable" and delete garbage records;
4) CopyTable back to original table;

My question is: why RepairTable doesn’t automatically delete garbage records based upon record checksum?

Thanks,

Mauricio Campana Nonino
Nonino Software

Mauricio,

> My question is: why RepairTable doesn’t automatically delete garbage records based upon record checksum?

If it did that then a damaged checksum would cause RepairTable to
destroy (potentially) perfectly valid records.

Eryk

Eryk,

<<If it did that then a damaged checksum would cause RepairTable to
destroy (potentially) perfectly valid records.>>

Yes, it makes sense. Although particularly in this table, the valid records had a correct checksum. So, another question: would be difficult to create a
CopyTableWithValidCheckSums function?

Thanks,

Mauricio Campana Nonino
Nonino Software

Mauricio,

<< Yes, it makes sense. Although particularly in this table, the valid
records had a correct checksum. So, another
question: would be difficult to create a CopyTableWithValidCheckSums
function? >>

I'll put it on the list of enhancement requests for DBISAM.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young,

<<I'll put it on the list of enhancement requests for DBISAM.>>

Thanks Tim. I was trying to do it by myself, but I realize I could not. When I try to open that corrupted table, it pops up a "Corrupted Header Error".
Then I have to repair the table, but doing it automatically fixes the record checksum, and then I can not check if a record is valid.

Mauricio Campana Nonino
Nonino Software