|
|
|
The number of active log files required to support server operation is nominally four (4). A number of conditions require more active log files. The most important of these are:
When the number of log files is about to increase, CTSTATUS.FCS receives a message to that effect. FairCom DB outputs an explanation as to the condition that triggered the increase. When the increase is caused by a pending transaction, we attempt to identify the user ID and node name associated with the transaction.
When the number of log files is not permitted to increase (because of FIXED_LOG_SPACE YES in the configuration information), and if the need for more logs is caused by a pending transaction, the server will disconnect the client associated with the transaction. If the following keyword
COMPATIBILITY NO_TRAN_DISCONNECT
is not part of FairCom DB configuration in ctsrvr.cfg, then the server will attempt to disconnect the client. If the client is not disconnected, and if the client does not make a subsequent server request, then the pending transaction will eventually lead to the server terminating abruptly with error L56. The server terminates as it cannot ensure that a commit or abort will be added to the transaction logs before the log that holds the TRANBEG entry will become inactive. (If the client makes a server request, it will see the transaction attribute that indicates the need to abandon the transaction, and the abnormal shutdown will be avoided.)
