Cisco Cisco IP Contact Center Release 4.6.1 Troubleshooting Guide

 

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

13

 

3.  Delete all data from TB_IMP_FCT_PARTITION with the 

RESOURCE_INSTANCE_ID of the failed database. This should 
cascade delete data from all the other state tables. 

4.  All the data in the following tables must be duplicated using the 

failed database RESOURCE_INSTANCE_ID. This essentially 
matches the state tables with the actual data in the database fact 
tables.  

• 

• 

• 

5.  Reset Replication.xml on the active importer. 

6.  Restart the Data Import component server service along with 

Unified CCMP Replication Publisher / Subscriber services on both 
servers.  

The Data Import component server will start importing and 
replicating data to the other side as normal. 

If there is no disk space for the importer, it will continue trying and failing 
to import data until disk space is made available. However the importer 
should always reset Unified CCMP database to a consistent state. 
Sometimes the importer cannot back out changes it has made to the 
database until disk space is made available. For example, disk space is 
often required by the SQL Server transaction log before changes are 
committed. 

There are several places where running out of disk space can cause an 
import to fail. For example when the importer reloads a dimension cache, 
it saves it to a session file on disk. The same occurs when the importer is 
processing downloads from the Admin Workstation. It is therefore difficult 
to specify exactly where the importer will fail when there is no disk space 
left. 

In all cases the importer should generate an exception (visible in the 
importer trace) and stop the current import. Once disk space is made 
available, the importer should reset the database to a consistent state and 
start importing again.