Hello,
We have been using HXTT DBF successfully for several months now, but today all of a sudden we have started getting errors in the log files stating:
java.sql.SQLException: Memo file conthdr.fpt can't beyond a maximum file size of 2GB.
Looking at the files from Windows explorer, the file sizes are:
conthdr.dbf 278,139 KB
conthdr.fpt 1,049,383 KB
So it appears that the conthdr.fpt file is only about 1GB, not even close to 2GB.
Please advise ASAP, this is now running in production so it is preventing users from updating some important business documents!
Thank you
Phil Ehrlich
|
I guess that your ftp file should contains an invalid freeblock number information.
1st solution: (it need some time to get a new dbf/fpt with index files)
First, you should backup your data files.
Secondly, you can use "pack table conthdr" to see whether you can get a compressed fpt file.
2nd soluton:
Download the latest package, which has added invalid freeblock number detection. If your issue disappear, then my guess is correct.
|
Hi, thank you for responding so quickly! I downloaded the latest package and installed in our application but unfortunately we are getting the exact same error message as before:
java.sql.SQLException: Memo file conthdr.fpt can't beyond a maximum file size of 2GB.
One other thing I thought of... I am updating this table inside of a java transaction with 4 other tables. I am doing this by calling setAutoCommit(false) on the java connection object. I don't know if somehow the file sizes of the 5 tables added together are above 2GB, but none of the files by themselves are more than 1 GB.
Please advise. This error is still blocking several critical production business functions.
Thank you
Phil
|
Please use an hex editor to open that conthdr.fpt, and let us know the first 4 bytes value. You can try to replace it with 00 00 00 00.
Otherwise you have to try 1st solution.
|
Hello,
I opened the conthdr.fpt file with a hex editor and the first 4 bytes are:
01 01 D2 40
For a temporary solution, we packed the file and it shrunk a bit, but we will face this issue again. I saved the original file that was having an issue and we can still recreate the error message.
**********
If you are not able to determine what the issue is, can you please add an option to disable the 2GB limit checking? Clearly there is an issue since the file is much less than 2GB and the FoxPro application which also uses this file can access it just fine.
**********
Thank you
Phil
|
>I opened the conthdr.fpt file with a hex editor and the first 4 bytes are:
>01 01 D2 40
The following 4 bytes should be 00 00 01 00, so that it beyongs 2GB limitation. After you pack your table, that invalid freeblock number information has been fixed. You should not meet that error again.
|
Main
webmaster@hxtt.com