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 IT27842 Status: Closed

A STALE SQLCA POINTER FROM SQLZESQLCODE() CORRUPTS THE STACK FRAME LEADING
TO AN ENDLESS LOOP

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
A stale SQLCA pointer from sqlzeSqlCode() corrupts the return
pointer in the stack frame leading to an endless loop

Setting up a connection idle threshold with a connect procedure
is enough to reproduce this scenario.
Repro steps:

-- Connection IDLE threshold
CREATE THRESHOLD CONIDLE FOR DATABASE ACTIVITIES ENFORCEMENT
DATABASE WHEN CONNECTIONIDLETIME > 1 MINUTES STOP EXECUTION
ALTER THRESHOLD CONIDLE ENABLE

-- Stored procedure
CREATE PROCEDURE DB2INST1.CNPROC
language sql
begin
IF ( CLIENT_HOST  'hostname' )
   THEN
      SIGNAL SQLSTATE '42502' SET MESSAGE_TEXT='Connection
refused !';--
   END IF;--
end;

-- DB config for connect_proc
db2 update db cfg using connect_proc DB2INST1.CNPROC

-- Terminate and reconnect
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.01.2019
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)