isolation & lock mode in onstat

Posted in 2003

Micha — Sat, 21 Jun 2003 20:47:00 +0200 — source: Usenet: comp.databases.informix

How reliable is the output of onstat -g sql as far as the isolation and lock mode is concerned? I have an ESQL/C process that sets committed read and wait 60, however in the output of onstat -g sql there is quite frequently DR for dirty read and Not Wait, which both would be a major problem for the application. I'm actually tracing a problem that would be explicable if the isolation were dirty read. This is 7.31.UC2 on solaris 5.7 for x86. --Micha

Related threads

Posting from the Informix-list
Migrating from IDS 9.40.UC6 to 11.50.UC3
Ip for a network session
questions onstat -g