what have to be monitored in db using promon

Firstly - I have flagged your posts as spam/abuse. The last 3 threads you created that is.

Secondly - the URL from James Palmer works just fine and points to the very first thread you created, which I believe you know quite well. You just decided to ignore it.

Now to your "question" - what do YOU think the activities are and should be? Why don't YOU try to play with promon and come up with what YOU think is important and then it can be discussed and explained here.

Thanks.

In order to sustain Libor, please have a look over the Progress documentation of promon:

documentation.progress.com/.../index.html.

Hi,

First of all I agree with Libor that YOU should decide what you want to do with promon. However I can give you some examples I'm using promon for:

- verify DB checkpointing mechanism

- writing in variable extents

- verify database settings

Kind Regards,

Jbr

Another things to look at are long running transactions in the R&D,1,4,3.

However "long" is a subjective term and is very dependent on the application code and the system performance.

will you please stop asking the /same/ question over and over again?  and stop making a different title each time. you are being quite tiresome.