Corrupt db? Corrupt NSF? Domino problem?

We’ve had our largest Domino database blow up twice in the last couple weeks. First time we received “This function is inappropriate for file system directories” whenever opening the database. The 2nd instance was indicating the NSF was not found–but it was there. Domino could not “see” it. Fixup and Updall failed with “PANIC” errors. Only solution was to recreate database from a replica.

The database that blew up was 2.5 times the size of the “good” replica we rebuilt it from which seems odd (although the good replica is used primarily by web users versus the bad replica which is used by Notes users which access many more views). We have about 80 users on the “bad” replica.

We have plenty of horsepower on the server: 4-way processor with 1 GB memory per CPU. Separate disk controller (and disk) for data. The database is large: 10-15 GB with about 600k documents. We do some archiving of documents now–obviously need to do more.

Wondering if others encountered similar problems with databases corrupting like this? Any ideas as to possible house cleaning? We do regular (weekly) fixups, updall’s and compacts. Any possible Domino problems? I’ve not found anything searching this forum nor the PMR database.

Sorry for the length of the post–and thanks for any insight…Regards, Rick.

Subject: Corrupt db? Corrupt NSF? Domino problem?

Housecleaning may not be the issue! If you were able to rebuild the db from a REPLICA, then the problem might be caused by a user, an agent or some other action within the db. Isolate activities and validate each to ensure it is NOT causing the problem.