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

WHEN DB2 TRACE IS ENABLED, CALLING A DB2 Z/OS STORED PROCEDURE FROM DB2
COMMAND WINDOW, MAY CRASH DB2BP

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When calling a DB2 Stored Procedure residing on DB2 z/OS, from 
DB2 Client Command Window, and DB2 trace enabled i.e db2trc is 
on, you may experience that calling a SP may crash the DB2 
backend 
process (db2bp).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* WHEN DB2 TRACE IS ENABLED, CALLING A DB2 Z/OS STORED         * 
* PROCEDURE                                                    * 
* FROM DB2 COMMAND WINDOW MAY CRASH DB2BP                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
31.12.2012
31.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList