RE: Mysterious sql problem
-----Original Message-----
From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]
On Behalf Of Simmons, Keith
Sent: Friday, November 05, 2004 11:09 AM
To: informix-list@iiug.org
Cc: dgriffen@finishline.com
Subject: RE: Mysterious sql problem
>Dave
>
>You say the exact same statement, but is the environment the
>same? i.e. do you have a lock mode set to wait in the app and
>not in dbaccess, do you set isolation dirty read in dbaccess
>but not in the app? What is the app session showing in the locks
>column when it is 'stuck'?
>
>Keith
Good question, it can be so many things - I can quickly think of temp
spaces (your system is very busy), disk access, update statistics,
memory .....
A whole lot of things in the environment. In a year an environment
normally changes a lot, in terms of usage and size ........
Run dbschema -d <database> -hd <table> to have a look at your update
stats on this table.
Dirk
sending to informix-list