Tracing sessions...

Hello guys,
I am wondering if there is any way to know in a trace file what date/time the Query was executed. Anyone can help me?
I'm on Oracle Standard Edition 9.2.0.7 (linux-32-bits).
The trace file is generated by "alter session set sql_trace=true".
Thanks,
Paulo.

Paulo,
There is no "automatic" option for seeing exactly when a query was executed, but if you start your trace with 'alter session set sql_trace true' the first few lines of trace (after the header) will be something like:
*** SESSION ID:(9.125) 2007-08-02 22:41:04.484
APPNAME mod='SQL*Plus' mh=3669949024 act='' ah=4029777240
=====================
PARSING IN CURSOR #1 len=32 dep=0 uid=64 oct=42 lid=64 tim=113867253130 hv=3979977633 ad='6d967ef8'
alter session set sql_trace true
END OF STMT
EXEC #1:c=0,e=69,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=113867232028Look out for the timestamps: "tim=nnnnnnnnnnnnnn". This is a 9i trace file, with the timestamps in microseconds (counting from the moment the instance started).
In this case you can see the trace starting at 2007-08-02 22:41:04.484, at which point, to within a few micro seconds, tim=113867253130, so you can correlate tim= values to clock time.
You will find a few small anomalies and sequencing oddities with the tim= timestamps; but you could get Cary Millsap's book on Optimizing Oracle Performance for explanations of these.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Similar Messages

Error event id 2 - Kernel Event Tracing - Session "" failed to start with the following error: 0xC000000D

I keep getting this strange error logged as Error event id 2. Note session string is blank "". Any ideas?
Log Name:      Microsoft-Windows-Kernel-EventTracing/Admin
Source:        Microsoft-Windows-Kernel-EventTracing
Date:          24/12/2009 09:08:20
Event ID:      2
Task Category: Session
Level:         Error
Keywords:      Session
User:          SYSTEM
Computer:      George-XXL
Description:
Session "" failed to start with the following error: 0xC000000D
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
    <EventID>2</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>12</Opcode>
    <Keywords>0x8000000000000010</Keywords>
    <TimeCreated SystemTime="2009-12-24T09:08:20.835299100Z" />
    <EventRecordID>36</EventRecordID>
    <Correlation />
    <Execution ProcessID="1944" ThreadID="1948" />
    <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
    <Computer>George-XXL</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="SessionName">
    </Data>
    <Data Name="FileName">
    </Data>
    <Data Name="ErrorCode">3221225485</Data>
    <Data Name="LoggingMode">5</Data>
</EventData>
</Event>

Can you let us know if you get any Blue Screen crush error while using your comptuer?
Generally we can safely ignore the errors in the Event log. Aas we don't if you have get other issues in your computer, you can test your computer in the Clean Boot mode. This method will help us determine if this issue is caused by a loading program or service.
You can try the the following steps:
1. Click the Start Button type "msconfig" (without quotation marks) in the Start Search box, and then press Enter.
2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".
Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK.
Please test this issue in this Clean Boot environment, if the issue disappears in the Clean Boot environment, you can use the dichtomy to quickly narrow down which entry is causing the issue. You can refer to the
KB929135.
Good luck!
John
This is a very poor answer. This guy doesn't know what he's talking about because if you tell someone its ok to "safely ignore the errors in the event log" as a blanket instruction ESPECIALLY because as he stated so himself
he didn't know if there were other issues with the OP's pc then he's giving really bad advice. If you ignore errors in the event log then over time your system will degrade and you will have other issues.. Every error on your pc should NOT be ignored.
It should be decided on a case by case situation.
Furthermore this is an error involving the Windows Session which it states has failed. Definitely should NOT be ignored.
I've got the same error which has suddenly just showed up. No BSOD, Do not have WHS installed and all my media center connectors have NEVER been connected. I don't believe this is a service issue. I think it has something
to do with kernel event tracing.
Of course, it's just my opinion....I could be wrong!

Problem in tracing session using ORADEBUG utility?

I want to trace a session using oradebug utility.what i have done is
SQL>oradebug setospid 25807
SQL> oradebug set ospid 27441
unknown command beginning "oradebug s..." - rest of line ignored.
How i can race another session using oradebug utility.
Thank you...

