Trace session
I have executed a SQL statement on two servers with exactly the same configuration,OS and DB version.I traced the sessions on both the servers executing the same SQL.Now i need to find out from those trace files which SQL is performing better then the other.what are the factors i need to cosider to come to a conclussion that this SQL's performance is better than the other SQL.The result of processed trace files using tkprof is as below.
//SQL in server A
SELECT SERVICE.TERM
FROM
abc.TARIF_SERVICES TS,abc.DIC_DATA SERVICE WHERE TS.N =:B2 AND TS.SERVICE=
SERVICE.CODE AND SERVICE.UP=9 AND SYSDATE BETWEEN SERVICE.FD AND SERVICE.TD
AND SERVICE.LANG=1 AND :B1 BETWEEN TS.FD AND TS.TD
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 5203 0.57 0.53 0 0 0 0
Fetch 5203 0.15 0.59 48 26071 0 5203
total 10407 0.73 1.13 48 26071 0 5203
Misses in library cache during parse: 0
Optimizer mode: CHOOSE
Parsing user id: 55 (recursive depth: 1)
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 48 0.01 0.33
//SQL in server B
SELECT SERVICE.TERM
FROM
abc.TARIF_SERVICES TS,abc.DIC_DATA SERVICE WHERE TS.N =:B2 AND TS.SERVICE=
SERVICE.CODE AND SERVICE.UP=9 AND SYSDATE BETWEEN SERVICE.FD AND SERVICE.TD
AND SERVICE.LANG=1 AND :B1 BETWEEN TS.FD AND TS.TD
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 5203 0.57 0.53 0 0 0 0
Fetch 5203 0.15 0.59 48 26071 0 5203
total 10407 0.73 1.13 48 26071 0 5203
Misses in library cache during parse: 0
Optimizer mode: CHOOSE
Parsing user id: 55 (recursive depth: 1)
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 48 0.01 0.33
Thank you all...
Formatting the output
SELECT SERVICE.TERM
FROM
abc.TARIF_SERVICES TS,abc.DIC_DATA SERVICE WHERE TS.N =:B2 AND TS.SERVICE=
SERVICE.CODE AND SERVICE.UP=9 AND SYSDATE BETWEEN SERVICE.FD AND SERVICE.TD
AND SERVICE.LANG=1 AND :B1 BETWEEN TS.FD AND TS.TD
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 5203 0.57 0.53 0 0 0 0
Fetch 5203 0.15 0.59 48 26071 0 5203
total 10407 0.73 1.13 48 26071 0 5203
Misses in library cache during parse: 0
Optimizer mode: CHOOSE
Parsing user id: 55 (recursive depth: 1)
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 48 0.01 0.33
//SQL in server B
SELECT SERVICE.TERM
FROM
abc.TARIF_SERVICES TS,abc.DIC_DATA SERVICE WHERE TS.N =:B2 AND TS.SERVICE=
SERVICE.CODE AND SERVICE.UP=9 AND SYSDATE BETWEEN SERVICE.FD AND SERVICE.TD
AND SERVICE.LANG=1 AND :B1 BETWEEN TS.FD AND TS.TD
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 5203 0.57 0.53 0 0 0 0
Fetch 5203 0.15 0.59 48 26071 0 5203
total 10407 0.73 1.13 48 26071 0 5203
Misses in library cache during parse: 0
Optimizer mode: CHOOSE
Parsing user id: 55 (recursive depth: 1)
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 48 0.01 0.33As Sybrand already mentioned,the results are identical.Is it somethig that is reported for either query that it is slow compared to the other one?If you suspect some performance degradation than you may want to trace both the queries with 10046 trace.Search this forum for this event and use it to trace the queries further.
Aman....
Similar Messages
-
Bug: Trace session from sessions report
Attempt to trace session against a 9.2.0.6 database, failed due to DBMS_MONITOR not available.
Is this a newer package that the database version needs to be verified and adjust to use this call instead for older databases? sys.dbms_system.set_boo_param_in_sessionActually what would be best would be to use this for < 10g databases:
dbms_system.set_ev (9,29,10046,X,'');
where level x would be in a dropdown box in the dialog when enabling tracing on the session.
As a developer and DBA, I enable trace at many different levels depending on what I am diagnosing. -
How to trace session(3rd paty application) accessing oracle
Solaris 9
oracle 9i and 10g
I would like to know how to trace session which is 3rd party application currently running .
I need to collect statisctics for currently running session.
Thanks.
Message was edited by:
user539835See this thread:
Re: SQL_TRACE help to newbie in oracle
Search the forum and you will also see how to manually decode most of the trace file.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc. -
Event Trace Session missing for Failover Cluster
I have a failover cluster setup and is managed via a Windows Domain controller for the failover cluster network. I am troubleshooting a potential issue with the failover cluster and the recommendation is to go into event viewer, app & service
logs, Microsoft, windows and look for failover cluster diagnostics and operations logs and these do not exist.
It appears they are created by having an event trace session associated with windows failover clustering but apparently it was't created when the cluster was created for some reason. I am wondering how to create the proper event trace session
in order to get these additional failover cluster logs created?Hello,
the following forum mat be the better one for your needs:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverClustering
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter: -
Failed to start one or more trace sessions
Hi,
I just installed the analyser on a Win2012R2 Core server and can not get the analyser to start.
===========================================
Failed to start one or more trace sessions due to the followinf errors:
Error Details:
Unable to start ETW session MMA-ETW-Livecapture-d28fac22-61bc-4e52-ac03-60fa79d2ec62
Host Name: Localhost
Error in the application.
===========================================
This is with the provider:
Microsoft-Windows-NDIS-PacketCapture
I have this error on two core machines so I missing something?!
BR
PerThis happens if you are not logged in as administrator, or perhaps if a session is already running. Does it change if you run Message Analyzer as administrator? What do you see when you type "Get-NetEventSession" form PowerShell?
Paul -
Trace session based on CLIENT_IDENTIFIER
Hello all,
i am on 11.2.0.1....we have a sap application and trying to trace a session from DB end....and seems like the job that the end user runs jumps from one session to another....in this senerio...how would i trace a session ??? i read article about dbms_monitor package to trace it...but as i mention, sap keep chaning the session from one to another.....
i read the below article...
http://ocsurabaya.wordpress.com/2007/07/18/tracing-sql-in-oracle-database-10g/
in which it suggest to set the service name and module name....but the problem is its hard to get the module name as its doing quite a few things....it jumps from one module to another....is there anyway to trace a session based on its CLIENT_IDENTIFIER (from v$session)....as this looks like the domian user account for that user who is running the job....
as i mentioned during that time(when job is ran)...the sid changes, modeule changes...the only thing consistent is the CLIENT_IDENTIFIER ( which seems to be the domian user name )...
so how can i trace a session based on CLIENT_IDENTIFIER ??user8363520 wrote:
Hello all,
i am on 11.2.0.1....we have a sap application and trying to trace a session from DB end....and seems like the job that the end user runs jumps from one session to another....in this senerio...how would i trace a session ??? i read article about dbms_monitor package to trace it...but as i mention, sap keep chaning the session from one to another.....
i read the below article...
http://ocsurabaya.wordpress.com/2007/07/18/tracing-sql-in-oracle-database-10g/
in which it suggest to set the service name and module name....but the problem is its hard to get the module name as its doing quite a few things....it jumps from one module to another....is there anyway to trace a session based on its CLIENT_IDENTIFIER (from v$session)....as this looks like the domian user account for that user who is running the job....
as i mentioned during that time(when job is ran)...the sid changes, modeule changes...the only thing consistent is the CLIENT_IDENTIFIER ( which seems to be the domian user name )...
so how can i trace a session based on CLIENT_IDENTIFIER ??is application 3-tier?
does application utilize connection pooling? -
We run SAP-J2EE 6.4 SP 17 on linux with JVM 1.4.2 in a cluster environment with 2 nodes.
We found out that often, the system creates a few hundred sessions objects with the same login id within 1-2 minutes of time frame.
Each line (out of a few hundreds) contain the following attributes
User Name: [email protected]
Session ID : (J2EE1234567)ID0012345678DB12345678901234567890End
Created On:17:24 02/09/07
Last Access:17:24 02/09/07
Expiration 17:54 02/09/07
Application:<b>sap.com/irj</b>
Note that the application attribute does not provide any real information about the application and process that created the sessions.
Is there any way to trace those session.
ThanksHi,
You can change the settings of logs and traces in Visual administrator.
go to /usr/sap/SID/JCxx/j2ee/admin
Then,./go.sh
enter with administrator credentials.
Under SIDserver---sevices--Log configurator.
go to Locations tab at the right side.
Then go to com---sapengineservices--
trace.
Change the severity of the trace level as required there.
reward points if helpful.............. -
hi all
i read some articals of how to trace oracle sessions and i have some question
i use database 10g
trace vs event ??? different between them ????
how to trace individual statement i hope to give me this point in ex:
due to i can't get the sql_id ,how to know the sql_is of specify statement??
thanks861100 wrote:
hi all
i read some articals of how to trace oracle sessions and i have some question
i use database 10g
trace vs event ??? different between them ????
how to trace individual statement i hope to give me this point in ex:
due to i can't get the sql_id ,how to know the sql_is of specify statement??
thanksHow do I ask a question on the forums?
SQL and PL/SQL FAQ
below show how to trace single SQL statement
bcm@bcm-laptop:~$ sqlplus user1/user1
SQL*Plus: Release 11.2.0.1.0 Production on Tue Aug 28 07:08:09 2012
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
07:08:09 SQL> set autotrace trace explain
07:08:28 SQL> select sysdate from dual;
Execution Plan
Plan hash value: 1388734953
| Id | Operation | Name | Rows | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 1 | 2 (0)| 00:00:01 |
| 1 | FAST DUAL | | 1 | 2 (0)| 00:00:01 |
07:08:37 SQL> -
Client identifier to trace sessions
Dear all,
I have CRM application installed in oracle soa 10.1.3 , (OID-connection pool). At the DB level, Data source user name is displayed in v$session. I understand that user session can be traced using
client_identifier. I referred below links :
http://download.oracle.com/docs/cd/B19306_01/network.102/b14266/apdvprxy.htm#i1009003
http://download.oracle.com/docs/cd/B28359_01/network.111/b28531/app_context.htm#CIHCFDJG
I couldn't understand the above notes.. Does this client identifier to be set in DB or application ? how I can set trace for this OID users ?
I know this is a DOC question, But I cannot understand this as am a newbie.
Please guide?
KaiThe idea behind client identifier is that it should be set on the appserver so that session usage across pooled connections can be tracked.
-
TRACE SESSION X TRACE USER (11gr2)
Hi,
We are facing performance isues on a Windows 2008 Oracle database (11.2.0.2) SAP BI Loads. There is a huge chain of jobs that are started and runs on the database with talkes a long time to execute. Let's supose that in this chain there are 500 jobs inside and takes more ou less than 15 to 20 hours. But, sometimes, this time increases and takes 30, 35, 40 hours.
So, we need to understand in which steps of the chain it takes more time, and one of the activities that we are planing is to trace all the execution and identify the waits.
The problem is:
. If there is a "father" process that call's the others, it would be easy since we could set the trace in this session.
Now,
How can we guarantee to trace all the chain since each step is one session opened on the database? Anybody know the usage or viability to trace the user at all? Any other options that could help us in this issue?
Doubt: Even that we set a trace on a "father" session, and this session calls/opens other sessions, this trace would contain all the instructions for all the sessions ou just the father? The trace sees a relation and traces all that are started in parallel?
Please disconsider tracing all the database. Not useful for this situation.
I aprreciate any HelpHi,
this does not seem to be a security related issue. While the scheduler may know the notion of 'chains' the sql_trace facility
has no understanding of inheritance, so to gather trace info build it into the jobs so they can set event 10046 in their
respective job sessions. Also if you generate an AWR report for the duration of the jobs, you may be able to pinpoint
certain sql statements using more resources, compare with AWR report for the 'normal' situation,
greetings,
Harm ten Napel -
How to generate the trace files for remote db link session's?
User are complaining, the db link queries are performing slowness..
how to enable the sql trace session for db link's in remote database...
Is there any way to enable sqltrace for the dblink session ?
if not how to enable the sql trace for entire database level, rather than session based...An explain plan of the SQL being ran on the local database will review the SQL being passed to the remote db. You can then explain that SQL on the remote db.
I have had to tune a few distribued queries so more than likely the explain plan alone will be enough to allow you to tune the query to improve performance. If not then you can go to the trouble of trying to set up dual traces.
HTH -- Mark D Powell -- -
Trace file created for the wrong session
DB version : 10.2.0.3.0
OS version: Solaris 5.10
2 node RAC
Using DBMS_MONITOR.SESSION_TRACE_ENABLE, I have been trying to trace an oracle session spawned by a C++ application.
So, i determined which instance this session is connected by querying gv$session. I logged in as SYS in that instance's Node and then issued
execute dbms_monitor.session_trace_enable(4371,98124, true, false);After enabling, i saw new A trace file being generated. But this trace is actually tracing SYS's session which executed dbms_monitor.session_trace_enable and not the session (4371,98124) !!! I tested few basic queries in SYS's session like
select sysdate from dualAnd i can see all these queries appearing in the trace file. What could be the cause of this issue?
I have noticed that
SHARED_SERVERS = 1 on both nodes. Is this causing this weird issue? For tracing, If i disable SHARED_SERVERS using
alter system set SHARED_SERVERS = 0
will it cause any connection problems for the client applications because of their tnsnames.ora file setting?John_75 wrote:
Thank you DBMS_DIRECT.
trace is enabled only on the instance to which the caller is connected
So, how do i enable tracing for sessions spawned by Java or C++ applications.
According to the documentation, i can use DBMS_MONITOR for tracing applications
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/sqltrace.htm
Your 2 node RAC has two instances (e.g. INST1 and INST2). My understanding of that is that with the above command, to be able to trace session 123 connected to INST1, your SYS need to be connected to INST1. To be able to trace session 456 connected to INST2, your SYS need to be connected to INST2. -
Signon tracing enable multi-session trace file?
Hi Guys,
When I enable PeopleCode tracing in signon tracing link, I found trace file was generated with somebody else name. I was thinking it should generate my trace file only. Does anyone know if it is correct or these is any configuration about this?
Thanks,
BobJohn_75 wrote:
Thank you DBMS_DIRECT.
trace is enabled only on the instance to which the caller is connected
So, how do i enable tracing for sessions spawned by Java or C++ applications.
According to the documentation, i can use DBMS_MONITOR for tracing applications
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/sqltrace.htm
Your 2 node RAC has two instances (e.g. INST1 and INST2). My understanding of that is that with the above command, to be able to trace session 123 connected to INST1, your SYS need to be connected to INST1. To be able to trace session 456 connected to INST2, your SYS need to be connected to INST2. -
How to generate trace file from different session?
I have a cron job which starts several Oracle stored proc (Oracle 9.2). I want to generate a trace file when the job is running. I know I can use this alter session command before I start this job. But this is my session not the job session. So this command won't generate trace file for job's session.
ALTER SESSION SET EVENTS '10046 TRACE NAME CONTEXT FOREVER, LEVEL 8';
Appreciate any ideas.
Thanks.
S.Easiest way is to use database control/grid control - click trace session button!
The 'old fashioned way is'
begin
DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION(SID,serial#,TRUE);
end;
find sid and serial# in a select from v$session
There are other ways too but this is probably the easiest.
You'll need appropriate privileges to run this .
Cheers,
Harry -
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
---------------------
Maybe you are looking for
-
MacMail no longer compatible - please help
Hi, Sometime ago MacMail was uninstalled from my system. I am currently using Leopard OSX 10.5.8 on a 2008 Macbook and I tried to re-install the MacMail application from my installations CDs, which it did. It installed version 3.4 of MacMail. However
-
Happy New Year! I am using PSE 10 on a Vista. In the editor, I save as a PSD File. During my work-flow, sometimes a box with a red X appears saying: Could not save because the file is already in use or was left open. What is this about? As you can im
-
Is it possible to disable panel stretch/"scaling" on a ThinkPad X200?
A few months ago, I was enlightened by a thread about how to disable panel stretching and enable the execute disable feature on my N200 laptop (these were features I'd been missing for years) by means of SymCmos. Now that I have an X200, I was impres
-
Why finger scanner doesn't recognize already given finger scanning.
Hi team, Device is accepting same finger scanning, it should either prompt with a message this finger scanning already exist?
-
How to organize a gaming project
Hi freinds,can any one guide how to develope a gaming project.