Close all SQL trace

Hi,how I can close all SQL trace .
that is I run a SQL with a client application such as SQL developer
and I want no one can see this SQL script use views such as v$sqltext,v$sql,v$sqlarea etc.

user11203282 wrote:
and I want no one can see this SQL script use views such as v$sqltext,v$sql,v$sqlarea etc.Every SQL is going to use these views. Can you elaborate a bit what exactly you are looking for ?
Amardeep Sidhu

Similar Messages

Ability to perform ALTER SESSION SET SQL TRACE but not all alter clauses

I see that in order to run the ALTER SESSION SET SQL TRACE command, the user should be explicitly granted alter session privilege as the CREATE SESSION privilege alone is not enough. Is there a way to grant the ability to perform ALTER SESSION SET SQL TRACE but not the other clauses such as GUARD, PARALLEL & RESUMABLE?.
Thanks
Sathya

If you are using Oracle 10g and above, you can use DBMS_SESSION.session_trace_enable procedure,
it doesn't require alter session system privilege.
Simple example:
SQL> connect test/test@//192.168.1.2:1521/xe
Connected.
SQL> alter session set tracefile_identifier='my_id';
Session altered.
SQL> alter session set sql_trace = true
2 ;
alter session set sql_trace = true
ERROR at line 1:
ORA-01031: insufficient privileges
SQL> execute dbms_session.session_trace_enable;
PL/SQL procedure successfully completed.
SQL> select * from user_sys_privs;
USERNAME                 PRIVILEGE                    ADM
TEST                      CREATE PROCEDURE                NO
TEST                      CREATE TABLE                    NO
TEST                      CREATE SEQUENCE                    NO
TEST                      CREATE TRIGGER                    NO
TEST                      SELECT ANY DICTIONARY               NO
TEST                      CREATE SYNONYM                    NO
TEST                      UNLIMITED TABLESPACE               NO
7 rows selected.
SQL> execute dbms_session.session_trace_disable;
PL/SQL procedure successfully completed.
SQL> disconnect
Disconnected from Oracle Database 10g Release 10.2.0.1.0 - Productionand here is result from tkprof:
TKPROF: Release 10.2.0.1.0 - Production on So Paź 23 00:53:07 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Trace file: xe_ora_176_my_id.trc
( ---- cut ---- )
select *
from
user_sys_privs
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.08       0.08          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        2      0.01       0.01          0         15          0           7
total        4      0.09       0.09          0         15          0           7
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 61
Rows     Row Source Operation
      7 HASH GROUP BY (cr=15 pr=0 pw=0 time=11494 us)
      7   CONCATENATION (cr=15 pr=0 pw=0 time=4913 us)
      0    MERGE JOIN CARTESIAN (cr=4 pr=0 pw=0 time=1169 us)
      0     NESTED LOOPS (cr=4 pr=0 pw=0 time=793 us)
      0      TABLE ACCESS FULL SYSAUTH$ (cr=4 pr=0 pw=0 time=592 us)
      0      INDEX RANGE SCAN I_SYSTEM_PRIVILEGE_MAP (cr=0 pr=0 pw=0 time=0 us)(object id 312)
      0     BUFFER SORT (cr=0 pr=0 pw=0 time=0 us)
      0      TABLE ACCESS FULL USER$ (cr=0 pr=0 pw=0 time=0 us)
      7    NESTED LOOPS (cr=11 pr=0 pw=0 time=3429 us)
      9     HASH JOIN (cr=9 pr=0 pw=0 time=2705 us)
      9      TABLE ACCESS FULL SYSAUTH$ (cr=4 pr=0 pw=0 time=512 us)
     63      TABLE ACCESS FULL USER$ (cr=5 pr=0 pw=0 time=914 us)
      7     INDEX RANGE SCAN I_SYSTEM_PRIVILEGE_MAP (cr=2 pr=0 pw=0 time=510 us)(object id 312)
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
SQL*Net message to client                       2        0.00          0.00
SQL*Net message from client                     2       20.64         20.65
BEGIN dbms_session.session_trace_disable; END;
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.01       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           1
Fetch        0      0.00       0.00          0          0          0           0
total        2      0.01       0.00          0          0          0           1
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 61

Trace all sql statements

Hi,
Is it possible to trace all the SQL's into one trace file or any other alternative to capture all the SQL statements.

