index warning after alfresco upgrade

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

gregkinmd

Hello,
We have a repository that dates back a while and has been upgraded several times to keep up with alfresco.   We recently upgraded to Alfresco 3.3 and all of our data seems to be in tact,  however,  when alfresco starts up with a full index I get some unusual errors in log file.

[repo.dictionary.DictionaryDAO] Type not found: {http://www.alfresco.org/model/application/1.0}projectfolder

My colleague and I believe that the data model used to create this content in the older version of alfresco is no longer available in 3.x.  I would like to know how to get rid of these errors.  Is there a way I can determine which folders in the repository are causing these errors, or perhaps make some changes to custom-repository.xml to correct the issue.

Any advice would be appreciated.


Thanks,
Greg

marcelogodois

I have the same problem, but with old nodes that should not exist anymore and its types doesn't exist neither. It seems to be an inconsitent database.

As long as I get the error at the lucene indexes build. I can't, evidently, find them out by lucene searches. Is there another way to find out those nodes and delete them? Maybe directly in the database for example? A way to check inconsistents database up?

Ex.: bellow the failed lucene indexation. It should not exist any node of the following type, because the type doesn't exist anymore. And all its nodes should be deleted. But It seems they are still in the database.

WARN  [repo.dictionary.DictionaryDAO] Type not found: {http://www.company.com/model/application/1.0}docRapportPaiement

Tks