suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT24830 Status: Closed

STEPPING TQS MAY EXPERIENCE A HANG IN SITUATIONS WHEN WE ARE TRYING TO
STOP TQ DRAINING AS A PERFORMANCE OPTIMIZATION.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Stepping TQs may experience a hang in situations when we are
trying to stop TQ draining as a performance optimization.

This may result in a application/agent hang issue on this SQL
statement.

The stacks for this applciation may look similar to the
following:

thread_wait
sqloWaitEDUWaitPost
WaitRecvReady
ReceiveBuffer
sqlkq_process_ctl_msg
sqlktins
sqlritqb
sqlriSectInvoke
sqlrr_smp_router

And

thread_wait
sqloWaitEDUWaitPost
WaitRecvReady
ReceiveBuffer
getNextBuffer
sqlkd_rcv_buffer
sqlkd_rcv_get_next_buffer
sqlkd_rcv_init
sqlkdReceiveReply
sqleReceiveAndMergeReplies
sqlrigca
sqlrices
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All Platforms.                                               *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 v10.5 Fixpack 10 or later.                    *
****************************************************************
Local Fix:
db2set DB2_RUNTIME_DEBUG_FLAGS=40000000
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT24811 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.04.2018
16.07.2018
16.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)