|
Problem IT23315
|
Status: Closed |
A TRAP, PANIC OR A -901 SQLCODE (SQLRA_FREE_SECTION: SECTION NOT CLOSED) OCCURS IN DPF |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
The -901 is in the "sqlra_free_section: section not closed" that
is captured below
2017-10-20-22.05.34.585319+000 I43783111A908 LEVEL: Severe
PID : 7143572 TID : 30767 PROC : db2sysc 30
INSTANCE: xxxxxx NODE : 030 DB : XXXXXXXX
APPHDL : 98-56472 APPID: 10.216.27.40.38376.171020220122
AUTHID : TDVBVP HOSTNAME: xxxxxxxxxx
EDUID : 30767 EDUNAME: db2agntp (XXXXX) 30
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: 38
sqlerrmc: sqlra_free_section: section not closed
sqlerrp : SQLRA141
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0xFFFFFF38 (6) 0x0000001E
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
Stacks for the -901 similar to
-------Frame------ ------Function + Offset------
0x090000000057FF14 pthread_kill + 0xD4
0x0900000007947FFC sqloDumpEDU + 0x9C
0x0900000008575230 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 +
0x150
0x090000000988A7B4 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x914
0x0900000007AA5E38 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x158
0x0900000007AA591C sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc +
0x27C
0x0900000007AA240C sqlrrSqlCode + 0x18C
0x0900000009848A00
sqlra_free_section__FP8sqlrr_cbP25sqlra_sql_context_siblingiN23
+ 0x580
0x090000000AA151B8
sqlra_get_section_subagent__FP8sqlrr_cbPUcsT2T3T2UsUliUi + 0xF38
0x09000000091C1EB4
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xDB4
0x09000000091A7220 IPRA.$sqleSubRequestRouter__FP8sqeAgentPUiPUl
+ 0x7C0
0x09000000091A12C8 sqleProcessSubRequest__FP8sqeAgent + 0x2C28
0x0900000007A7002C RunEDU__8sqeAgentFv + 0x9EC
0x0900000007A52D20 EDUDriver__9sqzEDUObjFv + 0x2E0
0x0900000007941C14 sqloEDUEntry + 0x374
</StackTrace>
------------------------
The following 2 stacks for a signal #11 (seg-v) can also result
<StackTrace>
-------------------------------------
0x0900000008B226D0
sqlra_cache_del_var__FP8sqlrr_cbP16sqlra_cached_variP23sqlra_cac
hed_dependency
+ 0xB50
0x090000000BD9EA10
sqlra_csm_drop_var__FP8sqlrr_cbPP16sqlra_cached_variP23sqlra_cac
hed_dependencyP
ib + 0x570
0x090000000BD92B14 sqlra_csm_clean_lru__FP8sqlrr_cbPb + 0x16B4
0x090000000BD8E388 sqlra_cache_space_mgmt__FP8sqlrr_cbUlb +
0x808
0x090000000BD99DF0 sqlraCacheSpaceDaemon__FP8sqeAgentPv + 0x2790
0x090000000BAE18CC sqleIndCoordProcessRequest__FP8sqeAgent +
0x174C
0x0900000007A700E8 RunEDU__8sqeAgentFv + 0xAA8
0x0900000007A52D20 EDUDriver__9sqzEDUObjFv + 0x2E0
0x0900000007941C14 sqloEDUEntry + 0x374
</StackTrace>
----------------------------------------------------------------
---
and
0x00007F17431800FF
_Z19sqlra_find_ship_varP8sqlrr_cbP13sqlra_ship_idS2_iP16sqlra_ca
ched_v
arP13sqlra_stmt_idPjS7_PiP14SQLP_LOCK_INFOSA_Pb + 0x8e66
0x00007F17430D167E
_Z26sqlra_get_section_subagentP8sqlrr_cbPhsS1_sS1_tmij + 0x2539
0x00007F1742D47F03
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x27ec
0x00007F173E6AFCFC address: 0x00007F173E6AFCFC ; dladdress:
0x00007F1729CB4000 ; offset i
n lib: 0x00000000149FBCFC ;
0x00007F173E6B13C6 _Z21sqleProcessSubRequestP8sqeAgent + 0x04d7
0x00007F173E70D4F7 _ZN8sqeAgent6RunEDUEv + 0x04db
Also a Panic may occur with the following stack:
0x0900000024E6D458 IPRA.$sqloDiagnoseFreeBlockFailure +
0x758
0x0900000024E6BB9C sqlofmblkEx + 0x11C
0x0900000026027A94 sqlra_cache_del_var + 0x1F14
0x09000000292A2810 sqlra_csm_drop_var + 0x570
0x0900000029296914 sqlra_csm_clean_lru + 0x16B4
0x0900000029292188 sqlra_cache_space_mgmt + 0x808
0x090000002929A96C sqlra_PCD_free_request + 0x36C
0x09000000292902C8 sqlra_cache_reserve_memory_int + 0x1C8
0x0900000026022DA4 sqlra_cache_ins_stmt + 0x664
0x0900000026021E04 sqlra_cache_find_stmt + 0xB84
0x0900000026003824 sqlra_find_var_stmt_latch + 0xC24
0x090000002601D658 sqlra_find_ship_var + 0x2718
0x0900000027F18C30 sqlra_get_section_subagent + 0xAB0
0x09000000266C5EB4 sqlrr_subagent_router + 0xDB4
0x09000000266AB220 IPRA.$sqleSubRequestRouter + 0x7C0
0x09000000266A52C8 sqleProcessSubRequest + 0x2C28 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.11.2017
19.03.2018
19.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
