I have a customer with IPCC 4.0(5), recently upgraded from 4.0(4)... they actually had this problem on the previous version as well.
Basically they have two clusters (one still on 4.0(4)) - on this HA cluster, the AgentStateDetail table on CRA_DB is updated pretty much in real time. It's then replicated every few minutes out to the secondary server.
The same normally applies ot their second cluster - however, occasionally we have seen that the updates slow down. Currently the AgentStateDetail updates every 5 minutes, at which point multiple updates go in to the DB at once. It also pretty much immediately replicates the changes out to the secondary server.
This causes problems as the wallboard/Checkmate data is stale compared to that shown in the Cisco Supervisor.
Has anyone seen this behaviour?
We have recently been running on the secondary server for about 2 weeks, and just failed it back this weekend... is there any extra action that needs to be taken to clear up the databases when we've been running on the secondary for a while? I've heard something manual needs to be done after 4 days, but not found solid info on it. I have noticed that there are currently more rows in the database on the secondary server in the AgentStateDetail table than on the primary, which suggests that some info has not replicated back to the primary...
Any suggestions welcomed!