Broken UCCE database replication

If you have deployed a HDS server to query historical data then data is being replicated between the Logger and HDS servers. This replication might fail if the recovery keys are not matching beteween the Logger and HDS. It is known to happen when you run setup on the HDS and change the site it was pointing to, or when the Recovery table is altered or truncated in some way.

To check whether data is still being replicated, execute the following query on the HDS database:

SELECT max(DateTime) AS EXPR1
FROM t_Termination_Call_Detail

In order to resolve the broken replication issue perform the following tasks out of business hours:

Stop the Logger and HDS services.
Run the following query on HDS database where replication is failing: “Truncate table Recovery”.
Start the Logger and HDS services. New recovery keys are created and the replication process wil start again.

If you have tracing enabled, you’d see a fair amount of messages in the “LoggerA/B replication” window when logged on to the Logger server. You can use the first check mentioned above to see whether the replication is up and running again.