I’m facing a strange problem since I upgrade toR5.x to R6 (6.0, then 6.5 and then 6.5.1: all versions have the same problem). In a couple of 24 hours some db became double or triple the size they should have. I have found
out that I can “fix” this launching “compact -D”.
For example a db whose size appear to be 150 MB, after compact -D became 48 MB. Furthermore,
I’ve realized that this problem occur only on win-hosted servers: in fact the same server is clustered with another running on linux and on that server the db size of these db remain normal.
Now: is there a way to “definitely fix” this problem ? I do not like the idea to be enforced to launch “compact -D” each night.
I would like to understand what the problem is
and solve it. Could you help me ?
Subject: After upgrade to R6 mail db size double or triple - need to run compact -D each morning
I have seen a “growth” problem on a Compaq server a year ago, reinstalling the server and updating the raid adapter fixed it.
However this was on 5.x and only a few databases.
What is the file and view size reported by statlog in log.nsf on the server.
Subject: After upgrade to R6 mail db size double or triple - need to run compact -D each morning
Compact -D remove any Viewindex. A Viewindex is needed to show view in client. Any open of a view rebuild this index. Any index need space in database so if you or an user or an agent open this view after compact -D the view will be rebuilded an the databaser will be bigger. This is an normal process and not a bug. If you delete the view every night with compact -D The first open of the database will be take longer because viexindex must be rebuilded. The viewindex will not be replicated so that the clusterdatabse will not be bigger if you do not open it.
Subject: RE: After upgrade to R6 mail db size double or triple - need to run compact -D each morning
To second that - the default mail databases in R6 are twice as large as in R5. That is just the design elements.
However, the veiw indexs DO NOT cluster replicate - so if I open mail on server a, but not on server b, there will be a size difference. To test this, open your mail file on both - they will begin to approach the same size on each server.