Upgrade 6.0.6->6.1.0 Breaks Document Library

[Andrew Carne，修改在12 年前。]

After finally getting an upgrade from 6.06->6.1.0 to at least partly work, I now seem to have everything except the Document Library (now Documents and Media) working.

If I access the document library, either through a portlet embedded in a page, or the control panel, it generates a long error dump which seems to stem from the following lines:

22:23:11,745 ERROR [JDBCExceptionReporter:75] Unknown column 'repository0_.uuid_' in 'field list'
22:23:11,755 ERROR [IncludeTag:426] Current URL /group/control_panel/manage?p_p_id=20&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&doAsGroupId=18&refererPlid=20538 generates exception: javax.servlet.ServletException: com.liferay.por
tal.kernel.exception.SystemException: com.liferay.portal.kernel.dao.orm.ORMException: org.hibernate.exception.SQLGrammarException: could not load an entity: [com.liferay.portal.model.impl.RepositoryImpl#18]
22:23:11,761 ERROR [IncludeTag:154] com.liferay.portal.kernel.exception.SystemException: com.liferay.portal.kernel.dao.orm.ORMException: org.hibernate.exception.SQLGrammarException: could not load an entity: [com.liferay.portal.model.imp
l.RepositoryImpl#18]

More of the trace can be provided if required.

[David H Nebinger，修改在12 年前。]

Well it would seem that LR thinks the database has been updated (meaning the version number is correct for 6.1), but the database update was not fully applied (hence the unknown column).

So at this point you could try to manually apply the sql to update the table, but the problem may actually be more pervasive (you fix this column only to find that there are others that are broken).

Starting the update over again might be the best path. Assuming that you're still in the testing process, I'd follow these steps:

1. Get a copy of the prod database and the data directory to the system you're doing the update on.
2. Get the 6.0.6 version of Liferay ready on the system you're doing the update on by tweaking the portal-ext.properties file.
3. Start the 6.0.6 instance, get logged in and verify all of the settings within the control panel, tweaking for the update system. Rebuild all of the indexes while you're there.
4. Make sure the entire site is functional, check the docs, the images, the journal articles, etc.

Only when the update system is ready (database is good, filesystem components are good, everything is consistent and running properly) should you attempt the 6.1 update.