|
|
|
RECOVER_DETAILS <YES | NO>
This keyword enables logging of detailed information about the FairCom DB automatic recovery process. The time spent for each phase of automatic recovery in addition to the number of transactions processed for each phase is provided. This keyword adds minimal overhead to FairCom Server operations.
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).
Default: YES
