IBM Support

IT07411: ODBC APPLICATIONS RETURN NO ROW AFTER UPGRADING THE DB2 GATEWAY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you have an ODBC application that connects to a DB2 server
    through a DB2 Gateway, your SELECT queries may return SQL0100W (
    (SQL_NO_DATA_FOUND ) after upgrading your DB2 Gateway to DB2
    10.5 FP4 (or later), even if those queries are supposed to
    return data.
    
    Example :
    
    DB2 Client -> DB2 Gateway ( 10.5 FP4 or FP5 ) -> DB2 Server
    
    On the DB2 client :
    
    more test.clp  :
    opt autocommit on
    opt echo on
    opt callerror on
    sqlallocenv 1
    sqlallocconnect 1 1
    sqlsetconnectattrw 1 SQL_ATTR_COMMITONEOF SQL_COMMITONEOF_ON
    SQLDriverConnectW 1 0 "DSN=SAMPLE;uid=user;pwd=password;" -3 255
    SQL_DRIVER_NO_PROMPT
    sqlallocstmt 1 1
    sqlexecdirectw 1 "select 'RESULT' from sysibm.sysdummy1" sql_nts
    sqlfreestmt 1  SQL_CLOSE
    killenv 1
    
    db2cli < test.clp
    ....
    > sqlexecdirectw 1 "select 'RESULT' from sysibm.sysdummy1"
    sql_nts
    SQLExecDirect: rc = 100 (SQL_NO_DATA_FOUND)
    ....
    

Local fix

  • add the following parameter in your db2dsdriver.cfg file
        <parameter name="CommitOnEOF" value="0"/>
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ODBC users with DB2 z/OS server                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 10.5 FP7 or later                             *
    ****************************************************************
    

Problem conclusion

  • The problem was first fixed in DB2 10.5 FP7
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT07411

  • Reported component name

    DB2 CONNECT

  • Reported component ID

    DB2CONNCT

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-02

  • Closed date

    2016-01-19

  • Last modified date

    2016-01-19

  • 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

    DB2 CONNECT

  • Fixed component ID

    DB2CONNCT

Applicable component levels

  • RA50 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.5","Edition":""}]

Document Information

Modified date:
19 January 2016