After using succesfully zope for some time I decided to cut a bit the database size. So I went to Control Panel/Database and clicked "Pack" for objects older than 10 days. At first everything seemed to work (I returned to the management screen seeing new - smaller - Data.fs size), but when I tried to preview my pages, terrible things happened - most pages turned to be not available, instead of seeing them I saw zope errors with useless descriptions like 'Zope error: error' etc (restarting browser and zope did not helped). Happily, during the process, the Data.fs.old file was created - stopping Zope, removing all Data.fs.<sth> and overwritting Data.fs with Data.fs.old returned zope instance to the previous state. So I will not click 'Pack' anymore. Has anyone notified similar problems? What could be going on? I use binary zope 2.2.0 distribution for Linux. The database has been created and always used with this distribution (just a few weeks ago) and has never been packed. The time on the machine seem to be correct (although IIRC there happened a moment a few weeks ago when it was for the short time incorrect). I use some custom ZClasses installed as a product developed within 'this' Control Panel/Products. By the way: to decrease database size I consider: - creating new Data.fs served via another (temporary) Zope instance (via just copying Data.fs.in) - exporting everything important from my current instance - importing those files into new instance - copying new Data.fs over the old one (of course each Data.fs copying is performed while both Zope's are shut down). Will it work as expected? Will I loose anything apart bobobase_modification_time? -- Serwis dla programistów z kącikiem mieszkaniowym: http://www.mk.w.pl | | You have the right to change your mind, to substitute functionality, | and to change priorities. (Ken Beck's Third Customer Right) |