Issues while Upgrading to SC5

[outlance]

Hi,

I'm not sure, but while performing the upgrade
on a test system (WinNT), the upgrade hanged and
the reason seems to be the screensaver.

So better switch it off before upgrading.

[outlance]

Other issues:

- perform a mass update on SYSBLOB and switch from problem to
probsummary
- add an alias field to the following dbdicts: contacts, incidents, probsummary, etc. In case of probsummary it is called: number.attach
- in the following and some more formats change property of subformats (virtual joins) : Display Using Table: "Yes"

[pelopennes]

Checklist:

Make sure, that Client side load/unload is deactivated while applying an
upgrade!!! Otherwise upgrade crashes and you don't know why!

Make changes in dbdict before applying test and custom upgrade!

Perform Mass Update on SYSBLOB and change application="problem" to application="probsummary".

After applying an upgrade in production remove ALL displayoptions and
load the displayoptions from your upgrade-development system (where
you performed the conflict resolution) from OS command line in RUN
directory (file.load displayoption.unl NULL NULL winnt) or unix.

Perform LFSCAN and LFMAP after backing up Production and before
applying the upgrade

[outlance]

Checklist:

If you test the going live by applying your custom upgrade to a copy
of a production system, answer the following question with "no":

Are you going to use this system to create a custome upgrade for
another system?


Create a DEFAULT record in table "inboxgrid", otherwise the favourite
inbox feature in sc.manage.... forms doesn't work.

[bieniekrobert]

Also during the upgrade process, i ran into issues with Change Management especially if your system is pushed out to RDBMS. When you are going through the upgrade wizard, there is a step were ServiceCenter ask you wither or not if you want to ServiceCenter to push out the Change Management tables. Select No. The reason is that when i have reached 97% of the upgrade process done. The upgrade bombs out and it does not start back where you left off. It starts all over again. :evil: I reported the problem to Peregrine HD. The only thing that they suggest is to select NO when ServiceCenter ask you if you want the system to do the push. Trust me the extra step of manually pushing out 3 tables is worth it instand of sitting there again for hours watching the upgrade process run. This will relieve alot of stress and headache.