Trace File STAT generated on J2EE

Hi everyone,
I am having problem with trace file called STAT. This file is being generated but I Don´t now by who.
They are being recorded on the file system sapdata3.
The system is J2EE SP15, XI 3.0 with Oracle Database!
Thanks

Hi Ricardo,
The stat files being generated by the CCMS Agent. Check
the link for more
http://help.sap.com/saphelp_erp2005/helpdata/en/c7/69bcc3f36611d3a6510000e835363f/frameset.htm
Regards
Srikishan

Similar Messages

Trace file getting generated

Hi,
We have PI 7.1 installed in landscape. Some trace files getting generated at
server\sapmnt\SID\DVEBMGS01\j2ee\cluster\server0\jrfc07500_06148.trc and utilizing more disk space aroung 1 GB.
Could you please let me know from where trace can be disabled
thanks

Hi Yash,
Please find the details on this link:
http://help.sap.com/saphelp_nw04/Helpdata/EN/f6/daea401675752ae10000000a155106/content.htm
name
jrfc*.trc
location
directory j2ee/cluster/server* or defined path
how to switch on and off set JVM options for the server via the Config Tool and restart server: -Djrfc.trace=0/1, -Djco.trace_path=[defined_path]
Kindly let us know if this resolves the problem.
Thanks.
Regards,
Shweta

Numerous trace files are generating every minute causing space issue

Hi All,
numerous trace files are generating every minute <SID>_<PID>_APPSPERF01.trc format.
entry in trace file will be like..
EXEC #10:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,plh=1734896627,tim=1339571764486430
WAIT #10: nam='SQL*Net message to client' ela= 6 driver id=1952673792 #bytes=1 p3=0 obj#=34562 tim=1339571764491273
FETCH #10:c=0,e=0,p=0,cr=2,cu=0,mis=0,r=1,dep=0,og=1,plh=1734896627,tim=1339571764486430
WAIT #10: nam='SQL*Net message from client' ela= 277 driver id=1952673792 #bytes=1 p3=0 obj#=34562 tim=1339571764491806
EXEC #11:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,plh=2638510909,tim=1339571764486430
FETCH #11:c=0,e=0,p=0,cr=9,cu=0,mis=0,r=0,dep=0,og=1,plh=2638510909,tim=1339571764486430
WAIT #11: nam='SQL*Net message to client' ela= 6 driver id=1952673792 #bytes=1 p3=0 obj#=34562 tim=1339571764493265
*** 2012-06-13 03:16:14.496
WAIT #11: nam='SQL*Net message from client' ela= 10003326 driver id=1952673792 #bytes=1 p3=0 obj#=34562 tim=1339571774496705
BINDS #10:
Bind#0
oacdty=01 mxl=32(21) mxlc=00 mal=00 scl=00 pre=00
oacflg=00 fl2=1000001 frm=01 csi=871 siz=2064 off=0
kxsbbbfp=2b8ec799df38 bln=32 avl=03 flg=05
value="535"
Bind#1
oacdty=01 mxl=32(21) mxlc=00 mal=00 scl=00 pre=00
oacflg=00 fl2=1000001 frm=01 csi=871 siz=0 off=32
kxsbbbfp=2b8ec799df58 bln=32 avl=04 flg=01
value="1003"
SQL> show parameter trace
NAME TYPE VALUE
tracefiles_public boolean TRUE
log_archive_trace integer 0
sec_protocol_error_trace_action string TRACE
sql_trace boolean FALSE
trace_enabled boolean TRUE
tracefile_identifier string
Profile options like "FND:Debug Log Enabled" and "Utilities:SQL Trace" are set to No
Can some one help me to stop these trace generation.
is there any way to find the cause for these trace?
Thanks in adv...

Hi;
Please check who enable trace. Please see:
How to audit users who enabled traces?
check concurrent programs first
*from the screen
*F11, then select the trace, then Ctrl+F11
Concurrent > program > define
open the form, press F11 (query mode), select the trace, then (ctrl + f11) this should return all concurrent programs which have trace enabled
Regard
Helios

Huge user trace files being generated under udump

last few days one of my database is generating huge number of user trace files under udump. I tried to investigate in alert.log file. But as I am not very expert to analyze the alert.log file I could not find the cause behind it. Only the ORA-00600: internal error code is found there. But it is a generic error . Please help.

