Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CUCM db replication problem

Hello, after reseting DB Layer Monitor Service, db replication is out of order in the cluster. RTMT is showing a replication status of 3 for publisher and 0 for subcriber node.

I try to stop replication on sub:

utils dbreplication stop SUB

=>replication stop correctly

I try to stop replication on pub:

utils dbreplication stop PUB

=> replication stop correctly

admin:utils dbreplication stop

********************************************************************************************

This command will delete the marker file(s) so that automatic replication setup is stopped

It will also stop any replication setup currently executing

********************************************************************************************

Deleted the marker file, auto replication setup is stopped

Service Manager is running

A Cisco DB Replicator[STOPPING]

A Cisco DB Replicator[STOPPING]

Commanded Out of Service

A Cisco DB Replicator[NOTRUNNING]

Service Manager is running

A Cisco DB Replicator[STARTED]

Completed replication process cleanup

Then try to reset replication:

utils dbreplication reset all

=> Failure with the following error

command failed -- Enterprise Replication not active (62)

Any help would be appreciated.

Best regards.

Julien.

  • IP Telephony
7 REPLIES
Hall of Fame Super Red

Re: CUCM db replication problem

Hi Julien,

You may be hitting this bug, it sure does sound like it.

CSCso82088 Bug Details

"utils dbreplication reset all" displays misleading failure message

Symptom:

Once database replication is stopped on all the nodes and then if the 'utils

dbreplication reset all' command is executed on the Publisher - it fails with

following error:

admin:utils dbreplication reset all

Replication reset is in progress. Replication setup will continue in background.

Please watch RTMT replication state on all nodes. It should go from 0 to 2.

When all subs have an RTMT Replicate State of 2, replication setup is complete.

If RTMT Replicate State shows 4, there is an error in replication setup.

DbMon correctly signalled

command failed -- Enterprise Replication not active (62)

command failed -- Enterprise Replication not active (62)

admin:

Workaround:

-----------

None

The replication eventually establishes successfully. Use the following command

to verify the replication status on all nodes in the cluster:

"show perf query class "Number of Replicates Created and State of Replication"

If the Replicate_State counter in the output of above command is 2, then it

means that replication is good.

Status

Fixed

Severity

3 - moderate

Last Modified

In Last 2 weeks

Product

Cisco Unified Communications Manager (CallManager)

Technology

1st Found-In

6.1(1.9901.136)

Fixed-In

6.1(2.9901.43)

6.1(2.1109.1)

7.0(0.66666.1)

7.0(0.66666.2)

6.1(3.1000.16)

Hope this helps!

Rob

"May your heart always be joyful And may your song always be sung May you stay forever young " - Dylan
New Member

Re: CUCM db replication problem

Thanks Rob for this bug id, but it seems replication status is stuck on 3 for pub and 0 for sub... May be i have to wait after doing this procedure.

admin:show perf query class "Number of Replicates Created and State of Replication"

==>query class :

- Perf class (Number of Replicates Created and State of Replication) has instances and values:

ReplicateCount -> Number of Replicates Created = 393

ReplicateCount -> Replicate_State = 3

admin:show perf query class "Number of Replicates Created and State of Replication"

==>query class :

- Perf class (Number of Replicates Created and State of Replication) has instances and values:

ReplicateCount -> Number of Replicates Created = 393

ReplicateCount -> Replicate_State = 0

Thanks again.

Julien.

Hall of Fame Super Red

Re: CUCM db replication problem

Hi Julien,

You are most welcome my friend! Give it some time to repair :) Don't forget the word "eventually" in the Bug notes.

Cheers!

Rob

"May your heart always be joyful And may your song always be sung May you stay forever young " - Dylan
New Member

Re: CUCM db replication problem

Hi Rob, unfortunatly, replication is always bad. I have tried repair, reset all, cluster reset... nothing is hapenning. I will program a cluster reboot during the night.

Julien.

New Member

Re: CUCM db replication problem

Hello, just to inform that after rebooting both CUCM, replication is now OK.

Julien.

New Member

Re: CUCM db replication problem

Hi,

I am having same concern for the database repliction for subscriber2.

DB is getting replicated between Pub , Sub 1. With Sub 2, there is noreplication happening. I checked in RTMT tool also, for PUB & SUB1, the Replicated Created it shows. But for Replicated count in Sub2 it shows none.

Where in status count for Pub & Sub1 is " 3" & Sub 2 is none.   I believe it should show sattus count = "2" .

So cannot understand why count = "3"

But after using " dbreplication reset all " command, after some time when i check with " utils dbreplication status"  in Pub, it shows the error logs of replicated between Pub & Sub1. But Sub2 is still not listed in the node option within "utils dbreplication status".

What could be the reason. ?

CUCM's are in single cluster

Pub IP = 10.5.x.x /24

Sub 1 IP = 10.5.x.x

Sub 2 IP = 10.6.x.x

CUCM is different VLAN

Please suggest

Thanks & Regards,

Navin

New Member

Re: CUCM db replication problem

Can anyone advise on which release of 6.1 this is fixed in?

Bug tool advises:
Fixed in: 6.1(2.9901.43) & 6.1(2.1109.1)

Assuming these are engineering specials?
Mention in 6.1(2) release notes as open caveat.
No release notes for 6.1(2)SU1 6.1(2)SU1A

Fixed in: 6.1(3.1000.16)    6.1(3)
No mention of bug fix in 6.1(3), 6.1(3a) or 6.1(3b) release notes

6.1(3.9999.1)    Assuming this is an engineering special?

No mention of bug fix in release notes for 6.1(4), 6.1(4a), 6.1(5)

Many thanks, Michael

4608
Views
0
Helpful
7
Replies
This widget could not be displayed.