RE: Mysterious sql problem
Expanding the term "environment" even further.....
What's your server doing during this time?
How long has it been up? Perhaps a reboot has activated something at
the server level (which may have been a recent change or something done
a long time ago/needed a reboot/never got one/now the server boots/chg
activates)....
What's your network doing?.... Is this a app running/connecting on the
same server as the DB or coming across a net as a client?...
You said you were IDS 9.3....
I heard 9.4 has dynamic set explain... You could turn that on for that
session (without putting it in code)...but you're not there...
Good luck,
NJ
-----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
-----------------------------------------
============================================================ The
information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
reproduction, dissemination or distribution of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and deleting it
from your computer. Thank you. Tellabs
============================================================
sending to informix-list