Trace files filling up on server

11.1.0.7 - 64 bit on Solaris
It appears tracing has been enabled on our database in the last one week as the trace directory is getting filled up.
However this is what it's showing:
SQL> show parameter trace
NAME                                 TYPE        VALUE
log_archive_trace                    integer           0
sec_protocol_error_trace_action string          TRACE
sql_trace                                boolean          FALSE
trace_enabled                        boolean           TRUE
tracefile_identifier                     string
It seems 11g have trace_enabled set to true by default.
My question is how do I find who's session is being traced?
Thanks

TGG, the OP posted the database parameters related to trace and sql_trace clearly shows as FALSE.
gbite, I would suggest looking at the content of some of the trace files. We have experienced more than one platform version specific trace file generation issue which caused hundreds of useless trace files to be generated. If the files contain the same messages you can then search Oracle support for a known problem which might have a solution available. If all the traces just appear to be regular session sql traces then the suggestion to look to see if any database event logon triggers exist and turn trace on.
Removing the trace files at the OS level should be an option in the meantime.
HTH -- Mark D Powell --

Similar Messages

Server is shutdown because of trace files filled up in drive

Hi,
Is there any option like to disable " sever shtdown" when drive is full.
Thanks
Shashikala

Hi,
As Dan pointed out, sp_trace_create comes with the option SHUTDOWN_ON_ERROR which can result in the above behavior.
You can consider not using the option SHUTDOWN_ON_ERROR while creating these traces to prevent this from happening. However this is not something you want to do considering the auditing requirements
Check the find anything relevant message in the application,system and SQL error logs to find the root cause of the issue.
Also, find this thread for reference:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/eb94db75-fed1-4a99-b321-4a931de402ed/strange-sql-error
Thanks.
Tracy Cai
TechNet Community Support

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 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

How to find the problem in EP trace file?

Hi
Last week all the role assignments to users under LDAP datasource got deleted from the portal. We have reuploaded the role assigmnet. Now got the trace files from the server. How to check what happend on that day ?
When all roles assignmnets gone?
Any Keywords to help!
Thanks!
Dhiya.J

Hi both,
I got the trace file already from J2EE server. Im struggling to find out anything from the trace file ..
How to check when role assignments got deleted ?
any LDAP configuration changes ?
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[6, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.5.trc]/>
<!NEXTFILE[defaultTrace.7.trc]/>
<!LOGHEADER[END]/>
#1.5 #0018FE349B47007000000C1900001A200004939077FC1A8D#1288148604431#System.err#sap.com/irj#System.err#gmbeqy#17773####c35ae9f0e17611df93420018fe349b47#SAPEngine_Application_Thread[impl:3]_7##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
#1.5 #0018FE349B47007000000C1A00001A200004939077FC1DC9#1288148604431#System.err#sap.com/irj#System.err#gmbeqy#17773####c35ae9f0e17611df93420018fe349b47#SAPEngine_Application_Thread[impl:3]_7##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
11d30a40e26211dfaa7e0018fe349b47#SAPEngine_Application_Thread[impl:3]_21##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0018FE349B470059000004C300001A20000493A816802148#1288250048138#com.sap.security.core.imp#sap.com/tcwddispwda#com.sap.security.core.imp.[cf=com.sap.security.core.imp.User][md=init][cl=22052]#gmrnis#29282##sghrppr1.sgh.shs_PPH_15804951#gmrnis#e42beac1e26211dfa6230018fe349b47#SAPEngine_Application_Thread[impl:3]_28##0#0#Error##Java###Error while populating "USER.CORP_LDAP.cn=norsheha bte ismail,ou=mro - hims,ou=sgh,dc=sgh,dc=shs,dc=com,dc=sg"
[EXCEPTION]
#1#com.sap.security.core.persistence.datasource.PersistenceException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001BD, problem 2001 (NO_OBJECT), data 0, best match of:
     'DC=sgh,DC=shs,DC=com,DC=sg'
     at com.sap.security.core.persistence.datasource.imp.LDAPPersistence.populatePrincipalDatabag(LDAPPersistence.java:1456)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.getPrincipalDatabag(PrincipalDatabagFactoryInstance.java:2307)
     at com.sap.security.core.imp.User.init(User.java:244)
     at com.sap.security.core.imp.AbstractPrincipal.<init>(AbstractPrincipal.java:186)
     at com.sap.security.core.imp.Principal.<init>(Principal.java:64)
     at com.sap.security.core.imp.User.<init>(User.java:213)
     at com.sap.security.core.imp.User.<init>(User.java:203)
