Cisco Cisco Unified Contact Center Management Portal 11.5(1) Troubleshooting Guide
18
Troubleshooting Guide for Cisco Unified Contact Center Management Portal Release 7.5(1)
These importer state tables are replicated using standard SQL Server
replication but are uniquely identified on each side via a
RESOURCE_INSTANCE_ID. The system on each side uses these state
tables to track the arrival of new data into the database fact tables for
further processing.
replication but are uniquely identified on each side via a
RESOURCE_INSTANCE_ID. The system on each side uses these state
tables to track the arrival of new data into the database fact tables for
further processing.
TB_IMP_FCT_PARTITION is the base state table. This contains a
definition of all the fact table partitions that have been created on each
side. There are usually two identical rows in here, differentiated by
RESOURCE_INSTANCE_ID (one for each side). This table links to
TB_IMP_FCT_PARTITION_TIDEMARK and
TB_IMP_FCT_PARTITION_TIDEMARK_SLICE.
definition of all the fact table partitions that have been created on each
side. There are usually two identical rows in here, differentiated by
RESOURCE_INSTANCE_ID (one for each side). This table links to
TB_IMP_FCT_PARTITION_TIDEMARK and
TB_IMP_FCT_PARTITION_TIDEMARK_SLICE.
Unfortunately, when one database is restored to another side, these state
tables are no longer correct. As a result, data may exist in the fact
partitions in the restored database that the system has no idea exists. The
following steps recover the state tables on the failed database. It is very
important that SQL Server replication is running while these steps are
performed.
tables are no longer correct. As a result, data may exist in the fact
partitions in the restored database that the system has no idea exists. The
following steps recover the state tables on the failed database. It is very
important that SQL Server replication is running while these steps are
performed.
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.
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.
matches the state tables with the actual data in the database fact
tables.
•
TB_IMP_FCT_PARTITION
•
TB_IMP_FCT_PARTITION_TIDEMARK
•
TB_IMP_FCT_PARTITION_TIDEMARK_SLICE
5. Replication.xml on the active importer can now be reset and the
Data Import component server service along with the Unified
Contact Center Management Portal Replication Publisher /
Subscriber services can be restarted on both servers. The Data
Import component server will start importing and replicating data
to the other side as normal.
Contact Center Management Portal Replication Publisher /
Subscriber services can be restarted on both servers. The Data
Import component server will start importing and replicating data
to the other side as normal.
Recovery after No Disk Space Available
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 the Unified Contact Center Management Portal
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).
to import data until disk space is made available. However the importer
should always reset the Unified Contact Center Management Portal
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
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