Re: java.io.IOException: read past EOF non-corrupt index

2009-01-07 Thread 1world1love
Ok. Just to followup, I performed the same steps with another of our indexes and did not have the same issue: Opening index @ /lucenedata/index4 Segments file=segments_85 numSegments=1 version=FORMAT_HAS_PROX [Lucene 2.4] 1 of 1: name=_42 docCount=3986767 compound=true hasProx=true

Re: java.io.IOException: read past EOF non-corrupt index

2009-01-07 Thread Marcelo Ochoa
Hi: Could you try open the index using Luke but using the JDK bundled with the Oracle DB? I mean, try to use Luke as an standalone application in the same machine but outside the OJVM using the JDK at: $ORACLE_HOME/jdk which was used to compile most of the classes running inside the OJV

Re: java.io.IOException: read past EOF non-corrupt index

2009-01-07 Thread 1world1love
Michael McCandless-2 wrote: > > That exception seems to indicate that the fdx file being opened by > FieldsReader is 0 length (it's trying to read the first int from that > file). > > Is the exception repeatable, if you try again to call > IndexReader.open? > > It's odd that CheckIndex finds

Re: java.io.IOException: read past EOF non-corrupt index

2009-01-07 Thread 1world1love
Toke Eskildsen wrote: > > A quick check when a corrupt index problem is encountered: > Does any of your machines run Java 1.6.0_04-1.6.0_10b25? > Thanks Toke. As I mentioned in my response to Erick, this is complicated by the fact that the error is within a java stored procedure in Oracle. Th

Re: java.io.IOException: read past EOF non-corrupt index

2009-01-07 Thread 1world1love
Erick Erickson wrote: > > I guess my first question, based on your statement that you ran > checkindex from a different machine would be whether you have > the same version of Lucene installed on both machines? And how > did you get your index where it is now? did you optmize it in place > or d

Re: java.io.IOException: read past EOF non-corrupt index

2009-01-07 Thread Michael McCandless
That exception seems to indicate that the fdx file being opened by FieldsReader is 0 length (it's trying to read the first int from that file). Is the exception repeatable, if you try again to call IndexReader.open? It's odd that CheckIndex finds no problem with the index, but opening an IndexR

Re: java.io.IOException: read past EOF non-corrupt index

2009-01-07 Thread Toke Eskildsen
On Tue, 2009-01-06 at 23:07 +0100, 1world1love wrote: > Greetings all. I have an index that I have optimized and when I try to open > the index I get this: > > java.io.IOException: read past EOF A quick check when a corrupt index problem is encountered: Does any of your machines run Java 1.6.0_04

Re: java.io.IOException: read past EOF non-corrupt index

2009-01-06 Thread Erick Erickson
I guess my first question, based on your statement that you ran checkindex from a different machine would be whether you have the same version of Lucene installed on both machines? And how did you get your index where it is now? did you optmize it in place or did you optimize it somewhere else and

java.io.IOException: read past EOF non-corrupt index

2009-01-06 Thread 1world1love
Greetings all. I have an index that I have optimized and when I try to open the index I get this: java.io.IOException: read past EOF at org.apache.lucene.store.BufferedIndexInput.readBytes(BufferedIndexInput.java) at org.apache.lucene.index.CompoundFileReader$CSIndexInput.readInte