Re: No inline metadata reader available for version 109
Natalia Shilenkova <[email protected]> Mon, 24 Jan 2011 21:50:54 -0500
| Newsgroups | gmane.text.xml.xindice.user |
|---|---|
| Message-ID | <[email protected]> |
On Jan 24, 2011, at 12:27 PM, Andre Juffer wrote: > Due to an expected crash of a server, a few (3) entries in the XML = database were corrupted. All but one could be restored from backup, by = deleting the affected entry and uploading the entry from backup. In all = these cases, the affected entry lost some data, causing XML parsing = errors. >=20 > However, in one case, I receive the following error: >=20 > No inline metadata reader available for version 109 >=20 > This prevents me to read or write that entry in question. All actions = cause the above error message to appear. This is very unfortunate as = XIndice has been extremely stable for years now. For the backup, I also = extract all entries into the separate location (in addition to just = copying the actual database), but now of course the extraction actually = fails: >=20 >=20 > [WARN] XMLCompressedInput - -invalid node type : 5 > [WARN] XMLCompressedInput - -invalid node type : 5 > [WARN] ElementImpl - -ignored exception = <java.io.EOFException>java.io.EOFException > at java.io.DataInputStream.readShort(DataInputStream.java:298) > at = org.apache.xindice.xml.dom.ElementImpl.loadAttributes(ElementImpl.java:175= ) > ..... > [WARN] ElementImpl - -ignored exception = <java.lang.NullPointerException>java.lang.NullPointerException > at = org.apache.xindice.xml.dom.ElementImpl.loadAttributes(ElementImpl.java:184= ) > ... >=20 > What would be the appropriate course of action to resolve this issue. = Is there a way to extract the binary file in another way (not XML-based) = so that I manually delete the affected entry. >=20 > XIndice version: v1.1b5-dev >=20 Andre, Are you trying to retrieve the corrupted document from the database or = just delete it? If it is the latter, then the simplest way, I think, is = to create new empty collection and load the existing documents. Does the exception for XMLCompressedInput happen for the same collection = and the same corrupt document or for some unrelated backup collection? Regards, Natalia > --=20 > Andre H. Juffer | Phone: +358-8-553 1161 > Biocenter Oulu and | Fax: +358-8-553-1141 > Department of Biochemistry | Email: [email protected] > University of Oulu, Finland | WWW: www.biochem.oulu.fi/Biocomputing/ > StruBioCat | WWW: www.strubiocat.oulu.fi > NordProt | WWW: www.nordprot.org > Triacle Biocomputing | WWW: www.triacle-bc.com