mosh 0 Report post Posted November 16, 2005 I have data corruption in a version 4.0d database. I believe that the corruption is in the file which contains the witness information. Which data file is it that contains the witness information? Would simply replacing that file with the corresponding file from a pre-corruption backup be a possible fix? Mosh Share this post Link to post Share on other sites
mosh 0 Report post Posted November 29, 2005 I have data corruption in a version 4.0d database. I believe that the corruption is in the file which contains the witness information. Which data file is it that contains the witness information? Would simply replacing that file with the corresponding file from a pre-corruption backup be a possible fix? Mosh <{POST_SNAPBACK}> I wasn't particularly impressed with the response (or lack thereof) to this post. However, with the help of one of Lee Hoffman's webpages, I was able to find what I hope is a solution to the witness corruption problem that I have been experiencing. Lee's TMG File Structure page <http://www.tmgtips.com/dbnames2.htm> states that the "e files" (that is, *_e.dbf, *_e.fpt, and *_e.cdx) contain the "Event witness" information. (After backing everything up,) I replaced these three files in the corrupt database with the corresponding three files extracted from my most recent uncorrupted backup. The database now seems to load properly with all of the most recent information entered, and without the witness corruption. Luckily, between the date of this last uncorrupted backup and the time that I noticed the corruption in the witnesses, I hadn't added nor changed any witness information. I'm posting this for the benefit of anyone who might have a similar problem in the future. Mosh Share this post Link to post Share on other sites
dakko 0 Report post Posted November 29, 2005 Thank you for posting the solution. My daughter is using v.4, and I will keep a copy of your post in case she encounters this problem. I like that you found a way to retain recent changes to the rest of the data, rather than just restoring from the last backup. Your taking the extra step to post this info is much appreciated. Share this post Link to post Share on other sites
John Cardinal 0 Report post Posted December 2, 2005 Please note that the E table is changed for both witnesses and principals. Replacing the E table using a previous version of the database is very dangerous and should be a last resort--and one followed by careful review of your data. Are you certain that the corruption in the most recent version of the DB can't be fixed? Share this post Link to post Share on other sites
mosh 0 Report post Posted December 4, 2005 Please note that the E table is changed for both witnesses and principals. Replacing the E table using a previous version of the database is very dangerous and should be a last resort--and one followed by careful review of your data. Are you certain that the corruption in the most recent version of the DB can't be fixed? <{POST_SNAPBACK}> I repeatedly asked WG support for help, and received absolutely no response. I'm not a programmer. My only other option would seem to be manually re-entering all of the data entered since the most recent uncorrupted backup (and hoping that I don't miss anything). Is that preferable? Moshe Share this post Link to post Share on other sites
John Cardinal 0 Report post Posted December 5, 2005 I repeatedly asked WG support for help, and received absolutely no response. I'm not a programmer. My only other option would seem to be manually re-entering all of the data entered since the most recent uncorrupted backup (and hoping that I don't miss anything). Is that preferable? That's what I'd do. Share this post Link to post Share on other sites
