PUBLIC - Liferay Portal Community Edition

Liferay 6.1.1 upgrade fails with MS SQL 2008 Database: UpgradeException from UpgradeDocumentLibrary cause by type -9 as DataType for NVARCHAR

Details

  • Branch Version/s:
    6.1.x
  • Backported to Branch:
    Committed
  • Similar Issues:
    Show 4 results 

Description

Various columns in the DLFileEntry-table are created as nvarchar with SQL type -9.
When the UpgradeProcess is running, the UpgradeOptimizedResultSetHandler throws an UpgradeException due to unsupported class type -9.

Caused by: com.liferay.portal.kernel.upgrade.UpgradeException: Upgrade code using unsupported class type -9
at com.liferay.portal.kernel.upgrade.dao.orm.UpgradeOptimizedResultSetHandler._getValue(UpgradeOptimizedResultSetHandler.java:243)
at com.liferay.portal.kernel.upgrade.dao.orm.UpgradeOptimizedResultSetHandler._cacheColumnValues(UpgradeOptimizedResultSetHandler.java:193)
at com.liferay.portal.kernel.upgrade.dao.orm.UpgradeOptimizedResultSetHandler.invoke(UpgradeOptimizedResultSetHandler.java:80)
... 35 more

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Marco Beelen added a comment -

After creating a local fix for the UpgradeOptimizedResultSetHandler to start to support data class type -9 (NVARCHAR) I got an expection with type -16:
The UpgradeOptimizedResultSetHandler only supports the following java.sql.Types.
Types.BIGINT
Types.BIT
Types.BLOB
Types.BOOLEAN
Types.CLOB
Types.DOUBLE
Types.FLOAT
Types.INTEGER
Types.NUMERIC
Types.SMALLINT
Types.TIMESTAMP
Types.VARCHAR

Since Java 1.6 addition types were added to support JDBC 4.0.

public final static int BOOLEAN = 16;
public final static int DATALINK = 70;
public final static int ROWID = -8;
public static final int LONGNVARCHAR = -16;
public static final int NCHAR = -15;
public static final int NCLOB = 2011;
public static final int NVARCHAR = -9;
public static final int SQLXML = 2009;

Using a JDBC 4.0 Driver iwth a properly implemented ResultSetMetaData would these kind of exceptions.
(Note even more types are availabe in the java.sql.Types 1.6 and 1.7)

Show
Marco Beelen added a comment - After creating a local fix for the UpgradeOptimizedResultSetHandler to start to support data class type -9 (NVARCHAR) I got an expection with type -16: The UpgradeOptimizedResultSetHandler only supports the following java.sql.Types. Types.BIGINT Types.BIT Types.BLOB Types.BOOLEAN Types.CLOB Types.DOUBLE Types.FLOAT Types.INTEGER Types.NUMERIC Types.SMALLINT Types.TIMESTAMP Types.VARCHAR Since Java 1.6 addition types were added to support JDBC 4.0. public final static int BOOLEAN = 16; public final static int DATALINK = 70; public final static int ROWID = -8; public static final int LONGNVARCHAR = -16; public static final int NCHAR = -15; public static final int NCLOB = 2011; public static final int NVARCHAR = -9; public static final int SQLXML = 2009; Using a JDBC 4.0 Driver iwth a properly implemented ResultSetMetaData would these kind of exceptions. (Note even more types are availabe in the java.sql.Types 1.6 and 1.7)
Hide
Permalink
Cristhian C Lopez added a comment -

I'm having the same issue!. Help is appreciated.

Show
Cristhian C Lopez added a comment - I'm having the same issue!. Help is appreciated.
Hide
Permalink
Cristhian C Lopez added a comment -

I solved it by modifying the class UpgradeOptimizedResultSetHandler.java by adding the following.

else if (t == Types.NVARCHAR) {
      value = GetterUtil.getString(_resultSet.getString(name));
}
else if (t == Types.LONGNVARCHAR) {
      value = GetterUtil.getString(_resultSet.getString(name));
}
Show
Cristhian C Lopez added a comment - I solved it by modifying the class UpgradeOptimizedResultSetHandler.java by adding the following. else if (t == Types.NVARCHAR) { value = GetterUtil.getString(_resultSet.getString(name)); } else if (t == Types.LONGNVARCHAR) { value = GetterUtil.getString(_resultSet.getString(name)); }
Hide
Permalink
Mika Koivisto added a comment -

Affects 6.2.x too

Show
Mika Koivisto added a comment - Affects 6.2.x too

People

Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    11 weeks, 3 days ago