sqlnet.log appears in home directory

[Paul Thomson_2]

There is one server in Australia which is generating a file sqlnet.log everytime someone connects in their home directory.

An example of the log is .....
Fatal NI connect error 12545, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=oracle)(ARGV0=oracle)(ARGS='(DESCR
IPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')(DETACH=NO))(CONNECT_DATA=(CID=(PRO
GRAM=)(HOST=as013_1)(USER=xxadmin))))

VERSION INFORMATION:
TNS for HPUX: Version 8.0.6.0.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 8.0.6.0.0 - Produc
tion
Time: 05-APR-03 13:52:02
Tracing not turned on.
Tns error struct:
nr err code: 12206
TNS-12206: Message 12206 not found; No message file for product=NETWORK, fac
ility=TNS
ns main err code: 12545
TNS-12545: Message 12545 not found; No message file for product=NETWORK, fac
ility=TNS
ns secondary err code: 12560
nt main err code: 515
TNS-00515: Message 515 not found; No message file for product=NETWORK, facil
ity=TNS
nt secondary err code: 2
nt OS err code: 0


Does anyone have an idea what may cause these ?? I can set a job to clear them down, but Iwould like tofully understand the reason what creates them.
Thankyou.

[Yogeeraj_1]

hi,

below a quote from metalink:



The logging is automatic, there is no way to turn logging off, but since you are on Unix server, you can redirect the log file to a null device, thus eliminating the problem of disk space consumption.

In the SQLNET.ORA file, set LOG_DIRECTORY_CLIENT and LOG_DIRECTORY_SERVER equal to a null device.

For example:
LOG_DIRECTORY_CLIENT = /dev/null
LOG_FILE_CLIENT = /dev/null

in SQLNET.ORA suppresses client logging completely.


To disable the listener from logging, set this parameter in the LISTENER.ORA file:
logging_listener = off



Regards
Yogeeraj

[Yogeeraj_1]

hi again,

Also, according to Metalink can also be a TWO_TASK configuration problem with the connection to the database.
It is recommended not to rely on TWO_TASK variable for making default connection.
E.g. In a proC program use:
EXEC SQL CONNECT :user IDENTIFIED BY :pwd USING :connect_string;

hth
Yogeeraj

[Brian Crabtree]

Somewhere in thier .profile (or related startup files) they are running a sqlplus connection to a tns entry that either does not exist, or they do not have access to view (tnsnames.ora file is unreadable). The TNS-12545 error relates to not being able to connect because the object (tns entry) does not exist.

They also do not have the ORACLE_HOME set correctly from the "No message file" errors below that.

Hope this helps,

Thanks,

Brian

[Indira Aramandla]

Hi,
Sqlnet.log trace file helps Tracing an operation and to obtain more information on the internal operations of the components of Net8. This information can be evaluated to identify the events that led to an error or see you is loging in for security purpose.

At the same time these log facility uses a large amount of disk space and may have a significant impact upon system performance.

You could redirect these log files to a location where you have other log files and then schedule a cron job to trim them on a regular basis.

The variables 'LOG_DIRECTORY_CLIENT' or 'LOG_DIRECTORY_SERVER' helps to specify an alternate directory for the log file.

If they are not specified in the sqlnet.ora file, it will default to the current working directory: $ORACLE_HOME/BIN.

If the 'LOG_DIRECTORY_CLIENT' or 'LOG_DIRECTORY_CLIENT' syntax is specified in the sqlnet.ora file, it should give you the directory:

LOG_DIRECTORY_CLIENT=c:\NET\ADMIN
LOG_DIRECTORY_SERVER=/tmp/trace

[T G Manikandan]

LOG_DIRECTORY_CLIENT is to be defined in the sqlnet.ora file.

Else by default when there is a sql session from a directory it has its log file there.


Thanks