1. Export will take some time or a long time to run.
You will have to either
a. Use CONSISTENT=Y (and hope that you are able to get a consistent export)
b. Stop Transactions for the duration.
In option a. if you do allow transactions those transactions will appear neither in the Export NOR in the "trace file" that you will be generating later !! You WILL lose transactions.
2. There's no way to get a "trace file" to capture all SQL statements and bind values across multiple database sessions such that they are properly synchronised in time.
a. You can't get a trace file that you can simply run to reapply transactions.
b. You can't sequence transactions from multiple sessions running concurrently.
3. How fast do you REALLY think you will be able to apply that "trace file" (which, in any case, you CANNOT generate) ? It will take noticeable to considerable time.
4. How do you propose to transfer the Export dump to the remote location ? When you have no network connectivity ? Via tapes, transfered by courier ? Then why can't you transfer a Database Hot Backup and ArchiveLogs via tapes, transferred by courier ?
Hemant K Chitale
http://hemantoracledba.blogspot.com

CLIENT 에서 SQL TRACE 뜨기

제품 : ORACLE SERVER
작성날짜 : 2002-05-07
PURPOSE
Client에서 SQL trace를 뜨는 방법
EXPLANATION
오라클을 사용하는 tool 에서 sql trace 를 사용하고자 하면
alter session set sql_trace=true ; 를 사용한다.
또는 dbms_session.set_sql_trace (true) 사용한다.
이는 forms 를 비롯하여 precompiler 를 포함한다.
또 이의 반대는
alter session set sql_trace= false ; 를 사용한다.
또는 dbms_session.set_sql_trace (false) 사용한다.
이 때 실행된 결과는 user_dump_dest 에 쌓이는데 , file 이름은 process 번호를
참고한다.
그러나 MTS 의 경우 trace file 의 구분이 모호해지므로 client를 connect 시
dedicate 로 붙여 trace 를 사용하여야 하며, 만일 다른 session 에서 다른
session의 것을 trace 뜨고 싶으면,
dbms_system.set_sql_trace_in_session 을 사용할 수 있다.
EXAMPLE
이의 사용법은 다음과 같다.
1. Setup
catproc.sql 에서 생성되는 package 와는 달리 dbms_system 의
public synonym 은 생성되지 않고 권한도 부여되지 않는다.
DB 생성 초기에 SYS user 만 reference 할 수 있으므로 이 package 를
사용할 user에게 권한을 부여한다.
예제 : GRANT EXECUTE ON DBMS_SYSTEM to username;
2. v$session 으로부터 SID 와 serial 번호를 부여한다.
SQL> select sid, serial#, osuser, username
2> from v$session;
SID SERIAL# OSUSER USERNAME
7 66 <osLogin> <oracleUserName>
3. 원하는 session 에서 SQL trace 를 setting 한다.
exec sys.dbms_system.set_sql_trace_in_session
(12,16631,TRUE);
또는 pl/sql procedure 에서:
begin
sys.dbms_session.set_sql_trace ((<sid>,<serial>,TRUE);
end
4. session 에서 SQL Trace 를 끝마친다. 이 결과는 user_dump_dest에
쌓인다.
exec sys.dbms_system.set_sql_trace_in_session
(<sid>,<serial>,FALSE);
또는 pl/sql procedure 에서
begin
sys.dbms_session.set_sql_trace (<sid>,<serial>,FALSE);
end
만일 os user 가 khpark 인 client 에서 실행하는 sql 의 trace 를 뜨고
싶으면
svrmgrl> select sid,serial#,osuser from v$session
where osuser='KHPARK';
sid serial# osuser
=================================================
8 12 khpark
svrmgr>execute dbms_system.set_sql_trace_in_session (8,12,TRUE);
이렇게 하면 udump 에 trace file 이 생기므로 이를 이용하여 tkprof 를 수행한다.
REFERENCE DOCUMENT
---------------------

Hello Carl,
SQL Trace and SQL Profiler are deprecated since SQL Server 2012 which means that at any future version it might not be available anymore. Have you considered using Extended Events - Microsoft.SqlServer.Management.XEvent
Namespace?
Ivan Donev MCT and MCSE Data Platform
I've spent a fair bit of time reading about XEvents - eventually I won't need SQL 2008 support anymore and I can stop using Trace - but I'm not seeing anything remotely close to TraceServer. What I see is an elaborate infrastructure for efficiently
collecting information about high volume OLTP workloads with minimal server impact. That's all well and good, but of no use to me at all. What I'm looking for is real-time information about OLAP database processing that I can embed in my app to
provide detailed metrics on same.
Presumably something can be put together using XEvents as the source and ETW as the target, with real-time monitoring of ETW events, but that's a lot of API to get a handle on, and I haven't seen any helpful samples that show putting it all together to get
a profiler-like experience with live viewing of processing events as they happen.
Any pointers to helpful samples/resources on XEvents are appreciated - long term, that's going to be my path, I'm sure.
-cd Mark the best replies as answers!

SQL Trace(ST05) and Run Time Analysys(SE30)

Hi ABAP Experts,
Can any one explain what is the use of
1) ST05 and
2) SE30
ponits will be given for clear cut explanation
Thanks and Regards
Vijaya

