dbhelper to fix broken sql replication

[balitewiczp]

trying to fix broken sql replication. republish popup window displays

"republish must be run in the directory with replication scripts. this is usually c:\programs\cisco\bin" Is it possible DBHelper was installed to the wrong location? thanks

[Jaime Valencia]

could be, make sure the actual dblhelper file is on the folder mentioned by the error

HTH

java

if this helps, please rate

[testeven]

Hi!

Remember you can only run the DBLhelper tool in the publisher server and as he said, it must be installed under:

C:\Program Files\Cisco\Bin

Also, these links might help, the first one talks about using DBLhelper and the second one can be used when the subscription needs to be fixed (recreated) manually.

*** Using DBLHelper to Reestablish a Broken Cisco CallManager Cluster SQL Subscription ***

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801e7ddf.shtml

*** Reestablishing a Broken CallManager Cluster SQL Subscription with Cisco CallManager ***

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801d11a6.shtml

Have a nice day!

Teresa.

[balitewiczp]

thank you all for your posts

[balitewiczp]

As a follow up question, am i correct in my thinking that a broken sql replication could contribute to cdr records not working?

[Jaime Valencia]

depends, were they working before??

most usually CDRs not working might be caused by passwords out of sync or misconfiguration

HTH

java

if this helps, please rate

[testeven]

Yes, a broken SQL replication can break CDR too. If it was working before and replication failed, the CDR data will not be uploaded to the ART/CDR Database, therefore the CDR reports can fail. Probably you'll see only past records and not the recent ones.

Regards,

Tere.