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

CRASH MAY OCCUR CREATING STORED PROCEDURE WITH XML QUERY WITH PASSING BY
REF ON HOST VARIABLE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Crash may occur creating stored procedure with XML query with 
PASSING BY REF on host variable 
 
Stack will show as: 
sqlriZigZagJoin.fdpr.chunk.3 
sqlriSectInvoke 
sqlrr_execute 
sqlrr_execute 
pvmPackage::executeSection 
PVM::executeQuery 
.PVM::loadImmediate 
pvm_entry 
sqlekpdb 
sqlmRoutineBegin
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Db2 Users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux,      * 
* UNIX, and Windows or later                                   * 
****************************************************************
Local Fix:
Cast the host variable as xml or set 
DB2_REDUCED_OPTIMIZATION="ZZJN OFF"
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, 
UNIX, and Windows
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.08.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)