Can't compact to ODS 43 from 41

HCL Domino Domino Forum
1

I recently upgraded a server to 6.0.3 from 5.0.12 and the ODS version on certain mail files will not upgrade from 41 to 43. I’ve tried offline compact as well as regular compact without any luck. Oddly compact is still doing it’s job by reducing file size but ODS remains at 41. I’ve even tried converting the design to a 6 format… nothing. Here is what I did as far as compact is concerned.

ie.

ncompact mail\file.nsf -c

ncompact mail\file.nsf -c -i -K -F

load compact mail\file.nsf -c

load compact

I’ve used other flavors as well. Has anyone experienced this problem? I my servers are in a clustered environment and I desperately want to replicate unread marks (it’s finally fixed). Without ODS 43 I’m OFL.

Thx in advance!!! Geoff

2

Subject: Can’t compact to ODS 43 from 41

I figured it out… I open the database in notespeak and discovered the field “creation class” was equal to “V5NoteFile”. That being the case, compact would not upgrade the ODS. Now if it was set to the default of “NoteFile” compact would work. I think. I had to copy the database with a new name. Now it’s ODS43.

3

Subject: RE: Can’t compact to ODS 43 from 41

I just ran into the same issue while doing an email database restore. I found that I had to run fixup on database before I could run compact to upgrade the ods. Give it a shot. It works slick.

4

Subject: Can’t compact to ODS 43 from 41(how to reset the creation-class of a db to ‘NoteFile’ from ‘V5NoteFile’)

Hans/Geoff,

I’m experiencing the same problem and can’t upgrade the ODS of recently upgraded mail files from ODS 41 to 43. I see the ‘V5NoteFile’ flag against the db creation-class entry in NotesPeek but am unable to reset it to ‘NoteFile’ by running the fixup task against the db in question.

You say you successfully reset this using fixup, can you detail how? What options did you use? where did you initiate the command? from the server console | command line | Admin client?

Any help would be greatly appreciated, thanks in advance.

Adam

5

Subject: *try compact -d. if that doesn’t work create a new replica.

6

Subject: RE: *try compact -d. if that doesn’t work create a new replica.

Thanks Wayne, but no joy.

I’ve logged this with IBM support who tell me that once the db creation-class is set, there is no way to change it.

Looks like the new replica route.