We have found that in several R6 upgrades there was much corruption in mail files and some other databases. We now run fixup utilites both before and after the upgrade.
In instances we wound up switching mail templates in order to even get fixup to run at all.
Anyone with similar experience? Any reason?
Subject: Database COrruption after R6.0.1 Server Upgrade
Would you post the exact steps you followed before and after the upgrade process. Corruption seems to occur mostly because steps outlined in the Red Book weren’t followed exactly, or the transaction log wasn’t disabled before the upgrade.
Jeff Dayton, PCLP, CLI
Subject: RE: Database COrruption after R6.0.1 Server Upgrade
JeffTL is not enabled. These are 2 cluster servers that are in their own cluster in one office.
Steps followed were same for each server:
1.get users off
2.BAck up server
3.Run fixup,updall -v and compact
4.Install 6.0.1
5.Bring up Domino. NO to nab upgrade as it was already R6
6.Check client access,mail routing etc
7.Quit Domino
8.INSTALL HOT FIX from Lotus that fixes HTTP problem.
9.Repeat 5 and 6
10 Repeat 3
11.BAckup
12.LEt users on
On the first full day, users were getting missing or invalid doc and replication failed.
AT this point we’re about to take both systems down and run maintenance.
Subject: You missed a parameter on the compact the second time around. “compact -C”
Subject: RE: You missed a parameter on the compact the second time around. “compact -C”
LOtus support didnt think -c was needed but I take your point. The doc does agree with you.
Subject: I have found that if you do not upgrade the ODS to 4.3 (which compact -C does) you will eventually get corrupted dbs on the server.
Subject: RE: I have found that if you do not upgrade the ODS to 4.3 (which compact -C does) you will eventually get corrupted dbs on the server.
OUR problem was that compact complained it could not run and until fixup ran , this was the case.Now we may not have shut down both servers completely leading to updates via cluster replication. And in this case, fixup was not completed ok.
Thus we solved our problems by shutting down both systems first. BTW we did not run compact with -C as it is not supported.
Subject: RE: I have found that if you do not upgrade the ODS to 4.3 (which compact -C does) you will eventually get corrupted dbs on the server.
compact -c not supported by who or what ? Compact -c does copy style compaction (R4 style) which in most case (even when your run TL) a good choice just after a server upgrade and this switch is available for all of us (this is not a hidden parameter)
Anyway in the Redbook we provided some basic steps which should avoid for most of you to run in trouble (I hope so)
About TL, one of its advantage is to reduce the number of database corruption (among other benefits as well), so I have really some difficulty to imagine than disabling TL before upgrading your server will reduce the possibility to get a db corrupted
JNK
Subject: Disable transaction logging ?
We are about to upgrade from 5.0.6a and 5.0.8 to 6.0.1CF1 and I have not seen any information about disabling the transaction logging before the upgrade. Where can I find this information ?You are not alone to have problems after upgrade to D6.x , take a look at this:
Regards
Lasse
Subject: What about 2 clustered servers being upgraded
This was the worst case of corruption. I wonder if we should take both clustert servers down together and do them so they cannot impact one another during the upgrade
Thoughts?
Subject: What about 2 clustered servers being upgraded
This was the worst case of corruption. I wonder if we should take both clustert servers down together and do them so they cannot impact one another during the upgrade
Thoughts?
Subject: What about 2 clustered servers being upgraded
This was the worst case of corruption. I wonder if we should take both clustert servers down together and do them so they cannot impact one another during the upgrade
Thoughts?
Subject: RE: Database COrruption after R6.0.1 Server Upgrade
Hi Robert,
please check my previous posting:
“ncompact and nfixup problems after upgrade from 5 to 6 and my workaround”
I think you can solve it with the mentioned compact -C option - Please send us the results…
do not hesitate to ask for detailed information…
cu all
Markus
Subject: RE: Database COrruption after R6.0.1 Server Upgrade
I am facing same problem when client is replicating mail file from server
“invalid or non-existing document”
Then I run compact -c to upgrade ODS to 43 in the client side, but I cannot upgrade my server ODS
becoz…the server is running still with R5.
I cannot run Fixup in the client side becoz I dont have fixup executablein the client.