On 01/15/2014 05:24 PM, Patrick Moens wrote: > Thanks Clemens & Sergiu, > > > Problem solved, The table space was almost full (98-99%). > > Now looking to migrate Xwiki 2.3 to 5.3 with a db of 20 gb. :/ > > Any suggestion, best practice or experiences? >
Biggest DB here has been just 10 GB ... however the main problem was about how to find places for backups. If possible, then I recommend copying the complete database and try to migrate the the copy with a separate 5.3-XWiki installation. If that works, replace the 2.3-installation with the 5.3-installation. That way, if something went wrong, you can repeat the complete process without bearing the actually running 2.3-instance. No matter how full the DB Server actually is I would recommend making at least backups before attempting a migration over 3 major release versions. The main configuration change I remember is the introduction of of the "environment.permanentDirectory" (in xwiki.properties). Because this directory also contains the index for the Solr which needs to be build after the update, expect the box to be quite a bit busy after firing up got the first time ... > > 2014/1/15 Sergiu Dumitriu <ser...@xwiki.org> > >> On 01/15/2014 06:46 AM, Clemens Klein-Robbenhaar wrote: >>> Hi Patrick, >>>> I'm working with a XWiki Enterprise 2.3 on tomcat and Oracle 10; >>>> >>>> Since 2 or 3 days, when we upload a new file to a page , the file is >>>> available during 1 min then the file size change to 0kb ; >>>> >>> It is not directly related, but I have seen a similar effect when using >> XWiki with a mySQL DB, which had a far too small "max_allowed_packet" >> config on the mySQL server. >>> Somehow an error was generated in the DB Server, but not properly >> propagated to the application. >>> >>> Maybe there is something similar in your case, even though the DB Server >> is different. There should be an error on the DB Server in that case. >>> >>> Hope this helps, >>> Clemens >> >> Yes, a database error is the general cause for this kind of behavior. >> What's happening is that the document is modified in memory to have the >> right attachment, it is placed in cache, but trying to save it to the >> database fails. As long as the document (and its attachment) is still in >> the cache, it will display fine. Once the attachment is evicted from the >> cache, trying to load it from the database will fail. >> >> However, in a transactional database I would expect the error to abort >> the whole thing and be displayed to the user when uploading. >> >> -- >> Sergiu Dumitriu >> http://purl.org/net/sergiu >> _______________________________________________ >> users mailing list >> users@xwiki.org >> http://lists.xwiki.org/mailman/listinfo/users >> _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
