Skip to main content


File and table requirements for data replication


File and table requirements for data replication


The FairCom replication version needs to be in sync with the versions of the FairCom server running on the source and target. It is important to install exactly the same build in all of these places.

A new replication agent is incompatible with log entries from an old replication agent and an old replication agent is incompatible with a new log entry. This incompatibility shows up as replication of file create failing with error 43 (FVER_ERR). When updating a source server, the replication agent must also be updated.

In V12 and later, replication supports files with:
  • Superfiles

  • Hot Alter Table

  • Partition file starting with V12 and later

Transaction processing

FairCom replication relies on a transaction log-based facility. Your files must be under transaction control to take advantage of FairCom replication. Review the FairCom ISAM for C Developers Guide for complete information on data integrity and enabling transaction processing at the file level.

Indexes and data files

For a file to be replicated there must be a unique qualifying replication index on that file.

Several conditions must be met for an index to qualify as a replication index:
  • The index must be unique.

  • The index must not have null key support enabled.

  • The index must not have a conditional index expression.

  • The index must be a permanent (not temporary) index.

  • Low-level updates are not allowed on files marked for replication.


    Indexes with serial segments (SRLSEG) and/or IDENTITY support require additional configuration considerations.

  • Data files require an extended header to be eligible for replication.

IFIL resource

The data files being replicated must contain an IFIL resource.