Setting logging trace level

Hello,
Is it possible to set the logging trace level(FATAL, ERROR, ...DEBUG) for the following jolt components :
JRLY, JRAD, JSL, JSH ? If yes how ? If no how can we debbug this component ? or make the logs more talkative ?
Thanks in advance for your answers
pledreau

There aren't any configurable debug levels available to customers in Jolt.
Your best bet for debugging this component is to turn on the TMTRACE
facility. Depending on which ATMI APIs your application is using, this will
produce few or no additional userlog messages from the Jolt processes
themselves, but it will produce a significant amount of additional userlog
information from the application servers that are called by Jolt, which may
be of help in debugging.
Ed
<First Last> wrote in message news:[email protected]..
Hello,
Is it possible to set the logging trace level(FATAL, ERROR, ...DEBUG) for
the following jolt components :
JRLY, JRAD, JSL, JSH ? If yes how ? If no how can we debbug this component
? or make the logs more talkative ?
Thanks in advance for your answers
pledreau

Similar Messages

How can I check and change the system set events trace level?

Dear all:
How can I check the system set events trace level? I don't want the alert_log so big.
Regards
Terry

Hi Terry;
Please check :
How to determine which system events are currently being set? [ID 845043.1]
How To List All The Named Events Set For A Database [ID 436036.1]
How to set EVENTS in the SPFILE [ID 160178.1]
Also check:
http://www.dba-oracle.com/t_grid_rac_events_in_Oracle.htm
http://www.akadia.com/services/ora_events.html
Hope it helps
Regard
Helios

Set logging severity level for clustered servers

How can I set the logging severity level for clustered servers just once at the cluster level rather than one at a time at the server level?

I know the logging is server by server, but surely there is a way to configure the multiple servers with one change rather than one by one. We have 40 some servers in the cluster.

Unable to set trace level

Hello,
I have a problem with the trace level (by trace level I mean this one: http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/tracing_logging.html) in the Java Console when deploying a Java Applet.
With "Next Generation Java Plugin" (JPI >= 1.6.0_10) disabled I am able to set a trace level (0-5) in the java console; if it is enabled I am not able to set a trace level. The Problem is: it seems all outputs written to the Java Console seem to be added to one string, so if there are many trace messages in the java console you'll get a OutOfMemoryException.
And to make things even better: with JPI 1.6U19 and U20 I am not even able to disable the "Next Generation Java Plugin" (well theoretically I am but it seems to ignore my settings).
Also adding Applet Parameters (-Djavaplugin.trace=false -Djavaplugin.trace.option=off) for setting tracelevels has no effect, I get trace messages for loading resources etc. in the java console (Stating "image loaded: jar:http://what.ever.else/some.jar!some.image").
I tested with various Java Plugins (1.6U17, U19 and U20) and various Browsers (IE6 and Firefox 3.5) on WinXP SP2 with no difference.
Does anybody have a clue how to turn off this tracing permanently as it fills up my heap?!?
cheers
Christian

Where exactely did you change the localisation to US and has this to be done on every client running the web interface or just the server it's running on?

How to launch Web administration service and set trace level for web dispac

Experts,
Can some one help on how to setup trace level for Web dispatcher? and how to launch web administration interface.
Thanks in advance.

Hi Sam,
You can launch the Web Dispatcher Interface through the follwing link:
http://host:port/sap/wdisp/admin
The Username & Password are created when the profile is run for the first time. The userid is ICMADM
This link points to the web disaptcher administration interface & its usage.
You can set the trace level once you login to the interface.
http://help.sap.com/saphelp_nw70/helpdata/en/4f/3bee29d9764e988bdeecdb4d484722/frameset.htm
Hope it is helpful.
Regards,
Abhishek

Trace levels

Hi,
We are facing problem of archieve folder occuping lot of space.
I would like to check if we have set optimum log & trace levels.
I have gone through below link:
http://help.sap.com/saphelp_nw04/helpdata/en/e2/f410409f088f5ce10000000a155106/frameset.htm
Here, it says that "tracing is not normally turned on".
How can I check if tracing is turned on or off in my case? Do I have to manually set all nodes in location tree to None and then change it to info as and when required?
Suggestions are appeciated.
Regards,
Apurva

