SQLIDEBUG and sqliprint
rkusenet wanted to trace every SQL statement of a session using SQLIDEBUG and sqliprint on IDS 9.21.UC4, and asked how to stop it and which manual covers it. He found it seemed not to work with JDBC. Amit Dandekar confirmed JDBC ignores SQLIDEBUG and said to set the PROTOCOLTRACE and PROTOCOLTRACELEVEL connection properties with the -g JDBC jars, per the JDBC programmer's manual.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
I need to trace every sql of a session for debugging purpose. Reading c.d.i archives it looks like SQLIDEBUG and sqlprint is a good option. I believe this is how sqlidebug starts export SQLIDEBUG=2:/tmp/sqllog export SQLIDEBUG where /tmp/sqllog is the name of the file to hold the data. How do I stop it once done. I believe the file size can grow rapidly. Also does SQLIDEBUG work only with a logged database, since it snifs the logical logs. Which manual describes these enviroment variables in detail. TIA. ravi
"rkusenet" <rkusenet@sympatico.ca> wrote in message news:c6oc0d$eahps$1@ID-75254.news.uni-berlin.de... > I need to trace every sql of a session for debugging purpose. Reading > c.d.i archives it looks like SQLIDEBUG and sqlprint is a good option. > > I believe this is how sqlidebug starts > > export SQLIDEBUG=2:/tmp/sqllog > export SQLIDEBUG looks like SQLIDEBUG can not be used with java/jdbc. It is only for 'C'. The ids version we are using is 9.21.UC4. Is this true?
JDBC does not recognize SQLIDEBUG when it is set as an environment variable . However you can get a sqli protocol trace via JDBC by setting JDBC connection property PROTOCOLTRACE and having "-g" jars in classpath. Refer to IBM Informix Programmers manual http://publibfi.boulder.ibm.com/epubs/pdf/ct1utna.pdf Page 301/424 of the pdf file for details. "rkusenet" <rkusenet@sympatico.ca> wrote in message news:<c6omfb$duekk$1@ID-75254.news.uni-berlin.de>... > "rkusenet" <rkusenet@sympatico.ca> wrote in message > news:c6oc0d$eahps$1@ID-75254.news.uni-berlin.de... > > I need to trace every sql of a session for debugging purpose. Reading > > c.d.i archives it looks like SQLIDEBUG and sqlprint is a good option. > > > > I believe this is how sqlidebug starts > > > > export SQLIDEBUG=2:/tmp/sqllog > > export SQLIDEBUG > > looks like SQLIDEBUG can not be used with java/jdbc. It is > only for 'C'. The ids version we are using is 9.21.UC4. > > Is this true?
JDBC driver will not recognize SQLIDEBUG set as environment variable However you can get sqli protocol trace by setting JDBC connection property "PROTOCOLTRACE" and "PROTOCOLTRACELEVEL" and having "-g" versions of jdbc jar files in classpath. Refer to JDBC Programmers manual page 301/424 for details. http://publibfi.boulder.ibm.com/epubs/pdf/ct1utna.pdf