Upgrading using DB2 from 5.2.3, 6.0.6, or 6.0.12 to 6.1.x fails when an organization containing 53 or more characters in the name is added

• Type: Bug
• Status: Closed
• Resolution: Duplicate
• Affects Version/s: 6.1.0 CE RC1, 6.2.0 CE M2
• Fix Version/s: 6.1.10 EE GA1, --Sprint 11/12, 6.2.0 CE M2
• Component/s: Environments, Environments > Databases
• Labels: None
• Environment: Tomcat 7.0.23 + DB2 9.7. 6.1.x GIT ID: 55dbe46f7bb96f60055f0f8a65687983848822a1.; Tomcat 7.0.23 + DB2 9.7. Trunk Revision: 95545.
• Branch Version/s:
  6.1.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/3692

If a user adds an organization containing 53 or more characters to 5.2.3, 6.0.6, or 6.0.12 and upgrades to 6.1.x while using DB2, the upgrade process fails.

Here are the steps to reproduce the issue:

1. Start Liferay 5.2.3, 6.0.6, or 6.0.12
2. Add an organization that has a name consisting of at least 53 characters
3. Stop Liferay
4. Start Liferay 6.1.x
5. The upgrade process will fail and the user will see exceptions