The archive folder contains the trace files in compressed format.
You can always delete the compress files if you are sure you don't need to see those trace entries.
Turning the Trace Levels to "Default" in Visual Administrator should reduce your trace output.
You should select the top level of the Log Configurator and then press the "set default" option to apply to all sub-levels.
Hope this helps.

Programmatic read access to applet console trace level

Is there any apis for getting the current trace level setting of the applet java console?

thanks for the info.
But as a user I would find it confusing, especially as that would mean to see traces from your applet I would have to turn on, and see, traces from the JVM mixed in with them.I'm surprised others don't use System.out.println, or e.printStackTrace in their applet code. Is that not common? It irritates me to know end that i'm not allowed (by the company) to have them there. So a problem occurs at a customer site, and there's no way to know what happened. So i was able to talk them into emitting important stuff as long as the user consciously set the trace level up, something a normal person would never do, most likely.
So how do other people log information from applets? I can't imagine you're actually logging errors to the filesystem? sending them back to the server? seems hard to believe anyone would do that?

RE: log trace on Service Object

I haven't tried myself; but got a copy from someone of part of technote
10398 which says (the minimum you need is:)
trc:in:1 Prints out information about interpreter state object.
10 - Print method entry/exit
trc:in:2 Trace the interpretation of method invocations and exception
handling
2 - Prints entry/exit and exceptions
trc:in:51:1 Traces method entry/exit by task
trc:in:54:1 Traces method entry/exit by application
Try it.
-----Original Message-----
From: Eric Abécassis [mailto:[email protected]]
Sent: Tuesday, April 13, 1999 10:24 AM
To: Forte User List
Subject: log trace on Service Object
Hi Everybody,
I would like to set log trace on each call (method entry and exit) on a
Service Object, but I didn't find any log flag which helps me.
Does someone have any ideas on how to do that ?
Thank you for your help !
Eric Abécassis <[email protected]>
Senior Architect
Sema Group DTS
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi Eric,
You can find on http://perso.club-internet.fr/dnguyen/ a little tool called CodeAdd which adds Entry and Return trace. I fact, you
can use it to add any kind of code at the beginning and the end of your methods.
It also allows you to add a pre-formated comments header in you code.
In a further version, It may be possible to replace a code sequence from your methods. For instance, you may add a trace class and
change a task.Part.LogMgr.Putline by a call to your own class, or need to suppress some lines.
Just be carefull to use the tool on a local backupo of your repository : CodeAdd updates your methods directly in the repository.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
Url : http://perso.club-internet.fr/dnguyen/
Eric =?iso-8859-1?Q?Ab=E9cassis?= a écrit:
Hi Everybody,
I would like to set log trace on each call (method entry and exit) on a
Service Object, but I didn't find any log flag which helps me.
Does someone have any ideas on how to do that ?
Thank you for your help !
Eric Abécassis <[email protected]>
Senior Architect
Sema Group DTS
Eric Abécassis <[email protected]>
Senior Architect
Sema Group DTS
Eric Abécassis
Senior Architect <[email protected]>
Sema Group DTS Courrier HTML
les Algorithmes - Pythagore A route des Lucioles, BP 279;Sophia Antipolis;;06905;France Tél. cellulaire: +33 (0) 6 62 36 68 83
Télécopie: +33 (0) 4 93 95 xx xx
Bureau: +33 (0) 4 93 95 46 50
Informations supplémentaires:
le nom ABECASSIS
Prénom Eric
Version 2.1-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Log trace on Service Object

Hi Everybody,
I would like to set log trace on each call (method entry and exit) on a
Service Object, but I didn't find any log flag which helps me.
Does someone have any ideas on how to do that ?
Thank you for your help !
Eric Abécassis <[email protected]>
Senior Architect
Sema Group DTS

