DB2 - Problem description
Problem IT21709 | Status: Closed |
CLI APPLICATION RECEIVES SIGNAL SIGSEGV DURING A CALL OF A STORED PROCEDURE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
If you have a CLI application that calls a stored procedure, it may receive a signal #11 : the first call of the SP fails with a SQL error and the DB2 CLI driver then tries to execute the statement again using more describe information received from the DB2 server. The issue happens during this describe step. example of the stack : Program received signal SIGSEGV, Segmentation fault 0x00007ffdb54b3b36 in SQLFetch2(CLI_STATEMENTINFO*, sqlca*, CLI_ERRORHEADERINFO*) () from /home/db2inst1/sqllib/lib64/libdb2o.so.1 #0 0x00007ffdb54b3b36 in SQLFetch2(CLI_STATEMENTINFO*, sqlca*, CLI_ERRORHEADERINFO*) () from /home/db2inst1/sqllib/lib64/libdb2o.so.1 #1 0x00007ffdb5517e49 in CLI_stpDescribeCall(CLI_STATEMENTINFO*, CLI_ERRORHEADERINFO*) () from /home/db2inst1/sqllib/lib64/libdb2o.so.1 #2 0x00007ffdb5515cf9 in CLI_stpRetryCall(CLI_STATEMENTINFO*, CLI_ERRORHEADERINFO*) () from /home/db2inst1/sqllib/lib64/libdb2o.so.1 #3 0x00007ffdb5466735 in SQLExecute2(CLI_STATEMENTINFO*, CLI_ERRORHEADERINFO*) () from /home/db2inst1/sqllib/lib64/libdb2o.so.1 #4 0x00007ffdb5447771 in SQLExecute () from /home/db2inst1/sqllib/lib64/libdb2o.so.1 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 FP2 * **************************************************************** | |
Local Fix: | |
Set DescribeCall to 0 in your db2cli.ini | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT16914 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.08.2017 17.10.2017 17.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |