index IX_8D83D0CE in 5.2 is unique, but in 6.1 is not unique - causes upgrade issues
Description
Environment
Liferay Version: 6.1
Operating System: Red Hat
Application Server: JBoss 5.x
Java Virtual Machine: Java 6
Database: Oracle 11g
Activity
Show:

Michael Saechang July 16, 2012 at 5:25 PM
Committed on:
Portal 6.1.x CE GIT ID: eb5ea62f1f5b148853a1cc74bb9c301f5eeb9030.
Portal 6.2.x GIT ID: 170d436cd328fe2de7ddd108a29aa7714f2dbdb2.

Barrie Selack June 28, 2012 at 8:44 AM
Need a resolution/suggestion on this as it's holding up a 6.1 upgrade.
Fixed
Details
Assignee
Michael SaechangMichael Saechang(Deactivated)Reporter
Barrie SelackBarrie Selack(Deactivated)Labels
Branch Version/s
6.1.xBackported to Branch
CommittedEpic/Theme
Fix Priority
5Git Pull Request
Components
Affects versions
Priority
Medium
Details
Details
Assignee

Reporter

Labels
Branch Version/s
6.1.x
Backported to Branch
Committed
Epic/Theme
Fix Priority
5
Git Pull Request
Components
Affects versions
Priority
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support

Linked Tickets
Created March 30, 2012 at 8:26 AM
Updated June 24, 2023 at 3:58 PM
Resolved July 16, 2012 at 5:26 PM
the index IX_8D83D0CE in a 5.2 SP3 DB has a unique constraint, and when upgrading to 6.1 throws and error (see below) but the sql scripts for 6.1 create this index as non unique. So it appears the index should be dropped and recreated during the upgrade.
14:23:23,575 ERROR [MainServlet:201] com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: java.sql.SQLException: ORA-00001: unique constraint (WBC_LIFERAY.IX_8D83D0CE) violated
com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: java.sql.SQLException: ORA-00001: unique constraint (WBC_LIFERAY.IX_8D83D0CE) violated