My question:
Is there any way to either stop logging Oracle this way or to limit the file
size for the SQLNET.LOG?
Thanks for any information.
Dieter
Dieter Gontermann <SHPFra...@shp-frankfurt.de> wrote in message
news:8p2asq$5u6$16$1...@news.t-online.com...
I'm not certain that that the ODBC driver has anything to do with
generating this file. Unless you've explictly turned logging on (from
the ODBC Data Source Administrator | Tracing) and set the log file to
SQLNET.LOG, the ODBC driver shouldn't be logging anything, much less 900
MB!
Is it possible that you've turned on logging of your SQL*Net connection?
Justin Cave
Oracle ODBC Development
Opinions expressed herein are mine and may not reflect those of Oracle
Corporation
Sent via Deja.com http://www.deja.com/
Before you buy.
Dieter Gontermann
<joc...@my-deja.com> schrieb in im Newsbeitrag:
8p6hlj$n84$1...@nnrp1.deja.com...
- I assume you've checked in the ODBC Data Source Administrator that
you've not turned logging on there.
- Are you certain that no one has turned on SQL*Net logging? It
definitely isn't turned on by default.
- To turn off SQL*Net tracing, open the file sqlnet.ora in your
%ORACLE_HOME%\network\admin directory and make sure you have the line
TRACE_LEVEL_CLIENT = OFF
Justin Cave
Oracle ODBC Development
Opinions expressed herein are my own and may not reflect those of Oracle
Corporation.
But I'm not sure, whether this SQLNET.LOG file is created by the normal
SQL*Net logging, because if there are no problems when accessing the
Oracle-databases, this file will not be created. In my opinion logging
should logg every step.
The file is only be created, when there are any problems connecting to the
database, for example if the network connection is broken. In that case,
every try to reach the database failes and therefore the error is logged
into SQLNET.LOG.
Dieter
Eric Givler <egi...@flash.net> schrieb in im Newsbeitrag:
Fhqt5.843$yY.6...@news.flash.net...