DB2 - Problem description
Problem IT24739 | Status: Closed |
DB2 CRASH ON -901 IN SQLRA_CACHE_FILL_SEC WITH "SECTION LENGTH MISMATCH" | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
DB2 crash with -901 in SQLRA_CACHE_FILL_SEC with "SECTION LENGTH MISMATCH" db2diag.log messages: 2016-08-13-01.00.00.381246-300 I16253924A589 LEVEL: Error PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (XXX) 0 FUNCTION: DB2 UDB, access plan manager, sqlra_cache_fill_sec, probe:290 MESSAGE : Section length fetched DATA #1 : Hexdump, 4 bytes 0x0A00000054BF4AF4 : 0000 14E0 .... 2016-08-13-01.00.00.381639-300 I16254514A590 LEVEL: Error PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : RCCOMUA APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (XXX) 0 FUNCTION: DB2 UDB, access plan manager, sqlra_cache_fill_sec, probe:300 MESSAGE : Section length expected DATA #1 : Hexdump, 4 bytes 0x0A000100A127E448 : 0000 19E0 .... 2016-08-13-01.00.00.381925-300 I16255105A601 LEVEL: Error PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (RCCOMUA) 0 FUNCTION: DB2 UDB, access plan manager, sqlra_cache_fill_sec, probe:310 MESSAGE : Section length recorded in section DATA #1 : Hexdump, 4 bytes 0x0A00000054BF4AA0 : 0000 1488 .... 2016-08-13-01.00.00.382207-300 I16255707A603 LEVEL: Error PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (XXX) 0 FUNCTION: DB2 UDB, access plan manager, sqlra_cache_fill_sec, probe:320 MESSAGE : Cached Package last bind time DATA #1 : Hexdump, 10 bytes 0x0A000100A127DF32 : 2016 0808 1501 0918 8246 ........F 2016-08-13-01.00.00.382490-300 I16256311A191 LEVEL: Severe PID:22282340 TID:34957 NODE:000 Title: Global Section Size Dump File:/home/db2inst1/sqllib/db2dump/22282340.34957.000.dump.bin 2016-08-13-01.00.00.385685-300 I16256503A194 LEVEL: Severe PID:22282340 TID:34957 NODE:000 Title: Global Section Address Dump File:/home/db2inst1/sqllib/db2dump/22282340.34957.000.dump.bin 2016-08-13-01.00.00.385972-300 I16256698A186 LEVEL: Severe PID:22282340 TID:34957 NODE:000 Title: Global Section Dump File:/home/db2inst1/sqllib/db2dump/22282340.34957.000.dump.bin 2016-08-13-01.00.00.386129-300 I16256885A193 LEVEL: Severe PID:22282340 TID:34957 NODE:000 Title: End of dumped section Dump File:/home/db2inst1/sqllib/db2dump/22282340.34957.000.dump.bin 2016-08-13-01.00.00.389124-300 E16257079A817 LEVEL: Error PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXXX EDUID : 34957 EDUNAME: db2agent (RCCOMUA) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:30 MESSAGE : ADM14005E The following error occurred: "AppErr". First Occurrence Data Capture (FODC) has been invoked in the following mode: "Automatic". Diagnostic information has been recorded in the directory named "/home/db2inst1/sqllib/db2dump/FODC_AppErr_2016-08-13-01.00.00.3 86297 _22282340_34957_000/". 2016-08-13-01.00.00.389820-300 E16257897A598 LEVEL: Severe PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (RCCOMUA) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:200 MESSAGE : ADM0001C A severe error has occurred. Examine the administration notification log and contact IBM Support if necessary. 2016-08-13-01.00.00.390375-300 I16258496A897 LEVEL: Severe PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (XXX) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 23 sqlerrmc: Section length mismatch sqlerrp : SQLRA01D sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFEA2 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2016-08-13-01.00.00.392505-300 I16261448A573 LEVEL: Severe PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (XXX) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:400 MESSAGE : CREATOR DATA #1 : Hexdump, 8 bytes 0x0A000100424A5BE8 : 4154 4741 5050 2020 ATGAPP 2016-08-13-01.00.00.393007-300 I16262022A573 LEVEL: Severe PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (RCCOMUA) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:450 MESSAGE : PACKAGE DATA #1 : Hexdump, 8 bytes 0x0A000100424A5BE0 : 5031 3435 3238 3731 P1452871 .... ...... 2016-08-13-01.00.01.895532-300 E16374303A1316 LEVEL: Severe PID : 22282340 TID : 34957 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : XXX APPHDL : 0-22423 APPID: 10.211.146.20.43928.160813060002 AUTHID : XXX HOSTNAME: XXX EDUID : 34957 EDUNAME: db2agent (XXX) 0 FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:90 MESSAGE : ADM14011C A critical failure has caused the following type of error: "Trap". The DB2 database manager cannot recover from the failure. First Occurrence Data Capture (FODC) was invoked in the following mode: "Automatic". FODC diagnostic information is located in the following directory: "/home/db2inst1/sqllib/db2dump/FODC_AppErr_2016-08-13-01.00.01.2 15712 _22282340_34957_000/". DATA #1 : Signal Number Recieved, 4 bytes 11 DATA #2 : Siginfo, 64 bytes 0x0A0000005480EDC0 : 0000 000B 0000 0000 0000 0032 0000 0000 ...........2.... 0x0A0000005480EDD0 : 0000 0000 0000 0000 5245 474B FFFF FFE8 ........REGK.... 0x0A0000005480EDE0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0A0000005480EDF0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 FP9 or higher * **************************************************************** | |
Local Fix: | |
Explicitly rebind the package using either the REBIND command or the BIND command. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.04.2018 14.05.2018 14.05.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |