Database corrupt - cannot allocate space after upgrade to R6

I know there are a few messages talking about thus, but has anyone figured out how to prevent it?

I upgraded our servers this weekend and over half of the users are getting this error. We are restarting the server over and over again to try to rectify the situation but that is a real problem in a 24x7 environment. I am getting a lot of flak for some thing that no one at IBM/Lotus is talking about.

How are we supposed to anticipate a problem if they won’t discuss it.

This is one more thing that makes upgrading Notes a real fight.

Subject: Database corrupt - cannot allocate space after upgrade to R6

We had this same issue after upgrading our environment from 5.0.7 to 6.5. The final solution was to upgrade all mail files to ODS43. According to Lotus support, there was probably some minor data corruption there before the upgrade that R5 wasn’t picking up on. And R6 was now seeing it but could not deal with it properly unless the db was ODS43.

So if you are planning to upgrade from R5, I would go right to ODS43 instead of waiting. You can always convert back if need be.

Subject: RE: Database corrupt - cannot allocate space after upgrade to R6

We just upgraded this weekend from 5.0.11 to 6.5.4 on windows NT, and IBM still haven’t solved this issue. We’re also getting corrupt databases after the upgrade. Hope to survive until this weekend and will consider running an compact to get to ods43 file format.

Subject: Database corrupt - cannot allocate space after upgrade to R6

I had the same problem when I started using the iNotes6 mail template. When I fell back to the iNotes5 template the database corruption stopped.

Subject: RE: Database corrupt - cannot allocate space after upgrade to R6

That is not an option. The reason we upgraded was for the new mail file features.

I appreciate your response, but unless we hear from IBM, this is going to be a big problem for everyone in the future.

Subject: RE: Database corrupt - cannot allocate space after upgrade to R6

Same for us. I have an open PMR with Lotus on this issue. I tried to fight through the problem for a week running fixup and compact when needed but it was consuming too much of my time, and inconveniencing our users.