|
Problem IC65710
|
Status: Closed |
DB2 GET SIGNAL 11 DURING THE ROLLBACK PROCESS WHEN CALLING NESTED STORE PROCEDURE IN DPF |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When customer is calling nested store procedure, some errors may
happen (such as dead lock), and the transaction may be rolled
back.
During the rollback process, DB2 may trap with signal #11 with
below call stacks:
...
(4) 0xe0000001304fe900 ---- Signal 11 (SIGSEGV) delivered ----
(5) 0xc0000000180a9a01
_Z19sqlri_send_dss_msgsP8sqlrr_cbP10sqlri_ssobP23connect_msg_lis
t_anchorPsi
+ 0x221 at sqlri_dss.C:2076
[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so]
(6) 0xc0000000180a5cd0 _Z9sqlri_dssP8sqlrr_cb + 0xcb0 at
sqlri_dss.C:1219 [/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so]
(7) 0xc0000000156c6d00
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x240
[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so]
(8) 0xc000000015235200
_Z29sqlrr_process_execute_requestP8sqlrr_cbi + 0x640 at
sqlrr_sql.C:1257 [/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so]
(9) 0xc00000001529e440
_Z13sqlrr_executeP14db2UCinterfaceP9UCstpInfo + 0x740
[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so]
or
5 sqlriecc
6 sqlra_close_section
7 sqlra_sqlC_free_section
8 sqlra_sqlC_free_sibling
9 sqlra_sqlC_rmv_invoc_siblings
10 sqlrr_destroy_invocation_cb
11 sqlrr_chk_destroy_invocation_cb
12 sqlrr_end_invocation
In the db2diag.log, customer may see below message indicating a
rollback is happening:
2009-01-01-00.00.00.000000+000 I111111111A111 LEVEL: Severe
PID : XXXXX TID : 1 PROC :
db2agent (DBNAME) 0
INSTANCE: db2inst1 NODE : 000 DB : DBNAME
APPHDL : 0-XXX APPID: XXXXXXXX
AUTHID : DB2INST1
FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20
MESSAGE : Received sqlcode -1229 (rollback) for request 80000017
(interrupt) from node number 0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When customer is calling nested store procedure, some *
* errorsmayhappen (such as dead lock), and the transaction *
* may berolledback.During the rollback process, DB2 may trap *
* with signal #11withbelow call stacks:...(4) *
* 0xe0000001304fe900 ---- Signal 11 (SIGSEGV) *
* delivered----(5) *
* 0xc0000000180a9a01_Z19sqlri_send_dss_msgsP8sqlrr_cbP10sqlri_ss
* 0x221 at *
* sqlri_dss.C:2076[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so](6) *
* 0xc0000000180a5cd0 _Z9sqlri_dssP8sqlrr_cb + 0xcb0 *
* atsqlri_dss.C:1219 *
* [/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so](7) *
* 0xc0000000156c6d00_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm
* + 0x240[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so](8) *
* 0xc000000015235200_Z29sqlrr_process_execute_requestP8sqlrr_cbi
* + 0x640 atsqlrr_sql.C:1257 *
* [/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so](9) *
* 0xc00000001529e440_Z13sqlrr_executeP14db2UCinterfaceP9UCstpInf
* + 0x740[/opt/IBM/db2/V9.1.6.SP/lib64/libdb2e.so]or5 *
* sqlriecc6 sqlra_close_section7 *
* sqlra_sqlC_free_section8 sqlra_sqlC_free_sibling9 *
* sqlra_sqlC_rmv_invoc_siblings10 *
* sqlrr_destroy_invocation_cb11 *
* sqlrr_chk_destroy_invocation_cb12 *
* sqlrr_end_invocationIn the db2diag.log, customer may see *
* below messageindicating arollback is *
* happening:2009-01-01-00.00.00.000000+000 I111111111A111 *
* LEVEL: SeverePID : XXXXX TID : 1 *
* PROC :db2agent (DBNAME) 0INSTANCE: db2inst1 NODE *
* : 000 DB : DBNAMEAPPHDL : 0-XXX *
* APPID: XXXXXXXXAUTHID : DB2INST1FUNCTION: DB2 UDB, base sys *
* utilities, sqleMergeSqlca,probe:20MESSAGE : Received sqlcode *
* -1229 (rollback) for request80000017(interrupt) from node *
* number 0 *
****************************************************************
* RECOMMENDATION: *
* Update to version 9.7 fix pack 2. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
This problem is first fixed in version 9.7 fix pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.01.2010
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