Hi,
The SQL Trace part of the Performance Trace tool allows you to see how the OPEN SQL statements that you use in ABAP programs are converted to standard SQL statements (see Embedded SQL) and the parameters with which the embedded SQL statements are passed to the database system.
Overview
From the time you turn on the trace function to the time you turn it off again, all database activity occurring either for a specific user or for an entire system is recorded. The SAP System takes OPEN SQL statements and converts them in to embedded SQL statements that it passes to the database and makes the results available. The embedded SQL statement and its parameters are recorded in the SQL Trace file. The results of the SQL statement, like return code, number of entries retrieved, inserted, or deleted by the database are recorded in the SQL Trace file as well. The log file also contains the runtime of the statement and the place in the application program, respectively transaction, from which it was called which enables additional analyses (supported by the SQL Trace function).
From the recorded SQL trace you can deduce:
·        which SQL statements your application carries out
·        which values the system uses for specific database accesses and changes
·        how the system translates ABAP OPEN SQL commands (such as SELECT) into standard SQL commands
·        where your application positions COMMIT statements
·        where your application makes repeated database accesses
·        what database accesses or changes occur in the update section of your application
Create a Trace (SQL Server Profiler)
To create a trace
On the File menu, click New Trace, and connect to an instance of SQL Server.
The Trace Properties dialog box appears.
Note:
The Trace Properties dialog box fails to appear, and the trace begins instead, if Start tracing immediately after making connection is selected. To turn off this setting, on the Tools menu, click Options, and clear the Start tracing immediately after making connection check box.
In the Trace name box, type a name for the trace.
In the Use the template list, select a trace template on which to base the trace, or select Blank if you do not want to use a template.
To save the trace results, do one of the following:
Click Save to file to capture the trace to a file. Specify a value for Set maximum file size. The default value is 5 megabytes (MB).
Optionally, select Enable file rollover to automatically create new files when the maximum file size is reached. You can also optionally select Server processes trace data, which causes the service that is running the trace to process trace data instead of the client application. When the server processes trace data, no events are skipped even under stress conditions, but server performance may be affected.
Click Save to table to capture the trace to a database table.
Optionally, click Set maximum rows, and specify a value.
Caution:
When you do not save the trace results to a file or table, you can view the trace while SQL Server Profiler is open. However, you lose the trace results after you stop the trace and close SQL Server Profiler. To avoid losing the trace results in this way, click Save on the File menu to save the results before you close SQL Server Profiler.
Optionally, select the Enable trace stop time check box, and specify a stop date and time.
To add or remove events, data columns or filters, click the Events Selection tab. For more information, see: How to: Specify Events and Data Columns for a Trace File (SQL Server Profiler)
Click Run to start the trace.
Runtime analysis:
se30 is the tcode for run time analysis, is a tool it
display report based on lps for abap pragram execution
time , data base load, system load. these are all will
display in micro seconds.this tool will use for Transaction
code, function modules , abap progrmes
In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.
For our case, let this be ZABAP_PERF_TUNING
After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the BACK button.
On the original SE30 screen, now click on ANALYZE button.
The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.
SQL trace:
/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy
SE30
/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy
regards,
vasavi.
kindly reward if helpful.

In SQL Trace how to see which statement getting more time .

Hi Expart,
In SQL Trace (T-code ST05) . I am running the standard transaction . how to see which statement
running more time and less time . suppose one statement running more time so how resolve the
performance .
Plz. reply me
Regards
Razz

> The ones in 'RED' color are the statement which are taking a lot of time and you need to
> optimise the same.
No, that is incorrect, the red ones show only the ones which need several hundret milliseconds in one execution. This can even be correct for hard tasks. And there are lots of problem, which you will not see
I have said everything here:
SQL trace:
/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy
Go to 'Tracelist' -> Summarize by SQL statements', this is the view which you want to see!
I summarizes all executions of the same statement.
There are even the checks explained, the slow ones are the one which need a lot of time per record!
See MinTime/Rec > 10.000 microseconds.
Check all number of records, executions, buffer, identicals.
The SE30 Tipps and Tricks will not help much.
Siegfried

Sql trace

Hi All,
I am new to this ABAP field..
I know how to do SQL trace ....But what I am not getting is " <b>HOW CAN WE TELL FROM THE OUTPUT OF SQL TRACE, THAT THIS IS THE CAUSE OF SLOW PERFORMANCE OF A REPORT</b>" Based on what are we determining the performance?
Can Anybody help me here pls?............
Kelly

Hi Kelly,
if you really have no idea, why a report is slow, then you have to start with SE30 (runtime analysis).
There are three bargraphs: ABAP / database / system.
System should be more or less nothing.
If ABAP is bigger than database: have a look at slow abap-statements (normally operations with internal tables: read, delete, loop where,...); classic reason: to much reads without binary search / sorted table / hashed table use.
If database is bigger than ABAP: have a look at your SQL statements. If you can see already forgotten key fields, fine - otherwise SQL trace will bring help in analyzing.
A SQL trace itself says nothing about overall performance (which is done by runtime analysis), only about database part. But 'normally' programmers have their ABAP-part in control and struggle only with slow selects: that's the reason, why often SQL trace is used immediately.
I hope, this brings a little bit light in your question,
regards,
Christian

How to look at the SQL trace in Oracle

Hi,
How do we look for the SQL trace in Oracle?
With SQL trace I mean all the SQL statements being executed in Oracle database ( including select ).
Thanks........

Thanks for a quick reply nbellam. I wonder if there is a way to find out the date and time when the sql was executed?

Unable to generate SQL trace file on a 10.2.0.1.0 database

Hello,
I am unable to generate SQL trace files on a 10.2.0.1.0 database (OS is Win2003 server 64 bits).
First I tried the way I used to do it on older databases (8i and 9i) :
execute dbms_system.set_sql_trace_in_session(sid, serial#, true);
I got no error, but no file was created in the user dump dest directory.
Then I've been searching and I've tried other things :
- I changed the user_dump_dest parameter
- I changed the tracefiles_public parameter value to "true", by modifying the init.ora file
- I tried another package :
exec dbms_monitor.session_trace_enable(139)
Nothing worked, I can't create any trace file...
Does anyone have an idea about this issue ?
thank you for you help !
Antoine

Hello,
thank you all for replying.
I have 2 instances on this machine, and I've just realized that with the other one I have no problem to generate sql trace files as usual.
But why the hell is it impossible on the first instance ? What difference between the 2 instances can explain this ?
This is pretty weird...
Otherwise I am experiencing serious performance problems on the instance where I can't creat trace files, there must be something wrong with it, but I can't figure it out
regards,
Antoine

What is SQL Trace and How to Use it .

Dear Experts .
1.) May You Please tell me What is the Purpose of SQL-Trace and How to use it ?
2.) What is purpose of T-codes SE30 and ST22 ?
Please it is urgent ...
Regards : Rajneesh

Hi
SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
STEPS
Run time analysis transaction SE30
In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.
For our case, let this be ZABAP_PERF_TUNING
After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the BACK button.
On the original SE30 screen, now click on ANALYZE button.
The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.
SQL Trace ST05
Starting the Trace:
To analyze a trace file, do the following:
Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.
Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).
If you want to switch on the trace under your user name, choose Trace on. If you want to pass on values for one or several filter criteria, choose Trace with Filter.
Typical filter criteria are: the name of the user, transaction name, process name, and program name.
Now run the program to be analyzed.
Stopping the Trace:
To deactivate the trace:
Choose Test Performance Trace in the ABAP Workbench. The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.
Select the trace functions that you want to switch off.
Choose Deactivate Trace. If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-
Analyzing a Sample trace data: PREPARE: Prepares the OPEN statement for use and determines the access method.
OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.
FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.

How I can forced close the Citadel Trace References

On my application I write data to Citadel traces using "Database Writing
VIs" (Open Trace.vi .. Write Trace.vi ... Close Trace.vi).
Sometimes if my application "crash" the Close Trace.vi is not executed and that's why the "trace references"
are NOT closed.
When start my application again I get error: "There is already an open writer for the selected trace."
This is natural because the references are not closed when application crash.
My question: How can I solve problem like this?
Is there any function on the Citadel Engine what I can use to "force"
close all writer references, reboot engine etc, get references already opened?
An attachments there is example VI and EXE.
Attachments:
CitadelTest-LV2011.zip ‏531 KB

