|
Problem IC95014
|
Status: Closed |
"DB2 PREP" IS FACING WITH SIGSEGV ERROR WHILE IT IS CALLED IN A MAKEFILE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 fixpack 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 version 10.1 fixpack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.08.2013
09.06.2014
09.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
