This message appears on many databases: “Error updating view in mail\xxx.nsf: Unable to write to database because database would exceed its disk quota”.Have I to quit the quota manually or are there any automatic solution for this?
Subject: Same prob on R6.5
Will be watching for possible solutions
Subject: Index and quotas
there is no automaic option for this. you have a quota on a mail file, that stops any increase to the size for any reason, that means view index updates can’t be built if it would push the database over quota, the only ways to stop this are to;
a. increase the quota to account for view indicies
b. remove the quota
c. use local replicas (and run the compact task on the server with the discard view indicies option every night to remove any views)
we currently use option c for our users/servers
Subject: RE: Index and quotas
Raymond,
I’m testing 6.5.3 FP1 mainly for cluster replication and quota issues with the repl_obeys_quotas (seems to be working in this release). FP1 also allowed updates of Inbox and All Documents view indexes even if this forces the DB to go over the quota.
However, I still get the same error on the server. The client can update its view indexes via CTRL+SHIFT+F9 and the error disappears but I can not fix the error when running updall on the server.
IBM, please isn’t it possible to add a notes.ini parameter that overrides all quota restrictions on server level?? This forum is full of replication, clustering, compact, transactional logging, indexing issues with quotas !!!
Stijn.