DB2 - Problem description
Problem IT31350 | Status: Closed |
MON_GET_LOCKS FAILS IN DPF WITH SQL1607N BECAUSE OF UNDERLYING RPC MECHANISM BEING LIMITED TO 2 GIGABYTES | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
MON_GET_LOCKS fails with SQL1607N because of underlying RPC mechanism being limited to 2 Gigabytes. This may cause many FODC_AppErr being generated and system getting stuck while filling up db2dump directory. You should see the following error messages in the db2diag.log: ---------------- EDUID : 38084 EDUNAME: db2agntp ( XXXXX) 3 FUNCTION: DB2 UDB, WLM, sqlrwGetLocks, probe:30 DATA #1 : String, 63 bytes Not able to process the data because the size is larger than 2G DATA #2 : signed integer, 8 bytes 2812656760 EDUID : 38084 EDUNAME: db2agntp ( XXXXX) 3 FUNCTION: DB2 UDB, WLM, sqlrwGetLocks, probe:35 MESSAGE : ZRC=0xFFFFF9B9=-1607 SQL1607N There is not enough working memory to execute the requested Database Monitor function. DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: 0 sqlerrml: 0 sqlerrmc: sqlerrp : SQL11014 sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000003 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: EDUID : 38084 EDUNAME: db2agntp ( XXXXX) 3 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 "/db2/XXXXX/db2dump/FODC_AppErr_2019-11-26-08.44.03.821402_54404 64_3808 4_003/". EDUID : 38084 EDUNAME: db2agntp ( XXXXX) 3 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. EDUID : 38084 EDUNAME: db2agntp ( XXXXX) 3 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 MESSAGE : ZRC=0xFFFFF9B9=-1607 SQL1607N There is not enough working memory to execute the requested Database Monitor function. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Issue to be fixed within future FixPack of Db2 version 11.5. * * Refer to APAR IT31536. * **************************************************************** | |
Local Fix: | |
In a partitioned database, we can connect to each partition and run the MON_GET_LOCKS. We can do that by using the command export DB2NODE= to change to a specific node and then execute the MON_GET_LOCKS only on the current member(using parameter -1). i.e. export DB2NODE=0 db2 terminate db2 connect to sample db2 "SELECT * FROM TABLE(MON_GET_LOCKS(NULL,-1)) AS T" | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Issue to be fixed within future FixPack of Db2 version 11.5. * * Refer to APAR IT31536. * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.12.2019 18.02.2021 18.02.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |