SQLIDEBUG, sqliprint
Posted in 1999
Topics: General Discussion
Following a hint of that friendly guy at Siemens Informix Support I found SQLIDEBUG (an environment variable) and sqliprint (a tool) to trace sql statements and other traffic between client and server. It seems that these are "undocumented features". Anyhow, I am looking for a documentation. Does anybody know where I can find it. TIA Reinhard
Reinhard Habichtsberg wrote: > Following a hint of that friendly guy at Siemens Informix Support > I found SQLIDEBUG (an environment variable) and sqliprint (a tool) > to trace sql statements and other traffic between client and server. > > It seems that these are "undocumented features". > Anyhow, I am looking for a documentation. > > Does anybody know where I can find it. Does it count if I write it now? SQLIDEBUG=2:prefix some_sql_command sqliprint prefix_* The first line sets the variable SQLIDEBUG to the value 2, followed by a colon and a prefix that will be applied to the file names. It then runs the program 'some_sql_command'. While the program is running, it will write the conversation between the program and the database to a file such as prefix_22334 (assuming the process ID of the program was 22334). You can then run sqliprint on the file. It will diagnose what the contents of the conversation means. The 2 is key; you can specify 1 instead, but sqliprint can't interpret the output (and, in all probability), neither can you. Errr; is there anything else I needed to say? -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.62 -- see http://www.perl.com/CPAN #include <disclaimer.h>