How to find out why a table is locked?

Hi! While upgrading a large database application to a new version, I noticed that the application accidently hung when inserting on a certain table. The sql code works ok for other databases (oracle, sybase). When using the previous version of the application, informix works fine. Hence, there must be a bug introduced inbetween the two versions causing this regression. I greatly welcome your hints how to find out what makes informix think that a table is locked (trace/debug/monitor commands). Thank you very much, Sven C. Koehler -- email: schween at snafu de

Oh come now. You have GOT to give us something more to work with. Art S. Kagel "Sven C. Koehler" wrote: > > Hi! > > While upgrading a large database application to a new version, I noticed that > the application accidently hung when inserting on a certain table. > The sql code works ok for other databases (oracle, sybase). When using > the previous version of the application, informix works fine. > Hence, there must be a bug introduced inbetween the two versions causing this > regression. > > I greatly welcome your hints how to find out what makes informix think that a > table is locked (trace/debug/monitor commands). > > Thank you very much, > > Sven C. Koehler > > -- > email: schween at snafu de

"Sven C. Koehler" wrote: > > Hi! > > While upgrading a large database application to a new version, I noticed that > the application accidently hung when inserting on a certain table. > The sql code works ok for other databases (oracle, sybase). When using > the previous version of the application, informix works fine.¨ Did you check your application logic/have to recompile the app? Did you check the lock level of the table - someone might have forgotten the -ss flag of the dbexport in which case you could have page mode locking where once you had row level locks. You could also investigate the options to oncheck. > Hence, there must be a bug introduced inbetween the two versions causing this > regression. Hmm yes, when my programs fail I always "know" it's an Informix bug, or an OS bug, or a hardware bug, or a localised glitch in the space-time continuum. But just sometimes it turns out to have been my fault all along... Anyway, did you check the Informix web site for bug reports? > > I greatly welcome your hints how to find out what makes informix think that a > table is locked (trace/debug/monitor commands). Well you could try onstat -k, or you could try selecting on syssessions and syslocks in the sysmaster database, that's if you have a version which supports these things. What version are you on, be the way? -- In article <3978CFF0.CB1B2BB2@my-deja.com.guacamole>, stacia123@my-deja.com.guacamole said: > Goldfish don't fit through the air nozzle of most erotic dolls.