company logo

Database :: enableReplication - Enable replication master

The function enables a database for running as replication master on a replication server.

In order to limit the transactions stored in the transaction log on the replication server, the maximum number of transactions has to be passed in iMaximumTransactions. When the maximum number of transactions has been exceeded, old transactions are removed from the transaction log. Thus, the replication database has to be reloaded, when a client exceeds the transaction limit, i.e. when its current transaction number is less than the servers transaction number minus iMaximumTransactions.

Implementation details

  1. Enable replication master
    Database  :: enableReplication ( int32 iMaximumTransactions )

    The function schuld be called in order to activate a replication database or in order to re-enable a replication database (reset last transaction number and increase RDB version).

    • iMaximumTransactions - Maximum number of transactions

      The maximum number of transactions limits the number of transactions stored in the transaction log of a replication server. When exceeding the maximum transaction number, the client base is considered as outdated and has to reload the database from the server.

  2. to list
  3. Enable replication master
    Database  :: enableReplication ( int32 iMaximumTransactions, int32 iRDBVersion )

    After disabling a replication database (e.g. for maintenance purposes), the RDB version is set to 0. When re-enabling a replication database in this case, the next higher RDB version number should be passed in iRDBVersion.

    • iMaximumTransactions - Maximum number of transactions

      The maximum number of transactions limits the number of transactions stored in the transaction log of a replication server. When exceeding the maximum transaction number, the client base is considered as outdated and has to reload the database from the server.

    • iRDBVersion - Replication database version
  4. to list