|
|
|
Reverts to the previous behavior of using direct I/O instead of O_DSYNC synchronous writes (or O_SYNC if O_DSYNC is not defined) for transaction logs on Solaris.
For Unix systems, enables the optional use of fdatasync() instead of fsync().
Forces the automatic addition of the WRITETHRU mode to all files opened without the TRNLOG file mode.
Provides a balance between update performance and recoverability of data in the event of an abnormal FairCom Server termination affecting non-transaction files.
Disables the ‘update’ flag on files with the WRITETHRU file mode.
Changes the number of I/O channels assigned to a file with ctDUPCHANEL in its file mode at open, unless the file is in the SET_FILE_CHANNELS list.
IDLE_NONTRANFLUSH and IDLE_TRANFLUSH
Deprecated: Sets the interval FairCom DB waits before checking to see if the server is idle before flushing data and index caches during idle time. These keywords have been replaced by the following:
Specifies the maximum number of failed IO_ERROR_BLOCK_SIZE-sized I/O operations that must occur before the I/O operation is considered to have failed.
Causes a read or write operation that fails with Windows system error 1450 (ERROR_NO_SYSTEM_RESOURCES) to be retried in blocks of the specified size.
Specifies a time in milliseconds between IO_ERROR_BLOCK_RETRY retry attempts.
Permits the number of I/O channels to be explicitly set for the named file regardless of whether the file mode, at open, includes ctDUPCHANEL.
Enables unbuffered I/O for the specified file on Windows systems.
Diagnostics
Diagnostics keywords are intended to be used to help collect data to be analyzed for troubleshooting. The use of these keywords should be avoided in normal operation as they may cause additional overhead (e.g., logging).
Enables a check on each write operation for a file for which direct I/O is requested that the properties of the write operation meet the direct I/O requirements.
DIAGNOSTICS LOWL_FILE_IO (DIAGNOSTICS LOWL_FILE_IO, DIAGNOSTICS LOWL_FILE_IO)
Logs low-level system errors into the server status file, CTSTATUS.FCS.