Thank you again. I got the clue from your reply.
The error message is pasted below in short.
ORA-00600: internal error code, arguments: [12333], [0], [0], [0], [], [], [], []
Current SQL statement for this session:
BEGIN :1 := TESTDBA.LOCAL_SYSDATE_SFT_FNC( 1,:2,:3 ); END;
And it is obvious that the function had some problem recently. We need to investigate on that. Now my request is
Please guide me how to check in metalink with the value '12333' which came as argument of ORA-00600 error. Here my job was easy as I got the problem function name . By I want to know the art of analysing the error message in alert.log file.
Also tell me which places I should check regularly as a responsibility of a DBA ?
What are the common errors in Alert log file? Where I should be cautioned ? Where I should ignore. Give me some tips please. Do not restrict your discussion on Alret.log only . Also please cover all important areas. If you think I am taking much of your time then please send me some link or source of PDF etc.

How to proceed further once the explain plan and trace files are generated?

Hi Friends,
I need to improve the performance of on of the views that i am working on.
As suggested in the thread - http://forums.oracle.com/forums/thread.jspa?threadID=863295&tstart=0 , i gave generated the explain plan and the trace file.
From the explain plan, we can see the expensive operations for the query.
Can any one please tell, how to proceed further from here on i.e. how to make this expensive operations less expensive?
For ex: FULL TABLE SCAN might be an expensive operation when the table has indexes.In such cases, how can we avoid such operations to make query faster?
Regards,
Sreekanth Munagala.

Hi Veena,
An earlier post by you regarding P45 is as below
Starter report P45(3) / P46 efiling for UK
from my understanding though i have not worked on GB Payroll you have said that you deleted IT 65 details of leaver,however there must be clusters generated in system from where the earlier data needs to be deleted and may be that is why you are facing the issue.
In Indian payroll when we execute text file for efiling of tax after challan mapping all the data compiles and sits in PCL cluster and therefore we are unable to generate form 16 with proper output,here we delete the clusters and rerun again the mappings and then check form 16.
Hope this might help you,Experts have suggested you earlier also,they may correct me for this.
Salil

Trace file not Generated.

Hey Guys,
I am using oracle 10g and trying to generate a trace file.
Using sql_Plus I can see that timed_statistics is set to true, max_dump_file_size is set to unlimited, and user_dump_dest is set to C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\DUMP.
In Oracle SQL Developer I am running the script:
alter session set sql_trace = true;
... PL/SQL block that I want to trace...
alter session set sql_trace = false;
After this sql runs without error there is no file on my computer at the user_dump_dest. In fact the path under user_dump_dest does not even exist. Do I have to create the path first? Am I looking in the wrong location? Am I doing something wrong when setting sql_trace?
Thanks,
Ian

In fact the path under user_dump_dest does not even exist.Perhaps this is the source of the mystery.
If Oracle has no place to actually write the file, how should it proceed?
as a proof of concept do the following
ALTER SESSION SET SQL_TRACE=TRUE;
show parameter dump
SELECT SYSDATE FROM DUAL;
ALTER SESSION SET SQL_TRACE=FALSE;
now find the trace file
post results from session above
Edited by: sb92075 on Jun 1, 2010 4:45 PM

Session trace files not generated

Hai all,
Am tracing a session as follows :
EXEC DBMS_SUPPORT.start_trace_in_session(sid=>2166, serial=>30629, waits=>TRUE, binds=>FALSE);
EXEC DBMS_SUPPORT.stop_trace_in_session(sid=>2166, serial=>30629);
but,no trace files are getting generated ?.. in udump dir..
Any idea ?
Kai

Likely a version and/or platform specific bug.
However, according to you this information is not important, or too much cumbersome to type, so no one can help you, even if you were told to include this several time.
If you want free support from volunteers, at least provide information to work in.
Or consider not posting at all.
Sybrand Bakker
Senior Oracle DBA

Sqlnet.ora trace files getting generated even after turning off tracing

