Cisco Cisco Unified Contact Center Management Portal 8.5 Troubleshooting Guide
28
Troubleshooting Guide for Cisco Unified Contact Center Management Portal Release 7.2(3)
3. 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
to specify exactly where the importer will fail when there is no disk space
left.
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.
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.
Network Disconnects in Replicated Environments
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 the Unified Contact
Center Management Portal database. The second connection is used by the
Data Import Server to replicate high volume fact data between the systems.
servers. The first is SQL Server replication which is used to replicate
dimension, member and administration tables in the Unified Contact
Center Management Portal database. The second connection is used by the
Data Import Server to replicate high volume fact data between the systems.
If this connection is broken, both replication connections are expected to
stop.
stop.