Hi Eric,
You can find on http://perso.club-internet.fr/dnguyen/ a little tool called CodeAdd which adds Entry and Return trace. I fact, you
can use it to add any kind of code at the beginning and the end of your methods.
It also allows you to add a pre-formated comments header in you code.
In a further version, It may be possible to replace a code sequence from your methods. For instance, you may add a trace class and
change a task.Part.LogMgr.Putline by a call to your own class, or need to suppress some lines.
Just be carefull to use the tool on a local backupo of your repository : CodeAdd updates your methods directly in the repository.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
Url : http://perso.club-internet.fr/dnguyen/
Eric =?iso-8859-1?Q?Ab=E9cassis?= a écrit:
Hi Everybody,
I would like to set log trace on each call (method entry and exit) on a
Service Object, but I didn't find any log flag which helps me.
Does someone have any ideas on how to do that ?
Thank you for your help !
Eric Abécassis <[email protected]>
Senior Architect
Sema Group DTS
Eric Abécassis <[email protected]>
Senior Architect
Sema Group DTS
Eric Abécassis
Senior Architect <[email protected]>
Sema Group DTS Courrier HTML
les Algorithmes - Pythagore A route des Lucioles, BP 279;Sophia Antipolis;;06905;France Tél. cellulaire: +33 (0) 6 62 36 68 83
Télécopie: +33 (0) 4 93 95 xx xx
Bureau: +33 (0) 4 93 95 46 50
Informations supplémentaires:
le nom ABECASSIS
Prénom Eric
Version 2.1-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Sbtio.log and trace levels

Hi all,
we're using Tivoli (TSM) with RMAN and I want to log error messages to USER_DUMP_DEST/sbtio.log . The log is there but always empty, even when there is a trace file stating there should be messages in it.
RMAN documentation says that sbtio.log must be configured with TSM. This does not seem to be true: I found that you can set a trace via ALLOCATE CHANNEL .... TRACE <integer>. I did NOT find anything in the RMAN documentation on this topic.
Can anyone enlighten me? What trace levels are there, what do I do to just get the errors dumped to the log? Any hints appreciated.
Thanks, Susanne

The 'details' can' tbe set to be more specific.
MAX_DUMP_FILE_SIZE specifies the maximum size of trace files (excluding the
alert file). Change this limit if you are concerned that trace files may use too much
space.
A numerical value for MAX_DUMP_FILE_SIZE specifies the maximum size in
operating system blocks.
A number followed by a K or M suffix specifies the file size in kilobytes or
megabytes.
The special value string UNLIMITED means that there is no upper limit on trace
file size. Thus, dump files can be as large as the operating system permits.
See Also:
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Your operating system-specific Oracle documentation for the
default value and range of values
Parameter type String
Syntax MAX_DUMP_FILE_SIZE = {integer [K | M] |
UNLIMITED}
Default value UNLIMITED
Parameter class Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values 0 to unlimited, or UNLIMITED
See Also: Oracle9i Database Administrators Guide and Oracle9i
Database Performance Tuning Guide and Reference for more
information on setting this parameter

Trace level of RWB's Message Monitoring - Detail Message - Tab "Audit log"

Hi,
My flow is: File -> PI -> Transformed File with seeburger module. Everything is good except the trace level in RWB.
Exactly, in our PI production, under RWB -> Message Monitoring, when I select a message (e.g PI -> Outside) and see its Detail, under tab "Audit Log", I have a log with only 2 pages (which corresponds to the sender part "File -> PI")... whereas in our PI pre-production, I have 4 pages for the exact same flow, on which I have also info of the receiver part "PI -> Outside"...
My question is just: do you know which parameter is involved in this trace level of RWB's Message Monitoring Detail log ?
regards.
Mickael
Note: in [Help SAP|http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/frameset.htm], I see only this sentence "Audit Log: The audit log for the selected message is displayed as the default setting.".
Edited by: Mickael Huchet on Oct 18, 2011 1:59 PM

