Technical References

Message:
“Fail: Assertion failed: syncMsg.UpdateKey == g.checksumInfo.updateKey”.
Cause:
The Config_Message_Log table in the logger database is empty.
Action:
Open icm\install\sysinit.sqlfile. Copy the insert statement for Config_Message_Log table and
run the same on the logger database.
Recovery Process Assert
Symptom:
The Recovery process asserts with the following message
Message:
“Fail: Assertion failed: (keytop - keybase) >= 0.0.”
Cause:
The recovery process has written a bad ToRecoveryKey value for a historical table in the
Recovery control table. It may happen if the system time has been set back on the Router node.
It may also happen if the logger and router on one side of the system start when does not see
another side is up and running. It therefore creates its own RecoveryKey instead of synchronize
with another side.
Action:
Manually remove the out of sequence ToRecoveryKey in the Recovery table on the HDS
database.
CICR Replication Cannot Replicate
Symptom:
CICR Replication cannot replicate
Message:
Cause:
The distributor is in different domains, or the NAM version is different from CICM version
Action:
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
518
Chapter 6: ICM/IPCC Database Troubleshooting