2017 R1

Settings for Using Fabasoft Folio Distributed Transaction ManagerPermanent link for this heading

The Fabasoft Folio Distributed Transaction Managers is used automatically when using Oracle Database.

It can be configured where the log file of Fabasoft Folio Distributed Transaction Manager should be placed and how long the Fabasoft Folio Distributed Transaction Manger timeout should be.

These values can be specified when creating a Fabasoft Folio COO Service. If the values are not specified, the default values are used.

After an installation it is still possible to change the values manually in the registry.

  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Fabasoft\Fabasoft Components Server\Domain <x.y>\Service <z>\Datasource\Default
    Note: When using Linux the registry path is mapped to a directory structure in /etc/fabasoft/settings. For more information about managing registry keys under Linux consult the white paper “Fabasoft Folio Environment Variables”.
  • FSCDTM_TXLOG_PATH:
    path, where the log file is placed (default value: value from COOROOT)
  • FSCDTM_TXLOG_TIMEOUT:
    Timeout in seconds (default value: 90)
  • SesTM
    Session Timeout (default value: 99; if the FSCDTM_TXLOG_TIMEOUT is set during Fabasoft Folio COO Service creation, the SesTm is automatically set too (SesTm = FSCDTM_TXLOG_TIMEOUT +10))

Note:

  • Using a cluster, the log files have to be available on the appropriate cluster resources (Fabasoft Folio Distributed Transaction Manager log files may exist only once).
  • For the DISTRIBUTED_LOCK_TIMEOUT oracle database parameter a value of 300 is recommended. If this value is not used (default value 60) errors (“ORA-02049: timeout: distributed transaction waiting for lock”, probably also “ORA-01591: lock held by in-doubt distributed transaction”) are possible.
    The timeouts should be configured to ensure:
    FSCDTM_TXLOG_TIMEOUT < SesTm < DISTRIBUTED_LOCK_TIMEOUT