RE: [DB2EUG] locks during inserts

[Reys, Ellen]

Title: Message

Reason code 2 means that you are running into the deadlock situation.

First of all, take a snapshot for locks while running both applications. See, where you have a lock contention. It might be on the systables as well.

 

Try changing your isolation level prior to connecting for the "select" session:

 

db2 terminate

db2 change isolation to ur

db2 connect to <db_name>

db2 "select ....."

 

Ellen Klebaner-Reys
Data Management Services
Inovant - a Visa Solutions Company
[EMAIL PROTECTED]/650-432-1746  m/s: 3125-1D

-----Original Message-----
From: steve shapero [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 1: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

 

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