home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC65471 Status: Closed

db2look receives segmentation fault if COMMENT statement is created on
a stored procedure having more than 70 parameters.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
db2look receives segmentation if it tries to generate a DDL for 
stored procedure with more than 70 parameters and comment. 
The following steps illustrate one of the scenario. 
 
1. Create a procesure with 80 parameters, then add a comment on 
the procedure. 
$ db2 connect to sample 
$ db2 "create procesure P80 (in p1 smallint, ...<params>..., in 
p80 smallint) language sql begin end" 
$ db2 "comment on P80 is 'aaaa'" 
 
2. Run db2look with -e option. 
$ db2look -d sample -e -o db2look.out 
-- No userid was specified, db2look tries to use Environment 
variable USER 
-- USER is: DB2INST1 
-- Creating DDL for table(s) 
-- Output is sent to file: db2look.out 
Segmentation fault(coredump) 
 
The stack trace shows strcmp() refers invalid address passed by 
create_comment_ddl(). 
(dbx) where 
strcmp.strcmp() at 0x100069c88 
create_comment_ddl(char*,char*,char*,char*,char,int,FILE*,int,sq 
lca*)(??, 
??, ??, ??, ??, ??, ??, ??) at 0x100022410 
create_stored_procedure_ddl(int,char*,int,char*,int,int,char,int 
,FILE*,int,sqlca*)(??, 
??, ??, ??, ??, ??, ??, ??) at 0x100044668 
create_ddl(int*,int*,int,int)(??, ??, ??, ??) at 0x100007f94 
main(??, ??) at 0x100001f74
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2look tool.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2look receives segmentation if it tries to generate a      * 
* DDLfor stored procedure with more than 70 parameters         * 
* andcomment.The following steps illustrate one of the         * 
* scenario.1. Create a procesure with 80 parameters, then add  * 
* a commenton the procedure.$ db2 connect to sample$ db2       * 
* "create procesure P80 (in p1 smallint, ...<params>...,in p80 * 
* smallint) language sql begin end"$ db2 "comment on P80 is    * 
* 'aaaa'"2. Run db2look with -e option.$ db2look -d sample -e  * 
* -o db2look.out-- No userid was specified, db2look tries to   * 
* use Environmentvariable USER-- USER is: DB2INST1-- Creating  * 
* DDL for table(s)-- Output is sent to file:                   * 
* db2look.outSegmentation fault(coredump)The stack trace shows * 
* strcmp() refers invalid address passedby                     * 
* create_comment_ddl().(dbx)                                   * 
* wherestrcmp.strcmpcreate_comment_ddlcreate_stored_procedure_dd 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to version 9.5 fixpack 6 or later.            * 
****************************************************************
Local Fix:
Please remove comment on the stored procesure(s).
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.5 Fix Pack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66766 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.01.2010
09.09.2010
09.09.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)