Upgrade 4.6.7 to 6.0.2CF2: Be Careful with multi-server environment

Strange things can happen, when you upgrade from 4.6.7 to 6.0.2

We upgraded one (out of two) server to 6.0.2. We did not want to upgrade the other one, it was obsolet after the upgrade.

We replicated all the databases to the new server.

To be sure, that all the databases where complete on the new server, I startet a

Repl NewServer/Org

on the console of the old server

BIG MISTAKE !

The templates pubnames.ntf and pernames.ntf are still replicas of the same templates in R4.

They replicated and afterwards I had mixed R4 / R6 templates.

I dont know, if any documentation warns you to replicate templates between R4 and R6 servers… But if there is no documentation: Please create it, so that nobody else gets this error (we had to copy working templates from a working installation)

Hope that helps anyone to avoid this issue

Regards

Torsten

Subject: Upgrade 4.6.7 to 6.0.2CF2: Be Careful with multi-server environment

Hello Torsten,

As part of your migration to R6 you should upgrade the R4 address book to the new release and administer it from the R6 client. I believe this is documented somewhere, probably the ibm redbook for migrating to R6 would be a good place to start.

It should not matter that the personal address book design is updated as you users will not normally receive template updates from the server to their local address book.

Cheers

Kristina