|
Problem IC69889
|
Status: Closed |
A FILE HANDLE WILL LEAK, IF GENREGFILE::OPENSCAN , PROBE:20 IS RECORDED IN DB2DIAG.LOG |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A File handle will leak, if GenRegFile::OpenScan , probe:20 is
recorded in db2diag.log
From db2diag.log,
2010-06-30-09.00.58.626926+540 I3582A1357 LEVEL: Error
PID : 454956 TID : 6099 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 3-44174 APPID: *N3.db2inst1.100707013023
AUTHID : db2inst1
EDUID : 6099 EDUNAME: db2agntp (SAMPLE) 99
FUNCTION: DB2 Common, Generic Registry, GenRegFile::OpenScan,
probe:20
MESSAGE :
ECF=0x900001BF=-1879047745=ECF_GENREG_OPEN_INPUT_FILE_FAILED
Failed to open the input registry
CALLED : OS, -, fopen
RETCODE : ECF=0x9000002D=-1879048147=ECF_FILE_PROCESS_MAX
The maximum number of file per process has already
been reached
DATA #1 : String, 19 bytes
/var/db2/global.reg
CALLSTCK:
{0} 0x0900000002FEAEFC pdOSSeLoggingCallback + 0x34
{1} 0x0900000000624424 oss_log__FP9OSSLogFacUiN32UlN26iPPc +
0x1C4
{2} 0x0900000000624810 ossLogRC + 0xD0
{3} 0x09000000010CEF6C OpenScan__10GenRegFileFv + 0x3CC
{4} 0x09000000010E928C ossOpenInstanceList__FPcPPvCb + 0x8C
{5} 0x0900000001811950 @71@EnvRegRefresh__FP12SEnvRegistry +
0x2C4
{6} 0x0900000001811578 @71@EnvRegOpen__FPP12SEnvRegistry +
0x84
{7} 0x09000000017A9160 @71@sqloPRegQueryDefaultValue__FiPcPCc
+ 0xC
{8} 0x0900000001816420 @71@EnvGetDB2SysVar__FiPcUl + 0x110
{9} 0x0900000001811118 @71@EnvQueryDB2SystemVariables__Fv +
0x80
In this case, opened file descriptor was not closed.
Then, you got the following using lsof.
COMMAND PID USER FD TYPE DEVICE
SIZE/OFF NODE NAME
db2sysc 229436 db2inst1 3r VREG 10,6
0 XXX /var (/dev/hd9var)
... snip ...
db2sysc 229436 db2inst1 22r VREG 10,6
0 XXX /var (/dev/hd9var)
db2sysc 229436 db2inst1 23r VREG 10,6
0 XXX /var (/dev/hd9var)
... snip ...
db2sysc 229436 db2inst1 999r VREG 10,6
0 XXX /var (/dev/hd9var)
db2sysc 229436 db2inst1 1000r VREG 10,6
0 XXX /var (/dev/hd9var)
... snip ...
db2sysc 229436 db2inst1 *484r VREG 10,6
0 XXX /var (/dev/hd9var)
db2sysc 229436 db2inst1 *485r VREG 10,6
0 XXX /var (/dev/hd9var)
db2sysc 229436 db2inst1 *486r VREG 10,6
0 XXX /var (/dev/hd9var)
db2sysc was TOO MANY opened /var... files due to the above(open
was successful, but lock file was error. if this case was
occurred, opened file descriptor was not closed) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* A File handle will leak, if GenRegFile::OpenScan , probe:20 *
* is recorded in db2diag.log *
* *
* From db2diag.log, *
* *
* 2010-06-30-09.00.58.626926+540 I3582A1357 LEVEL:Error *
* PID : 454956 TID : 6099 PROC *
* :db2sysc 0 *
* INSTANCE: db2inst1 NODE : 000 DB : SAMPLE *
* APPHDL : 3-44174 APPID: *
* *N3.db2inst1.100707013023 *
* AUTHID : db2inst1 *
* EDUID : 6099 EDUNAME: db2agntp (SAMPLE) 99 *
* FUNCTION: DB2 Common, Generic Registry, *
* GenRegFile::OpenScan,probe:20 *
* *
* MESSAGE : *
* ECF=0x900001BF=-1879047745=ECF_GENREG_OPEN_INPUT_FILE_FAILED *
* Failed to open the input registry *
* CALLED : OS, -, fopen *
* RETCODE : ECF=0x9000002D=-1879048147=ECF_FILE_PROCESS_MAX *
* The maximum number of file per process has already *
* been reached *
* *
* DATA #1 : String, 19 bytes *
* /var/db2/global.reg *
* *
* CALLSTCK: *
* {0} 0x0900000002FEAEFC pdOSSeLoggingCallback + 0x34 *
* {1} 0x0900000000624424 oss_log__FP9OSSLogFacUiN32UlN26iPPc *
* + 0x1C4 *
* {2} 0x0900000000624810 ossLogRC + 0xD0 *
* {3} 0x09000000010CEF6C OpenScan__10GenRegFileFv + 0x3CC *
* {4} 0x09000000010E928C ossOpenInstanceList__FPcPPvCb + *
* 0x8C *
* {5} 0x0900000001811950 @71@EnvRegRefresh__FP12SEnvRegistry *
* + 0x2C4 *
* {6} 0x0900000001811578 @71@EnvRegOpen__FPP12SEnvRegistry + *
* 0x84 *
* {7} 0x09000000017A9160@71@sqloPRegQueryDefaultValue__FiPcPCc *
* + 0xC *
* {8} 0x0900000001816420 @71@EnvGetDB2SysVar__FiPcUl + 0x110 *
* {9} 0x0900000001811118 @71@EnvQueryDB2SystemVariables__Fv *
* + 0x80 *
* *
* In this case, opened file descriptor was not closed. *
* *
* Then, you got the following using lsof. *
* COMMAND PID USER FD TYPE DEVICE *
* SIZE/OFF NODE NAME *
* *
* db2sysc 229436 db2inst1 3r VREG 10,6 *
* 0 XXX /var (/dev/hd9var) *
* ... snip ... *
* db2sysc 229436 db2inst1 22r VREG 10,6 *
* 0 XXX /var (/dev/hd9var) *
* db2sysc 229436 db2inst1 23r VREG 10,6 *
* 0 XXX /var (/dev/hd9var) *
* ... snip ... *
* db2sysc 229436 db2inst1 999r VREG 10,6 *
* 0 XXX /var (/dev/hd9var) *
* db2sysc 229436 db2inst1 1000r VREG 10,6 *
* 0 XXX /var (/dev/hd9var) *
* ... snip ... *
* db2sysc 229436 db2inst1 *484r VREG 10,6 *
* 0 XXX /var (/dev/hd9var) *
* db2sysc 229436 db2inst1 *485r VREG 10,6 *
* 0 XXX /var (/dev/hd9var) *
* db2sysc 229436 db2inst1 *486r VREG 10,6 *
* 0 XXX /var (/dev/hd9var) *
* *
* db2sysc was TOO MANY opened /var... files due to the *
* above *
* (open was successful, but lock file was error. *
* if this case was occurred, opened file descriptor was not *
* closed) *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.7 fix pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC72123 IC72987
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.07.2010
10.05.2011
13.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
