IBM Informix Enterprise Replication(ER/CDR) best practices

IBM Informix Enterprise Replication(ER/CDR) best practices -- Posted by inturi on Saturday, March 22 2008

Avoid replicating large transactions
Always create replicated tables with row locking. Page locking tables may reduce apply performance
If you are replicating buffered logging database, consider changing it to unbuffered logging database
Make sure system clocks for replication servers are always in sync. Otherwise Enterprise Replication latency might suffer if you have replicates with timestamp or stored procedure conflict rules.
Make sure you configure atleast two sbspaces for CDR_QDATA_SBSPACE -- one logging and one non-logging sbspace
If possible size your logical logs so that log switch interval is atleast 60 minutes.
Monitor ER alarms through alarm program. If possible try adding chunk to queue data sbspace automatically through alarm program when queue data sbspace full alarm is raised. Look at replication manual for complete ER alarm list.
Monitor large transaction replication statistics using onstat -g grp pager command. Ideally you shoudn't be replicating large transaction. If that is not possible then make sure that you configure temporary sbspace and set its name in SBSPACETEMP. This way grouper paging will not consume logical log space while paging large transaction in grouper.