DB2 FOR LUW / DB2FORLUW / 970 - DB2

During processing of host variables such as VARCHAR's 
customers might be facing with the make program error exit(2) 
due to "db2 prep" receiving SIGSEGV error.  Same "db2 prep" 
command is working well on CLP command prompt but it causes a 
make error if it is called in the makefile. 
 
  Customer might see below stack trace during the processing of 
host variables declared in a declare section. Most possible host 
variables which are causing error are VARCHAR's. 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x090000000003BB20 atoi + 0x20 
0x0900000001346340 @90@sqlagp_expression__FsPs + 0x570 
0x09000000013460C0 @90@sqlagp_expression__FsPs + 0x2F0 
0x09000000013486A8 sqlagp_parse__FP13sqlagp_parsersT2 + 0xE0 
0x0900000002008280 sqlacg_decpro__FUi + 0x1DC 
0x0900000002019DC0 sqlacp_prosrc__Fv + 0x164 
0x0900000001708464 sqlacm_main__FP10sqlagi_inpP5sqlcai + 0x11C 
0x09000000016F67BC sqlaprep + 0x28C 
0x000000010004EFA4 clpbp_exe_sqlaprep__Fv + 0x1A4 
0x0000000100001A94 clp_bp_con__Fv + 0x9D4 
0x0000000100000ADC main + 0x25C 
</StackTrace>

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 fixpack 9                         * 
****************************************************************

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 version 9.7 fixpack 9

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC95014 IC95015 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

19.08.2013
18.12.2013
18.12.2013

9.7.FP9