Cisco Cisco IPCC Web Option Troubleshooting Guide
Troubleshooting Guide for Cisco Unified Contact Center Management Portal Release 8.0(1)
11
</LinkedServers>
</Publisher>
<Subscriber SubscriberId=”ReplicationSubscriber” Port=”7500”
ReplicatedDirectory=”\IMPORTER\Replicated” />
</Replication>
<Subscriber SubscriberId=”ReplicationSubscriber” Port=”7500”
ReplicatedDirectory=”\IMPORTER\Replicated” />
</Replication>
Once the failed server has been fixed, perform the following steps:
1. Switch off the Data Import Server and Unified Contact Center
Management Portal Replication Publisher / Subscriber services.
2. Delete everything in the ToReplicate and Replicated folders on
both servers.
3. Switch off SQL Replication between the two databases.
4. On the active importer take a snapshot of the SQL Server database
and restore it on the failed side. At this point both databases
contain identical data.
contain identical data.
5. Bring up SQL Server replication between the two databases.
Each table imported by the importer has a tide mark. The tide mark is
essentially a bookmark storing the location where everything has been
imported up to. Everything after the tide mark has yet to be imported.
The importer imports a chunk of available data from each file in turn
and updates the tide mark afterwards. The tide marks are stored in a
table called TB_IMP_TIDEMARK.
essentially a bookmark storing the location where everything has been
imported up to. Everything after the tide mark has yet to be imported.
The importer imports a chunk of available data from each file in turn
and updates the tide mark afterwards. The tide marks are stored in a
table called TB_IMP_TIDEMARK.
Make the following changes on the failed server:
1. The tide marks in TB_IMP_TIDEMARK will be incorrect once
the database has been restored on the failed side. Delete all rows
from the table that contains the failed server
RESOURCE_INSTANCE_ID. On the failed server call
ap_clu01_get_exony_db_resource_instance from SQL Server
Management Studio to get its RESOURCE_INSTANCE_ID.
from the table that contains the failed server
RESOURCE_INSTANCE_ID. On the failed server call
ap_clu01_get_exony_db_resource_instance from SQL Server
Management Studio to get its RESOURCE_INSTANCE_ID.
2. After deleting all the rows for the failed database server, duplicate
each remaining row in the TB_IMP_TIDEMARK table. Each
duplicated row must have its RESOURCE_INSTANCE_ID
changed to the failed server identifier. Doing this ensures that both
servers have identical tide marks and so match the data in the fact
tables and dimensions.
duplicated row must have its RESOURCE_INSTANCE_ID
changed to the failed server identifier. Doing this ensures that both
servers have identical tide marks and so match the data in the fact
tables and dimensions.