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

STORED PROCEDURE MAY TRAP WITH SIGILL DURING RUNTIME PROCESSING

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Execution of a stored procedure may trap during runtime 
processing by database manager in the following stack: 
 
-------Frame------ ------Function + Offset------ 
0x0900000007049A88 sqlriSectInvoke(sqlrr_cb *, sqlri_opparm *) + 
0x090000000707C0E8 sqlrr_process_execute_request(sqlrr_cb *, 
0x090000000707C3B4 sqlrr_execute(db2UCinterface *, UCstpInfo *) 
0x0900000004FA6CC8 pvmPackage::executeSection(sqlca *, unsigned 
0x0900000004F9B504 PVM::executeQuery(unsigned int, bool) + 0x1BC 
0x0900000004F99CA4 PVM::run(void) + 0xFC 
0x0900000004F97258 pvm_entry + 0x10 
0x09000000070D635C sqloInvokeFnArgs + 0xD4 
0x0900000002F83314 sqloInvokeFnArgs@glue4D5 + 0x78 
0x090000000357CF58 sqlriInvokerTrusted(sqlri_ufob *, 
 
The trap file and db2diag.log will report the following signal: 
 
Signal #4 (SIGILL): si_addr is 0x0000000000000000, si_code is 
0x0000001E (ILL_ILLOPC:Illegal opcode.) 
 
The trap will cause instance to crash. However, trapping in this 
code path is sustainable and it should not trigger an intstance 
crash. Database manager should be able to apply the trap 
resilience and return an error message to the application which 
calls the stored procedure, without bringing down the instance.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP6 or subsequent fix pack.               * 
****************************************************************
Local Fix:
Recompiling the stored procedure may alleviate the problem.
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
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

Solution
Problem First Fixed in DB2 Version 9.7 Fix Pack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84261 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.10.2011
12.02.2013
12.02.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList