This is a discussion on Re: [Info-Ingres] table lock escalations in errlog within the Ingres forums, part of the Database Server Software category; --> Hi Franky Connect to iidbdb and issue the command set trace point sc924 233571; \g \q Then stand back ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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, > > 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 > > _______________________________________________ > Info-Ingres mailing list > Info-Ingres@kettleriverconsulting.com > http://www.kettleriverconsulting.com...fo/info-ingres > |
| Thread Tools | |
| Display Modes | |
|
|