Hi Shabarish,
Thanks that will help to localize my search.
else by hazard, you don't know which parameter in this tree is for the "Audit Log"?
coz I did a quick look in prod and pre-prod, but it seems the severity is the same (e.g "Info" for most of them) whereas the trace level of "Audit log" is different.
Thanks for
Regards.

Accessing trace level or logging flag from applet

I need to do some performance tracking related logging from my applet. It will be decided at runtime whether the applet should perform logging or not. The logging should work for java plugin 1.4.x.
The java plugin console provides the facility to set trace level and enable / disable logging. Is there some way I can access these values from my applet? Is it possible to access the PluginLogger from my applet ?

Thanks for the reply.
If I set a runtime parameter on the Java Plug-in Control Panel, I need to access it through my applet.
I am not able to figure out how to access the runtime parameters from my applet.

NET8의 LOGGING과 TRACE 관련 PARAMETER에 대한 Q & A

제품 : SQL*NET
작성날짜 : 2002-05-07
NET8의 LOGGING과 TRACE 관련 PARAMETER에 대한 Q & A
=================================================
PURPOSE
Net8을 이용하면서 발생하는 문제를 추적 하기위해 oracle의 configuration
file에 들어갈 수 있는 parameter와 logging과 tracing을 하는 방법에 대해
질의/응답을 통해 알아 보도록 한다.
Explanation
1) NET8에서 trace를 사용하는 이유와 어떤 component들에 trace를 할 수 있나?
Trace의 특징은 네트워크을 수행하게 될때 network event들을 기술한다
즉 trace와 관련된 일련의 문장들이 자세하게 생성된다.
"Tracing"의 운영으로 log파일에 제공되어 있는 것 보다 NET8의 component들의
내부적인 정보를 보다 많이 얻을 수 있다.
이러한 정보는 에러의 결과로 인하여 발생하는 동일한 event들로 파일들에
결과가 생성되어 이를 이용하여 문제의 원인을 판단할 수 있다.
주의 : trace의 기능을 이용하는 경우 충분한 disk space와 system performance의
현격한 저하를 가져올 수 있다 즉 trace의 기능은 반드시 필요할
경우에만 사용할 것을 권한다.
<< trace의 기능을 이용하여 trace를 할 수 있는 component들 >>
* Network listener
* Net8 components on the client and server
* Connection Manager
* Oracle Names Server
* Oracle Names Control Utility
* TNSPING utility
2) 어떤 parameter들을 설정하면 trace 기능을 이용할 수 있는가 ?
tracing을 하기 위해서는 특정 trace parameter들을 설정함으로써 가능하며
아래에 주어진 방법들과 또는 utility들중 하나를 선택하여 설정함으로써
사용할 수 있다.
* Component Configuration Files
* Component Control Utilities
* Oracle Trace
component의 configuration 파일을 이용하여 traceing parameter를 설정하려면
1.component의 configuration 파일에 다음의 traceing parameter를 설정한다.
- SQLNET.ORA for client or server, LISTENER.ORA for listener:
TRACE_LEVEL_<CLIENT/LISTENER/SERVER>=(0/4/10/16)
TRACE_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
LOG_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
2.만일 component들이 수행중인 동안 configuration 파일의 수정이 있었다면
병경된 parameter들을 사용하기 위해 component들을 다시 시작하여야 한다.
component control utility들을 이용하여 trace parameter들을 설정하려면
1. listener의 경우, Listener Control Utility(lsnrctl)에서 TRACE 명령어를
이용하여 listener가 수행중인 동안에도 trace level을 설정할 수 있다.
EX)
     RC80:/mnt3/rctest80> lsnrctl
     LSNRCTL for SVR4: Version 8.0.4.0.0 - Production on 01-SEP-98 15:16:52
     (c) Copyright 1997 Oracle Corporation. All rights reserved.
     Welcome to LSNRCTL, type "help" for information.
     LSNRCTL> trace admin
     Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
     Opened trace file: /mnt4/coe/app/oracle/product/8.0.4/network/trace/
