Hi Everybody
After I did mvn -U clean Pakage and ant update for dspace .cfg &
inputform.xml
I just run index init but this error comes
Anybody helps me
Exception: Unknown format version: -9
org.apache.lucene.index.CorruptIndexException: Unknown format version:
-9
at
org.apache.lucene.
Can index-init be run while the system is active? I have found in the past ( 2
yeaars ago or so) that I get sql errors.
--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability
We are upgrading from 1.6.2 to 1.7.0.
Things went well until we ran index-init. (we are using Oracle)
Here's the error message:
[dspace@DSpace bin]$ dspace index-init
Started: 1297273130922
Ended: 1297273137465
Elapsed time: 6 secs (6543 msecs)
Exception: Value for item_id is not an
HI,
Can you try adding -v afterwards to turn on verbose logging, and so we get a
bit more of what the cause might be? Also, you shouldn't need to run it as sudo?
/home/dspace/bin/index-init -v
cheers,
Steve
On 15/11/2010, at 9:56 PM, Webshet, Sisay (ILRI) wrote:
> Hi All,
>
> This is my sec
Hi All,
This is my second time to post this for you,
sudo /home/dspace/bin/index-init
Creating browse and search indexes
Exception: java.lang.ClassNotFoundException:
java.sql.SQLException: java.lang.ClassNotFoundException:
at
org.dspace.storage.rdbms.DatabaseManager.initializ
Hi All,
Iam on upgrading of dspace 1.5.2 into 1.6.2.some steps are fine,
How ever at last the following error happens. Can you tell me the reason
why please?
sudo /home/dspace/bin/index-init
Creating browse and search indexes
Exception: java.lang.ClassNotFoundException:
java
Hello ,
i am trying to update Dspace from 1.4.2 to 1.5.1 , when i generating indexes
with index-init command it throws up an error ,
Do anyone have any idea what i am doing wrong .
this is the output of the command .
[r...@localhost bin]# ./index-update
Creating browse index
Exception in thread
373-7599 x81928
http://www.library.auckland.ac.nz/
From: Jeffrey Trimble [mailto:jtrim...@cc.ysu.edu]
Sent: Friday, 17 April 2009 6:48 a.m.
To: DSpace Tech
Subject: [Dspace-tech] Index-Init failed
I've started to convert my production server to 1.5.1 and have
received
this error when issui
1142, New Zealand
Ph: 64 9 373-7599 x81928
http://www.library.auckland.ac.nz/
From: Jeffrey Trimble [mailto:jtrim...@cc.ysu.edu]
Sent: Friday, 17 April 2009 6:48 a.m.
To: DSpace Tech
Subject: [Dspace-tech] Index-Init failed
I've started to convert my production server to 1.5.1 and have
I've started to convert my production server to 1.5.1 and have received
this error when issuing index-init:
$ ./index-init
Creating browse index
Creating search index
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:
You can run index-init with the website up, but bear in mind:
1) There may be a few exceptions thrown whilst the tables are being
created (prior to population)
2) The browse lists won't be fully populated until the index-init script
has finished running (may take some time on a large repository
Can I be running index-init with the website up, or does the website
need to be down.
I just upgraded to 151 and was getting some out of memory error. I'm
thinking I needed to run index-init after the upgrade.
Thanks!
Jose
---
Jeffrey,
Page 52 is correct. Page 64 is a copy of the old comments from dspace.cfg.
The comments and example in dspace.cfg are also correct, and should have
guided you away from the erroneous information in p64 of the manual ;)
Your configuration should be:
webui.browse.index.1 = dateissued:it
Okay, I've followed the conflicting examples for the browse index
(see p. 52 vs. p. 64 of the May 2008 manual)
and here's the error I've run into the browse configuration:
Creating browse index
Exception in thread "main" org.dspace.browse.BrowseException: Browse
Index confi
guration is not v
Ran into an issue (other than the Lucene 2.3.2 issue mentioned earlier
this month). I was updating my instance, going step-by-step in the
update docs and when I got to the part to run index-init, I get an SQL
exception:
Exception in thread "main" java.lang.IllegalArgumentException: No such
col
gs
> Sent: Monday, June 09, 2008 11:20 AM
> To: Blanco, Jose
> Cc: dspace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] Index-init error
>
> Jose,
>
> There is a known corruption bug in Lucene 2.3.0, that is meant to
> be fixed in the later releases (they are
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham Triggs
Sent: Monday, June 09, 2008 11:20 AM
To: Blanco, Jose
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Index-init error
Jose,
There is a known corruption bug in Lucene 2.3.0, that is meant to be fixed in
We moved the branch to 2.3.0 some time ago, to get the improvements that
were part of that release.
But we haven't done anything since then.
If someone is able to reproduce a problem with 2.3.0, then it's an
important test to see if it has been fixed with the subsequent releases.
G
Mark Diggo
Did we upgrade this in the branch Graham?
On Jun 9, 2008, at 8:20 AM, Graham Triggs wrote:
> Jose,
>
> There is a known corruption bug in Lucene 2.3.0, that is meant to be
> fixed in the later releases (they are currently on 2.3.2)
>
> Instead of going back to an older version, can you try using
Jose,
There is a known corruption bug in Lucene 2.3.0, that is meant to be
fixed in the later releases (they are currently on 2.3.2)
Instead of going back to an older version, can you try using the latest
version of Lucene (2.3.2)?
There are some useful changes in the 2.3.x series that I would
I'm on dspace 1.5, and when I try index-init, I get these errors:
Exception in thread "Thread-267"
org.apache.lucene.index.MergePolicy$MergeException:
org.apache.lucene.index.CorruptIndexException: doc counts differ for
segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
at
org.apac
I found this on the web:
http://www.gossamer-threads.com/lists/lucene/java-dev/61151
And I do have Java(TM) SE Runtime Environment (build 1.6.0_06-b02).
Does any one have this SDK, but having it work successfully. Does this
mean that if you want to used Lucene 2.3, there are certain SDK's you
c
I'm on dspace 1.5, and when I try index-init, I get these errors:
Exception in thread "Thread-267"
org.apache.lucene.index.MergePolicy$MergeException:
org.apache.lucene.index.CorruptIndexException: doc counts differ for
segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
at
org.apac
Hi,
I had a similar problem when I tested 1.4 --> 1.5,
The problem was in the configuration file dspace.cfg
Check the values for:
${default.db.name}
${default.db.url}
${default.db.driver}
${default.db.username}
${default.db.password}
I hope this helps.
Hamish Brett wrote:
> Hi
>
> I am upgrading
Hi
I am upgrading to 1.5 from 1.4.1 when I rebuild the browse and search
indexes eith
$index-init
I receive the following error
Exception in thread "main" java.sql.SQLException:
java.lang.ClassNotFoundException:
at
org.dspace.storage.rdbms.DatabaseManager.initialize(DatabaseManager.java
25 matches
Mail list logo
