IBM Support

IC69396: DB2 CLIENT TRAPPED IN FUNCTION SQLEUCLOCKCONNECTION USING MSDTC

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • DB2 client trap at disconnect with the following stack.
    
    db2app!sqleUClockConnection+0x38
    [T:\db2_v97fp2\nt32\n100304\engn\include\sqleu_client_inlines.h
    @ 679]
    db2app!XADTCObject::BlockOnEvent+0x175 [sqlxadtc.C @ 1085]
    db2app!XADTCObject::Disconnect+0x1b2 [sqlxadtc.C @ 920]
    db2app!sqlxaDTCDisconnect+0xf2 [sqlxadtc.C @ 447]
    db2app!CLI_sqlDisconnect+0x406 [clisql.C @ 2781]
    db2app!SQLDisconnect2+0x339 [cliconn.C @ 6596]
    db2app!SQLDisconnect+0x769 [cliconn.C @ 6396]
    mscorwks!Thread::EndThreadAffinity+0xa8
    
    
    The trap can occur in multi threaded setup. The trap can occur
    when a thread tries to access the connection to process a
    disconnect request. But another thread had already cleaned up
    connection resources because of an error condition.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Windows applications using MSDTC                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DB2 client trap at disconnect with the following stack.      *
    *                                                              *
    * db2app!sqleUClockConnection+0x38                             *
    * [T:\db2_v97fp2\nt32\n100304\engn\include\sqleu_client_inlines.
    * @ 679]                                                       *
    * db2app!XADTCObject::BlockOnEvent+0x175 [sqlxadtc.C @ 1085]   *
    * db2app!XADTCObject::Disconnect+0x1b2 [sqlxadtc.C @ 920]      *
    * db2app!sqlxaDTCDisconnect+0xf2 [sqlxadtc.C @ 447]            *
    * db2app!CLI_sqlDisconnect+0x406 [clisql.C @ 2781]             *
    * db2app!SQLDisconnect2+0x339 [cliconn.C @ 6596]               *
    * db2app!SQLDisconnect+0x769 [cliconn.C @ 6396]                *
    * mscorwks!Thread::EndThreadAffinity+0xa8                      *
    *                                                              *
    *                                                              *
    * The trap can occur in multi threaded setup. The trap can     *
    * occur                                                        *
    * when a thread tries to access the connection to process a    *
    * disconnect request. But another thread had already cleaned   *
    * up                                                           *
    * connection resources because of an error condition.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to v9.7.3                                            *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC69396

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-22

  • Closed date

    2010-09-16

  • Last modified date

    2010-09-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC69397

Fix information

Applicable component levels

  • R970 PSN

       UP

  • R970 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC69396

Modified date: 16 September 2010