lsnr_coe.trc
     The command completed successfully
     LSNRCTL> trace off
     Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
     The command completed successfully
     LSNRCTL> exit
     RC80:/mnt3/rctest80>
2. Oracle Names의 경우, Names Control Utility(namesctl)에서 TRACE_LEVEL
명령어를 이용하여 Oracle Names가 수행중인 동안에도 trace level을
설정할 수 있다.
주의 : Connection Manager의 경우, trace level은 configuration 파일인 CMAN.ORA
에서만 설정할 수 있다.
Oracle Enterprose manager(이하 OEM)에 있는 Oracle Trace는 trace parameter들을
설정하고 GUI를 통해 trace data의 형태를 볼수 있도록 하는 tracing tool이다.
3) trace된 data를 해석할 수 있는 다른 utility들이 있다면 ?
Trace Assistant를 사용하면 사용자의 *.trc 파일 (SQL*Net v2의 형식에 의해
생성된) 또는 *.txt (Orace Trace 과 TRCFMT에 의해 생성된 출력물)을 통해
trac된 정보를 해석할 수 있다.
이 유틸리티 네트워크의 문제들로 인해 발생하는 문제점들을 진단하고
해결하는 데 보다 많은 정보를 제공하여 사용자의 이해를 돕는다.
* the source and destination of trace files
* the flow of packets between network nodes
* which component of Net8 is failing
* pertinent error codes
다음에 주어진 명령어를 수행하므로써 Trace Assistant 실행할 수 있다.
trcasst [options] <filename>
Trace Assistant Text Formatting Options
-o Displays connectivity and Two Task Common (TTC) information.
After the -o the following options may be used:
c (for summary connectivity information)
d (for detailed connectivity information)
u (for summary TTC information)
t (for detailed TTC information)
q (displays SQL commands enhancing summary TTC information)
-p Oracle Internal Use Only
-s Displays statistical information
-e Enables display of error information After the -e, zero
or one error decoding level may follow:
0 or nothing : translates the NS error numbers dumped from the
nserror function plus lists all other errors
1 : displays only the NS error translation from the nserror function
2 : displays error numbers without translation
만일 option들이 제공되지 않는다면 기본적으로 -odt -e -s가 지정되어 자세한
connectivity, Two-Task Common, 에러 level 0 그리고 통계정보들이 tracing 된다.
4) SQL*Net v2 tracing과 어떻게 다른가 ?
Net8 tracing에서는 이전 버전인 SQL*NET V2에서 제공 되는 모든 option을
포함하고 있고 Oracle Trace의 기능이 추가되었다.
이것은 Oracle Trace Repository를 OEM 콘솔을 통하여 사용자의 trace 정보를
관리할 수 있도록 허용한다.
5) *.cdf와 *.dat은 어떤 파일 인가 ?
*.cdf 와 *.dat 파일들은 Oracle Trace에 의해 생성되는 파일들로서 이 파일들을
읽기 위해서는 반드시 trcfmt utility를 이용해야만 한다.
trcfmt는 binary (*.dat와 *.cdf의 확장자) 파일내에 있는 data를
일반 text(.txt의 확장자)로 정보를 추출한다. 이 tool을 사용하기 위해서는
다음의 명령어를 이용하면 된다.
trcfmt collection.cdf
주의 : .cdf와 .dat파일이 존재하는 디렉토리가 아닌 곳에서 이 tool을 이용
     한다면 path가 포함되야 한다. 만일 하나의 .cdf 와 .dat 파일들내에
     여러 프로세스들의 tracing정보가 수집된다면 그것들은 process_id.txt의
