|
|
|
FairCom DB can completely recover from normal server shutdowns when data is under complete transaction processing control. These options control how recovery proceeds in various scenarios.
WARNING: Use caution when specifying options skipping files as they can result in data loss if you're not absolutely certain of the operation of your application regards to data file handling.
Enables logging of detailed information about the FairCom DB automatic recovery process.
Allows setting separate limits on the number of files used during automatic recovery and regular operations.
Loads one or more transaction logs into memory during automatic recovery to speed the recovery process.
Causes files that appear to have been properly closed to not be updated during recovery.
Causes automatic recovery to recover to the last Restore Point.
Redirects filename references in the transaction logs during automatic recovery to the specified new filename.
Specifies a file containing a list of files to be altered using the filename redirection rules specified with REDIRECT options.
Forces automatic recovery to skip any file that is not accessible.
If a user file required during automatic recovery is missing, this keyword causes an error to be logged so the FairCom Server will successfully start up.
Forces automatic recovery to continue in an unusual situation in which index reconstruction fails during automatic recovery.
