2006/2/15, Jose Linares <[EMAIL PROTECTED]>: > Hi, I'm new in MaxDB and I'm having some problems with it. First I have 2 > branches of my office but boith access the same database. One of them has > an slow connection and sometimes when they try to save some information, the > records in the database get locked for a long time (well at least I think > this is, because when all the connections where in the same branch I have no > problem). I want to know 1) if there's a query or something where I can > detect who is making the lock, so I can kill it; 2) how can I get over this > problem.
The proper solution seems to be either to provide a faster network connection or do smaller transactions via the slow link. Maybe you have a bug in your application code that doesn't properly commit all transactions. Alternatively you could try to use a different transaction isolation level - whether this makes sense depends on the nature of your db usage. IMHO killing locks is only an emergency solution for deadlock cases and other situations where nothings else helps. Kind regards robert -- Have a look: http://www.flickr.com/photos/fussel-foto/ -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