이름과 함께 파일이 추출될 것이다.
6) trac관련 configuration은 어떤 것이 있으며 설정할 수 있는 parameter는
무엇이 있는가 ?
==========================================================================
|| SQLNET.ORA Parameters ||
==========================================================================
DAEMON.TRACE_DIRECTORY
Purpose: Controls the destination directory of the Oracle
Enterprise Manager daemon trace file
Default Value: $ORACLE_HOME/network/trace
Description
Available Oracle Enterprise Manager Installation Guide
Example: DAEMON.TRACE_DIRECTORY=/oracle/traces
DAEMON.TRACE_LEVEL
Purpose: Turns tracing on/off to a certain specified level for
the Oracle Enterprise Manager daemon.
Default Value: 0 or OFF
* 0 or OFF - No trace output
* 4 or USER - User trace information
Available Values
* 10 or ADMIN - Administration trace information
* 16 or SUPPORT - WorldWide Customer Support trace
information
Description
Available Oracle Enterprise Manager Installation Guide
Example: DAEMON.TRACE_LEVEL=10
DAEMON.TRACE_MASK
Purpose: Specifies that only the Oracle Enterprise Manager daemon
trace entries are logged into the trace file.
Default Value: $ORACLE_HOME/network/trace
Description
Available Oracle Enterprise Manager Installation Guide
Example: DAEMON.TRACE_MASK=(106)
LOG_DIRECTORY_CLIENT
Purpose: Controls the directory for where the log file is written
Default Value: Current directory where executable is started from.
Example: LOG_DIRECTORY_CLIENT=/oracle/network/trace
LOG_DIRECTORY_SERVER
Purpose: Controls the directory for where the log file is written
Default Value: Current directory where executable is started from.
Valid in File: SQLNET.ORA
Example: LOG_DIRECTORY_SERVER=/oracle/network/trace
LOG_FILE_CLIENT
Purpose: Controls the log output filename for an Oracle client.
Default Value: SQLNET.LOG
Example: LOG_FILE_CLIENT=client
LOG_FILE_SERVER
Purpose: Controls the log output filename for an Oracle server.
Default Value: SQLNET.LOG
Example: LOG_FILE_SERVER=svr
NAMESCTL.TRACE_LEVEL
Purpose: Indicates the level at which the NAMESCTL program should
be traced.
Default Value: OFF
Values: OFF, USER, or ADMIN
Example: NAMESCTL.TRACE_LEVEL=ADMIN
NAMESCTL.TRACE_FILE
Purpose: Indicates the file in which the NAMESCTL trace output is
placed.
Default Value: namesctl_PID.cdf and namesctl_PID.dat
Example: NAMESCTL.TRACE_FILE=NMSCTL
NAMESCTL.TRACE_DIRECTORY
Purpose: Indicates the directory where trace output from the NAMESCTL
utility is placed.
Default
Value: $ORACLE_HOME/network/trace
Example: NAMESCTL.TRACE_DIRECTORY=/ORACLE/TRACE
NAMESCTL.TRACE_UNIQUE
Indicates whether a process identifier is appended to the
Purpose: name of each trace file generated, so that several can
coexist.
Default
Value: OFF
Values: OFF or ON
Example: NAMESCTL.TRACE_UNIQUE = ON
TNSPING.TRACE_DIRECTORY
Purpose: Control the destination directory of the trace file
Default Value: $ORACLE_HOME/network/trace
Example: TNSPING.TRACE_DIRECTORY=/oracle/traces
TNSPING.TRACE_LEVEL
Purpose: Turns tracing on/off to a certain specified level
Default Value: 0 or OFF
* 0 or OFF - No trace output
* 4 or USER - User trace information
Available Values
* 10 or ADMIN - Administration trace information
* 16 or SUPPORT - WorldWide Customer Support trace
information
Example: TNSPING.TRACE_LEVEL=10
TRACE_DIRECTORY_CLIENT
Purpose: Control the destination directory of the trace file
Default Value: $ORACLE_HOME/network/trace
Example: TRACE_DIRECTORY_CLIENT=/oracle/traces
TRACE_DIRECTORY_SERVER
Purpose: Control the destination directory of the trace file
Default Value: $ORACLE_HOME/network/trace
Example: TRACE_DIRECTORY_SERVER=/oracle/traces
TRACE_FILE_CLIENT
Purpose: Controls the name of the client trace file
Default Value: SQLNET.CDF and SQLNET.DAT
Example: TRACE_FILE_CLIENT=cli
TRACE_FILE_SERVER
Purpose: Controls the name of the server trace file
Default Value: SVR_PID.CDF and SVR_PID.DAT
Example: TRACE_FILE_SERVER=svr
TRACE_LEVEL_CLIENT
Purpose: Turns tracing on/off to a certain specified level
Default Value: 0 or OFF
* 0 or OFF - No trace output
* 4 or USER - User trace information
Available Values
* 10 or ADMIN - Administration trace information
* 16 or SUPPORT - WorldWide Customer Support trace
information
Example: TRACE_LEVEL_CLIENT=10
TRACE_LEVEL_SERVER
Purpose: Turns tracing on/off to a certain specified level
Default Value: 0 or OFF
* 0 or OFF - No trace output
* 4 or USER - User trace information
Available Values
* 10 or ADMIN - Administration trace information
* 16 or SUPPORT - WorldWide Customer Support trace
information
Example: TRACE_LEVEL_SERVER=10
TRACE_UNIQUE_CLIENT
Used to make each client trace file have a unique name to
Purpose: prevent each trace file from being overwritten with the next
occurrence of the client. The PID is attached to the end of
the filename.
Default
Value: OFF
Example: TRACE_UNIQUE_CLIENT=ON
USE_CMAN
If the session is in an Enhanced Discovery Network with a
Purpose: Names Server, this parameter forces all sessions to go
through a Connection Manager to get to the server.
Default
Value: FALSE
Values: TRUE or FALSE
Example: USE_CMAN=TRUE
==========================================================================
|| LISTENER.ORA Parameters ||
==========================================================================
LOG_DIRECTORY_listener_name
Purpose: Controls the directory for where the log file is written
Default Value: Current directory where executable is started from.
Example: LOG_DIRECTORY_LISTENER=/oracle/traces
LOG_FILE_listener_name
Purpose: Specifies the filename where the log information is
written
Default Value: listener_name.log
Example: LOG_FILE_LISTENER=lsnr
TRACE_DIRECTORY_listener_name
Purpose: Control the destination directory of the trace file
Default Value: $ORACLE_HOME/network/trace
Example: TRACE_DIRECTORY_LISTENER=/oracle/traces
TRACE_FILE_listener_name
Purpose: Controls the name of the listener trace file
Default Value: LISTENER_NAME.CDF and LISTENER_NAME.DAT
Example: TRACE_FILE_LISTENER=lsnr
TRACE_LEVEL_listener_name
Purpose: Turns tracing on/off to a certain specified level
Default Value: 0 or OFF
* 0 or OFF - No trace output
* 4 or USER - User trace information
Available Values
* 10 or ADMIN - Administration trace information
* 16 - WorldWide Customer Support trace information
Example: TRACE_LEVEL_LISTENER=10
==========================================================================
|| NAMES.ORA Parameters ||
==========================================================================
NAMES.TRACE_DIRECTORY
Purpose: Indicates the name of the directory to which trace files
from a Names Server trace session are written.
Default
Value: platform specific
Example: names.trace_directory = complete_directory_name
NAMES.TRACE_FILE
Purpose: Indicates the name of the output file from a Names Server
trace session. The filename extension is always.trc
Default
Value: names
Example: names.trace_file = filename
NAMES.TRACE_LEVEL
Purpose: Indicates the level at which the Names Server is to be
traced.
Default Value: OFF
Example: names.trace_level = OFF
NAMES.TRACE_UNIQUE
indicates whether each trace file has a unique name, allowing
Purpose: multiple trace files to coexist. If the value is set to ON, a
process identifier is appended to the name of each trace file
generated.
Default
Value: OFF
Example: names.trace_unique = ON
names.trace_file = names_05.trc
==========================================================================
CMAN.ORA Parameters
==========================================================================
TRACING
Default
Value: NO
Example: TRACING = NO
References
7) listener.log 파일에 loggin정보를 남기지 않게 하는 방법이 있나요 ?
고객이 개발하여 사용중인 application에서 NET8을 이용하여 접속하거나 접속을
종료하는 경우 listener.log에 이와 관련된 정보가 남으며, 수 많흔 사용자가
접속을 하게되므로서 급속하게 listener.log 파일이 커져 file system이 꽉
차거나 데이터베이스가 hang이 되는 결과를 초래하는 경우가 있다.
고객들은 listener.log에 write할수 있는 메세지의 양에 제한을 두기를 원하는
경우가 있으나 이러한 기능은 제공되지 않는다. 하지만 listener의 logging은
on 또는 off를 할 수는 있다.
Net8에서는 listener.ora에 "LOGGING_(the listener name)=off"를 설정하게 되면
listener의 logging을 멈출 수 있다.
** SQL*NET 2.3.x 에서도 이 parameter가 유효한가요 ? **
물론 사용이 가능합니다. NET8에서 사용하는 것과 동일하게 parameter를
listener.ora에 설정함으로서 가능합니다.
EX)
LOGGING_LISTENER=OFF
이 parameter는 listener의 전체 logging을 disable하는 parameter로 일부만
여과하여 logging할 수 있는 기능은 아니다.
이 parameter는 NET8에 알려진 parameter로 SQL*NET 2.3.x manuals에 나와
있지는 않지만 정상적으로 사용할 수 있다.
Reference Ducumment
---------------------

