|
|
|
Full ACID transaction processing of data is the gold standard for ensuring data integrity. Maintaining database changes in write-ahead logs to secure data is a complex and intricate process. As such, multiple features and options are available to fine tune this process for the best performance vs. integrity.
Allows newly created non-transaction files to be created in PREIMG mode.
AUTO_RESTORE_POINT (SUBSYSTEM)
Supports a configuration option to automatically perform restore points.
Extends the automatic transaction support to include recoverable transactions without any application change.
Automatic transactions will be considered “light weight” so the transaction log is not flushed to disk on an automatic commit.
A transaction will automatically be started when creating a transaction-controlled ISAM file.
Sets the maximum number of checkpoints to be written before a buffer (data or index) holding an image for a transaction controlled file will be flushed.
Specifies the time in seconds between checkpoint checks.
Sets the interval between checkpoints (which can speed up recovery at the expense of performance during updates).
If the checkpoint used for automatic recovery does not appear to be valid, enables the server to attempt to start recovery at the location of the next to last checkpoint.
Specifies how many consecutive logs may be processed without a checkpoint until the FairCom Server terminates.
Controls the time, in milliseconds, the transaction manager waits after a transaction completes before flushing the transaction to disk.
Determines the rate at which the nominal commit delay time is adjusted as the number of cohorts increases or decreases.
Minimum time allowable for commit delay to be overridden - Do not use unless instructed to by FairCom.
For advanced control of the intricate commit delay timing statistics by adjusting the commit delay time calculation.
Same as COMMIT_DELAY, but interpreted as microseconds.
Provides an additional tuning mechanism for the COMMIT_READ_LOCK retry value.
Instructs the FairCom Server to open its transaction logs in synchronous write mode.
Forces transaction controlled data files to be written directly to disk, skipping the calls to flush their OS buffers.
COMPATIBILITY TINDEX_WRITETHRU
Forces transaction controlled index files to be written directly to disk, skipping the calls to flush their OS buffers.
Disables the FairCom Server from automatically adjusting the size of transaction log files to accommodate long records.
Allows LOGIDX index file mode support to be forced on, off, or disabled.
Specifies the number of non-active transaction log files kept on disk in addition to the active log files.
Allows the server to maintain information about the last N Restore Points.
Affects how compression is applied to log entries: if the compression does not fit in a buffer of size (<factor> * input_size / 100), then no compression takes place. Not currently supported.
Affects how compression is applied to log entries: if the variable region is less than this threshold, no compression is attempted. Not currently supported.
The alternative name for even numbered transaction log files.
The alternative name for odd numbered transaction log files.
Changes the page size block of the transaction log buffer.
Specifies the number of megabytes of disk space allocated to storing active transaction logs.
Enables transaction log templates.
Specifies the percentage of data that is written to the target transaction log file after which the copy operation sleeps for the number of milliseconds specified for the LOG_TEMPLATE_COPY_SLEEP_TIME option.
Causes the copying of the log template to pause for the specified number of milliseconds each time it has written the percentage of data specified by LOG_TEMPLATE_COPY_SLEEP_PCT to the target transaction log file.
Any transaction that exceeds the elapsed transaction time specified will be considered a long transaction for monitoring purposes.
Specifies an optional limit for how many active transaction logs a transaction spans before it is aborted or abandoned.
Controls how many logs a transaction can span before attempts are made to abort or abandon the transaction.
The alternative name for the file containing preimages swapped to disk.
The alternative name for even numbered start file.
The alternative name for odd numbered start file.
Causes transaction begin and commit operations to skip the flushing of the log file when its argument is YES.
Skips the sync'ing to disk from a log flush operation.
Specifies a transaction number threshold value.
Allows the server administrator to determine when the server will issue a warning that its transaction number is approaching the limit.
Sets a time limit on a transaction after which the transaction is aborted.
Controls the maximum number of updates to a buffer (data or index) before it is flushed.
Enables separate unbuffered I/O for transaction logs.
