FairCom ISAM for C

Recovery Capabilities

There are three different situations requiring user intervention that may be reported at the end of automatic recovery: file compression not completed, index requires rebuilding, and primary and mirror file out-of-sync (note that the first two of these are not related to mirroring).

1. File compression: if file compression is interrupted, automatic recovery will report the files involved (original and temporary). If the temporary file does not exist, then the data file compression is completed, but the indexes must be rebuilt. If the temporary file still exists, then the original file must be replaced with the temporary file, and the indexes rebuilt.
2. In the event that an index file b-tree appears beyond repair because of a loop in its leaf node links, the index file is listed so that it can be rebuilt. (This condition has not been encountered.)
3. When a primary and mirror file get out-of-sync, beyond the ability of automatic recovery to make them both good, the most up-to-date file is recovered.

If any of these conditions arise, recovery completes but a listing of the files and conditions is given on the screen and in the CTSTATUS.FCS file.

One of the following error codes will then terminate the recovery:

Value	Symbolic Constant	Explanation
570	RCL1_ERR	Incomplete compression.
571	RCL2_ERR	Index rebuild required.
572	RCL3_ERR	Incomplete compression & index re-build required.
573	RCL4_ERR	Primary/mirror out-of-sync. copy good file over bad.
574	RCL5_ERR	Incomplete compression & primary/mirror out-of-sync.
575	RCL6_ERR	Index rebuild required & primary\mirror out-of-sync.
576	RCL7_ERR	Incomplete compression & index re-build required & primary/mirror out-of-sync.