HA Constraint

In the following cases, data between a master database and a slave database may not match.

If a trigger has been set in HA configuration, data mismatch between the Master and the Slave may occur. This is because a trigger that has been executed in the master database is executed again in the slave database.

If a method is used in HA configuration, data mismatch between the Master and the Slave may occur. This is because the replication log is not created when the method is used.

If an operation is performed in HA configuration using CUBRID Manager, data mismatch between the Master and the Slave may occur. This is because the replication log is not created when certain jobs are performed in CUBRID Manager.

If an operation is performed in standalone mode during HA configuration, data mismatch between the Master and the Slave may occur. As a standalone mode is one in which DB operations can be performed when server processes are not running, the log of jobs performed in standalone mode is not reflected in the Slave database.