When I open BEx, error message appears: "....trace level 8 activated.."

Hi,
when i open bex, then it appears:
"SAPGUI 640
Enviroment information:
Directory: 'C:\Documents and Setting\ ...\SapWorkDir
trace level 8 activated
logging activated
For maximum data security delete the settings as soon as possible."
But I dont know, which setting it is meaning.
Thanks zd.

Jan,
The "*." should NOT be in the registry.
We are still experiencing the problem and have a customer message into SAP. The problem only occurs logging on through SAP Portal. It occurs on Sun J2SE version 1.5 and 1.4.2 consistently. It occurs using the Microsoft VM occaisionaly. Deleting cookies, temporary internet files and clearing the history in IE seems to solve the problem for users using the Microsoft JVM.
We are on XP SP2 with all the latest MS security patches. Since we use Portals as the main logon process, we have the registry key set to prevent saplogon from launching when the user logs on.
Hope that helps,
John

Running out of disk space - IGS Log Trace

Hello,
for a few weeks we are continuously running out of disk space on our CE7.2 Application Server.
The following files are increasing every second:
Path: usr\sap\C72\J00\igs\log
mux_sapce72.trc
pw_sapce72_0.trc
pw_sapce72_1.trc
The entry that is written into these files per second is always similar to this one:
[ServerTcpIp::NiServerloop] After NiSelSelect, ret=-5
[ServerTcpIp::NiServerloop] timeout --> continue
[ServerTcpIp::NiServerloop] Before NiSelSelect
[ServerTcpIp::NiServerloop] After NiSelSelect, ret=-5
[ServerTcpIp::NiServerloop] timeout --> continue
[ServerTcpIp::NiServerloop] Before NiSelSelect
[ServerTcpIp::NiServerloop] After NiSelSelect, ret=-5
[ServerTcpIp::NiServerloop] timeout --> continue
[ServerTcpIp::NiServerloop] Before NiSelSelect
[ServerTcpIp::NiServerloop] After NiSelSelect, ret=-5
[ServerTcpIp::NiServerloop] timeout --> continue
[ServerTcpIp::NiServerloop] Before NiSelSelect
Does anybody know what's the reason for this is and how to solve it?
Thanks in advance!
Michael

Hi...Michael....
What is your IGS 720 SP Level ?
What is IGS trace level ? if it is "1" .....set to "0".
.....Note 1423280 - IGS 720 creates huge trace files...If time allows look at this note if it is relevent...
Rgds
PR

Setting logging trace level

Similar Messages

Maybe you are looking for