FairCom Corporation
Your Location: USA | Europe | Brazil | Japan

Home / Technical News / Corrected Handling of Segmented Files During Automatic Recovery

Correct Handling of Segmented Files During Automatic Recovery

10 June 2009

Affected Builds: All builds prior to 090610
Criteria: Segmented file, Automatic recovery after a failed c‑treeACE Server process
Indications: Renamed file segments

During automatic recovery of a failed c‑treeACE process, existing file segments were renamed and thus subsequently not available to the application resulting in apparent missing data. During recovery, an attempt is made to open all segments of a segmented file found in the transaction logs. To open the segments, the segment definition resource must be read from the primary segment. However, an internal file map attribute had not been initialized resulting in a failed call. This failed call caused the recovery process to believe the additional segments did not exist. When later attempting to create the file segment, and that segment already existed, c‑treeACE then renamed the segment. The uninitialized attributes are now properly assigned avoiding this potential incorrect renaming of segmented files.

FairCom customers on current maintenance can request an updated V9 server line at any time. Please contact your nearest FairCom office should you have any concerns that you are impacted by this update.

“The speed comparisons between FoxPro/CodeBase and SQL databases such as DB2, Sybase, and MS SQL are misleading. The very nature of SQL databases is slow throughput. FairCom has a much faster and very reliable solution. We changed to FairCom because we needed a back end that could handle real world loads reliably, and we needed the flexibility to support different platforms. Since we made the change, our customer support calls are down 75%!”

Ken Morris
President/CEO, M-Systems, Inc.

Copyright 2014 FairCom Corporation. All rights reserved.