Product Documentation

c-treeACE V10.0 Update Guide

Previous Topic

Next Topic

Additional Recovery Logging

Automatic Recovery is used to bring transaction controlled c-treeACE data and index files back to a consistent state in the event of an unplanned server outage. The recovery process occurs over several phases. Various details of these phases can be observed with the RECOVER_DETAILS YES server configuration option. This logging of details is now on by default, and RECOVERY_DETAILS NO can be used to suppress this logging.

c-treeACE recovery has been further modified to enhance the logging of details with additional messages specifying phase and progress during the automatic recovery process. Index composition can frequently be a phase that takes the longest amount of recovery time. As it is useful to know the proceedings of this phase, specific messages are now output describing the progress of this phase, and the index member involved. These descriptions are output whether or not the LOGIDX option is in force.

Below is an example of messages that can be found in CTSTATUS.FCS when LOGIDX is not used during automatic recovery. The description in square brackets indicates why LOGIDX was not used:

Mon Nov 23 09:32:44 2009

- User# 00001 Index repair time: 0 seconds.

Mon Nov 23 09:32:49 2009

- User# 00001 tranrcv: Reconstructing index mark.idx [LOGIDX not in file header]

Mon Nov 23 09:32:51 2009

- User# 00001 tranrcv: Reconstructing index mark.idx M#01 [LOGIDX not in file header]

Mon Nov 23 09:32:52 2009

- User# 00001 tranrcv: Reconstructing index mark.idx M#02 [LOGIDX not in file header]

Mon Nov 23 09:32:53 2009

- User# 00001 Index composition time: 9 seconds.

Below is an example of messages found in CTSTATUS.FCS when LOGIDX is used during automatic recovery:

Mon Nov 23 10:46:26 2009

- User# 00001 Index repair time: 0 second(s) for 1 repair(s).

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Recomposing index file FAIRCOM.FCS DI:

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Processing abort node list entries.

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Recomposing index file mark.idx:

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Processing LOGIDX node entries.

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Checking index delete stack.

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Recomposing index file mark.idx M#01:

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Processing LOGIDX node entries.

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Recomposing index file mark.idx M#02:

Mon Nov 23 10:46:26 2009

- User# 00001 tranrcv: Processing LOGIDX node entries.

Mon Nov 23 10:46:26 2009

- User# 00001 Index composition time: 0 second(s).

TOCIndex