Hi,
I have been searching this forum and found many suggestions concerning fixup, fixup is temporary resolving the issue, but the problem comes back the next day.
Here is the situation, users are able to enter into the database, they are able to edit the document but when saving the message “Database corrupt - Cannot allocate space” prompt. It also occurs when navigating throug some views, but not always the same views.
The database is present on several servers but the issue occurs only on 2 of them.
-
Space is not a problem
-
We have stop the replication, but issue still occuring
-
We have set all agents to run at night, but the issue still occuring sometime in the morning
Any suggestions would be appreciated.
Mikael
Subject: Database corrupt - Cannot allocate space
Hi,
Execute Load fixup, updall & Compact commands at Server Console and it should be ok.
Thanks,
Pervela Malllik Ram Sharma
Subject: Database corrupt - Cannot allocate space
In my experience you should:
1.- delete database replicas from all servers
2.- repair the source database (fixup, update, compact)
3.- if you want to be 100% sure - replace template on source database.
4.- finally, create a new replica on all servers.
And no more errors.
Good luck.
Subject: RE: Database corrupt - Cannot allocate space
Hello William,
I work in the same team as Mikael and we have already stopped all replicas of the database from and to the server in problem. There’s still a corruption.
Everytime the db is corrupted (three times a day in average) an admin Notes executes the command: load fixup -J -O -F and the bd works normally for a few hours.
There are just a few points from your response that I think we have not tried:
-
Update and compact. I think they are executed every night on the server but are there special options that we should add?
-
Replace template. What is the expected result of this? Get rid of a corrupted design element?
Thank you.
Subject: RE: Database corrupt - Cannot allocate space
It’s possible that some process/task is affecting you (on remote servers), if you have programs scheduled (disable temporaly) and then you can run directly this command on source db (fixup/compact) to see the error message… or check the domino event log. I think you should replace design to ensure all objects are Ok or create a new database from a replica and start all replication process from this one.