RE: isolation level
Pankaj-
Lock mode wait is designed to allow statements to grab data as
soon as the conflicting application finishes with it, rather than just
erring out. I'd suggest using LOCK MODE WAIT 3 to allow 3 seconds for
your update to complete. If application speed is not an issue, you may
want to run a bit longer.
--EEM
> -----Original Message-----
> From: Scott Mackenzie [mailto:scottm@dinecollege.edu]
> Sent: Thursday, September 15, 2005 4:18 PM
> To: informix-list@iiug.org
> Subject: RE: isolation level
>
> -----Original Message-----
> From: owner-informix-list@iiug.org
[mailto:owner-informix-list@iiug.org]
> On Behalf Of Pankaj Patel (DHL US)
> Sent: Thursday, September 15, 2005 12:39 PM
> To: Art S. Kagel; prateek_mjv@yahoo.com; informix-list@iiug.org
> Subject: isolation level
>
> Art, I have lock isolation level question. I have a DB which is more
> like a look up DB, once in a while it gets updates and all the tables
> have page level locking.
> When the DB is accessed remotely sometimes application errors out with
> 243: Could not position within a table>
> My suggestion for the developers at first was to use set isolation to
> dirty read, but the application needs updated information not stale
> data, does using lock mode wait make sense here?. I thought usually
> locks mode wait is used only to make updates or it could be used in
this
> case even though it is just for selects?.
>
> Thanks
>
> Pankaj Patel
> (480)-375-7803
>
> If you can react the same way to winning and losing, that's a big
> accomplishment. That quality is important because it stays with you
the
> rest of your life. - Chris Evert
> sending to informix-list
>
>
> Pankaj,
>
> Sometimes you can get that error when your select returns either
> zero or more than one response - anything other than one.
>
>
> Scott MacKenzie - Dine' College ISD
> Phone/Voice Mail: 928-724-3376
> Email: scottm at dinecollege.edu
> sending to informix-list
sending to informix-list