Showing results for 
Search instead for 
Did you mean: 

Core Issue

The user observes the issue when the Cisco CallManager databases are not in sync or there is some issue with the Cisco Real-time Information Server (RIS) Data Collector.


In order to resolve this issue, complete these steps:

  1. Use the DBHelper utility in order to navigate to c:\program files\cisco\bin and double-click on dblhelper.exe. It displays with green smiley faces for each Cisco CallManager server. If it does not, choose Reinitialize and Republish. The DBHelper tool attempts to fix any database corruptions.

    The DBHelper can also look into name resolution problems and report if there are issues with the name resolution scheme on a network.
  2. Refer to the Reestablish the Relationship Between Publisher and Subscriber Using DBLHelper section of Using DBLHelper to Reestablish a Broken Cisco CallManager Cluster SQL Subscription for information on how to obtain DBLHelper.
  3. Restart Tomcat service.
  4. In case the issue is still not resolved, reset the RIS service on all Cisco CallManager applications in the cluster.

Refer to the Replication Fails Between the Publisher and the Subscriber section of Cisco CallManager System Issues for more information.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links