Hi

I'm doing a 4.13 to 5.1 upgrade in the lab with a copy of our production
database.  During the database installation the 40 minute counter hit zero
before the progress bar hit 100% (it was at 98% I think).  Once the counter
hit zero it extended the time by 2 hours and 40 minutes.  The progress bar
is at 100% now but I have 2 hours 35 minutes to go before I can continue the
installation.

Do I really have to wait for the extended timer to expire before continuing
or is there some way to force it to continue?

--
kris seraphine

[ Post a follow-up to this message ]

Yes.

It won't take all that time, it just allocated enough to finish...



Jonathan

On 3/23/07, Kris Seraphine <baryonyx5@gmail.com> wrote:
>
> Hi
>
> I'm doing a 4.13 to 5.1 upgrade in the lab with a copy of our production
> database.  During the database installation the 40 minute counter hit zero
> before the progress bar hit 100% (it was at 98% I think).  Once the counte
r
> hit zero it extended the time by 2 hours and 40 minutes.  The progress bar
> is at 100% now but I have 2 hours 35 minutes to go before I can continue t
he
> installation.
>
> Do I really have to wait for the extended timer to expire before
> continuing or is there some way to force it to continue?
>
> --
> kris seraphine
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>

[ Post a follow-up to this message ]

Hi Kris,

On Fri, Mar 23, 2007 at 05:10:08PM -0500, Kris Seraphine wrote:
>
> I'm doing a 4.13 to 5.1 upgrade in the lab with a copy of our production
> database.  During the database installation the 40 minute counter hit zero
> before the progress bar hit 100% (it was at 98% I think).  Once the counte
r
> hit zero it extended the time by 2 hours and 40 minutes.  The progress bar
> is at 100% now but I have 2 hours 35 minutes to go before I can continue t
he
> installation.

Chances are it won't finish at all. This is a known problem.

> Do I really have to wait for the extended timer to expire before continuin
g
> or is there some way to force it to continue?

Start a Task Manager and have a look whether you're running on a
grinding 100% CPU. If so, you may have hit the "cannot stop the database"
bug. Check whether the database service named ccm is in state "Stopping"
without ever doing so. If this is the case, go fetch yourself kill.exe
(from the W2k resource kit), find the PID of the process in question
and kick it firmly in the head. Things will resolve magically.

Do *NOT* try to kill the PID using Task Manager. Things will only get
worse. Been there, done that, almost freaked out.

HTH,
Andre.
--
The _S_anta _C_laus _O_peration
or "how to turn a complete illusion into a neverending money source"

-> Andre Beck    +++ ABP-RIPE +++    IBH Prof. Dr. Horn GmbH, Dresden <-

[ Post a follow-up to this message ]