Re: lock probs, implicit "update statistics for procedure .." ?
Is there a CSDK involved in the whole mix .... There was a bug in in the ODBC driver bundled with the CSDK (Bug#162089) which sent an implicit UPDATE STATS to the server ... the bug has been fixed in ODBC driver 3.82 (which comes with 2.81.TC2). HTH Thanx much, Rajib Sarkar Advisory Software Engineer (RAS) IBM Data Management Group Ph : (602)-217-2100 Fax: (602)-217-2100 T/L : 667-2100 As long as you derive inner help and comfort from anything, keep it -- Mahatma Gandhi "Langelage, Frank" To: informix-list@iiug.org <frank@lafr.de> cc: Sent by: Subject: lock probs, implicit "update statistics for procedure .." ? owner-informix-li st@iiug.org 08/18/2003 02:57 PM Please respond to "Langelage, Frank" Whe recently sometimes get lock problems at one of our customers. We found out, that the system tables sysprocplan and sysdistrib where locked by a db session started by our application. But from our application we do not execute a "update statistics". Is it possible, that the engine executes something that locks the tables mentioned above ? We entertain suspicion that a stored procedure which is used inside of an select statement causes the trouble. But the problem is not reproducable so far. OS is SunOS 5.8 (Solaris 8), Server 7.31FD5. regards - Frank sending to informix-list
Rajib Sarkar wrote: > Is there a CSDK involved in the whole mix .... There was a bug in in the > ODBC driver bundled with the CSDK (Bug#162089) which sent an implicit > UPDATE STATS to the server ... the bug has been fixed in ODBC driver 3.82 > (which comes with 2.81.TC2). > No, ODBC is not envolved. ESQLC is used. But today I found the reason for the lock problem. We use Art Kagel's dostats to do an update statistics on the whole database mostly with default options. Only options on command line are -d and -x, if an exclude file exists. If -x is used, only table statistics are updated. The procedure statistics are outdated then and are updated the first time the proc is used. Default for our app is, that we are in transaction. So the session holds locks on sys-tables until some time later a commit is executed. All other sessions which want to use the same proc hold on because of "set lock mode to wait". Thanks for your help ! Regards - Frank
On Tue, 19 Aug 2003 16:58:30 -0400, Langelage, Frank wrote: Just add the -p option to reenable stored procedure stats updates when using -t, -i and/or -x. Art S. Kagel > Rajib Sarkar wrote: >> Is there a CSDK involved in the whole mix .... There was a bug in in >> the ODBC driver bundled with the CSDK (Bug#162089) which sent an >> implicit UPDATE STATS to the server ... the bug has been fixed in ODBC >> driver 3.82 (which comes with 2.81.TC2). >> >> > No, ODBC is not envolved. ESQLC is used. But today I found the reason > for the lock problem. > > We use Art Kagel's dostats to do an update statistics on the whole > database mostly with default options. Only options on command line are > -d and -x, if an exclude file exists. If -x is used, only table > statistics are updated. The procedure statistics are outdated then and > are updated the first time the proc is used. Default for our app is, > that we are in transaction. So the session holds > locks on sys-tables until some time later a commit is executed. All > other sessions which want to use the same proc hold on because of "set > lock mode to wait". > > Thanks for your help ! > > > Regards - Frank