Can not upgrade Document Library to 5.1 EE/5.2 EE in DB2

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1 EE SP4 (5.1.7), 5.2 EE SP2 (5.2.6)
• Fix Version/s: 5.1 EE SP5 (5.1.8), 5.2 EE SP3 (5.2.7)
• Component/s: Core Infrastructure > Upgrade Framework, Environments > Databases
• Labels: None
• Environment: DB2 8.x

The upgrade process for upgrading Document Library to 5.1 EE or 5.2 EE (com.liferay.portal.upgrade.v5_2_0.UpgradeDocumentLibrary) never finishes because DB2 uses one connection to select a set of rows, and a second connection to update those rows.

The fix for this issue depends on the JDBC pooling that is used:

TOMCAT JDBC POOLING

Set the defaultTransactionIsolation attribute in the Resource element to READ_UNCOMMITTED. For example:

<Context path="" crossContext="true">
<Resource
defaultTransactionIsolation="READ_UNCOMMITTED"
name="jdbc/LiferayPool"
auth="Container"
type="javax.sql.DataSource"
driverClassName="com.ibm.db2.jcc.DB2Driver"
url="jdbc:db2:lportal"
username="db2admin"
password="lportal"
maxActive="20"
/>

C3P0

Set the following in portal-ext.properties:
jdbc.default.transactionIsolation=1

DBCP

Set the following in portal-ext.properties:
jdbc.default.defaultTransactionIsolation=READ_UNCOMMITTED

PRIMSON

Set the following in portal-ext.properties:
jdbc.default.connectionTransactionIsolation=TRANSACTION_READ_UNCOMMITTED