>> > Welcome to the world of deadlocks. I can only recommend some good
long
> > reading of the rather excellent Sybase documentation on deadlocks
(which
> > will happen even if you upgrade to 12.0 and use row level locking).
> Sorry Matt, but that's not what's happening at all. If this were a
> deadlock one of the connections would get a 1205 error (i.e. "your
> command has been aborted as the deadlock victim").
Yes, I thought this was an issue with locking at first, but it was
happening even with just one process accessing DB.
> In this case this is a bug in the network handling code of the
> original 11.0.3.3 release for linux. Upgrading to 11.0.3.3#6 should
> fix the problem.
It sure fixed my problem, thanks a lot Michael.
Vlad Jebelev
