Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a 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
DB2 agent process may get signal 11(SIGSEGV) and then the whole DB2 instance will crash. After receiving this signal 11, in db2diag.log you will following messages: ========================================================= 2008-06-21-18.19.23.518986+480 I1944935A518 LEVEL: Error PID : 12345 TID : 1 PROC : db2agent (SAMPLE) 0 INSTANCE: DB2INST NODE : 000 DB : SAMPLE APPHDL : 0-123 APPID: 11.222.333.44.55555.01234567891 AUTHID : DB2INST FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:1 MESSAGE : Error in agent servicing application with coor_node: DATA #1 : Hexdump, 2 bytes 0x9FFFFFFFFFFECF70 : 0000 .. ........................................................ 2008-06-21-18.19.23.861824+480 I1949696A536 LEVEL: Error PID : 12345 TID : 1 PROC : db2agent (SAMPLE) 0 INSTANCE: DB2INST NODE : 000 DB : SAMPLE APPHDL : 0-123 APPID: 11.222.333.44.55555.01234567891 AUTHID : DB2INST FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:10 MESSAGE : Error in agent servicing application with APPLICATION NAME: DATA #1 : Hexdump, 11 bytes 0xC0000008ED4B1466 : FFFF FFFF FFFF FFFF FFFF FF appl_name ========================================================= We may confirm this issue from the call stack within the trap file generated for DB2 agent process when DB2 crashed. Before getting signal 11, the call stack in DB2 agent process may look like this: ========================================================= (5) 0xc00000000e7d5c81 _Z19sqlri_send_dss_msgsP8sqlrr_cbP10sqlri_ssobP23connect_msg_lis t_anchorPsi + 0x221 at sqlri_dss.C:2076 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (6) 0xc00000000e7d1f70 _Z9sqlri_dssP8sqlrr_cb + 0xcb0 at sqlri_dss.C:1219 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (7) 0xc00000000e7fb8a0 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x240 at /view/db2_v91fp5_hpipf64_s080512/vbs/engn/include/sqlri_inlines. h:3132 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (8) 0xc00000000e4b1090 _Z29sqlrr_process_execute_requestP8sqlrr_cbi + 0x2170 at sqlrr_sql.C:1257 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (9) 0xc00000000e47e240 _Z13sqlrr_executeP14db2UCinterfaceP9UCstpInfo + 0x740 at sqlrr_req_sql.C:772 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (10) 0xc00000000b88f1f0 _Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP14sqljsDDMObject + 0x420 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (11) 0xc00000000b8c1620 _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP14sqljsDDMObjectP14db2 UCinterface + 0x340 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (12) 0xc00000000b964970 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x230 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (13) 0xc00000000b9276b0 _Z10sqljsSqlamP14db2UCinterfaceP13sqle_agent_cbb + 0x230 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (14) 0xc00000000b834ba0 _Z18sqljsDriveRequestsP13sqle_agent_cbP11UCconHandle + 0x100 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (15) 0xc00000000b8adb10 _Z22sqljsDrdaAsInnerDriverP17sqlcc_init_structb + 0x4f0 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (16) 0xc00000000b8351d0 _Z17sqljsDrdaAsDriverP17sqlcc_init_struct + 0x110 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (17) 0xc00000000b9230e0 _Z12sqleRunAgentPcj + 0x840 at sqleagnt.C:1585 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (18) 0xc00000000ba464b0 _Z13sqloCreateEDUPFvPcjES_mP13SQLO_EDU_INFOPi + 0x690 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] ========================================================= Or like this: ========================================================= (5) 0xc00000000bbcc511 _Z8sqlrieccP8sqlrr_cbiii + 0x2a51 at sqlri_mpp.C:675 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (6) 0xc00000000b7ad850 _Z19sqlra_close_sectionP8sqlrr_cbP25sqlra_sql_context_siblingiii iiii + 0x190 at /view/db2_v91fp5_hpipf64_s080512/vbs/engn/include/sqlra_inlines. h:906 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (7) 0xc00000000b7aedb0 _Z27sqlrr_process_close_requestP8sqlrr_cbiiii + 0xb30 at sqlrr_sql.C:285 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (8) 0xc00000000b7883d0 _Z11sqlrr_closeP14db2UCinterfaceP15db2UCCursorInfo + 0x230 at sqlrr_req_sql.C:2283 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (9) 0xc000000009cdcbd0 _Z16sqljs_ddm_clsqryP14db2UCinterfaceP14sqljsDDMObject + 0x2b0 at sqljsqry.C:2170 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (10) 0xc000000008bc16c0 _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP14sqljsDDMObjectP14db2 UCinterface + 0x3e0 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (11) 0xc000000008c64970 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x230 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (12) 0xc000000008c276b0 _Z10sqljsSqlamP14db2UCinterfaceP13sqle_agent_cbb + 0x230 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (13) 0xc000000008b34ba0 _Z18sqljsDriveRequestsP13sqle_agent_cbP11UCconHandle + 0x100 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (14) 0xc000000008badb10 _Z22sqljsDrdaAsInnerDriverP17sqlcc_init_structb + 0x4f0 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (15) 0xc000000008b351d0 _Z17sqljsDrdaAsDriverP17sqlcc_init_struct + 0x110 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (16) 0xc000000008c230e0 _Z12sqleRunAgentPcj + 0x840 at sqleagnt.C:1585 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (17) 0xc000000008d464b0 _Z13sqloCreateEDUPFvPcjES_mP13SQLO_EDU_INFOPi + 0x690 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] ========================================================= There may be more symptoms than the two call stacks shown above as it's not easy to say exactly what applications will fail in this issue. If you could ensure whether you hit this APAR or not, please contact IBM support for help. . Note that this APAR completes the fix in IZ19154. If IZ19154 has been applied, then this APAR should be applied as well.
Local fix
Problem summary
User Affected: All users of V9.1 on Linux, Unix and Windows platforms. Problem Abstract: DB2 agent process may get signal 11 and then cause DB2 instance crash. Problem Description: DB2 agent process may get signal 11(SIGSEGV) and then the whole DB2 instance will crash. After receiving this signal 11, in db2diag.log you will following messages: ========================================================= 2008-06-21-18.19.23.518986+480 I1944935A518 LEVEL: Error PID : 12345 TID : 1 PROC : db2agent (SAMPLE) 0 INSTANCE: DB2INST NODE : 000 DB : SAMPLE APPHDL : 0-123 APPID: 11.222.333.44.55555.01234567891 AUTHID : DB2INST FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:1 MESSAGE : Error in agent servicing application with coor_node: DATA #1 : Hexdump, 2 bytes 0x9FFFFFFFFFFECF70 : 0000 .. ........................................................ 2008-06-21-18.19.23.861824+480 I1949696A536 LEVEL: Error PID : 12345 TID : 1 PROC : db2agent (SAMPLE) 0 INSTANCE: DB2INST NODE : 000 DB : SAMPLE APPHDL : 0-123 APPID: 11.222.333.44.55555.01234567891 AUTHID : DB2INST FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:10 MESSAGE : Error in agent servicing application with APPLICATION NAME: DATA #1 : Hexdump, 11 bytes 0xC0000008ED4B1466 : FFFF FFFF FFFF FFFF FFFF FF appl_name ========================================================= We may confirm this issue from the call stack within the trap file generated for DB2 agent process when DB2 crashed. Before getting signal 11, the call stack in DB2 agent process may look like this: ========================================================= (5) 0xc00000000e7d5c81 _Z19sqlri_send_dss_msgsP8sqlrr_cbP10sqlri_ssobP23connect_msg_lis t_anchorPsi + 0x221 at sqlri_dss.C:2076 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (6) 0xc00000000e7d1f70 _Z9sqlri_dssP8sqlrr_cb + 0xcb0 at sqlri_dss.C:1219 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (7) 0xc00000000e7fb8a0 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x240 at /view/db2_v91fp5_hpipf64_s080512/vbs/engn/include/sqlri_inlines. h:3132 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (8) 0xc00000000e4b1090 _Z29sqlrr_process_execute_requestP8sqlrr_cbi + 0x2170 at sqlrr_sql.C:1257 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (9) 0xc00000000e47e240 _Z13sqlrr_executeP14db2UCinterfaceP9UCstpInfo + 0x740 at sqlrr_req_sql.C:772 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (10) 0xc00000000b88f1f0 _Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP14sqljsDDMObject + 0x420 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (11) 0xc00000000b8c1620 _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP14sqljsDDMObjectP14db2 UCinterface + 0x340 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (12) 0xc00000000b964970 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x230 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (13) 0xc00000000b9276b0 _Z10sqljsSqlamP14db2UCinterfaceP13sqle_agent_cbb + 0x230 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (14) 0xc00000000b834ba0 _Z18sqljsDriveRequestsP13sqle_agent_cbP11UCconHandle + 0x100 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (15) 0xc00000000b8adb10 _Z22sqljsDrdaAsInnerDriverP17sqlcc_init_structb + 0x4f0 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (16) 0xc00000000b8351d0 _Z17sqljsDrdaAsDriverP17sqlcc_init_struct + 0x110 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (17) 0xc00000000b9230e0 _Z12sqleRunAgentPcj + 0x840 at sqleagnt.C:1585 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (18) 0xc00000000ba464b0 _Z13sqloCreateEDUPFvPcjES_mP13SQLO_EDU_INFOPi + 0x690 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] ========================================================= Or like this: ========================================================= (5) 0xc00000000bbcc511 _Z8sqlrieccP8sqlrr_cbiii + 0x2a51 at sqlri_mpp.C:675 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (6) 0xc00000000b7ad850 _Z19sqlra_close_sectionP8sqlrr_cbP25sqlra_sql_context_siblingiii iiii + 0x190 at /view/db2_v91fp5_hpipf64_s080512/vbs/engn/include/sqlra_inlines. h:906 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (7) 0xc00000000b7aedb0 _Z27sqlrr_process_close_requestP8sqlrr_cbiiii + 0xb30 at sqlrr_sql.C:285 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (8) 0xc00000000b7883d0 _Z11sqlrr_closeP14db2UCinterfaceP15db2UCCursorInfo + 0x230 at sqlrr_req_sql.C:2283 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (9) 0xc000000009cdcbd0 _Z16sqljs_ddm_clsqryP14db2UCinterfaceP14sqljsDDMObject + 0x2b0 at sqljsqry.C:2170 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (10) 0xc000000008bc16c0 _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP14sqljsDDMObjectP14db2 UCinterface + 0x3e0 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (11) 0xc000000008c64970 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x230 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (12) 0xc000000008c276b0 _Z10sqljsSqlamP14db2UCinterfaceP13sqle_agent_cbb + 0x230 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (13) 0xc000000008b34ba0 _Z18sqljsDriveRequestsP13sqle_agent_cbP11UCconHandle + 0x100 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (14) 0xc000000008badb10 _Z22sqljsDrdaAsInnerDriverP17sqlcc_init_structb + 0x4f0 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (15) 0xc000000008b351d0 _Z17sqljsDrdaAsDriverP17sqlcc_init_struct + 0x110 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (16) 0xc000000008c230e0 _Z12sqleRunAgentPcj + 0x840 at sqleagnt.C:1585 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] (17) 0xc000000008d464b0 _Z13sqloCreateEDUPFvPcjES_mP13SQLO_EDU_INFOPi + 0x690 [/opt/IBM/db2/V9.1.5/lib64/libdb2e.so] ========================================================= There may be more symptoms than the two call stacks shown above as it's not easy to say exactly what applications will fail in this issue. If you could ensure whether you hit this APAR or not, please contact IBM support for help.
Problem conclusion
First fixed in DB2 UDB Version 9.1 FixPak 6.
Temporary fix
Comments
APAR Information
APAR number
IZ25933
Reported component name
DB2 UDB ESE HP-
Reported component ID
5765F4103
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-06-30
Closed date
2008-11-02
Last modified date
2009-06-12
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 HP-
Fixed component ID
5765F4103
Applicable component levels
R910 PSY
UP
R950 PSY
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:
12 June 2009