cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade from 2.0 to 2.1: Some documents are not displayed

ironman77
Champ in-the-making
Champ in-the-making
Hi,

i recently upgraded from Alfresco 2.0 community to Alfresco 2.1 community. After the upgrade i noticed, that some documents & folders are not displayed in the web client.

Theses documents include:
    Instances of my own docmodel
    Freemarker-Template documents
    Folders (they are only displayed in the tree on the left-side)
Using the nodebrowser, i can see the the documents. I could also access them via  the web-service api and the download/template servlet.

Is this a upgrade related problem??
14 REPLIES 14

ironman77
Champ in-the-making
Champ in-the-making
Rebuilding the lucene index solved the issue.
Maybe this step should be added to the

http://wiki.alfresco.com/wiki/General_Upgrade_Process

guide?

seraphon
Champ in-the-making
Champ in-the-making
Hi

Can you please precise what you mean by rebuilding the lucene index?
How do you rebuild the lucene index?

Regards
Seraphon

ironman77
Champ in-the-making
Champ in-the-making
I don't know if this is the "official" way to rebuild the index, but it works:

Step 1: Stop Alfresco
Step 2: Delete everything under
<ALFRESCO_HOME>/alf_data/lucene-indexes
Step 3: Edit the following property file:
<ALRESCO_HOME>/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/repository.properties
Set the property index.recovery.mode as follows:
# The index recovery mode (NONE, VALIDATE, AUTO, FULL)
index.recovery.mode=FULL
Step 4: Start Alfresco

Watch the log file, alfresco will rebuild the lucene index. You may also want to set index.recovery.mode back to VALIDATE.

kevinr
Star Contributor
Star Contributor
Yes that is the correct way.

Kevin

gilles
Champ in-the-making
Champ in-the-making
Remember: The settings in 'custom-repository.properties' can override the 'repository.properties' (My bad experience who can maybe help someone else).

savah
Champ in-the-making
Champ in-the-making
We are having some problems with lucene indexes. Tried to rebuild the whole thing, set the mode to
# The index recovery mode (NONE, VALIDATE, AUTO, FULL)
index.recovery.mode=FULL
but it keeps on throwing exceptions when it finishes.

Just to understand…In order to rebuild the indexes is this the only step I should do or do I have to set up
# Database configuration
db.schema.update=true
db.driver=org.gjt.mm.mysql.Driver
db.name=alfresco
db.url=jdbc:mysql:///${db.name}
db.username=alfresco
db.password=alfresco
db.pool.initial=10
db.pool.max=20

to my database config? I am using SQL Server through jtds.

kevinr
Star Contributor
Star Contributor
What exceptions? Sometimes the "to text" process will through a bunch of non-fatal exceptions if the various 3rd party libraries used to perform text conversion cannot process some documents - it is not fatal and does not stop the server from starting correctly. Of course that may not be what you are seeing Smiley Happy

Kev

savah
Champ in-the-making
Champ in-the-making
Greetings kev and thanks for the reply… I will try to rebuild the indexes again today and I will post the error message…FYI It was fatal and the server did not start… :cry:

But should I set up the db properties before rebuilding or it has nothing to do with the rebuild itself ?

We have set up the dbconnection properties on to custom-repository.properties

Should I try putting index.recovery.mode=FULL there ? Will it work ?

kevinr
Star Contributor
Star Contributor
Yes index.recovery.mode=FULL in the properties file is all you need in theory.

Kev