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

ERROR SQL1034C/SQL1124N IF USING INLINE SQL AS PARAMETER TO STORED
PROCEDURE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Using inline sql as parameter to stored procedure could cause 
the database to come down with error SQL1034C or SQL1124N. 
 
Following example will reproduce the behaviour: 
 
CREATE TABLE db2v97.tab1( tstamp timestamp not null primary 
key)@ 
 
INSERT INTO db2v97.tab1 VALUES(current_timestamp)@ 
 
CREATE PROCEDURE db2v97.SP_MAX_TSTAMP 
( 
        IN pTimestamp TIMESTAMP 
        ,OUT pOutVal TIMESTAMP 
) 
SPECIFIC SP_MAX_TSTAMP 
DYNAMIC RESULT SETS 1 
P1: BEGIN 
        DECLARE vOutVal timestamp; 
 
        select 
          tstamp 
        into 
          vOutVal 
        from 
          db2v97.tab1 
        where 
          tstamp = pTimestamp 
        ; 
        SET pOutVal = vOutVal; 
END P1 
@ 
 
CALL db2v97.SP_MAX_TSTAMP( (select max(tstamp) from 
db2v97.tab1),?) @ 
 
 
The stack will look like following: 
 
... sqldScanInvalidate... + 0x100 
... sqldScanInvalidate...  + 0x74 
... sqlriSectInvoke...  + 0xBD4 
... sqlriSectInvoke...  - 0x788 
... sqlrr_process_execute_request...  - 0x430 
... sqlrr_execute...  + 0x240
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Using inline sql as parameter to stored procedure could      * 
* cause the database to come down with error SQL1034C or       * 
* SQL1124N.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 FixPack 1                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.09.2009
16.12.2009
16.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList