IBM Support

PI06963: RUNNING SQLSERVER RESULTS IN COM.MICROSOFT.SQLSERVER.JDBC.SQLSERVEREXCEPTION ERRORS

Subscribe

You can track all active APARs for this component.

 

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4JV8","label":"IBM uDeploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"500","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 October 2021