Database has maxed out at the ODS41 65 GB limit nsf "Database is corrupt - cannot allocate space"

I have a client with a very large database in R5; so large in fact that they just maxed out at 65 GB and can no longer access the database. I have copied the file to a client running R6.5.4 in an attempt to get upgrade the database to ODS43. So far, no luck at all.

It won’t open, it wont pass a consistency check (I’ve been advised to create a new replica - kind of hard whe you can’t access the database!). I tried running ncompact -m -c -i from the command line and get “Database is corrupt…”.

Does anyone out there know how to get out of this?

Subject: Database has maxed out at the ODS41 65 GB limit nsf “Database is corrupt - cannot allocate space”

There is no 65 GB “limit” in ODS41. That (64 GB, actually) was merely the maximum certified/supported size, and the maximum file size allowed under Windows NTFS (without the XP/2003 extentions). If the file was sitting on Windows and needed to exceed 64GB, then it has been truncated and likely cannot be recovered, and no, compacting to ODS43 will not allow the file to exceed the maximum file size allowed under a given operating system.

Subject: Not so sure about this…

I tested the same thing on windows server 2003 and had the exact same results (using domino 6.5.4). There seems to be some conflicting information out about this. MS says that there is not files size limit on 2003 (there is a limit but it is so large that it is not of concern for this.)

Subject: RE: Not so sure about this…

That depends on the file system. NTFS maxes out at 64GB per file, but there is an extended-length version available in 2003 that uses a secondary table to manage the associated allocation units. Like any FS, though, it has to have been set up that way when you formatted the disc/partition in the first place.