deadlock or timeout error

[rajas...@my-deja.com]

Hi,

I am connecting to DB2 5.0 on MVS OS/390 from a windows NT using ODBC.
Below are the sequence of steps I do

1) 2 users connect to DB2
2) Both of them set autocommit to false
3) first user inserts a record into a table say mytable
4) second users issues a update statement on the same table, mytable.

I get an error "[IBM][CLI Driver][DB2] SQL0913N Unsuccessful execution
caused by deadlock or timeout. Reason code "00C9008E".
SQLSTATE=57033"

How can I do what I want to do with out errors.

any help appreciated.

Thanks,
-raja

Sent via Deja.com http://www.deja.com/
Before you buy.

[Phil Castle]

the first thing to do is to look at the system log on OS/390 - there will be
errror messages for the timeout event which will tell you what resource the
timeout occurred on.
1. if it was an index (most likely), it could be because you are using a
Type I index. Consider changing this to a Type II index (no locking is done
on Type II indexes).
2. if it was the table, look at the locksize for the tablespace - if it is
PAGE think about changing this to ROW.

Phil Castle.

<rajas...@my-deja.com> wrote in message
news:8aj1cg$teu$1...@nnrp1.deja.com...

[rajas...@my-deja.com]

The table doesn't have any indexes defined. I changed the LOCKSIZE to
ROW, I still get the same error. Any ideas?
Thanks,
-raja
In article <d%bz4.169$%ek1.9...@news.xtra.co.nz>,

[Phil Castle]

do you get an error message in the OS/390 system log, and if so what does it
say? Paste in the text so I can look at it....
Also - what rows are being updated in 4)? Not the whole table I hope as this
might well cause locking problems.

Phil.

<rajas...@my-deja.com> wrote in message
news:8aofkf$sns$1...@nnrp1.deja.com...

[rajas...@my-deja.com]

Below is the syslog message. The update statement is for only one row.
Thanks,
-raja
DSNT376I - PLAN=DISTSERV WITH 909
CORRELATION-ID=Program
CONNECTION-ID=SERVER
LUW-ID=GA070AC9.E204.028F16201600=392
THREAD-INFO=SYR:N00F2BB6:SYR:Program
IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN=DISTSERV
WITH
CORRELATION-ID=Program
CONNECTION-ID=SERVER
LUW-ID=GA070AC9.E004.028F16201558=390
THREAD-INFO=QSM:N00F2BB6:QSM:Program
ON MEMBER DSN1
DSNT501I - DSNILMCL RESOURCE UNAVAILABLE 910
CORRELATION-ID=Program
CONNECTION-ID=SERVER
LUW-ID=GA070AC9.E204.028F16201600=392
REASON 00C9008E
TYPE 00000304
NAME QSM .CORDOCS .X'000002' '.X'17'
In article <SDVz4.283$D6q1....@news.xtra.co.nz>,

[eric pearson]

Teach the villain:

CORRELATION-ID=Program
CONNECTION-ID=SERVER
LUW-ID=GA070AC9.E004.028F16201558=390
THREAD-INFO=QSM:N00F2BB6:QSM:Program
ON MEMBER DSN1

to use COMMIT!!!!

regards,
eric pearson
db2...@nospammindspring.com

[rajas...@my-deja.com]

How should I use COMMIT?

Thanks,
-raja
In article <ru63ds02jfdtm2bjo...@4ax.com>,

[skeane]

Seems to me that if there are no indexes on the table, then DB2
has no way to know that you are attempting to update a single
row. It mus do a tablescan to find whether any rows, including
the one locked by the insert, qualify.

Try indexing the table on the update keys.

* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

[Chollian Newsgroup User]