<div dir="ltr"><div>We came from ccm 3.3(5) and did a complete rebuild, of the system by extracting everything from sql, because DMA was no option.</div>
<div>ccm 3.3.5 was integrated with ad, so upgrading to 4.2 and then upgrading with DMA was no option for us, as DMA is just not reliable enough. (from several experiences)</div>
<div>As the not all the enduser stuff could be migrated anyway, a rebuilt with the extracted data was our best and fastest option.</div>
<div>Migration scenario was trunk between old and new cluster, as big bang was not possible ( 100+ vg248`s). and DN`s spreadout through everywhere.</div>
<div>We were able to dynamically migrate end-users from the old to the new cluster, keeping features and apps like voicemail and ipccx, and attendant application (3rd party), and billing app.</div>
<div><br>wherever possible i try to avoid using DMA, as i just cannot rely on it.</div>
<div>also if i quote projects like these, i just can`t afford the lost hours/days and sometimes weeks because of faulty DMA behaviour. (unfortunately from experience)</div>
<div> </div>
<div>However, after upgrading the complete environment, i cannot say i have had any issues worth mentioning as unstable.</div>
<div> </div>
<div>just my 2 cents,</div>
<div> </div>
<div>erik<br></div>
<div class="gmail_quote">On Mon, Aug 11, 2008 at 9:49 PM, Carter, Bill <span dir="ltr"><<a href="mailto:bcarter@sentinel.com">bcarter@sentinel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang="EN-US" vlink="purple" link="blue">
<div>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d">What version are you coming from? I have done several 6.1.1.1000-13 installs and upgrades. No problems with 6.1.2.1000-13.</span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d">Ran into a bug this weekend when upgrading from 4.2(3) SR3 or greater to UCM 6.1(2). This bug effects upgrades from 4.2(3) to UCM version 6.X and 7.X</span></p>
<p> </p>
<p><a href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsl26081" target="_blank">CSCsl26081</a></p>
<p> </p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d">The bug involves the migration of the file "VG224_display_instance-mgcp.xml". When the install of 6.X is merging data from the DMA file, it will try to import this xml file and fail. At this point the display on UCM 6.X reads "Halted: Installation failed". You then have the option of dumping diagnostic files and starting over.</span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d">Nothing in the logs indicates what the problem is. This error appears approximately 1 hour into an upgrade.</span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d">2 Workarounds:</span></p>
<ol style="MARGIN-TOP: 0in" type="1">
<li style="COLOR: #1f497d"><span style="FONT-SIZE: 11pt">Prior to UCM 6.X Installation/Upgrade</span></li>
<ol style="MARGIN-TOP: 0in" type="a">
<li style="COLOR: #1f497d"><span style="FONT-SIZE: 11pt">Run DMA on the CM 4.2(3) publisher, correct any errors as normal</span></li>
<li style="COLOR: #1f497d"><span style="FONT-SIZE: 11pt">delete the file "VG224_display_instance-mgcp.xml" from C:\Program Files\Cisco\Bin\Xmltemp\Xml</span></li>
<li style="COLOR: #1f497d"><span style="FONT-SIZE: 11pt">Re-Run DMA on the 4.2(3) Publisher</span></li>
<li style="COLOR: #1f497d"><span style="FONT-SIZE: 11pt">Proceed with an upgrade to UCM 6.X</span></li></ol>
<li style="COLOR: #1f497d"><span style="FONT-SIZE: 11pt">After starting the UCM 6.X installation / Before Import of DMA File (at this point UCM 6.X is installing on the server and the hard drives have been formatted).</span></li>
<ol style="MARGIN-TOP: 0in" type="a">
<li style="COLOR: #1f497d"><span style="FONT-SIZE: 11pt">Go into the DMA***.tar file and delete the file. This is complicated because you don't actually want to open the file.</span></li></ol></ol>
<div class="Ih2E3d">
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span style="FONT-SIZE: 11pt"> </span></p>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p><b><span style="FONT-SIZE: 10pt">From:</span></b><span style="FONT-SIZE: 10pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Scott Voll<br>
<b>Sent:</b> Monday, August 11, 2008 2:43 PM<br><b>To:</b> Cisco VoIP<br><b>Subject:</b> [cisco-voip] CM stable @ 6.1.2.1106?</span></p></div>
<p> </p></div>
<div>
<div>
<p>I'm putting a new / upgraded CM 6.1.2 into production this weekend. Should I be running 6.1.2.1000-13 or 1106-1? any issues with either one?</p></div>
<div>
<p> </p></div>
<div>
<p>Thanks</p></div>
<div>
<p> </p></div>
<div>
<p>Scott</p></div></div></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>