Prime 3.3 upgrade

[fabianwickman]

Hi,

I am in the process of performing an inline upgrade of our prime infrastructure 3.1.6 to 3.3.0.

With the installation file:

PI-Upgrade-3.3.0.0.342.tar.gz

I have been accessing the console in the VM to check in on the upgrade.

However, the installation seems stuck on this:

Step 3 of 7 : Executing Pre-install ...

And then a cursor blinkning.

I know it says that it may take som time. 

But this has taken 72 hours.

Does anyone have any similar experiences? 

Should I wait and see or abort the upgrade and do a restore from backup?

Thank you!

Best regards,

Fabian

[marce1000]

 - Abort and restore from backup.

M.

[fabianwickman]

Why? Because Prime 3.3 isn't good or because the upgrade has stalled? 

[marce1000]

 - The latter probably, it would be advisable to deploy a virgin 3.1 , restore your backup and try the upgrade again. To my opinion a 'simple restore' is not an option,because the upgrade-attempted-machine is left in an undefined state. Starting from a new deployment also has the benefit that it is probably 'more clean and neat' (for upgrading purposes).

M.

[fabianwickman]

Thanks for the reply.

I am going to wait 1-2 days more.

After that I'm thinking of deploying a new Prime 3.3 and restoring the application backup from the 3.1.6

What do you mean with "simple restore"?

[marce1000]

>wait 1-2 days  more

  Safe your breath , start now !

>install 3.3 and restore the backup

    Probably the best option

  With 'simple restore' ; I ment restoring on a box where the upgrade failed.

M.

[fabianwickman]

Well, it is a Prime with 7000 AP:s so I'll wait one more day. Because it doesn't show any errors, just a blinking cursor. 

Thank you for your input Marce. 

[fabianwickman · Accepted solution]

I did power off on the server.

The upgrade process stopped and the server was ok when it was powered on. 

The procedure then was to install maintenance release 3.1.7 and update 2.0

After that, do a "ncs cleanup" and "ncs stop".

I the tried the upgrade again, and it worked fine. 

[patoberli]

Having the same issue, but from 3.2.2 to 3.3.0. It froze at a different step though, at "Step 6 of 7 -> under step 1 of 5" (or similar like this).
Force rebooted (by pressing ctrl+alt+del) after some 20 hours of waiting at that step and now it's starting up again. Will try with the cleanup now.