Cisco Cisco Unified Contact Center Management Portal 8.5 Troubleshooting Guide

Troubleshooting Guide for Cisco Unified Contact Center Management Portal Release 7.1(3)

UPDATE TB_CLU_GROUP

SET SERVER_ID = ‘<NEW_ACTIVE_IMPORTER_SERVER_ID>’

WHERE GROUP_ID IN

(‘<GROUP_ID_FROM_EARLIER>’,

‘<GROUP_ID_FROM_ EARLIER >’,

‘<GROUP_ID_FROM_ EARLIER >’)

Example using the GROUP_ID result set shown earlier:

UPDATE TB_CLU_GROUP

SET SERVER_ID = ‘7707C4EF-F58A-412C-9BA8-1A108409B379’

WHERE GROUP_ID IN

(‘C617D006-8A1B-44F2-BB1B-592BA9FA3958’,

‘98DC97B7-E519-41AF-893C-580D94ACEE4F’,

‘17C25CA8-E257-4929-ABD8-1AB443534102’,

‘F648492C-9AC1-4B89-98AD-9F5FBF20CC35’,

‘D562A378-8EBE-4A41-9A34-E8B0F126CBA5’)

6. Start the Data Import Server service on both sides. Start the

Unified Contact Center Management Portal Replication Subscriber
and Publisher Service on both servers. The system will then start
importing on the other side as normal. Assuming that the SQL
Server and Unified Contact Center Management Portal Replication
services have been configured correctly, the imported data should
start being replicated.

The SQL Server Replication Monitor Manager can help verify this.
The Replicated folder on the original server should also show data
arriving from the new active importer.

Active Importer Server Crash

If a server crash or otherwise unrecoverable error occurs on the active
importer then the other side needs to be brought into service as quickly as
possible. The Data Import Server is designed to minimize the down time
before importing can be restarted.