On 9/28/07, ioffe <[EMAIL PROTECTED]> wrote:
> Our xindice 1.1b4 db just stopped functioning this morning. I tried to figure
> out the problem myself, but Xindice project is complex.
>
> Here is the stacktrace with embedded style use.
>
> org.apache.xindice.core.meta.inline.InlineMetaException: No inline metadata
> reader available for version 32
>
> org.apache.xindice.core.meta.inline.InlineMetaService.readDatabaseEntry(InlineMetaService.java:134)
>         org.apache.xindice.core.Collection.getEntry(Collection.java:729)
>         org.apache.xindice.core.Collection.getDocument(Collection.java:570)
>         
> org.apache.xindice.server.UglyBrowser.getDetailView(UglyBrowser.java:187)
>         org.apache.xindice.server.UglyBrowser.doGet(UglyBrowser.java:82)
>         org.apache.xindice.server.XindiceServlet.doGet(XindiceServlet.java:84)

it looks like collection file got corrupted. There were number of
fixes since 1.1b4 for this kind of problem.

> Please, please, please help. I need to figure out what does it mean or at
> least how to retrieve the xml content this tbl? If the content is gone then
> I am majorly screwed (since it wasn't backuped). In the collection  I have
> to files(xsd and xml). xsd file is perfectly accessable, but xml file can
> not be read anymore.

Version 1.1 has xindice_rebuild utility that can read and rebuild
collections, but I am afraid in this particular case it won't help you
- it will just skip bad record, which isn't  what you want.

How big is the collection? Does it have sensitive data in it? I can
try to recover the document or at least parts of it from the tbl file
if it is possible for you to send the file to me. Cannot guarantee
success, however....

If you decide to go this route - please send tbl file, collection
configuration (located in system SysConfig collection) and symbol
table for the collection (located in system SysSymbols collection) to
my email. In any case, create a copy of a broken collection file so it
won't be damaged more than it already is.

Natalia

Reply via email to