Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
If an application is interrupted in the middle of executing a SQL stored procedure, you may observe the following db2diag.log messages This occurs because the SQL procedure may not acknowledge the interrupt request immediately, potentially allowing additional SQL statements within the SQL procedure to be executed. Each subsequent statement may throw a -20139 error. This APAR will correct the interrupt checking so that the SQL stored procedure will terminate when the interrupt is received and prevent the subsequent logic in the stored procedure from continuing. 2008-08-06-11.31.41.482035-240 I1130G1039 LEVEL: Error PID : 13819 TID : 3017074352 PROC : db2agent (TEST1) INSTANCE: db2inst1 NODE : 000 DB : TEST1 APPHDL : 0-191 APPID: *LOCAL.db2inst1.080806153109 MESSAGE : Severe TERMINATE err at nest lvl 1, in SQL from rtn DB2INST1.PROCEDURE5: DATA #1 : Hexdump, 136 bytes 0xB3D0B330 : 5351 4C43 4120 2020 8800 0000 48FC FFFF SQLCA ....H... 0xB3D0B340 : 0000 2020 2020 2020 2020 2020 2020 2020 .. 0xB3D0B350 : 2020 2020 2020 2020 2020 2020 2020 2020 0xB3D0B360 : 2020 2020 2020 2020 2020 2020 2020 2020 0xB3D0B370 : 2020 2020 2020 2020 2020 2020 2020 2020 0xB3D0B380 : 2020 2020 2020 2020 5351 4C52 5230 4131 SQLRR0A1 0xB3D0B390 : 0300 1080 0300 0000 0000 0000 0000 0000 ................ 0xB3D0B3A0 : 0000 0000 0000 0000 2020 2020 2020 2020 ........ 0xB3D0B3B0 : 2020 2035 3730 3134 57014 2008-08-06-11.31.41.485960-240 I2170G764 LEVEL: Error PID : 13819 TID : 3017074352 PROC : db2agent (TEST1) INSTANCE: db2inst1 NODE : 000 DB : TEST1 APPHDL : 0-191 APPID: *LOCAL.db2inst1.080806153109 MESSAGE : sqlrr_rds_common_pre1(): DATA #1 : Hexdump, 92 bytes 0xBFEA4864 : 2D32 3031 3339 3A20 5072 696F 7220 6E65 -20139: Prior ne 0xBFEA4874 : 7374 6564 2054 4552 4D49 4E41 5445 2065 sted TERMINATE e 0xBFEA4884 : 7272 2E20 5271 7374 2061 7420 6E65 7374 rr. Rqst at nest 0xBFEA4894 : 206C 766C 2031 2066 726F 6D20 7274 6E20 lvl 1 from rtn 0xBFEA48A4 : 4442 3249 4E53 5431 2E50 524F 4345 4455 DB2INST1.PROCEDU 0xBFEA48B4 : 5245 3520 6967 6E6F 7265 642E RE5 ignored Note: After this fix the first Severe TERMINATE error will still be seen. However, the subsequent -20139 error(s) will not occur.
Local fix
Problem summary
If an application is interrupted in the middle of executing a SQL stored procedure, you may observe the following db2diag.log messages This occurs because the SQL procedure may not acknowledge the interrupt request immediately, potentially allowing additional SQL statements within the SQL procedure to be executed. Each subsequent statement may throw a -20139 error. This APAR will correct the interrupt checking so that the SQL stored procedure will terminate when the interrupt is received and prevent the subsequent logic in the stored procedure from continuing. 2008-08-06-11.31.41.482035-240 I1130G1039 LEVEL: Error PID : 13819 TID : 3017074352 PROC : db2agent (TEST1) INSTANCE: db2inst1 NODE : 000 DB : TEST1 APPHDL : 0-191 APPID: *LOCAL.db2inst1.080806153109 MESSAGE : Severe TERMINATE err at nest lvl 1, in SQL from rtn DB2INST1.PROCEDURE5: DATA #1 : Hexdump, 136 bytes 0xB3D0B330 : 5351 4C43 4120 2020 8800 0000 48FC FFFF SQLCA ....H... 0xB3D0B340 : 0000 2020 2020 2020 2020 2020 2020 2020 .. 0xB3D0B350 : 2020 2020 2020 2020 2020 2020 2020 2020 0xB3D0B360 : 2020 2020 2020 2020 2020 2020 2020 2020 0xB3D0B370 : 2020 2020 2020 2020 2020 2020 2020 2020 0xB3D0B380 : 2020 2020 2020 2020 5351 4C52 5230 4131 SQLRR0A1 0xB3D0B390 : 0300 1080 0300 0000 0000 0000 0000 0000 ................ 0xB3D0B3A0 : 0000 0000 0000 0000 2020 2020 2020 2020 ........ 0xB3D0B3B0 : 2020 2035 3730 3134 57014 2008-08-06-11.31.41.485960-240 I2170G764 LEVEL: Error PID : 13819 TID : 3017074352 PROC : db2agent (TEST1) INSTANCE: db2inst1 NODE : 000 DB : TEST1 APPHDL : 0-191 APPID: *LOCAL.db2inst1.080806153109 MESSAGE : sqlrr_rds_common_pre1(): DATA #1 : Hexdump, 92 bytes 0xBFEA4864 : 2D32 3031 3339 3A20 5072 696F 7220 6E65 -20139: Prior ne 0xBFEA4874 : 7374 6564 2054 4552 4D49 4E41 5445 2065 sted TERMINATE e 0xBFEA4884 : 7272 2E20 5271 7374 2061 7420 6E65 7374 rr. Rqst at nest 0xBFEA4894 : 206C 766C 2031 2066 726F 6D20 7274 6E20 lvl 1 from rtn 0xBFEA48A4 : 4442 3249 4E53 5431 2E50 524F 4345 4455 DB2INST1.PROCEDU 0xBFEA48B4 : 5245 3520 6967 6E6F 7265 642E RE5 ignored Note: After this fix the first Severe TERMINATE error will still be seen. However, the subsequent -20139 error(s) will not occur.
Problem conclusion
First fixed in DB2 UDB Version 9.1, FixPak 7
Temporary fix
Comments
APAR Information
APAR number
IZ29542
Reported component name
DB2 UDB ESE SOL
Reported component ID
5765F4102
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-08-11
Closed date
2009-04-17
Last modified date
2009-04-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB ESE SOL
Fixed component ID
5765F4102
Applicable component levels
R910 PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
17 April 2009