Cisco Cisco IPCC Web Option Troubleshooting Guide
Troubleshooting Guide for Cisco Unified Contact Center Management Portal Release 8.0(1)
9
4. Common Issues
Database Server Errors
Required Initial Data Import Never Stops
When installing, it is necessary to import data before setting up Cisco
Unified Communications Managers. In some cases, this import does not
appear to stop. This may indicate a database connection failure.
Unified Communications Managers. In some cases, this import does not
appear to stop. This may indicate a database connection failure.
Use the Management Studio to verify that data is being imported to
TB_DIM_AGENT in the database created by Unified CCMP. By default,
this is the Portal database. If it is, the import is proceeding normally.
TB_DIM_AGENT in the database created by Unified CCMP. By default,
this is the Portal database. If it is, the import is proceeding normally.
If no data is being imported, ensure that the Read-only user on the Admin
Workstation databases has DataReader permissions and that other details
such as the password are correct.
Workstation databases has DataReader permissions and that other details
such as the password are correct.
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.
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.
The following steps describe the actions to perform on the inactive side.
1. Turn off the Data Import Server and Management Portal
Replication Subscriber. It is very important that these services shut
down properly otherwise the system may be in an inconsistent
state. If either of these fails to shut down properly, then they
should be restarted and allowed to run for at least 30 minutes. This
should give them sufficient time to recover their state and roll
back any inconsistencies.
down properly otherwise the system may be in an inconsistent
state. If either of these fails to shut down properly, then they
should be restarted and allowed to run for at least 30 minutes. This
should give them sufficient time to recover their state and roll
back any inconsistencies.
2. Check the TS_IMP_DIRECTORY_STATUS table. This table
contains one row for each replicated session directory. If there are
any rows in this table that have a status other than F, then the
database state is inconsistent. The only recourse is to restart the
Data Import Server to give it time to recover. After approximately
any rows in this table that have a status other than F, then the
database state is inconsistent. The only recourse is to restart the
Data Import Server to give it time to recover. After approximately