Upgrading client ODS - what are others doing?

Hi, we are part way through upgrading all our clients from 6.5.6 to 8.5.1, but keeping the mail template on 6.5 until all users are upgraded. We have had several reports of users getting frequent crashes. I have raised a PMR and it seems that some of the problem is caused by users having databases on a very old ODS - 20 - for a local address book and local mail replica. To resolve you either have to run compact on the local databases or replace - both fiddly with remote users. My question is - are other administrators upgrading the users ODS as part of their upgrade procedure? Also are you adding the line Create_R8_databases=1 to their notes.ini? (after upgrading the mail templates that is…)WE haven’t built this into our upgrade procedure and am now concerned that we might be getting more crashes. I don’t remember seeing this as a part of the suggested users upgrade steps - would welcome any comments that could help clear this up, thanks, Anne

Subject: Approach - use the IND file extension

After upgrading the servers and then loading the 8.5 client binaries I took batches of user mail files over a period of a week off hours using the “ind” extension. Executing these commands from the console after each finishes:

load compact -c mailfiles1.ind

load convert -s -u -f mailfiles1.ind * mail85.ntf

load updall mailfiles1.ind

The IND file extension allows you to batch user mail files into a single file for execution. This is extremely helpful when you want to stage your migration and is fast.

Did this while the Domino server was running but suggest you “quit” the router while this is running. Or if you can, quit the server and then run the OS executables for compact, convert and updall.

I planned all my mail files by dumping select files into a text files and then just created the corresponding IND files under the data directory of the 8.5 mail server:

mailfiles1.ind

mail\user1.nsf

mail\user2.nsf

mail\user3.nsf

mailfiles2.ind

mail\user4.nsf

mail\user5.nsf

mail\user6.nsf

mailfiles3.ind

mail\user7.nsf

mail\user8.nsf

mail\user9.nsf

You need to list the files line by line AND make sure you add a blank line at the end. There seemed to be a bug where the last entry wasn’t recognized as an “end-of-file” and would skip it.

I suggest you try a couple mail files and watch the console to see how this works.

We upgraded from 6.5.6 to 8.5.0 . You will also need to set the resource reservation database with some update fields.

See some of my other post earlier this year. There are things to watch out for with the personal address book not upgrading . In our case the user’s PAB did not show the 8.5 design which caused problems.

Subject: ini update: Create_R85_databases=1

EOM

Subject: compact dbs required?

Hi Charles, as far as I am aware setting this on the client will mean that future dbs will becreated in the new ODS but exisiting ones will only be uogrtaded if you run compact

Also, this line doesn’t get added by default in the upgrade so presumably we will need to script a change to everyone’s ini file once the server ODS has been updsate?

Subject: ini

Looks like you can update ini settings in a desktop policy in 8.5.1 on the Custom Settings tab. You need to click a few times on the right toggle to see that hidden tab.

Also, yes, they will not get ODS 51 unless they do a copy style compact (ncompact.exe -c db.nsf) after udating the ini on existing local db’s.

A manual ini update also requires rebooting the client to take effect. Not sure on the policy way.

Subject: Do you have nsd files from the Notes Client Crashes you can send to me?

Also send the PMR number as well… Thanks!

Things should work fine on your Notes Client with older ODS versions… It’s a bug if it does not…

It would not hurt you to plan ODS Upgrades of your Notes Clients as you’ll get all the performance improvements with later ODS Versions locally… Also, for DAOS Exploitaton to work at it’s best it’s recommended you upgrade to ODS 51 on several of your local databases as well.

CREATE_R85_DATABASES=1

jpaganet@us.ibm.com

Subject: NSD & PMR

Hi JohnThanks for your reply

The PMR no was 52531 999 866

I do have the NSDs but don’t seem to be able to attach files in here and it might be a bit much to paste it all - 3 MBs worth of text per file - but they zip up nicely! The NSDs were attached to the PMR if you have access to that

Anne