Re: SE Help !!!!!

When running SE you need to remember that it uses UNIX locks to hold it's own locks, so the number of UNIX locks almost vertainly need increasing in the kernel. I'm not saying that this will sort your problem - just that it's a point to remember. 'sar -v' (on our system) shows the state of play with regard to numbers present & used. It is possible to determine who has a database table open (and therefore may have it locked) with the UNIX 'fuser' command. Again, this may or may not help. Regards In article <Bs-d3ps.jorget@delphi.com> jorget@delphi.com "Jorge Torralba" writes: > We are running Informix 4gl version 4.10.UE2 on the SE engine 5.00.UC2 > The hardware is a Sequent S81 Dynix/ptx 2.0.3 > The problem: > We believe we are having a serious problem with database locking. We have > looked at the standard disk contention issues but have not been able to > ascertain any good information on who has what locked. I miss Online :-( > > Is there any way short of writing very extensive logging functions ( we have > lots of code ), to determine who has a table/row locked in SE ? Informix > says "no" but im not always convinced by that. > > Some users are being locked for 30+ minutes. -- ============================================================================ Sally Woolrich | This mail contains my personal sally@excelsis.demon.co.uk | views not those of my employer! ============================================================================