DB2 - Problembeschreibung
Problem IT00379 | Status: Geschlossen |
ADM2017C MAY BE OCURRED EVEN IF FILESYSTEM HAS ENOUGH ROOM. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB version 10.5 fixpack 4. * **************************************************************** | |
Local-Fix: | |
Lösung | |
First fixed in DB2 Version 10.5 Fix Pack 4. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 18.03.2014 15.09.2014 15.09.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |