Replication of the SQL database is a core function of Cisco CallManager
clusters. The server with the master copy of the database is called the
publisher, while the servers that replicate the database are called
In the event that your subscriber stops the replication of data from
the publisher, you need to rebuild the publisher/subscriber relationship(s). In
order to do this, go into the SQL Server database and manually rebuild the
This is a list of possible symptoms if the subscriber stops replicating
from the publisher:
Changes that are made on the publisher are not reflected on phones
that are registered with the subscriber.
Outbound calls fail on phones registered with the subscriber. As soon
as you dial 9, you hear a re-order tone.
Call Forward All (CFwdALL) does not work.
IP phone displays Error Database.
Note: Refer to
DBLHelper to Reestablish a Broken Cisco CallManager Cluster SQL
Subscription for more information.
This document assumes that the SQL Administrator (sa) account password
is available for both the publisher and subscriber.
The information in this document is based on these software versions:
Note: If you have Cisco CallManager version 3.3, refer to
a Broken CallManager Cluster SQL Subscription with Cisco CallManager
The information presented in this document was created from devices in
a specific lab environment. All of the devices used in this document started
with a cleared (default) configuration. If you work in a live network, ensure
that you understand the potential impact of any command before you use
Refer to the
Technical Tips Conventions for more information on document
Complete these steps in order to reestablish the relationship between
the two systems. First, the subscription of the subscriber needs to be
recreated on the publisher. Then, the subscription needs to be deleted and
recreated on the subscriber system.
Complete these steps:
On the publisher, select Programs > Microsoft SQL Server
7.0 > Enterprise Manager in order to start the SQL Enterprise
The subscription can be recreated from the publisher. Under
Microsoft SQL Server, select New SQL Server Registration...
The Register SQL Server Wizard appears.
Make sure that the From now on I want to perform the task
without using a wizard is not checked. Click
The other SQL servers that reside on the Cisco CallManagers need to
appear in the Additional Servers box.
Select all servers and Add them to the Added
servers box. Click Next.
Select The SQL Server login information that was assigned
to me by the system administrator and click
Use the "sa" account and password for the subscriber system on the
Note: This is the sa account and password from the SUBSCRIBER system.
The password is selected when the subscriber system is installed.
Choose the option to Add the SQL server(s) to the existing
SQL Server group in the Select SQL Server Group window. The Group name
chosen here is SQL Server Group.
The status of the addition of the added server(s)
The message states "Registered successfully". Click
Something like this window appears.
If you see the two servers listed, it means that they are
recognized by the publisher. Data can be shared with these servers.
Complete these steps:
Under the Enterprise Manager, navigate to the SQL Server tree and
locate the Publication for the CCM0301 database (Microsoft SQL Servers
> SQL Server Group > Machine_name > Databases > CCM0301 >
Publications). Select the Cisco CallManager subscription that fails
and delete the entry.
Caution: Select the area as shown by the arrow in this graphic. Do not
delete the book icon on the left.
There is a warning that indicates that the subscription is removed
at the publisher, but not the subscriber. Click Yes if you
want to connect to the subscriber and delete the subscription.
The next message indicates that the subscription is deleted but the
data is not deleted. Click OK.
Complete these steps:
The subscription must be added back into the subscriber SQL server.
Select the SQL server name of the subscriber that you just deleted from the
publisher. In this configuration, the publisher is AVVID_LAB_PUB and the
subscriber is AVVID_LAB_SUB1. You have just deleted the AVVID_LAB_SUB1
subscription from the AVVID_LAB_PUB publication. In order to resubscribe to the
publication, choose the AVVID_LAB_SUB1 SQL server and select
the CCM0301 database. Right-click to get the menu. Then select
New > Pull Subscription from the menu.
Note: Always choose the latest version of the database, not the earlier
(CCM0301 in this example) version.
Click Next when the Pull Subscription Wizard
On the Choose Publication window, expand the publisher (which needs
to be listed) and select the CCM0301 database. Click
Select Using SQL Server Authentication of this
account on the Specify Synchronization Agent Login
. The login name is sa and the password is the same password as the
publishers 'sa' account.
Select Yes, make this an immediate-updating
subscription(s) on the Specify Immediate-Updating Subscription(s)
window. Then click Next.
Select Yes, initialize the schema and data at the
Subscriber on the Initialize Subscription window and click
Select Continuously on the Set Distribution Agent
Schedule window and click Next.
The next step verifies that both the SQL server agent and the
Microsoft DTC services run. Click Next.
Click Finish on the Completing the Pull
Subscription Wizard window.
The Wizard sets up the subscription and displays a success when
The Wizard sets up the subscription.
A display that indicates success appears when the process
Now that the subscription is created, the snapshot agent must be
run in order to get the data out to the subscriber for synchronization. Select
the publisher SQL server and navigate to Replication Monitor >
Publishers > Machine_name >CCM0301 subscription. Select the
Snapshot entry and choose Start. The snapshot
agent runs at this point. It takes about three to five minutes to complete the
task. Once the snapshot agent completes, the pull agent starts to apply the
snapshot to the subscriber. This takes another three to five minutes.
Once the pull subscription completes, on the publisher, select the
subscriber SQL server and open the pull subscriptions for the CCM0301 database.
The subscription needs to be in an active state and it needs to wait for
Note: If the last action still reads "Waiting for snapshot agent to
become available", press F5 in order to refresh the
At this time, the subscriber is now resynchronized with the
publisher and updates are recorded in the local subscriber SQL database.
Complete the steps:
Create a device on the publishing server that is easily
recognizable to test the propagation of data. Click Insert.
The device does not need to be functional. Click Update and
Go into the SQL Enterprise Manager, expand the SQL subscriber in
question and look in the database table to see if the new device is present.
The more recognizable the device is, the easier it is to