Christian,
I can’t reliably reproduce the behaviour at all at the moment but I’m losing a fair number of databases to the problem. I first thought it was related to running out of disk space mid-operation but I don’t think that’s the cause. I just wanted to check that I wasn’t doing anything I shouldn’t before I try to find a reproducible error.
UPDINDEX is really useful for my use case but seems to leave me with database in GB range until I OPTIMIZE them. I shall continue monitoring.
Many thanks, James
On 8 Jan 2016, at 19:00, Christian Grün christian.gruen@gmail.com wrote:
So another question - these seem to come about from running OPTIMIZE ALL on databases with UPDINDEX TRUE. Is there any reason that OPTIMIZE ALL can’t be run on such databases?
It shouldn’t cause any problems. Here is a little command scripts that demonstrates that it should work alright:
<commands> <set option='updindex'>true</set> <create-db name='db'/> <add path='a.xml'><a/></add> <add path='b.xml'><b/></add> <optimize-all/> <info-db/> <close/> </commands>
Can you also reproduce the behavior with smaller data sets?
Thanks, Christian