db2event => db2detaildeadlock, useless entry every 8 seconds fills mydatabase creating errors

[Nokao]

I use db2 9 express-c

Hi... I'm having that problem...
.....every less-than-10-seconds, a entry like that (I displayed that
entry with the command db2evmon -db 'MYDATABASE' -evm
'DB2DETAILDEADLOCK' ):
Database Name: MYDATABASE
Database Path: /home/db2inst1/db2inst1/NODE0000/SQL00003/
First connection timestamp: 19/11/2007 12:57:28.850635
Event Monitor Start time: 19/11/2007 12:57:28.962415

Is stored in the DB2DETAILDEADLOCK table...

That causes, when the database reach his maximum filesize (default
from db2 is 50 Mb) a lot of errors in the main db2diag.log.
(The errors are DIA8052C ...."monitor full of data").

Temporarily, I resolved the problem moving the files inside the /
db2event/db2detaildeadlock/ folder in another folder, and db2 created
another database immediatly starting again to fill it with useless
entrys.

How can I avoid him to write that thing thousand times a day?

Thank you.

[Ian]

Nokao wrote:

I use db2 9 express-c

Hi... I'm having that problem...
....every less-than-10-seconds, a entry like that (I displayed that
entry with the command db2evmon -db 'MYDATABASE' -evm
'DB2DETAILDEADLOCK' ):
Database Name: MYDATABASE
Database Path: /home/db2inst1/db2inst1/NODE0000/SQL00003/
First connection timestamp: 19/11/2007 12:57:28.850635
Event Monitor Start time: 19/11/2007 12:57:28.962415

Is stored in the DB2DETAILDEADLOCK table...

That causes, when the database reach his maximum filesize (default
from db2 is 50 Mb) a lot of errors in the main db2diag.log.
(The errors are DIA8052C ...."monitor full of data").

Temporarily, I resolved the problem moving the files inside the /
db2event/db2detaildeadlock/ folder in another folder, and db2 created
another database immediatly starting again to fill it with useless
entrys.

How can I avoid him to write that thing thousand times a day?

This is happening because the database is being activated and
deactivated very frequently.

Normally DB2 will automatically activate a database (allocate
memory for bufferpools, etc.) when the first application connects
to the database, and deactivate it (release memory) after the last
application disconnects.

Database activation also results in an event for the default
DB2DETAILDEADLOCK event monitor, which is the source of your
complaint.

So, you have 2 options:

1) Activate your database explicitly using the ACTIVATE DATABASE
command

2) Drop the DB2DETAILDEADLOCK event monitor.

[Nokao]

On 19 Nov, 22:16, Ian <[e-mail]:

Nokao wrote:

I use db2 9 express-c

Hi... I'm having that problem...
....every less-than-10-seconds, a entry like that (I displayed that
entry with the command db2evmon -db 'MYDATABASE' -evm
'DB2DETAILDEADLOCK' ):
Database Name: MYDATABASE
Database Path: /home/db2inst1/db2inst1/NODE0000/SQL00003/
First connection timestamp: 19/11/2007 12:57:28.850635
Event Monitor Start time: 19/11/2007 12:57:28.962415

Is stored in the DB2DETAILDEADLOCK table...

That causes, when the database reach his maximum filesize (default
from db2 is 50 Mb) a lot of errors in the main db2diag.log.
(The errors are DIA8052C ...."monitor full of data").

Temporarily, I resolved the problem moving the files inside the /
db2event/db2detaildeadlock/ folder in another folder, and db2 created
another database immediatly starting again to fill it with useless
entrys.

How can I avoid him to write that thing thousand times a day?

This is happening because the database is being activated and
deactivated very frequently.

Normally DB2 will automatically activate a database (allocate
memory for bufferpools, etc.) when the first application connects
to the database, and deactivate it (release memory) after the last
application disconnects.

Database activation also results in an event for the default
DB2DETAILDEADLOCK event monitor, which is the source of your
complaint.

So, you have 2 options:

1) Activate your database explicitly using the ACTIVATE DATABASE
command

2) Drop the DB2DETAILDEADLOCK event monitor.

Wow, that's an Answer ;)

Thank to you, I understood that the problem is for sure the php
website that is using DB2, through the ODBC driver.

Probably, there is some configuration for the ODBC driver to keep the
connection alive someway... but I suppose that also the website have
to be changed for re-use the connection.

If you have further informations about it, give them to me.

Otherwise, how can I drop the DB2DETAILDEADLOCK event monitor?

[The Boss]

Nokao wrote:

On 19 Nov, 22:16, Ian <[e-mail]:

>Nokao wrote:

>>I use db2 9 express-c

>>Hi... I'm having that problem...
....every less-than-10-seconds, a entry like that (I displayed that
entry with the command db2evmon -db 'MYDATABASE' -evm
'DB2DETAILDEADLOCK' ):
Database Name: MYDATABASE
Database Path: /home/db2inst1/db2inst1/NODE0000/SQL00003/
First connection timestamp: 19/11/2007 12:57:28.850635
Event Monitor Start time: 19/11/2007 12:57:28.962415

>>Is stored in the DB2DETAILDEADLOCK table...

>>That causes, when the database reach his maximum filesize (default
from db2 is 50 Mb) a lot of errors in the main db2diag.log.
(The errors are DIA8052C ...."monitor full of data").

>>Temporarily, I resolved the problem moving the files inside the /
db2event/db2detaildeadlock/ folder in another folder, and db2
created another database immediatly starting again to fill it with
useless entrys.

>>How can I avoid him to write that thing thousand times a day?

This is happening because the database is being activated and
deactivated very frequently.

Normally DB2 will automatically activate a database (allocate
memory for bufferpools, etc.) when the first application connects
to the database, and deactivate it (release memory) after the last
application disconnects.

Database activation also results in an event for the default
DB2DETAILDEADLOCK event monitor, which is the source of your
complaint.

So, you have 2 options:

1) Activate your database explicitly using the ACTIVATE DATABASE
command

2) Drop the DB2DETAILDEADLOCK event monitor.

Wow, that's an Answer ;)

Thank to you, I understood that the problem is for sure the php
website that is using DB2, through the ODBC driver.

Probably, there is some configuration for the ODBC driver to keep the
connection alive someway... but I suppose that also the website have
to be changed for re-use the connection.

If you have further informations about it, give them to me.

Otherwise, how can I drop the DB2DETAILDEADLOCK event monitor?

You can either deactivate the event monitor via:
db2 "set event monitor DB2DETAILDEADLOCK state 0"
or drop it entirely via:
db2 "drop event monitor DB2DETAILDEADLOCK"

--
Jeroen