各位大神求帮助，求问题的原因及解决方法？
2017-09-27-07.48.25.344904+480 I11275040A1438 LEVEL: Error
PID : 6309 TID : 2838 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : HBYDJH
APPHDL : 0-55521 APPID: *LOCAL.DB2.170926235021
AUTHID : DB2INSTL
EDUID : 2838 EDUNAME: db2evmgi (DB2DETAILDEADLOCK) 0
FUNCTION: DB2 UDB, database monitor, sqm_evmon_ftarget::sqm_evmon_ftarget, probe:296
MESSAGE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor full of data"
DIA8052C The Event Monitor "" has reached its file capacity. Delete
the files in the target directory "" or move them to another
directory.DATA #1 : signed integer, 4 bytes
0
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
[0] 0xFFFFFFFF78F20E44 _1cRsqm_evmon_ftarget2t6MpnOsqmEvmonWriter_pi_v + 0x46C
[1] 0xFFFFFFFF78F35214 _1cOsqmEvmonWriterKinitTarget6M_i + 0xE4
[2] 0xFFFFFFFF78F347D8 _1cOsqmEvmonWriterIactivate6M_i + 0x708
[3] 0xFFFFFFFF78F32F00 _1cOsqmEvmonWriterLevmonWriter6M_i + 0x88
[4] 0xFFFFFFFF78944E54 _1cbAsqleIndCoordProcessRequest6FpnIsqeAgent__v + 0x95C
[5] 0xFFFFFFFF789823A0 _1cIsqeAgentGRunEDU6M_v + 0x7B0
[6] 0xFFFFFFFF7B5AC454 _1cKsqlzRunEDU6FpcI_v + 0xD4
[7] 0xFFFFFFFF7A070E54 sqloEDUEntry + 0x3D4
[8] 0xFFFFFFFF750D8B64 _thr_slot_offset + 0x488
[9] 0x0000000000000000 ?unknown + 0x0
2017-09-27-07.48.25.347794+480 I11276479A818 LEVEL: Error
PID : 6309 TID : 2838 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : HBYDJH
APPHDL : 0-55521 APPID: *LOCAL.DB2.170926235021
AUTHID : DB2INSTL
EDUID : 2838 EDUNAME: db2evmgi (DB2DETAILDEADLOCK) 0
FUNCTION: DB2 UDB, database monitor, sqmEvmonWriter::initTarget, probe:40
MESSAGE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor full of data"
DIA8052C The Event Monitor "" has reached its file capacity. Delete
the files in the target directory "" or move them to another
directory.DATA #1 : String, 17 bytes
DB2DETAILDEADLOCK
DATA #2 : String with size, 68 bytes
/jhdata/HBYDJH/db2inst1/NODE0000/SQL00001/db2event/db2detaildeadlock
2同行回答
这个报错没关系
是你在设置db2 deadlock的event monitor的时候，设置了最大的文件数量，而你的死锁监视器目前还是开启状态，导致新的死锁信息写不进你设置的文件中，很简单
1.要么关闭死锁事件监视，DB2DIAG不再报错：
db2 "set event monitor db2detaildeadlock state 0"
2.要么到设置的文件目录删除死锁的文件，但是删除的方法，等到死锁产生的文件又满了的话，还将继续报错
cd /jhdata/HBYDJH/db2inst1/NODE0000/SQL00001/db2event/db2detaildeadlock
rm *.evt
3.分析产生的死锁文件，协同应用开发人员，找到问题的根源，不让死锁继续产生，并清理死锁事件监视产生的文件：
db2evmon -db dbname -evmon db2detaildeadlock
4.扩大死锁监视文件的数量
收起
报错比较详细了，按照提示处理就OK
The Event Monitor "" has reached its file capacity. Delete
the files in the target directory "" or move them to another
directory，