We are using NIFNSF (view indexes out of db’s) for cca 6-7 months. However, some databases have regularly this problem :
“Error updating view ‘#290’ in myDB.nsf: Database is corrupt – Cannot allocate space”
In most cases we can fix this problem via deletion of indexes (> load compact -d myDB.nsf) or via creation of new replica (> load compact -REPLICA - RESTART myDB.nsf)
Do you have similar issues? How can I focus the source of problems (is there any NIFNSF debug option?)
Thanks for any tip…
Subject: Thanks, Mike…
… do you mean copy.style compact, don’t? I do not know any copy style fixup method…
Anayway - thanks, I forwarded your tip to our admins in order to try “copy - style” processing…
Subject: Backup a file copy – then fixup?
I’d do a copy-style fixup after making a file copy off the server.
If the main NOTEID index is corrupt, it’ll do this. But you could lose docs without hanging onto a backup copy and experimenting with what you can replicate-in from it.
Subject: Y’can try a compact, but copy it and try a fixup first.
Sorry, I did merge 2 thoughts, you’re right.
Subject: Fixup, Updall without success…
… after reocuring thios problem, we tried fixup resp. updall, but without success.
Finally - we had fix it via compact - d (discarding view indexes) - but I think, problem will reappear (according to our last experieneces)…