Steve,
In
order to avoid timeouts while running queries against tables with concurrent
inserts, you can either:
Change
the insert process to issue more frequent commits, however, depending on the
type of query, you may still get lock waits.
Change
the query to use UR (uncommited read). However, this means that the reader
will be getting inconsistent data, since no row locks will be taken.
Wayne Driscoll
Product Developer
Quest Software
Inc.
[EMAIL PROTECTED]
Note: All opinions are strictly my own.
-----Original Message-----
From: steve shapero [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 3:47 PM
To: [EMAIL PROTECTED]
Subject: [DB2EUG] locks during inserts
From: steve shapero [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 3:47 PM
To: [EMAIL PROTECTED]
Subject: [DB2EUG] locks during inserts
hi
group--
i am doing some
large inserts into a UDB 7.2 db from an Access client. during this time,
if i try to run a select on this table, i get
SQL0911N The
current transaction has been rolled back because of a deadlock
or timeout. Reason code "2". SQLSTATE=40001
or timeout. Reason code "2". SQLSTATE=40001
should i be using a
different isolation level? i need to be able to do the selects so my
website doesn't go down when i am doing updates...
sorry if this is a
stupid question...
thanks
steve
