[cisco-voip] CUCM 4.2(3) to 6.1

[Nick Griffin]

So I've proceeded to dump CDR data, and re-run the dma tool again. This time
I let the tool run for 12-13 hours where it sat at the validating phase
until we cancelled it early this morning. Others have mentioning disabling
the CCM service on the publisher and running it again. Should I give this a
try, are there any potential side affects that could affect the upgrade? I
realize the lack of functionality with the pub unavailable is an issue. At
this point I have no errors that are sticking out, and really nothing to go
on. I'll have to wait to see what tac says.

On Wed, Mar 5, 2008 at 3:30 PM, James Buchanan <jbuchanan at ctiusa.com> wrote:

> Yes, I've seen it take about that long.
>
> ----- Original Message -----
> From: Nick Griffin <nick.jon.griffin at gmail.com>
> To: James Buchanan
> Cc: cisco-voip at puck.nether.net <cisco-voip at puck.nether.net>
> Sent: Wed Mar 05 16:25:10 2008
> Subject: Re: [cisco-voip] CUCM 4.2(3) to 6.1
>
> Have you personally seen it take that much longer? The issue is it pegs
> the cpu at 100%, causing some issues. Thanks
>
>
> On Wed, Mar 5, 2008 at 3:06 PM, James Buchanan <jbuchanan at ctiusa.com>
> wrote:
>
>
>        Sometimes, purging the CAR/CDR data can speed this up. Otherwise,
> just wait it out.
>
>
>
>        From: cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] On Behalf Of Nick Griffin
>        Sent: Wednesday, March 05, 2008 2:56 PM
>        To: cisco-voip at puck.nether.net
>        Subject: [cisco-voip] CUCM 4.2(3) to 6.1
>
>
>
>        I'm attempting to run the DMA 6.1.1a tool to gather data from a
> publisher at 4.2(3). Prior to running dma I ran the upgrade assistant to
> make sure things are in order, replication/etc. The process appears to get
> through the initial phases very quickly, it then reaches the end stages of
> accessing and validating the database, it estimates 48 minutes. The first
> time I let it ran well over an hour, closer to 2 however it never completed.
> I cancelled the export, and there were two warning for 2 users with invalid
> primary extensions. It ended up creating the tar file (around 45MB, this
> seems small!) I've since fixed those issues and have attempted to run the
> dma again and it appears to again be hanging. Has anyone ran into this
> situation? I am currently awaiting a response from tac.
>
>
>
>        Thanks in advance,
>
>
>
>        Nick Griffin
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080306/567e14c5/attachment.html