Re: [Exist-open] how to manually remove corrupt resources

[RR <sec...@gm...>]

Joe, thanks for the tip to the emergency export, I hadn't tried that
yet. So I did indeed proceed with it, and while I got two error
messages, the same problem persists. Thus, I'm back to where I'm
started.

Executed:
java -jar start.jar org.exist.backup.ExportMain

Received:
ERR_DOM_INDEX:
Failed to access node 1 through dom.dbx index. Wrong storage address.
Expected: -1; got: 7108170874880 - 16534
Document ID: 30
ERR_DOM_INDEX:
Failed to access node 1.15 through dom.dbx index. Wrong storage
address. Expected: -1; got: 541767174717479 - 164924
Document ID: 46621
ERRORS FOUND.

Any way to remove these nodes manually so that I can access the rest
of my data via the administration tool (web and GUI are both hosed)?




On Sat, May 26, 2012 at 9:21 AM, Joe Wicentowski <jo...@gm...> wrote:
>>>> Trying to delete a resource via API or via REST and am failing with an
>>>> NPE coming from (final cause):
>>>> Caused by: java.lang.NullPointerException
>>>>        at org.exist.storage.NativeBroker.removeXMLResource(NativeBroker.java:2255)
>>>
>>> eXist version?
>>
>> 1.4.1
>
> I can't speak to this exact error (perhaps someone more familiar with
> the source can), but since this sounds like a database corruption
> problem, I would do a backup and restore, as outlined at
> http://exist-db.org/exist/backup.xml.  If the backup fails, use the
> Emergency Export Tool described on that page.  Then, once your data is
> recovered, I would update to eXist 1.4.2, which improves stability and
> performance -- and will hopefully prevent the type of corruption you
> experienced here.
>
> Cheers,
> Joe