Hi,
I have recently added the following parameters to the sqlnet.ora file.
TRACE_LEVEL_SERVER=16
TRACE_FILE_SERVER=SERVER
TRACE_DIRECTORY_SERVER=/ftpland/trace
TRACE_TIMESTAMP_SERVER=on
Even after removing these enteries from the sqlnet.ora I still see the trave files being generated.
#####enable tracing###################
#Trace_level_server=0
#Trace_filelen_server=1000
#Trace_fileno_server=1
#Trace_timestamp_server=on
#Trace_directory_server=/opt/oracle/product/10.2.0/network/trace
#Diag_adr_enabled=off
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
SQLNET.EXPIRE_TIME = 10
NAMES.DEFAULT_DOMAIN = bsca.eds.com
NAME.DEFAULT_ZONE = bsca.eds.com
SQLNET.CRYPTO_SEED = "232166927-1713903352"
NAMES.DIRECTORY_PATH = (ONAMES,TNSNAMES)
NAMES.PREFERRED_SERVERS =
      (ADDRESS_LIST =
        (ADDRESS =
          (COMMUNITY = TCP.bsca.eds.com)
          (PROTOCOL = TCP)
          (Host = oraclenames1.bsca.eds.com)
          (Port = 1575)
        (ADDRESS =
          (COMMUNITY = TCP.bsca.eds.com)
          (PROTOCOL = TCP)
          (Host = oraclenames2.bsca.eds.com)
          (Port = 1575)
NAME.PREFERRED_SERVERS =
      (ADDRESS_LIST =
        (ADDRESS =
          (COMMUNITY = TCP.bsca.eds.com)
          (PROTOCOL = TCP)
          (Host = oraclenames1.bsca.eds.com)
          (Port = 1575)
(ADDRESS =
          (COMMUNITY = TCP.bsca.eds.com)
          (PROTOCOL = TCP)
          (Host = oraclenames2.bsca.eds.com)
          (Port = 1575)
BEQUEATH_DETACH=YES
Regards,
VN

SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME =ROSDMP.bsca.eds.com)
      (ORACLE_HOME = /opt/oracle/product/10.2.0)
      (SID_NAME = ROSDMP)
TRACE_LEVEL_LISTENER=16
I believe, this is the reason, you are seeing trace files even after disabling it in sqlnet.ora

10053 - no trace file generated

Hi,
no 10053 trace file is generated in the diag directory.
sql_trace = true
trace_enabled = true
i set
ALTER SESSION SET TRACEFILE_IDENTIFIER = 'TEST';
ALTER SESSION SET EVENTS='10053 trace name context forever, level 1';
but there is no trace file generated.
Something seems to be missing.
Any help would be much appreciated!
Best Regards
user11368124

thanks for your messages.
@Dom Brooks
the Oracle release is 11.2 running on Ubuntu.
Added flushing pool. That statement was missing.
But unfortunately the 10053 trace file is still not generated.
i am running the following query mentioned in the article "Examining the Oracle Database 10053 Trace Event Dump File" of Steve Callan:
alter system set TRACE_ENABLED = true;
alter system set SQL_TRACE = true;
alter session set statistics_level=all;
--alter session set max_dump_file_size = unlimited;
--oradebug setmypid
--oradebug unlimit
--oradebug event 10053 trace name context forever, level 1
ALTER SESSION SET TRACEFILE_IDENTIFIER = 'TEST';
alter session set events '10046 trace name context forever, level 12';
alter session set events '10053 trace name context forever, level 1';
-- plan_table exists
select * from plan_table
-- flushing pool
alter system flush shared_pool;
explain plan for
SELECT ch.channel_class,
c.cust_city,
t.calendar_quarter_desc,
SUM(s.amount_sold) sales_amount
FROM sh.sales s,
sh.times t,
sh.customers c,
sh.channels ch
WHERE s.time_id = t.time_id
AND s.cust_id = c.cust_id
AND s.channel_id = ch.channel_id
AND c.cust_state_province = 'CA'
AND ch.channel_desc in ('Internet','Catalog')
AND t.calendar_quarter_desc IN ('1999-01','1999-02')
GROUP BY ch.channel_class, c.cust_city, t.calendar_quarter_desc
ORDER by 1,2,3,4;
Best Regards
user11368124

Dbms_monitor.session_trace_enable does not generate the trace file

hi All,
i'm trying the example from Tom Kyte's <<expert oracle database architecture>>, after runnning the java code using dbms_monitor.session_trace_enable, the trace file for the session can't be found in user_dump_dest, could anyone help explain. oracle version is 10.2.0.1.0 on RHEL 5. thanks.
[oracle@CS-RHEL chapter09]$ cat perftest.java
import java.sql.*;
import oracle.jdbc.OracleDriver;
import java.util.Date;
public class perftest
public static void main (String arr[]) throws Exception
    DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
    Connection con = DriverManager.getConnection
          ("jdbc:oracle:thin:@127.0.0.1:1522:cs10g",
            "sid", "sid");
    Integer iters = new Integer(arr[0]);
    Integer commitCnt = new Integer(arr[1]);
    con.setAutoCommit(false);
    doInserts( con, 1, 1 );
    Statement stmt = con.createStatement ();
    stmt.execute
    ( "begin dbms_monitor.session_trace_enable(waits=>TRUE); end;" );
    doInserts( con, iters.intValue(), commitCnt.intValue() );
    doInserts( con, iters.intValue(), iters.intValue() );
    con.commit();
    con.close();
static void doInserts(Connection con, int count, int commitCount )
throws Exception
    PreparedStatement ps =
       con.prepareStatement
       ("insert into test " +
        "(id, code, descr, insert_user, insert_date)"
        + " values (?,?,?, user, sysdate)");
    PreparedStatement commit =
       con.prepareStatement
       ("begin /* commit size = " + commitCount + " */ commit; end;" );
    int rowcnt = 0;
    int committed = 0;
    long start = new Date().getTime();
    for (int i = 0; i < count; i++ )
      ps.setInt(1,i);
      ps.setString(2,"PS - code" + i);
      ps.setString(3,"PS - desc" + i);
      ps.executeUpdate();
      rowcnt++;
      if ( rowcnt == commitCount )
        commit.executeUpdate();
        rowcnt = 0;
        committed++;
    con.commit();
    long end = new Date().getTime();
    System.out.println
    ("pstatement " + count + " times in " +
     (end - start) + " milli seconds committed = "+committed);
}run the java class
[oracle@CS-RHEL chapter09]$ java -cp .:./ojdbc14.jar perftest 1000 1
pstatement 1 times in 5 milli seconds committed = 1
pstatement 1000 times in 2255 milli seconds committed = 1000
pstatement 1000 times in 509 milli seconds committed = 1

hi virendra.k and Kecskemethy,
thanks for your help. believe i find the arnswer.
1. i used shared server connection. i can find the trace info in the backgroup_dump_dest, in the files: cs10g_s000_17467.trc and cs10g_s001_17469.trc
Ref:http://www.dbspecialists.com/files/presentations/tracing_ind_sessions.html
First, rather than using DBMS_MONITOR.CLIENT_ID_TRACE_ENABLE, we use DBMS_MONITOR.SESSION_TRACE_ENABLE. This can be run either by the session itself,
or by another session (specifying the SID of the session to be traced). The tracing output will be in the instance’s background_dump_dest directory,
rather than the user_dump_dest. And then you use trcsess with the session_id option, where session ID is actually the SID.SERIAL# of the session
(from v$session). Again you get a consolidated trace file containing just the activity of the desired session.2. after change to dedicated server, the trace file is generated in user_dump_dest now.
sid@CS10G> show parameter trace_enable
NAME                                 TYPE        VALUE
trace_enabled                        boolean     TRUE
sid@CS10G> show parameter shared_servers
NAME                                 TYPE        VALUE
max_shared_servers                   integer
shared_servers                       integer     10
sid@CS10G> alter system set shared_servers=0
2 ;
System altered.
[oracle@CS-RHEL udump]$ pwd
/home/u02/app/oracle/product/11.1.0/db_1/admin/cs10g/udump
[oracle@CS-RHEL udump]$ tail -25 cs10g_ora_22313.trc
WAIT #8: nam='SQL*Net message to client' ela= 2 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901405248
WAIT #8: nam='SQL*Net message from client' ela= 151 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901405433
=====================
PARSING IN CURSOR #9 len=43 dep=0 uid=61 oct=47 lid=61 tim=1220152901405586 hv=1042574845 ad='3ace843c'
begin /* commit size = 1000 */ commit; end;
END OF STMT
PARSE #9:c=0,e=99,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=1220152901405582
=====================
PARSING IN CURSOR #10 len=6 dep=1 uid=61 oct=44 lid=61 tim=1220152901405781 hv=255718823 ad='0'
COMMIT
END OF STMT
PARSE #10:c=0,e=13,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=0,tim=1220152901405776
XCTEND rlbk=0, rd_only=0
EXEC #10:c=0,e=146,p=0,cr=0,cu=1,mis=0,r=0,dep=1,og=0,tim=1220152901406000
EXEC #9:c=999,e=396,p=0,cr=0,cu=1,mis=0,r=1,dep=0,og=1,tim=1220152901406082
WAIT #9: nam='log file sync' ela= 3234 buffer#=5459 p2=0 p3=0 obj#=-1 tim=1220152901409385
WAIT #9: nam='SQL*Net message to client' ela= 2 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901409450
WAIT #9: nam='SQL*Net message from client' ela= 142 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901409633
XCTEND rlbk=0, rd_only=1
WAIT #0: nam='SQL*Net message to client' ela= 1 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901409735
WAIT #0: nam='SQL*Net message from client' ela= 283 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901410043
XCTEND rlbk=0, rd_only=1
WAIT #0: nam='SQL*Net message to client' ela= 2 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901410146
WAIT #0: nam='SQL*Net message from client' ela= 316 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=1220152901410489
XCTEND rlbk=0, rd_only=1

Generating trace file in udump

Hi,
Database is 10.1.0.5 on windows 2003. There is trace file getting generated in udump which says:
opitsk: network error occurred while two-task session server trying to send break; error code = 12152
Thanks

I'm getting the same since patching from 10.1.0.5 patch 2 to patch25 when connecting over PL/SQL Developer and quering with large resultsets:
PL/SQL Dev query session lost on large resultsets after db update
Did you solve your problem ?

Do you know Timmings for trace files generated?

Hi,
I have done some sql traceing using DBMS_MONITOR package.
We can also enable SQL traceing using DBMS_SESSION.
I want to generate sql trace file for "particuler part of application".
When i did that i got some sql trace files,, now that "particuler part of application" was over application was idle..
but as time goes these files are still populating in size means they are still sql traceing going on...
My question is when and how trace files are generated?
Do you have idea???
Thanks and Regards,
Rushang Kansara
Message was edited by:
Rush

also what content of my sql trace file should i
consider for exacly tracing that "particuler part of
application".
Rushang
Parse Count To Execute Ratio
Take the numbers of parse count and divide it by numbers of time execute count if it is 1 then it means you are parsing the same statment everytime,If this ratio is 1 then it will latch the shared SQL area which will degrade the overall performance.Like if you execute a query which is using bind variable and this query is at yours front end level trigger (Forms) POST_QUERY then it will show you (parse count=execute count) which shows you are parsing for every triggering event which is bad ,for that you should put this seqeuel within PL/SQL procedure which cache the cursor and will turn in (parse count<Execute Count).
Large Diffrence Between Elasped Time And CPU Time
If this diffrence (Elapsed time[b]-CPU time)>1 then it means you are spending yours time in for waiting resources this waiting resources will in turn wait events e.g some one updated the row and dont realease by COMMIT or ROLBACK and the same span of time you want to update then you will see a lock in tkprof result in wait event section.If you read the data from hard disk (as first time you issue it reads from HD and then put into buffer cache during this reading a latch is grabed and will not let you read this data until you perform the alls read from HD to buffer cache this will also show you in wait events which is cache buffers chain
Fetch Calls
If yours Fetch calls=Rows then it means you are not using Bulk fetch and yours this code will take a lot of roundtrips which will in turn jam the network.
Disk Count
If every time yours disk count=current + query mode then you are reading alls block from disk alls the time ,usually oracle read once from disk and put it into SGA and should be found in SGA second time.
And there is many more...depend on yors environemnt setup but above are common.
As you said its reproducing the tkprof again and again ,make sure you terminate the session or you explicitly turn off the tracer by
ALTER SESSION SET SQL_TRACE=FALSE Khurram

Too many trace files generated by program ORACLE.EXE (J001) in "bdump"

Hi,
Please help!
the following trace file messages have been created in my "bdump" folder about every 6 minutes, so it generates about 200 files per hours. Can someone tell me how to solve the error or stop the trace files be generated. Thanks.
Windows thread id: 5520, image: ORACLE.EXE (J001)
*** 2009-05-22 12:49:21.372
*** ACTION NAME:() 2009-05-22 12:49:21.372
*** MODULE NAME:() 2009-05-22 12:49:21.372
*** SERVICE NAME:(SYS$USERS) 2009-05-22 12:49:21.372
*** SESSION ID:(312.292) 2009-05-22 12:49:21.372
java.io.IOException: service early exit: code=1 : err=The system cannot find the path specified.
: out=
at oracle.wh.runtime.server.Util.execRuntimeService(Util.java:122)
CJ

No version number and not enough information in what you posted to help you.
Did this just start?
If so what actions preceded it?
Or is this a new install?
Have you tried bouncing the instance?
If it were my system I would have already searched the knowledgebase at metalink and opened an SR if I couldn't find a solution. Did you?

SQL Developer generates strange trace files on server

Hello out there,
I observed the generation of some strange trace files on the database server (Oracle 11.0.2.0.2 64bit on Win 2008R2).
Whenever I start SQL Developer (3.2.20.09.87 64bit with JDK 1.7.0_17 64bit on Win7 64bit) for each connection I defined one trace file like this is generated:
Trace file C:\ORACLE\diag\rdbms\ora\ora\trace\ora_ora_8500.trc
Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
Windows NT Version V6.1 Service Pack 1
CPU : 2 - type 8664, 2 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:990M/3959M, Ph+PgF:3743M/7918M
Instance name: ora
Redo thread mounted by this instance: 1
Oracle process number: 23
Windows thread id: 8500, image: ORACLE.EXE (SHAD)
*** 2013-03-06 08:04:13.842
*** CLIENT ID:() 2013-03-06 08:04:13.842
*** SERVICE NAME:() 2013-03-06 08:04:13.842
*** MODULE NAME:() 2013-03-06 08:04:13.842
*** ACTION NAME:() 2013-03-06 08:04:13.842
Breaking the connection before proto/dty negotiation, error raised 3113I enabled listener log to find out the origin of this and it contains lines like the following:
06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49320)) * establish * ora.vu * 0
06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49322)) * establish * ora.vu * 0
06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49323)) * establish * ora.vu * 0
06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49325)) * establish * ora.vu * 0
06-MRZ-2013 08:04:14 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49329)) * establish * ora.vu * 0
06-MRZ-2013 08:04:14 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49331)) * establish * ora.vu * 0The IP address is mine and I have excatly 6 connections defined for that server. On other servers, similar trace files are generated, one for each connection in my SQL Developer.
This also occurred with JDK 1.6 so I don't think it's a Java issue.
Besides the generation of the trace files there seem to be no other problems.
Any ideas?

