<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Get a Unified Database Status report from CURT and open a TAC SR. Unless you know exactly what you are doing and exactly how your replication is broken you will very likely just make things worse.<div><br></div><div>The few docs out there aren't very thorough, but at least should be updated to not guarantee a call to TAC after following them. A comprehensive doc is in the works but not completed that I'm aware of.</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-Ryan</div></span>
</div>
<br><div><div>On Sep 16, 2010, at 1:42 PM, Afzal Bhutta wrote:</div><br class="Apple-interchange-newline">What is the best practice to fix CUCM DB-Replication issue very quickly?<br>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div><br></div></body></html>