From: Sava J. <sju...@mr...> - 2012-02-29 19:12:01
|
Hi All, just came across the emergency and I hope someone from eXist community could help us. We have a client running older eXist version (1.2.6-rev9165) db corrupted ... when doing the Consistency Check, I can see many temp (garbage) files ... I have tried to do "Direct access" ... the tool fails! I can open java "DB Admin" tool, but can not really manipulate the data nor I can back it up. dom.dbx is around 1GB in size! Is there any way/chance someone could help us retrieve the data? Please ... and THANKS! Sava |
From: Wolfgang M. <wol...@ex...> - 2012-02-29 19:42:39
|
> db corrupted ... when doing the Consistency Check, I can see many temp > (garbage) files ... I have tried to do "Direct access" ... the tool fails! I would need to see where exactly the consistency check fails (any exception before it stops?). Maybe we could work around the error and at least restore the documents. It should usually be possible to at least restore most documents even if the collection hierarchy is damaged. The easiest way would be if you could zip dom.dbx, elements.dbx and symbols.dbx and provide them to me. Wolfgang > I can open java "DB Admin" tool, but can not really manipulate the data > nor I can back it up. > > dom.dbx is around 1GB in size! > > Is there any way/chance someone could help us retrieve the data? > > Please ... and THANKS! > > Sava > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
From: Wolfgang M. <wol...@ex...> - 2012-02-29 21:30:08
|
Sava, it seems the only collection damaged is /db/system/temp/visits, which would be ok because /db/system/temp does only store temporary resources created at query time. The export fails/hangs when it tries to clean up the temporary collection. I worked around this by commenting out the body of the method cleanUpTempResource in src/org/exist/storage/NativeBroker.java. You can do this yourself and the export should work again. The export writes some orphaned resources into /db/_lost_and_found_, but I believe those are the ones from the damaged /db/system/temp/visits collection. The temporary resources collection has been a frequent source of trouble in 1.2.x. 1.4.x and 2.0.x don't need it anymore. So updating is definitely recommended! I'll upload the archive to my dropbox and send you the link once it's there. Wolfgang |
From: Sava J. <sju...@mr...> - 2012-02-29 20:05:19
|
Wolfgang Meier <wolfgang <at> exist-db.org> writes: > > > db corrupted ... when doing the Consistency Check, I can see many temp > > (garbage) files ... I have tried to do "Direct access" ... the tool fails! > > I would need to see where exactly the consistency check fails (any > exception before it stops?). Maybe we could work around the error and > at least restore the documents. It should usually be possible to at > least restore most documents even if the collection hierarchy is > damaged. > > The easiest way would be if you could zip dom.dbx, elements.dbx and > symbols.dbx and provide them to me. > > Wolfgang > Hi Wolfgang, MANY thanks for reply ... I REALLY appreciate it! The zipped files are ~ 160MB large ... how can I send them to you? THANKS THANKS THANKS!!! Sava |