Hello Mikko!
I can see that we have Services as NI Citadel 4 Service and NI Citadel 5 from Services in Administration tools. Can you try to restart them and see if the effect is something that you need. From then maybe we could try something out.
BR,
Make Nguyen
NI Finland Technical support.
Attachments:
citadel.png ‏151 KB

Can I set up SQL Trace or Audit to connect to servers

I have a server (2003) with SQL (2005) on it.
If i install MS SQL Management Studio 2012 on my PC, can I audit what SQL on that server is doing by connecting to it from the PC ?
Or would it be better to set up SQL Trace on the server itself ?
Thanks
Pete

So if I install SSMS 2012 on my PC, I can connect to the databases on different servers from 1 place.
Yes, as long as there is network connection. In SSMS open up the Registered Servers window and register all servers:
http://technet.microsoft.com/en-us/library/ms188231.aspx
Related thread:
http://social.msdn.microsoft.com/forums/sqlserver/en-US/8209ad2c-6efd-49d6-9605-b7f348eb56bb/how-to-connect-sql-database-on-different-network
Setting up server-side tracing:
http://www.sqlusa.com/bestpractices/createtrace/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

How to set SQL trace in OCI session ?

Hello,
In a SQL*Plus session, I can use the SQL statement "alter session set sql_trace=true;" to set SQL trace in that session only. I assume I could execute the same SQL statement from C code in an OCI client and achieve the same goal.
However, if I cannot change the code of this OCI client, is there a way to set SQL trace for that single session alone, without changing the C code? Say, through an environment variable, configuration file, etc.?
Thanks.

I am not aware of a way to selectively enable the server-side tracing without modifying the client code.
There is client tracing available by setting the environment variable EVENT_10842 as follows:
"server=<>;user=<>;stmt=<>;level=<>;interval=<>"
e.g.
setenv EVENT_10842 "server=inst1,inst2;user=scott,system;stmt=all;level=15"
Where:
"server" is a comma separated list or "all"
"user" is a comma separated list or "all"
"stmt" can be INSERT,UPDATE,DELETE,SELECT or "all"
The following levels are supported:
1 - Trace all server attach and server detach calls for servers listed in "server" attribute of the environment variable.
2 - Trace all session begin, logon, session end, logoff calls for the users listed in "user" attribute of the environment variable.
3 - Trace all prepare, execute, fetch calls for the specified statement types listed in "stmt" attribute of environment variable.
4 - Trace all Bind, Define, Describe calls.
5 - Trace all OCI LOB calls
7 - Get statistical info on all connection pooling /connection related calls
8 - Get statistical info on all session info
9 - Get statistical info on all handle info
10 - Get statistical info on time taken in execute and fetch calls
11 - Get statistical info on transaction related calls
15 - Trace all calls with statistical info.

Generate Sql Trace in oracle reports

Hi,
My Reports version is 10.1.2.0.2 and I would like to see the trace files of the sql queries that are executed while generating a report using rwbuilder.
I tried using a Formula column, with
SRW.DO_SQL('ALTER SESSION SET SQL_TRACE=TRUE');
return(1);
Also, I enable system level trace to capture anything and everything that is being fired into DB from reports.
I tried,
ksh rwthinclient.sh report=$REPORT_FILE_PATH/Journal.rdf server=$REPORT_SERVER userid=$ORAUSERID/$ORAPASSWD@$REPORT_DATABASE destype=cache desformat=pdf TRACEFILE=ver1.trc TRACEOPTS=trace_all TRACEMODE=trace_replace RUN_DATE=$CurDate;
I do not get trace at all. Kindly help me out.

Hi,
Maybe have a look at this MOS note: Running SQL*Trace on an Applications Report [ID 1019231.6]
Regards Peter

Explain plan not displayed in sql trace file

Hello,
I don't understand why in sql trace file, after tkprof transformation, for several queries the explain plan is displayed and for several queries, no explain plan is displayed.
How can I have the explain plan for all queries?
Thanks for your help.

Was this a trace started on an already running task? Was the trace stopped before the task completed? Did the trace file reach its set size limit before the task compled?
In all three cases above you would have cursors that were not closed and stats information not written to the trace file resulting in incomplete data for some SQL.
HTH -- Mark D Powell --

Close all SQL trace

Similar Messages

Maybe you are looking for