Fixes are available
IBM UrbanCode Deploy Fix Pack 3 (6.0.1.3) for 6.0.1
IBM UrbanCode Deploy Fix Pack 4 (6.0.1.4) for 6.0.1
IBM UrbanCode Deploy Interim Fix 1 for 6.0.1.4
IBM UrbanCode Deploy Fix Pack 5 (6.0.1.5) for 6.0.1
IBM UrbanCode Deploy Fix Pack 6 (6.0.1.6) for 6.0.1
IBM UrbanCode Deploy Fix Pack 7 (6.0.1.7) for 6.0.1
IBM UrbanCode Deploy Fix Pack 8 (6.0.1.8) for 6.0.1
IBM UrbanCode Deploy Fix Pack 9 (6.0.1.9) for 6.0.1
IBM UrbanCode Deploy Fix Pack 10 (6.0.1.10) for 6.0.1
IBM UrbanCode Deploy Fix Pack 11 (6.0.1.11) for 6.0.1
IBM UrbanCode Deploy Fix Pack 12 (6.0.1.12) for 6.0.1
IBM UrbanCode Deploy iFix 1 for 6.0.1.9
APAR status
Closed as program error.
Error description
When using SQLServer, you see the following kinds of errors in the log file 2013-10-25 10:08:50,248 - The ntext data type cannot be selected as DISTINCT because it is not comparable. 2013-10-25 10:08:50,249 - org.hibernate.exception.SQLGrammarException: could not execute query org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConver ter.java:92) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptio nHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2536)..... Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The ntext data type cannot be selected as DISTINCT because it is not comparable. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabase Error(SQLServerException.java:216) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQ LServerStatement.java:1515) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecut ePreparedStatement(SQLServerPreparedStatement.java:404) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmt ExecCmd.doExecute(SQLServerPreparedStatement.java:350) The SQLGrammerException is a bug specific to SQLServer, resulting from attempting to run a "DISTINCT" comparison on a deprecated datatype which does not support that operation
Local fix
There is no known workaround at this time
Problem summary
**************************************************************** * USERS AFFECTED: * * Users with Microsoft SQL Server as the UCD database * **************************************************************** * PROBLEM DESCRIPTION: * * When using SQLServer, you see the following kinds of errors * * in * * the log file * * * * 2013-10-25 10:08:50,248 - The ntext data type cannot be * * selected * * as DISTINCT because it is not comparable. * * 2013-10-25 10:08:50,249 - * * org.hibernate.exception.SQLGrammarException: could not * * execute * * query * * org.hibernate.exception.SQLGrammarException: could not * * execute * * query * * at * * org.hibernate.exception.SQLStateConverter.convert(SQLStateCo * * nver * * ter.java:92) * * at * * org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExce * * ptio * * nHelper.java:66) * * at * * org.hibernate.loader.Loader.doList(Loader.java:2536)..... * * Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: * * The * * ntext data type cannot be selected as DISTINCT because it is * * not * * comparable. * * at * * com.microsoft.sqlserver.jdbc.SQLServerException.makeFromData * * base * * Error(SQLServerException.java:216) * * at * * com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResul * * t(SQ * * LServerStatement.java:1515) * * at * * com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doEx * * ecut * * ePreparedStatement(SQLServerPreparedStatement.java:404) * * at * * com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$Prep * * Stmt * * ExecCmd.doExecute(SQLServerPreparedStatement.java:350) * * * * The SQLGrammerException is a bug specific to SQLServer, * * resulting from attempting to run a "DISTINCT" comparison on * * a * * deprecated datatype which does not support that operation * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
A fix is provided in IBM UrbanCode Deploy 6.0.1.3
Temporary fix
Comments
APAR Information
APAR number
PI06963
Reported component name
UDEPLOY
Reported component ID
5725M7700
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-11-26
Closed date
2014-02-20
Last modified date
2014-02-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
UDEPLOY
Fixed component ID
5725M7700
Applicable component levels
R500 PSN
UP
R500 PSY
UP
Document Information
Modified date:
14 October 2021