suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT27842 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
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-Zusammenfassung:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.01.2019
16.01.2020
16.01.2020
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version