Re: sqlnet.log

I agree with you - I don't want the log in the root directory. If it were placed there by by something other than oracle I wouldn't be so concerned, but since the oracle unix account seems to have some special kernal priviledges that other normal user accounts don't have I fear that it might be able to blow right past the barrier that prevents non-root accounts from writing to the last 10% of space in the root file system.

If I defind a directory for the log file in $ORACLE_HOME/network/admin/sqlnet.ora will that always force the log to be in that location for the server?

I probably have a bit of a strange situation here in that I am working with Lucent Conversant machines. Because of the way that Conversants operate it is sometimes necessary to access a remote database server. To do this we define a database link (in conversant terms a "handle"). In this case how is the location of the client sqlnet.log handled? Would it be created in the CWD of the user account that owns the programs which comprise the "conversant" application?. If so, the sqlnet.ora be placed in the home directory of that account?

I've been a dba for a while, but it has only been in the past six months that I've had to get involved with networking issues and it has been a real trial by fire for me.

Ken

Rick Wessman wrote:

> Kenneth C Stahl <BluesSax_at_Unforgettable.com> writes:
> > In the absence of a sqlnet.ora file in $ORACLE_HOME/network/admin, how
> > does oracle determine where to put the log file? For some reason the
> > sqlnet.log files seem to crop up in a variety of places on my system and
> > so far I haven't seen a real pattern.
> The sqlnet.log is put into the current directory unless specified otherwise.
> >
> > Also, when does sqlnet.ora get read? When oracle starts? When the
> > listener starts? When the system reboots? Is there any way of
> > controlling the level of information sent to sqlnet.log in a manner
> > similar to the say that the level of data to listener.log can be
> > controlled?
> Sqlnet.ora is read when the process starts. So, when the database starts, it
> reads sqlnet.ora. When a client program connects, it reads it.
> >
> > I've seen some references in the past to a .sqlnet.ora (note the '.' at
> > the beginning of the name - it is a hidden file) that is to be placed in
> > the home directory of a unix user account. Does anyone know anything
> > about this? Supposedly it overrides the system level sqlnet.ora.
> It used to be supported, but I'm not sure that it is now.
> > The reasons I ask all of this is because one of the systems I work with
> > seems to have a habit of placing sqlnet.log in the root directory. The
> > root file system on this box is already pretty full and I just don't
> > need to have log files being created there. However, I'm also interested
> > in learning whatever else anyone knows about all of the things I
> > mentioned.
> Placing sqlnet.log in the root directory is a bad idea, IMO, since some Unix
> systems will crash if / gets full.
> For the server, I would place it under $ORACLE_HOME. For client programs, I
> would allow it to be created in the current directory as it can contain
> valuable debugging information.
Received on Thu Jul 01 1999 - 10:11:50 CDT