User1 probably locked the table (lock escalation), this would cause user1 to
go into 'lock wait' which would timeout depending on the db config, then
user1 may have filled the transaction log and had to rollback

-----Original Message-----
From: Sathya.[Email Address Removed] [mailto:Sathya.[Email Address Removed]
Sent: Wednesday, April 14, 2004 10:07 AM
To: [Email Address Removed] Can anybody tell me the reason for this






Hi,

We are running DB2 UDB 7.2.4 on Aix 4.3 with multi Partition.

User 1 was doing a bulk insert of 2 million rows into a table without
committing in between.

User 2, At the same time, launched a query which involved full access of
this table along with other tables.

What happened was User 2 got a Time out message after few mintues. To the
surprize User 1 transaction got ROLLED BACK.

Any reason why?

Thanks in Advance




---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
Get today's cartoon: http://www.LazyDBA.com
To unsubscribe, e-mail: db2udbdba-[Email Address Removed] additional commands, e-mail: db2udbdba-[Email Address Removed]DB2 & UDB email list listserv db2-l LazyDBA home page