table lock escalations in errlog

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

franky.leeuwerck@gmail.com - 25 Jan 2007 15:23 GMT

Hi folks,

We are logging the table level lock escalations in the errlog.log of
our Ingres DBMS systems.
This is without doubt a usefull source for debugging performance and
locking issues.

Example :
E_DM9063_LK_TABLE_MAXLOCKS Current logical lock count ( 101 ) on
resource myTable in database myDatabase exceeds the specified maximum (
100 ). Escalating to table level lock.

Wouldn't it be much more interesting to see also the query involved ?
Is there a setting available to see this reported too ?

Franky

Reply to this Message

martin.bowes@ctsu.ox.ac.uk - 25 Jan 2007 15:54 GMT

Hi Franky

Connect to iidbdb and issue the command
set trace point sc924 233571;
\g
\q

Then stand back and watch the fun in the errlog.

When you wan tto turn it off, use set notrace point sc924.

Marty

> Hi folks,
>
[quoted text clipped - 16 lines]
> Info-Ingres@kettleriverconsulting.com
> http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres

Reply to this Message

franky.leeuwerck@gmail.com - 26 Jan 2007 08:15 GMT

Hi Marty,

Thanks for your input there .. looks promising.
Some of the dbms's I am looking at are running multiple iidbms servers.
Will it work for these too ?
I'm thinking about activating this permanently .. in some case we have
hundreds of lock escalations per week which will cause the log to grow
quickly.

Regards,
Franky
On Jan 25, 4:54 pm, martin.bo...@ctsu.ox.ac.uk wrote:

> Hi Franky
>
[quoted text clipped - 29 lines]
> > Info-Ing...@kettleriverconsulting.com
> >http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres- Hide quoted text -- Show quoted text -

Reply to this Message