Cisco Cisco IPCC Web Option Troubleshooting Guide

 

14 

 

Troubleshooting Guide for Cisco Unified Contact Center Management Portal Release 8.0(1) 

There are two types of replication connection between the database 
servers. The first is SQL Server replication, which is used to replicate 
dimension, member and administration tables in Unified CCMP database. 
The second connection is used by the Data Import Server to replicate audit 
data between the systems. 

If this connection is broken, both replication connections are expected to 
stop.  

While the connection is down, disk space will fill up on the active 
importer. This is because it is accumulating session files from the running 
importer which cannot be replicated to the other side. Once the connection 
is re-established the session files waiting to be replicated will be processed 
and data should not be lost as a result. 

Once the connection is re-established,both connections should start 
working again and catch up where they left off. For SQL Server 
replication this can be monitored through the Management Studio 
Replication Monitor. Data Import Server replication can be monitored by 
opening Windows Explorer on the configured ToReplicate folder. 

 

 

An extended interruption of replication may result in the Transaction Log 
becoming full. No logged operations can be performed while the 
Transaction Log is in this state. 

First, check that the transaction log is indeed full. If certain that the 
underlying issue has been fixed, extend the Transaction Log. This allows 
operations to be performed again. Once the system has recovered, use 
DBCC SHRINKFILE to shrink the log back to normal size. 

It sometimes happens that while replication is down, the same user is 
created on both the publisher and the subscriber. When replication is 
brought back up again, the presence of two records containing fields that 
must be unique (such as the login name) causes replication to fail.