The correct syntax is
oradebug setospid <Unix pid>
You can 'attach' to one process only.
You have two oradebug setospid commands issued, the latter one is wrong, but wouldn't have worked anyway.
The usual method to trace a session is
oradebug setospid ...
oradebug event 10046 trace name context forever, level 12
This should work.
Note you can accomplish the same using dbms_system.set_ev
Sybrand Bakker
Senior Oracle DBA

How to trace for multiple user sessions?

Hello -
I have a username from the app that has 7 connections to the database. What is the easiest way that I can run the 10046 trace event across all 7 sessions, and also name the trace files so they can be recognized in user_dump?
Thanks in advance!

Check what sid and serial# has session:
select sid, serial# from sys.v_$session where ...
start tracing session with:
execute dbms_system.set_sql_trace_in_session(sid, serial#, true);
stop tracing with
execute dbms_system.set_sql_trace_in_session(sid, serial#, false);
Look into udump directory for trace files:
The default name for a trace files is INSTANCE_PID_ora_TRACEID.trc where:
INSTANCE is the name of the Oracle instance,
PID is the operating system process ID (V$PROCESS.OSPID); and
TRACEID is a character string of your choosing.

Trace other session in 9.2.0.6

Hi,
I'm mostly using oradebug for setting 10046 trace event in other session .
This works without problems , until I hit old 9.2.0.6 DB on WINDOWS 2000 .
Every time I'm using that approach
ORADEBUG SETOSPID &OSPID ;
ORADEBUG EVENT 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12;
ORADEBUG TRACEFILE_NAME;
Traced process gives:
ORA-03113: end-of-file on communication channelI've tried exec dbms_system.set_ev(10,20,10046,12,''); with no success as well (same error) .
How You deal with that kind of old software on Windows 2000 ?
Please advice with real life experience I've read doc :).
Regards
GregG

Thanks , looks like that worked .
I did some additional tests and here follows my thoughts:
1. All mentioned methods works (oradebug, dbms_system.set_ev) if traced session is not in tight pl/sql loop like:
declare
l_c number;
begin
for i in 1 .. 1000
loop
select count(*) into l_c from dba_source;
end loop;
end;
/Session which is doing so crashed in all cased with exception of usage dbms_support .
So, thanks again.
Regards
GregG

Why is serial# needed for unique session info

hello everybody,
as you know, a session is unique with 2 fields, SID and SERIAL# which exist on v$session view.
my question is why is serial# needed and for which case serial# is changing.
now, you can say that, "only oracle developers know this, that is the design" but what i mean is, for ex: if i wanted to find a session which is blocked by another session, I use this:
select * from v$session where blocking_session is not null;in blocking_Session field, oracle gives me the session id (SID) which is blocking a session. so i can use this SID and i can kill it for instance but SID is not unique for a session I can find more than one session with same SID which one is the blocking one ?
in real life i didnt see an example of that, there is no same sid in system like my blocking session example. so I believe that serial# is assigning for another purpose, I mean, i thougth that it could be for autonomous transaction, maybe they user same sid but differen serial# but when i tested it, i saw that i was wrong.
so, why serial# is exists. if this is a design issue, how can i find a blocking session by just using SID info ?
thanks a lot.

Not surprisingly, an explanation may already be found in the documentation (and copied in Rene's reply above):
See http://docs.oracle.com/cd/E11882_01/server.112/e25513/dynviews_3016.htm (column description).
Or search:
http://www.oracle.com/pls/db112/search?word=sid+serial%23&partno=
Besides for terminating sessions, serial# may be relevant when e.g. tracing sessions (SQL Trace).
Not sure what type of example you were looking for, but I came up with this in about five seconds:
C:\Users>sqlplus blocker_user
Enter password:
Connected to:
Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production
SQL> select sid,serial# from v$session where sid=(select sid from v$mystat where rownum=1);
       SID    SERIAL#
       136         27
SQL> conn other_user
Enter password:
Connected.
SQL> select sid,serial# from v$session where sid=(select sid from v$mystat where rownum=1);
       SID    SERIAL#
       136         29Edited by: orafad on Feb 1, 2012 12:18 AM

Oracle Trace File generation for a session

Hi,
I am using oracle 10g(10.2.0.5) in RHEL5 server. i have used the exec dbms_system.set_sql_trace_in_session(147,3,TRUE); statement to trace a particular session. i am able to trace successfully but i have created a new table in that session where i am not able to find any create table statement in the generated trace file but i can find the insert statements which i performed on the newly created table in the trace file.
Does DDL statements not recorded in the trace events???
Regards,
007

Hi;
Please see below doc which may helps you
DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION DOES NOT GENERATE TRACE FOR ACTIVE SESSION [ID 236178.1]
How To Enable SQL Trace for All New Sessions [ID 178923.1]
Tracing Sessions in Oracle Using the DBMS_SUPPORT Package [ID 62160.1]
Regard
Helios

10046 event tracing

How would I enable 10046 event tracing in HTMLDB? I'm guessing that it's similar to '&p_trace=YES' but I can't hit upon the right way to do it.
Thanks.

David,
One more note, tracing and debugging are supported only for applications with build status set to "Run and Build Application". Setting an application's build status to "Run Application Only" (on the application attributes page) allows developers to prevent users from tracing sessions and displaying debug pages.
Scott

High Disk I/O Problem

Hello all
why every server have a capture Process have this problem "High Disk I/O" ???
in all configurations , transactions load (high or low) , number of connections (high or low)
i try to keep server without any transactions or any connections for 6 day and i still have this Problem
it seems a serious problem without fixing
release 10.2.0.1

hi rijesh
SEGMENT_NAME Size in MB SUM(BLOCKS)
LOGMNR_RESTART_CKPT$ .5 64
in Oracle Enterprise manager wait event is :
Wait event "Streams capture: waiting for archive log" in wait class "Other" was consuming significant database time.
i traced session that cause this wait event and generate tkprof file but i think there is nothing useful :
{color:#0000ff}TKPROF: Release 10.2.0.1.0 - Production on Mon Nov 17 16:08:35 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
{color}
{color:#0000ff}Trace file: C:\oracle\admin\test\bdump\test_p000_3740.trc
Sort options: prsdsk exedsk fchdsk
count = number of times OCI procedure was executed
cpu = cpu time in seconds executing
elapsed = elapsed time in seconds executing
disk = number of physical reads of buffers from disk
query = number of buffers gotten for consistent read
current = number of buffers gotten in current mode (usually for update)
rows = number of rows processed by the fetch or execute call
Trace file: C:\oracle\admin\test\bdump\test_p000_3740.trc
Trace file compatibility: 10.01.00
Sort options: prsdsk exedsk fchdsk
1 session in tracefile.
0 user SQL statements in trace file.
0 internal SQL statements in trace file.
0 SQL statements in trace file.
0 unique SQL statements in trace file.
10268 lines in trace file.
0 elapsed seconds in trace file.
{color}
i tried to open trace file "test_p000_3740.trc" and i found this :
{color:#0000ff}Dump file c:\oracle\admin\test\bdump\test_p000_3740.trc
Mon Nov 17 14:52:21 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining options
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 4 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:2789M/4094M, Ph+PgF:4519M/5972M, VA:1627M/2047M
Instance name: test
{color}
{color:#0000ff}Redo thread mounted by this instance: 1
Oracle process number: 29
{color}
{color:#0000ff}Windows thread id: 3740, image: ORACLE.EXE (P000)
*** 2008-11-17 14:52:21.652
*** SERVICE NAME:(SYS$USERS) 2008-11-17 14:52:21.652
*** SESSION ID:(144.2) 2008-11-17 14:52:21.652
WAIT #0: nam='control file sequential read' ela= 234 file#=0 block#=1 blocks=1 obj#=-1 tim=3793171610
WAIT #0: nam='control file sequential read' ela= 294 file#=1 block#=1 blocks=1 obj#=-1 tim=3793186744
WAIT #0: nam='control file sequential read' ela= 208 file#=2 block#=1 blocks=1 obj#=-1 tim=3793187894
WAIT #0: nam='control file sequential read' ela= 182 file#=0 block#=16 blocks=1 obj#=-1 tim=3793188866
WAIT #0: nam='control file sequential read' ela= 233 file#=0 block#=18 blocks=1 obj#=-1 tim=3793189902
WAIT #0: nam='log file sequential read' ela= 12608 log#=0 block#=43745 blocks=8192 obj#=-1 tim=3793255308
WAIT #0: nam='log file sequential read' ela= 68218 log#=0 block#=43745 blocks=8192 obj#=-1 tim=3793363640
WAIT #0: nam='log file sequential read' ela= 100 log#=0 block#=1 blocks=1 obj#=-1 tim=3793518549
WAIT #0: nam='log file sequential read' ela= 89 log#=0 block#=1 blocks=1 obj#=-1 tim=3793541091
WAIT #0: nam='control file sequential read' ela= 14717 file#=0 block#=1 blocks=1 obj#=-1 tim=3793556425
WAIT #0: nam='control file sequential read' ela= 6630 file#=1 block#=1 blocks=1 obj#=-1 tim=3793563619
WAIT #0: nam='control file sequential read' ela= 9355 file#=2 block#=1 blocks=1 obj#=-1 tim=3793573635
WAIT #0: nam='control file sequential read' ela= 11426 file#=0 block#=16 blocks=1 obj#=-1 tim=3793585608
WAIT #0: nam='control file sequential read' ela= 201 file#=0 block#=18 blocks=1 obj#=-1 tim=3793586348
WAIT #0: nam='control file sequential read' ela= 190 file#=0 block#=1 blocks=1 obj#=-1 tim=3793587134
WAIT #0: nam='control file sequential read' ela= 186 file#=1 block#=1 blocks=1 obj#=-1 tim=3793587842
WAIT #0: nam='control file sequential read' ela= 185 file#=2 block#=1 blocks=1 obj#=-1 tim=3793588548
WAIT #0: nam='control file sequential read' ela= 187 file#=0 block#=16 blocks=1 obj#=-1 tim=3793589241
WAIT #0: nam='control file sequential read' ela= 185 file#=0 block#=18 blocks=1 obj#=-1 tim=3793589944
WAIT #0: nam='log file sequential read' ela= 72452 log#=0 block#=43745 blocks=8192 obj#=-1 tim=3793663620
WAIT #0: nam='log file sequential read' ela= 106739 log#=0 block#=43745 blocks=8192 obj#=-1 tim=3793771943
WAIT #0: nam='log file sequential read' ela= 95 log#=0 block#=1 blocks=1 obj#=-1 tim=3793908609
WAIT #0: nam='log file sequential read' ela= 111 log#=0 block#=1 blocks=1 obj#=-1 tim=3793925054
WAIT #0: nam='control file sequential read' ela= 22382 file#=0 block#=1 blocks=1 obj#=-1 tim=3793948070
WAIT #0: nam='control file sequential read' ela= 6591 file#=1 block#=1 blocks=1 obj#=-1 tim=3793955243
WAIT #0: nam='control file sequential read' ela= 9478 file#=2 block#=1 blocks=1 obj#=-1 tim=3793965270
WAIT #0: nam='control file sequential read' ela= 11449 file#=0 block#=16 blocks=1 obj#=-1 tim=3793977257
WAIT #0: nam='control file sequential read' ela= 203 file#=0 block#=18 blocks=1 obj#=-1 tim=3793977980
{color}
any suggestions my friend
Best regards
Edited by: wassim haddad on Nov 17, 2008 5:47 AM

Create a new trace-file

hello together,
i have a question according to creation of new user trace files in user_dump_dest:
with the following command:
EXEC dbms_system.set_sql_trace_in_session(18,628,TRUE);
I created a new file in the trace directory.
Then I stopped the tracing with:
EXEC dbms_system.set_sql_trace_in_session(18,628,FALSE);
I disconnected with the traced session sid=18 and connected once again.
With retracing the session I didn't get a new trace file but the existing trace file was actualized.
=> what do I have to do to achive a new trace file for the second session-tracing?
Thanks and Regards
Stefan

Hello Maran,
I only want to trace one session; but I want to create a new trace file for the second run when tracing; but at the moment the first trace file will be continued...
thanks

Problem with xperf

Hi,
I followed the instructions in
Silverlight TV 57: Performance Tuning Your Apps
and when opening the ETL file (created from
HeapMonitor) using xperf I got this warning:
Performance Analyzer noticed that 13912 events and 0 buffers were lost in this trace.
This is usually caused by insufficient disk bandwidth for ETW logging.
Please try increasing the minimum and maximum number of buffers and/or
the buffer size. Doubling these values would be a good first attempt.
Please note, though, that this action increases the amount of memory
reserved for ETW buffers, increasing memory pressure on your scenario.
See "xperf -help start" for the associated command line options.
XPERF MIGHT NOT BE ABLE TO PROVIDE RELIABLE DATA IN THIS SITUATION.
Would you like to continue analyzing this trace?
(I just clicked on Yes)
Is that usual? I tried it in two computers running Windows 7 and got the same warning window.
The commandline help wasn't very helpful...

The key clue here is the first line in the body of that error message, the part that says "This is usually caused by insufficient disk bandwidth for ETW logging." You can try the corrections suggested in the error message, modifying the buffer sizes may
very well help.
However, I've found that there are a couple tricks to getting this work reliably.
HeapMonitor is simply a light-weight wrapper around XPerf that enables the ETW loggers necessary to collect heap trace information. Some of these ETW loggers are system-wide rather than being specific to a process, thus, minimizing the amount of activity
on the system can help reduce the number of events being logged and therefore reduce the amount of bandwidth necessary to flush the in-memory buffers to disk. In short, close down as many applications and services as you can before collecting your trace.
If you have multiple hard disks, start your tracing session from the opposite disk than the one that your OS partition resides on. Windows reads and writes to the disk a decent amount in normal operation. Whenever the disk is busy doing things for Windows,
it can't be flushing your event buffers to disk. Ensuring that your trace is being written to a non-OS disk increases the chance that your events will be flushed to disk before they are lost.It
It isn't always the end of the world when that message pops up either. I've been able to gather a lot of useful information from traces with lost events, though I wouldn't recommend making a habit of it :)
Try these ideas out and let me know if they work for you.
Mike

My Windows 7 Starter keep shut down by itself 6-7 time a day.

My Notebook shut-down often, Can you please help me to rectify. I have checked the log note as: Kernel Event Tracing - #Session "Microsoft Security Client OOBE " stoppedd due to the following error: 0xC000000D # What is this problem? Thank.

Fro Hotogeek:
This procedure appears to solve the issue.
It MUST be done Exactly by the Steps.
1. DISABLE the Microsoft Antimalware Service
2. REBOOT the machine
3. DELELETE the EppOobe.etl File
(Reference Path) C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl
4. REBOOT the machine
5. ENABLE the Microsoft Antimalware Service
6. REBOOT the machine
7. Frequently CHECK the Administrative Events Log under Custom Views to ensure the error does not reappear.
NOTE: Just Deleting the EppOobe.etl file and Rebooting will NOT work.
M.

Statistics_level = ALL

On 10.2.0.3:
I have this delete statement. It takes 40 seconds to execute 1500 times with statistics_level parameter set to ALL.
Compared to 4 seconds with statistics_level parameter set to TYPICAL.
Here is a tkprof report with statistics_level = TYPICAL:
call count cpu elapsed disk query current rows
Parse 0 0.00 0.00 0 0 0 0
Execute 1500 4.33 4.23 20 57852 1570 500
Fetch 0 0.00 0.00 0 0 0 0
total 1500 4.33 4.23 20 57852 1570 500
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 109 (DBFRONT) (recursive depth: 1)
Rows Execution Plan
0 DELETE STATEMENT MODE: ALL_ROWS
0 DELETE OF 'SONG_LIST_JUK_DETAIL'
0 HASH JOIN (ANTI)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'SONG_LIST_JUK_DETAIL_PK' (INDEX (UNIQUE))
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'IDX_JUK_HD_SONG_HDIDSONID' (INDEX (UNIQUE))
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 20 0.00 0.00
BWT, how do i edit this thread so my tkprof report be readable to you?
And here is my tkprof report with statistics_level = ALL:
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 1500 40.64 40.01 35 41741 2607 1467
Fetch 0 0.00 0.00 0 0 0 0
total 1501 40.64 40.01 35 41741 2607 1467
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 109 (DBFRONT) (recursive depth: 1)
Rows Execution Plan
0 DELETE STATEMENT MODE: ALL_ROWS
0 DELETE OF 'SONG_LIST_JUK_DETAIL'
0 HASH JOIN (ANTI)
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'SONG_LIST_JUK_DETAIL_PK' (INDEX (UNIQUE))
0 INDEX MODE: ANALYZED (RANGE SCAN) OF
'IDX_JUK_HD_SONG_HDIDSONID' (INDEX (UNIQUE))
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
db file sequential read 35 0.04 0.08
Same plan is used in both cases. I notice the following:
both have INDEX MODE: ANALYZED (RANGE SCAN) OF.
I cannot find documentation regarding INDEX MODE: ANALYZED (RANGE SCAN) OF.
Does anyone has a link that points to this?
Why does it says "mode:analyzed"
Anyone has an explication? Like the optimizer does more work when statistics_level = ALL , and thats why it took more time to execute. Should i have run something in the dbms_stats package on top of using statistics_level = ALL?
Here is the script for my stats gathering for my table:
execute dbms_stats.gather_table_stats(ownname=> USER, tabname=> 'SONG_LIST_JUK_DETAIL' , estimate_percent=> DBMS_STATS.AUTO_SAMPLE_SIZE, cascade=> DBMS_STATS.AUTO_CASCADE, degree=> null, no_invalidate=> DBMS_STATS.AUTO_INVALIDATE,granularity=> 'AUTO',method_opt=> 'FOR ALL COLUMNS SIZE AUTO');
Should that ive run the stats differently so the query run fast with statistics_level set to ALL?

With statistics_level = ALL, Oracle will have to do a little more, so a slight increase in cpu time is expected, but not like you are showing here.
However, before investigating this myself, I see you have some odd differences. When you take a closer look at the tkprof output, you see the first delete statement had actually deleted 500 rows, while the second was deleting 1467 rows. So it looks like your delete statements cannot be compared.
Also the number of rows is missing from the row source operation. Are you sure you properly disconnected your traced session to make sure all cursors were closed?
> BWT, how do i edit this thread so my tkprof report be readable to you?
Just click the edit icon next to the reply icon and add the tags [pre] and [/pre] around the code and tkprof output.
Regards,
Rob.

Microsoft Security Client OOBE stopped due to the following error: 0xC000000D

I keep getting this error in my event Viewer and I removed Microsoft Security Client a few weeks ago and replaced it with Bitdefender 2012
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D
I am also getting these aswell...
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x0811960D92F5. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the
network address (DHCP) server.
A problem prevented Customer Experience Improvement Program data from being sent to Microsoft, (Error 80004005).

If you do not want to reinstall Microsoft Security Essentials to stop this problem, there is a step which you MUST, I repeat, MUST follow. As indicated above by Zuhl3156, YOU MUST, again, MUST shutdown the security counter. This is a problem
when you uninstall MSE, it does not remove the security counter. This is the reason that everyone says to delete the C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl file. This file is used and created by this counter.
If you have uninstalled the MES, then you MUST delete the C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl. But, MOST IMPORTANTLY, you MUST go into into Computer Management and drill down into:
System Tools -> Performance -> Data Collector Sets -> Startup Event Tracing Sessions
Then, in the frame to the right on that window, select Microsoft Security Client OOBE, right click on it and select Properties. Then DISABLE it (uncheck the Enabled box). Then, when you select OK, if you have uninstalled MSE and NOT reinstalled
it, the entry in the right frame will 'magically' disappear.
This is a problem with the uninstall of MSE and needs to be resolved by Microsoft (hopefully they are reading this). It has taken me DAYS to discover this, and many different attempts to resolve this. But, apparently, this has now resolved my
problem. I have seen performance counters cause many problems in my experience with Windows, and am very confident that this resolves the issue.
I cannot thank Zuhl3156 enough for his suggestion and my willingness to try it (I noticed 'performance counter' and jumped on it). It seems to work wonderfully for the moment.
I hope this helps someone else who has spent days trying to chase this nightmare down.
Jim

Dev_LDAP.trc is growing

Hi Experts
               One of our production system's filesystem is growing by dev_LDAP.trc file. This file continuous growing. Current size of this file is 1.6 GB. Is anybody have idea for this cause.Please reaply me.
dev_LDAP.trc file contents.
Slot 0 (SAPWEBPSWD): >>> ldap_initU(host="LDAPSERV.TSL.TELUS.COM", port=389)
sapldap [418]: >>> ldap_init()
sapldap [420]: <<< ldap_init()
Slot 0 (SAPWEBPSWD): <<< ldap_initU() == <NOT NULL> := connected
Slot 0 (SAPWEBPSWD): >>> ldap_set_option(version=3)
Slot 0 (SAPWEBPSWD): <<< ldap_set_option() == 0
Slot 0 (SAPWEBPSWD): >>> ldap_simple_bind_sU(dn="uid=t829712,ou=people,ou=internal,o=telus,c=ca", password: not initial)
sapldap [517]: >>> ldap_simple_bind_s()
sapldap [519]: <<< ldap_simple_bind_s()
Slot 0 (SAPWEBPSWD): <<< ldap_simple_bind_sU() == 0 := success
Slot 0 (SAPWEBPSWD): >>> ldap_search_sU(base="O=TELUS, C=CA", filter="(&(objectclass=person)(uid=t829712))", scope=2)
sapldap [599]: >>> ldap_search_st()
sapldap [602]: <<< ldap_search_st()
Slot 0 (SAPWEBPSWD): <<< ldap_search_sU() == 0
sapldap [654]: >>> ldap_get_dn()
sapldap [656]: <<< ldap_get_dn()
sapldap [667]: >>> ldap_memfree(DN)
sapldap [669]: <<< ldap_memfree(DN)
sapldap [685]: >>> ldap_first_attribute()
sapldap [687]: <<< ldap_first_attribute()
sapldap [700]: >>> ldap_memfree(ATTR)
sapldap [702]: <<< ldap_memfree(ATTR)
sapldap [763]: >>> ldap_get_values()
sapldap [765]: <<< ldap_get_values()
sapldap [805]: >>> ldap_value_free()
sapldap [807]: <<< ldap_value_free()
sapldap [718]: >>> ldap_next_attribute()
sapldap [720]: <<< ldap_next_attribute()
sapldap [734]: >>> ldap_memfree(ATTR)
sapldap [736]: <<< ldap_memfree(ATTR)
sapldap [763]: >>> ldap_get_values()
sapldap [765]: <<< ldap_get_values()
sapldap [805]: >>> ldap_value_free()
sapldap [807]: <<< ldap_value_free()
Thanks & Regards
Jignesh
Message was edited by:
        Jignesh Patel
Message was edited by:
        Jignesh Patel

Hi,
Try this...i dont that it will work or not just give a trial.....
1. Create the registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
     ldap\Tracing\App1.exe
and then start a tracing session using the following command:
C:\>tracelog.exe -start ldaptrace -guid #099614a5-5dd7-4788-8bc9-e29f43db28fc -f .\ldap.etl -flag 0x80000
2. After this command has started, DEBUG_BIND tracing messages will be written to .\ldap.etl. Execute App1.exe and reproduce the unexpected behavior.
3. Shut down the tracing session as follows:
C:\>tracelog.exe -stop ldaptrace
4. Delete the registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
     ldap\Tracing\App1.exe
so that no other users can trace App1.exe.
5. Use a Trace Consumer such as Tracerpt.exe to review the information in the trace log:
C:\>tracerpt.exe .\ldap.etl -o -report
thnx
RK

Tracing sessions...

Similar Messages

Maybe you are looking for