Hi,
I think Srini is probably correct. The noted bug applies to 11.2.0.1 and up, is fixed in 12c, and included in an 11.2.0.3 patch. However the version of SQL Developer also affects the creation of trace files on product startup (prior to any user initiated db connect attempts).
For example,
A. SQL Developer 3.1.07.42 - no such trace files created.
B. SQL Developer 3.2.20.09.87 - such trace files created for 11.2.0.1 connections, but not 10g XE or 12c connections.
So I presume an OCIServerAttach call got added in 3.2.2, not sure in support of which feature, but the bug will only impact users of 11.2.0.1, 11.2.0.2, and unpatched 11.2.0.3 DB releases.
Regards,
Gary
SQL Developer Team

Trace enabled, but no trace file generated

I have enabled trace (Application Developer -> Concurrent -> Program, find the report, tick 'Enabled Trace', save), then i execute the report, but no trace file is generated, check the fnd_concurrent_requests table, the record has oracle_process_id=null.
what can I do to have trace generated?

Hi,
I have enabled trace (Application Developer -> Concurrent -> Program, find the report, tick 'Enabled Trace', save), then i execute the report, but no trace file is generated, check the fnd_concurrent_requests table, the record has oracle_process_id=null.
what can I do to have trace generated?Please enable trace from Apps 11i form -> Help -> Diagnostic -> Trace ( Here u can select the option like Regular trace, trace with bin etc) as per your requirement. But for this trace profile option should be enabled for your user.
Regards,
X A H E E R

Trace File STAT generated on J2EE

Similar Messages

Maybe you are looking for