Can the following be coded? If not is there a third party product that does
this?

Contention detection routines

It occurs to me that it may be random chance that we catch conflicts between
some of our processes and their locking strategy. Is it possible to
establish a set of rules that we feel should not be broken by an individual
process and then set up some pro-active DB2 monitoring for these conditions
on our development databases?

Off the top of my head
Page read locks held for >15? seconds
Page write locks held for >15? Seconds
lock escalation

Perhaps the held locks need a red/amber threshold red = 15+ and amber = 5+ ?


Regards

Alex Cosser


The Royal Bank of Scotland plc, Registered in Scotland No. 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB

Authorised and regulated by the Financial Services Authority.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate.


DB2 & UDB email list listserv db2-l LazyDBA home page