Notes database corrupts intermittently 1

[0taku3]

One of our Notes 4.5 workflow databases is corrupting intermittently.
It runs ok for a while then the server log shows
'database is corrupt -- cannot allocate space'.
The log file shows different views being opened each time the corruption occurs.

Our Systems Team have tried replication and compacting the db on the filesystem
and expanded the disk size to ensure there are no space issues.

From a design point of view, the db runs on a v5 server with v4.5 clients.
We have set all the design elements to R4 and also used NotesDocumentCollection
to ensure the agents collect all documents before working on them to prevent
any view conflicts.

The database will work again for a few days then fails. Does anybody have any
suggestions on further steps we can take to stabilise the db? Thanks.

 

[geier]

If possible make a complete new copy of the database - replication won't help you in the long run. We experience this problem from time to time with mail-databases and copy always seems to work for us. If this database is replicated to different servers or users then this will not be possible as this would change the replic-ID. I know that there is a way to manually edit the replica-ID of a database via a hex-editor-tool but personally I have never done it and can therefore give not advice about that.