SQLIDEBUG exact content of the output
Hi, has anybody a description, what's in the output-File when SQLIDEBUG is set? Is it possible to analyze all statements from the client to the server? Thanks Ruediger Papke
In article <36A1B4E1.B43BD1F5@t-online.de>, Rüdiger Papke <Ruediger.Papke@t-online.de> writes >Hi, >has anybody a description, what's in the output-File >when SQLIDEBUG is set? >Is it possible to analyze all statements from the client to the server? > This is an internal thing, only Informix support know about it and you should only use it when they advise you to. The have an internal Informix-only tool called sqliprint to view it! >Thanks > >Ruediger Papke -- David Williams
David Williams wrote: > In article <36A1B4E1.B43BD1F5@t-online.de>, Rüdiger Papke > <Ruediger.Papke@t-online.de> writes > >has anybody a description, what's in the output-File > >when SQLIDEBUG is set? > >Is it possible to analyze all statements from the client to the > >server? > > This is an internal thing, only Informix support know about it > and you should only use it when they advise you to. > > The have an internal Informix-only tool called sqliprint to view it! And sqliprint is distributed as standard on the most recent products. I'm not sure whether it was added to ClientSDK (a logical place to put it) or whether it comes with the servers instead -- I've not checked. And I don't know whether it is documented anywhere... Sorry; I haven't memorized the correct way to set SQLIDEBUG to get the data in a format that sqliprint can process. However, you can certainly see all the statements sent to the server from a single process using SQLIDEBUG and sqliprint -- and it can be very enlightening to do so. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>
Jonathan Leffler wrote: > > David Williams wrote: > > In article <36A1B4E1.B43BD1F5@t-online.de>, Rüdiger Papke > > <Ruediger.Papke@t-online.de> writes > > >has anybody a description, what's in the output-File > > >when SQLIDEBUG is set? > > >Is it possible to analyze all statements from the client to the > > >server? > > > > This is an internal thing, only Informix support know about it > > and you should only use it when they advise you to. > > > > The have an internal Informix-only tool called sqliprint to view it! > > And sqliprint is distributed as standard on the most recent products. > I'm not sure whether it was added to ClientSDK (a logical place to > put it) or whether it comes with the servers instead -- I've not > checked. And I don't know whether it is documented anywhere... It comes with the ClientSDK. > Sorry; I haven't memorized the correct way to set SQLIDEBUG to get > the data in a format that sqliprint can process. However, you can > certainly see all the statements sent to the server from a single > process using SQLIDEBUG and sqliprint -- and it can be very > enlightening to do so. either export SQLIDEBUG=1:/tmp/filename or export SQLIDEBUG=2:/tmp/filename > -- > Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) > Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN > #include <disclaimer.h> Best regards, Stefan Weideneder
In article <36A33A3F.3C287F2A@weideneder.de>, Stefan Weideneder <stefan@weideneder.de> writes >Jonathan Leffler wrote: >> >> David Williams wrote: >> > In article <36A1B4E1.B43BD1F5@t-online.de>, Rüdiger Papke >> > <Ruediger.Papke@t-online.de> writes >> > >has anybody a description, what's in the output-File >> > >when SQLIDEBUG is set? >> > >Is it possible to analyze all statements from the client to the >> > >server? >> > >> > This is an internal thing, only Informix support know about it >> > and you should only use it when they advise you to. >> > >> > The have an internal Informix-only tool called sqliprint to view it! >> >> And sqliprint is distributed as standard on the most recent products. >> I'm not sure whether it was added to ClientSDK (a logical place to >> put it) or whether it comes with the servers instead -- I've not >> checked. And I don't know whether it is documented anywhere... > >It comes with the ClientSDK. > True, I just installed it today (CLISDK 2.8) >> Sorry; I haven't memorized the correct way to set SQLIDEBUG to get >> the data in a format that sqliprint can process. However, you can >> certainly see all the statements sent to the server from a single >> process using SQLIDEBUG and sqliprint -- and it can be very >> enlightening to do so. > >either > >export SQLIDEBUG=1:/tmp/filename >or >export SQLIDEBUG=2:/tmp/filename > ??? What is the difference SQLIDEBUG is not documented and only available via Tech Support... > >> -- >> Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) >> Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN >> #include <disclaimer.h> > >Best regards, > >Stefan Weideneder -- David Williams