|
Problem IC99906
|
Status: Closed |
ADM2017C MAY BE OCURRED EVEN IF FILESYSTEM HAS ENOUGH ROOM. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Create eventmonitor with MAXFILES 1 MAXFILESIZE NONE
ie)
db2 "CREATE EVENT MONITOR EVTTEST FOR STATEMENTS, TRANSACTIONS
WRITE TO FILE '/work/evttest' MAXFILES 1 MAXFILESIZE NONE
AUTOSTART"
db2 SET EVENT MONITOR EVTTEST STATE=1
db2diag.log was recorded the following messages even if
filesystem had enough room.
2014-02-12-12.11.50.664097+540 I17656A637 LEVEL:
Warning
PID : 4194498 TID : 6709 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-38 APPID: *LOCAL.DB2.140212031200
AUTHID : DB2I1002 HOSTNAME: host1
EDUID : 6709 EDUNAME: db2evmli (EVTTEST) 0
FUNCTION: DB2 UDB, database monitor, sqmEvmonWriter::activate,
probe:40
MESSAGE : ADM2017C The Event Monitor "EVTTEST" has reached its
file capacity.
Delete the files in the target directory
"/work/evttest" or move them
to another directory.
$ ls -l
total 8388600
-rw-r--r-- 1 db2inst1 db2iadm1 4294951222 Jan 22 09:14
00000000.evt
-rw-r----- 1 db2inst1 db2iadm1 33 Jan 21 20:04
db2event.ctl
$ df -k /work
Filesystem 1024-blocks Free %Used Iused %Iused
Mounted on
/dev/fslv00 18874368 5662836 70% 18338 2% /work |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 10.1 fixpack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.03.2014
09.06.2014
09.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