It keeps on going like this ... any key word to search?
Thanks!

Analyzing the trace file

Does someone know the meaning of the NTTCNR and the NTTVLSER codes in the
trace file from the Oracle server????
Below is an example of the mentioned codes in the trace:
nttcnr: entry
nttcnr: waiting to accept a connection.
nttvlser: entry
nttvlser: valid node check on incoming node 10.20.30.201
nttvlser: Accepted Entry: 10.20.30.201
nttcnr: exit
null

Hi,
I am new in sap i would like to mare about ST01 in deatil .
Regards
Pallav

Moving Default Trace File in SQL Server

How can I move the default trace file in SQL server?
SQL Server 2012?
Thanks in advance
ebro

Please have a look at these links:
Change path for default SQL Server trace
Steps to change the default location of SQL Server /SQL Server Agent - Error log files
DETERMINING DEFAULT TRACE LOCATION
Collecting the Information in the Default Trace
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog

DeskI Job Server Hangs with Connection timed out error in trace file

Hi, in these days I have a problem with Desktop Intelligence Job Server. After some hours after its starting (it's restarted every day in the morning to allow db backup) in the trace file I can see errors like this:
[Wed Apr 8 09:58:40 2009]      28116   1457753008      (../iinfoprocessing_implmixedproc.cpp:607): trace message: Failed to send message to child: 28527, err 0, PipeListener: timed out reading from pipe: Connection timed out
[Wed Apr 8 09:58:43 2009]      28116   1457753008      (csipipe.cpp:242): trace message: PipeListener: ReadString(1) timed out: Connection timed out
[Wed Apr 8 09:58:43 2009]      28116   1457753008      (../iinfoprocessing_implmixedproc.cpp:607): trace message: Failed to send message to child: 28529, err 0, PipeListener: timed out reading from pipe: Connection timed out
[Wed Apr 8 09:58:46 2009]      28116   1457753008      (csipipe.cpp:242): trace message: PipeListener: ReadString(1) timed out: Connection timed out
[Wed Apr 8 09:58:46 2009]      28116   1457753008      (../iinfoprocessing_implmixedproc.cpp:607): trace message: Failed to send message to child: 28553, err 0, PipeListener: timed out reading from pipe: Connection timed out
[Wed Apr 8 09:58:49 2009]      28116   1457753008      (csipipe.cpp:242): trace message: PipeListener: ReadString(1) timed out: Connection timed out
[Wed Apr 8 09:58:49 2009]      28116   1457753008      (../iinfoprocessing_implmixedproc.cpp:607): trace message: Failed to send message to child: 28555, err 0, PipeListener: timed out reading from pipe: Connection timed out
[Wed Apr 8 09:58:52 2009]      28116   1457753008      (csipipe.cpp:242): trace message: PipeListener: ReadString(1) timed out: Connection timed out
[Wed Apr 8 09:58:52 2009]      28116   1457753008      (../iinfoprocessing_implmixedproc.cpp:607): trace message: Failed to send message to child: 28591, err 0, PipeListener: timed out reading from pipe: Connection timed out
All job submitted remains in "Suspend" mode and never pass in "Executing".
To solve the problem I've to manually stop and restart the DeskIjob server, but after some hours the problem reappear.
How to solve it?
I've installed Business Objects XI R2 SP5 on Linux SLES 10
Thanks

Checking the jobcd trace of child process in connection timeout, I can see, at the time in which in jobsd process the error occurs, the following error:
[Thu Apr 9 09:14:08 2009]      8940    1452690272      (../ijob_implmixedproc.cpp:143): trace message: MixedProcMgr: msg = GetLoad
[Thu Apr 9 09:14:08 2009]      8940    1452690272      (../ijob_implmixedproc.cpp:128): trace message: MixedProcMgr: timed out wating for new jobs, shutting down.
[Thu Apr 9 09:14:08 2009]      8940    1452690272      (pp_procFC.cpp:3716): trace message: IJobDllUnInitialize
[Thu Apr 9 09:14:08 2009]      8940    1452690272      (pp_procFC.cpp:951): trace message: ReleaseStaticSubsystem()
[Thu Apr 9 09:14:08 2009]      8940    1452690272      (pp_procFC.cpp:168): trace message: t_shutdown_ptr::reset()
[Thu Apr 9 09:14:08 2009]      8940    1452690272      (pp_procFC.cpp:172): trace message: Shutting down INTERFACE
[Thu Apr 9 09:14:08 2009]      8940    1452690272      trace message: TraceLog: [ENTER] BOLApp::ExitInstance
[Thu Apr 9 09:14:08 2009]      8940    1452690272      trace message: TraceLog: [ENTER] ~_BOUserUniverseManager
[Thu Apr 9 09:14:08 2009]      8940    1452690272      trace message: TraceLog: [ENTER] ReleaseUniverseCache
[Thu Apr 9 09:14:08 2009]      8940    1452690272      trace message: TraceLog: [EXIT] ReleaseUniverseCache: 0
[Thu Apr 9 09:14:08 2009]      8940    1452690272      trace message: TraceLog: [EXIT] ~_BOUserUniverseManager: 0
The error occurs exaclty 2 hours after the starting of the child ... I don't think it's a coincidence ....
Edited by: David Loreto on Apr 9, 2009 11:41 AM

Report Server Generating big size trace file

We are using Report Service which is part of 9iAS suite. Its generating a trace file (server name.trc). This file keeps growing and depending on the number of requests we receive sometimes its size goes in Giga bytes. Anybody knows why its doing that and how to get rid of this behavior ?

Tracing is useful for troubleshooting purposes. If you do not need tracing please open the file
$OH\reports\conf\server_name.conf
and comment the "trace" element. You will need to restart the server for this to take effect

Thanks
The Oracle Reports Team

Java Exceptions in Server Trace file

Is it possible to tell the Server (817)
not to write the Java exceptions into the trace file ?
thx in advance
null

Ludovik Segaert wrote:
I have a java server that also acts as a client to another java server. When this second server throws an exception, it never reaches the first server acting as a client.Any ideas?What version of WLE ? Does the server acting as a client execute normally
or does it get a different exception?
Peter

Trc file fills server

Hello
I have downloaded and installed SQL Developer 1.1.
Unfortunately it has caused our server to crash twice in two days.
Oracle writes a trc file see below
Fri Dec 22 09:47:25 2006
Errors in file d:\oracle\admin\oracle\udump\oracle_ora_3376.trc:
ORA-00600: internal error code, arguments: [17182], [0x3480110], [], [], [], [], [], []
Which went on to fill up the server disk. It also did this yesterday.
I think it happens when I open the tree view and ask to see the DDL for a view.
If you need more info please ask.
Andrew.

SQL Dev uses different queries and different methods to access the database than other tools. Namely, SQL through JDBC. That being said, neither of those can directly kill a database. There are no special tie-ins that allow low level access to the database processes or anything special like that, it is just plain old SQL. I have no doubt that your database crashed, and no doubt that something that SQL Developer ran that killed it, but the crash was from the database. If you can figure out what query crashed it, you can run it in SQL Plus and the database will probably crash from that too.
There are a couple of threads on here regarding the performance of the tree. Basically, there are some queries that run to populate Other Users and Tables lists that are very slow under some circumstances and you are probably running into those. One of those queries could have run long enough to cause a crash on your server..although it seems amazing to me that a long running query could crash the database.
There are a couple of hacks to fix this performance problem, but the simplest thing is to revert to an evaluation build of 1.1 or to go back to 1.0.
Regardless of the above advice, I think that you should open up a service request with oracle. There may be some database parameters to tweak, patches to apply, or they may provide a patch for 1.1 that allows the tree to run more efficiently.
Eric

Trace file having ??? for report server's engine

I'm facing problem regarding the font for trace file of report engine. Trace is showing ??? like the following. Can anybody help me how to change the language for the the trace only.
Error 50103 (C Engine): ERR REP-0501: ??? ???? ??? ????? ?????? ???????? ???????
ORA-24323: value not allowed
We have nls_language=AMERICAN_AMERICA.AR8MSWIN1256 in system registry as our application requires it. If it is due to the nls setting then why half of msg is in english.
Regards

Slow running reports often are not the result of a flawed report, but rather a flawed configuration. For example:
1. If you call your reports (from Forms) via the default or inProcess Reports Server, often because startup time is slow, it will appear that it took too long for the report to be delievered. Using a stand-alone Rep Server is the preferred way to do this.
2. If your Forms application makes numerous calls to RRO (RUN_REPORT_OBJECT), this can tend to result in what might appear as a memory leak (although it is not). The result is delayed processing because of the excessive memory use. This problem has been overcome in Forms/Reports 11 by the use of JVM pooling. However in v10 enabling "6i compatibility" mode is the way to overcome the issue. See Note 266073.1
3. If the report runs fine from the Builder and it is connecting to the same db as when you run it from App Server, the issue is unlikely a db problem. However, if you want to look anyway, enable sqlnet tracing.
4. To enable Reports tracing and investigate other tuning options, refer to the Reports 10 documentation:
http://docs.oracle.com/cd/B14099_11/bi.1012/b14048/pbr_tune.htm
Almost forgot to mentioned this one....
If you are using a v11 db with App Server 10, you will probably want to consider reviewing Note 1099035.1 as it discusses an issue related to performance with such a configuration.
Edited by: Michael Ferrante on Apr 10, 2012 8:49 AM

Shared server trace file

Hi All,
Our production db is 10.2.0.3 with 2 nodes RAC in MS 2003 window servers. I am wondering what kind of information that Oracle capture in the shared server trace file (file name looks like instance_s001_3333.trc) . When I open some of these files I always see one query always there along with the messages like:
WAIT #8: nam='gc cr block 2-way' ela= 1222 p1=65 p2=49677 p3=1 obj#=69689 tim=4137263779
WAIT #8: nam='gc cr block 2-way' ela= 593 p1=65 p2=50863 p3=1 obj#=69689 tim=4137265531
WAIT #8: nam='gc cr block 2-way' ela= 592 p1=65 p2=50879 p3=1 obj#=69689 tim=4137266700
Should we need to tune this query to make it disappear in the shared server trace files? What are the conditions to trigger Oracle put this query into trace file?
Thank you very much in advance for your support!
Shirley

These trace files are very likely generated by some trace statements originating from client programs connected to shared server processes such as client application processes, SQL*Plus, SQL Developer, OEM, TOAD, etc.
Is your client application instrumented ?
Do some people analyze performance problems on the database side ?
The triggering statements may be some ALTER SESSION statements or package calls like DBMS_MONITOR in 10g or other
(see examples in http://www.oracle.com/technology/oramag/oracle/04-jan/o14tech_perf.html).
You should also check that instances are not configured with instance level tracing:
show parameter sql_traceYou can also check current database sessions sql tracing status with:
select sid, serial, program, sql_trace from v$session where username is not null;

Portal Trace file monitoring in TREX

HI guys,
We have a problem with the trace file.
[16:30:22.078] trace_entries   - Check completed, calling back to master and posting results...
[16:30:22.078] trace_entries   - slave hollywood:30011 ok: 200
[16:30:22.092] trace_entries   - response: OK - thanks
[16:30:22.812] open_handles    - Check completed, calling back to master and posting results...
[16:30:22.828] open_handles    - response: OK - thanks
[16:30:24.030] open_handles    - slave summary result computed
[16:30:24.092] trace_entries   - slave summary result computed
[16:33:22.030] open_handles    - trigger slave hollywood:30011
[16:33:22.046] scheduler       - Checks ran.
[16:33:22.046] trace_entries   - trigger slave hollywood:30011
[16:33:22.078] http6616        - serving request /?slavestart
This trace file is repeated and filling the harddisk
Thus ultimately reducing the portal performance.
Any idea like which program in TREX generates this trace file ..etc
In general how to detect corresponding program of the trace file
will reward points for the good reply
regards,
vijay.

Hi Sanam,
For the TREX Preprocessor trace, You define the maximum file size for the input and output of documents in INI file - TREXPreprocessor.ini
The default size is set to 'Unlimited'
Please check the following values maintained in the configuration file.
Section: [ httpclient ]
Parameter: max_content_length
Default: Unlimited
Also read,
http://help.sap.com/saphelp_sm32/helpdata/en/1d/8d49cc304dd843a3a4a23d74888939/content.htm
Hope this is helpful.
Regards,
Varun

11g Trace File Problem

I have an 11.1.0.7 database on a Windows 2003 64bit server. When I was building the database I turned on tracing in the SQLNET.ORA file. It didn't seem to work and I forgot about it and while I was backing up the server I noticed that a couple of directories were filling fast with trace files. They are under \Ora11g\diag\clients\user_"oracle user account"\host_2328975676_11\trace.
I went back and cleared out all of the extra lines in the sqlnet.ora file leaving only "sqlnet.authentication_services = (none)" and then bumped the database and restarted the listener. The files keep building up. I have two other databases setup exactly the same way on the same server/os combinations and I don't have these trace files building up. Is there somewhere else that I need to look where tracing might have been turned on when I altered the sqlnet.ora file? The database runs fine, I just don't want to have to clean these directories out. Thanks for any help.

CKPT wrote:
You can check with NET MANAGER or NETCA
I looked at Net Manager but I don't know what setting to look for. I didn't see anything about tracing. I don't know how to attach a trace file to this post so I copied some text from it. I don't know if that helps.
Trace file d:\ora11g\diag\clients\user_oraaxdb\host_2328975676_11\trace\ora_976_3032.trc
2011-01-22 17:38:37.028976 : nioqsn:entry
2011-01-22 17:38:37.031654 : nioqsn:exit
2011-01-22 17:38:37.031694 : nioqrc:entry
2011-01-22 17:38:37.031722 : nsbasic_bsd:entry
2011-01-22 17:38:37.031747 : nsbasic_bsd:tot=0, plen=68.
2011-01-22 17:38:37.031793 : nsbasic_bsd:packet dump
2011-01-22 17:38:37.031846 : nsbasic_bsd:00 44 00 00 06 00 00 00 |.D......|
2011-01-22 17:38:37.031873 : nsbasic_bsd:00 00 11 69 C2 FE FF FF |...iÂþÿÿ|
2011-01-22 17:38:37.031898 : nsbasic_bsd:FF FF FF FF FF 01 00 00 |ÿÿÿÿÿ...|
2011-01-22 17:38:37.032145 : nsbasic_bsd:00 00 00 00 00 02 00 00 |........|
2011-01-22 17:38:37.032169 : nsbasic_bsd:00 03 3B C3 FE FF FF FF |..;Ãþÿÿÿ|
2011-01-22 17:38:37.032188 : nsbasic_bsd:FF FF FF FF FF 00 00 00 |ÿÿÿÿÿ...|
2011-01-22 17:38:37.032208 : nsbasic_bsd:00 00 00 00 FE FF FF FF |....þÿÿÿ|
2011-01-22 17:38:37.032227 : nsbasic_bsd:FF FF FF FF FE FF FF FF |ÿÿÿÿþÿÿÿ|
2011-01-22 17:38:37.032246 : nsbasic_bsd:FF FF FF FF |ÿÿÿÿ |
2011-01-22 17:38:37.032265 : nsbasic_bsd:exit (0)
2011-01-22 17:38:37.032285 : nsbasic_brc:entry: oln/tot=0
2011-01-22 17:38:37.032309 : nsbasic_brc:type=6, plen=179
2011-01-22 17:38:37.032333 : nsbasic_brc:what=1, tot =179
2011-01-22 17:38:37.032352 : nsbasic_brc:packet dump
2011-01-22 17:38:37.032372 : nsbasic_brc:00 B3 00 00 06 00 00 00 |.³......|
2011-01-22 17:38:37.032393 : nsbasic_brc:00 00 08 9A 00 9A 4F 72 |...š.šOr|
2011-01-22 17:38:37.032413 : nsbasic_brc:61 63 6C 65 20 44 61 74 |acle.Dat|
2011-01-22 17:38:37.032432 : nsbasic_brc:61 62 61 73 65 20 31 31 |abase.11|
2011-01-22 17:38:37.032451 : nsbasic_brc:67 20 45 6E 74 65 72 70 |g.Enterp|
2011-01-22 17:38:37.032470 : nsbasic_brc:72 69 73 65 20 45 64 69 |rise.Edi|
2011-01-22 17:38:37.032490 : nsbasic_brc:74 69 6F 6E 20 52 65 6C |tion.Rel|
2011-01-22 17:38:37.032509 : nsbasic_brc:65 61 73 65 20 31 31 2E |ease.11.|
2011-01-22 17:38:37.032528 : nsbasic_brc:31 2E 30 2E 37 2E 30 20 |1.0.7.0.|
2011-01-22 17:38:37.032547 : nsbasic_brc:2D 20 36 34 62 69 74 20 |-.64bit.|
2011-01-22 17:38:37.032566 : nsbasic_brc:50 72 6F 64 75 63 74 69 |Producti|
2011-01-22 17:38:37.032585 : nsbasic_brc:6F 6E 0A 57 69 74 68 20 |on.With.|
2011-01-22 17:38:37.032604 : nsbasic_brc:74 68 65 20 50 61 72 74 |the.Part|
2011-01-22 17:38:37.032623 : nsbasic_brc:69 74 69 6F 6E 69 6E 67 |itioning|
2011-01-22 17:38:37.032642 : nsbasic_brc:2C 20 4F 4C 41 50 2C 20 |,.OLAP,.|
2011-01-22 17:38:37.032661 : nsbasic_brc:44 61 74 61 20 4D 69 6E |Data.Min|
2011-01-22 17:38:37.032680 : nsbasic_brc:69 6E 67 20 61 6E 64 20 |ing.and.|
2011-01-22 17:38:37.032700 : nsbasic_brc:52 65 61 6C 20 41 70 70 |Real.App|
2011-01-22 17:38:37.032719 : nsbasic_brc:6C 69 63 61 74 69 6F 6E |lication|
2011-01-22 17:38:37.032741 : nsbasic_brc:20 54 65 73 74 69 6E 67 |.Testing|
2011-01-22 17:38:37.032760 : nsbasic_brc:20 6F 70 74 69 6F 6E 73 |.options|
2011-01-22 17:38:37.032779 : nsbasic_brc:00 07 10 0B 09 01 00 00 |........|
2011-01-22 17:38:37.032798 : nsbasic_brc:00 51 04 |.Q. |
2011-01-22 17:38:37.032816 : nsbasic_brc:exit: oln=0, dln=169, tot=179, rc=0
2011-01-22 17:38:37.032835 : nioqrc:exit
2011-01-22 17:38:37.033295 : nioqsn:entry
2011-01-22 17:38:37.033313 : nioqsn:exit
2011-01-22 17:38:37.033331 : nioqsn:entry
2011-01-22 17:38:37.033342 : nsbasic_bsd:entry
2011-01-22 17:38:37.033352 : nsbasic_bsd:tot=0, plen=8155.
2011-01-22 17:38:37.033483 : nsbasic_bsd:packet dump
2011-01-22 17:38:37.033499 : nsbasic_bsd:1F DB 00 00 06 00 00 00 |.Û......|
2011-01-22 17:38:37.033511 : nsbasic_bsd:00 00 03 5E C4 29 05 04 |...^Ä)..|
2011-01-22 17:38:37.033523 : nsbasic_bsd:00 00 00 00 00 FE FF FF |.....þÿÿ|

Trace files filling up on server

Similar Messages

Maybe you are looking for