Trace file missing

Hi,
The trace file of an application GDS in a production MDM system was missing.Where as it was present in Development MDM System.Compared all the preoperties in log configurator.Also checked the severity levels and other info in log viewer.They were same.Can anyone help me what do I need to change to get the trace file found.
Does any XML file needs to be changed in config tool or visual admin?If so, where?Please help.
Thanks,
Sudheer

basically all log files present inside folder of mdm sever -
> logs
but might be in your case log file moght be deleted so you need to restart the server so it will automatically create new log file. or you can trace the path of your log folder through mds.ini file might be your problem get sloved

Similar Messages

  • Trace file is missing

    Hi,
    The trace file of an application GDS in a production MDM system was missing.Where as it was present in Development MDM System.Compared all the preoperties in log configurator.Also checked the severity levels and other info in log viewer.They were same.Can anyone help me what do I need to change to get the trace file found.
    Does any XML file needs to be changed in config tool or visual admin?If so, where?Please help.
    Thanks,
    Sudheer

    wrong forum, don't think this is fall under appl server area.
    please check with MDM Forum, as GDS is under MDM area.
    Expert Forums » SAP NetWeaver » SAP Master Data Management
    Anyway, SAP Note 733903 might be helpful.
    cheers,
    vincent

  • Details missing in default trace file of XI

    Hi Experts,
    I am doing RFC to RFC scenario. I am getting checkered flag in SXMB_MONI. But for some reason i am not getting the details of my scenario in the default trace of XI. I'm not sure if the detiails of scenarios involving RFC's will be updated in the trace files. If yes, please help me in finding the reasons as to why it is not heppening in my case.
    Thanks and Regards,
    Hari.

    Hi,
    Increase your logging/ Tracing levels in the Integration engine configuration to see the synchronous message in the SXMB_MONI.
    1.Execute SXMB_ADM in the ABAP stack of XI
    2.Navigate to Configuration --> Integration Engine Configuration --> Change Specific Configuration Data
    Set the following:
    Category : Runtime
    Parameter : LOGGING_SYNC
    value : 1 (activated)
    Parameter : TRACE_LEVEL 3
    value : 3 (activated)
    For information on how to activate and deactivate traces, see the following SAP Note: 532918    (RFC Trace Generation)
    also go with below links
    Configuring the Trace File
    http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
    Enqueue Trace Analysis
    http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
    Enqueue Trace Records
    http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
    Please let me know if this helps you or do you need any more info.

  • Continual library cache misses in trace file for spatial queries

    Hi all,
    Could somebody explain to me how the SQL parse engine works for spatial queries.
    My understanding is that Oracle creates a hash value for SQL that is parsed with no errors. This hash value is then stored in the library cache ready to be matched against other incoming SQL statements. This provides one of the main reasons for using parametising SQL in languages such as PL/SQL, .Net etc and improves performance on query intensive applications.
    However i have noticed that for spatial, any queries except for refreshes of identical ones already sent, the SQL engines re parses the query. This can take upto 0.2 seconds which is causing a performance bottle neck.
    When looking at the full trace file of a single spatial query using SDO_FILTER with a query window the amount of additional internal queries that are performed is quiet a lot. Are these additional queries included in the total parse time?
    I am wondering why for spatial queries the only way to get a hit in the library cache was to refresh an exact same SQL that had been previously sent?
    Thanks
    Daniel

    Those additional internal queries are not included in the parse time,
    if they are used in the execution time.
    Edited by: yhu on Mar 4, 2011 10:52 AM

  • Missing Oracle trace file

    I gained a new database - and if it didnt have data in it or a PRODUCTION box I'd rebuild!
    Windows Server 2003 Enterprise x64 Edition SP2 running 10g 10.2.0.3
    Management Packs active: Database Diagnostics, Database Tuning, Database Configuration
    user_dump_dest = c:\oracle\admiprod\udump
    Executing:
    select
    u_dump.value || '/' ||
    db_name.value || '_ora_' ||
    v$process.spid ||
    nvl2(v$process.traceid, '_' || v$process.traceid, null )
    || '.trc' "Trace File"
    from
    v$parameter u_dump
    cross join v$parameter db_name
    cross join v$process
    join v$session
    on v$process.addr = v$session.paddr
    where
    u_dump.name = 'user_dump_dest' and
    db_name.name = 'db_name' and
    v$session.audsid=sys_context('userenv','sessionid');
    Results: C:\oracle\admin\prod\udump/prod_ora_388.trc (NOTE THE "/" IS CODED TO RETURN AS SUCH)
    YET prod_ora_388.trc is NOT found at C:\oracle\admin\prod\udump OR anywhere on the C or associated D drives - any idea what is going on here, and if so how to correct it so the trc does show up?

    Did You enabled session tracing for that particular user?
    If not, the of course You will find no trace file, just the possible name will be returned and path.
    For first enable tracing, then look at trace directory for particular file.
    And / is returned just because script is for unix. In your case you should replace it with \ as it is windows env.
    and it's easier to identify trace files just adding some identifier to them with
    alter session set tracefile_identifier ="some_name";
    then in udump dierctory just search for this name.

  • Not able to get the actual plan from trace file

    Hi all
    I have a Db package and want to get actual execution plan of all the statements in that pakcage it does provides the plan for System's statements but does not displays the plan for Sql statements
    DB version 9.2.0 using the following sequence of insructions
    set timing on
    set serveroutput on
    alter session set events '10046 trace name context forever ,level 12';
    begin
    run_service.collect_data(sysdate);
    end;
    alter session set sql_trace=false;
    exit; ---exit from Sql
    now look at the output
    select distinct obj#,containerobj#,pflags,xpflags,mflags
    from
    sum$, suminline$ where sumobj#=obj# and inline#=:1
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.00 0 0 0 0
    Execute 1 0.00 0.00 0 0 0 0
    Fetch 1 0.00 0.00 1 1 0 0
    total 3 0.00 0.00 1 1 0 0
    Misses in library cache during parse: 0
    Optimizer goal: CHOOSE
    Parsing user id: SYS (recursive depth: 2)
    Rows Row Source Operation
    0 SORT UNIQUE
    0 NESTED LOOPS
    0 TABLE ACCESS BY INDEX ROWID SUMINLINE$
    0 INDEX RANGE SCAN I_SUMINLINE$_2 (object id 1614116)
    0 TABLE ACCESS BY INDEX ROWID SUM$
    0 INDEX UNIQUE SCAN I_SUM$_1 (object id 319)
    Elapsed times include waiting on following events:
    Event waited on Times Max. Wait Total Waited
    ---------------------------------------- Waited ---------- ------------
    db file sequential read 1 0.00 0.00
    SELECT SEQ_NUM, S_DATE, S_TIME, CSTATUS, G_SERVICE,
    B_REFERENCE, V_REFERENCE, M_PRIORITY
    FROM GL_HIST
    ORDER BY S_DATE DESC, S_TIME DESC
    call count cpu elapsed disk query current rows
    Parse 1 0.01 0.01 0 0 0 0
    Execute 2819 0.37 0.32 0 0 0 0
    Fetch 2819 2.50 20.47 2786 20164 0 2819
    total 5639 2.88 20.81 2786 20164 0 2819
    Misses in library cache during parse: 1
    Optimizer goal: CHOOSE
    Parsing user id: 15550 (recursive depth: 1)
    Elapsed times include waiting on following events:
    Event waited on Times Max. Wait Total Waited
    ---------------------------------------- Waited ---------- ------------
    db file sequential read 2786 0.05 18.19
    latch free 4 0.04 0.06
    UPDATE G_ORIG SET G_SERVICE = :B1
    WHERE
    SEQ_NUM = :B5 AND S_DATE = :B4 AND S_TIME = :B3 AND
    C_STATUS = :B2 AND NVL(G_SERVICE, '+') <> NVL(:B1, '+')
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.03 0 0 0 0
    Execute 3731 0.74 0.99 261 18712 119 54
    Fetch 0 0.00 0.00 0 0 0 0
    total 3732 0.74 1.02 261 18712 119 54
    Misses in library cache during parse: 1
    Optimizer goal: CHOOSE
    Parsing user id: 15550 (recursive depth: 1)
    Elapsed times include waiting on following events:
    Event waited on Times Max. Wait Total Waited
    ---------------------------------------- Waited ---------- ------------
    db file sequential read 261 0.01 0.19
    latch free 9 0.01 0.04
    COMMIT

    Remove the line alter session set sql_trace=false and just exit/disconnect. The explain plain is contained in the STAT lines in the trace file and are only written when the cursor closes. If you turn off tracing before the cursor closes the STAT lines will not get written.

  • Ora-00604 error while taking tkprof of a trace file

    Sorry i am giving the full erro but omitting exact table names
    Hi ,
    I have an error while taking tkprof of a trace file.
    I gave the following command ---
    tkprof <source.trc> <file.prc> sys=no sort=exeela,fchela,prsela explain= /
    error is --
    Error in create table of EXPLAIN PLAN table : unix_session_user.prof$paln_table
    ORA-00604: error occurred at recursive SQL level 1
    ORA-20001: Step-6:DDL
    Event Security. You are not permitted to perform the requested structural
    changes to PROF (TABLE)
    Event triggered : CREATE
    ora_login_user
    (session_user) : unix_session_user(dummy)
    Search : select count(*) from
    tabl(dummy table name) where obj_name like '%\%%' escape '\' and obj_type =
    'TABLE' and obj_type = 'USER' and ( event_CREATE = 'Y' or status =
    'Override')
    ORA-06512: at line 162
    ORA-06510: PL/SQL: unhandled
    user-defined exception
    EXPLAIN PLAN option disabled.
    i searched for the error and in oracle forum i found a solution .. http://forums.oracle.com/forums/thread.jspa?threadID=844287&tstart=0
    but after giving the table option it is giving the same error
    tkprof <source.trc> <file.prc> sys=no sort=exeela,fchela,prsela table=old_schema.plan_table explain= /
    it again gave the same error.
    In both two cases it gives elapsed time results,library cache missing etc but before giving this it throws ORA-00604 error as stated above
    then i again correct the tkprof statement ..
    tkprof <source.trc> <file.prc> sys=no sort=exeela,fchela,prsela table=new_schema.plan_table explain= /
    say this schema name here i used is dummy schema name.
    My question is did this error came as we had not sufficient previlages in the old_schema but that previleges we have in new_schema?
    My databse version is 9.2.0.4.0
    Thanks in advance
    Edited by: bp on Feb 3, 2009 11:36 PM
    Edited by: bp on Feb 3, 2009 11:40 PM

    Please post here full error message, there should be lines with ORA-00604 and then some other ORA as well.
    And are there any trace files generated during this error?
    And as You can see from error description, probably You will have to contact with Oracle support in order to solve this case:
    oerr ora 00604
    00604, 00000, "error occurred at recursive SQL level %s"
    // *Cause:  An error occurred while processing a recursive SQL statement
    // (a statement applying to internal dictionary tables).
    // *Action: If the situation described in the next error on the stack
    // can be corrected, do so; otherwise contact Oracle Support.

  • Music files missing/hidden in folder on network hdd

    Hi all,
    I have setup my home net work with a iMac (mountain Lion) backed up by a TimeCapsule and at the back of the TimeCapsule I have a 2TB networked external HDD. My iTunes library is located on this HDD, I take care not to start up iTunes before this networked external HDD has propoerly mounted to avoid any conflicts with links to my itunes library files and folders.
    The other day I noticed a few missing files (the dreaded exclamation mark !), not too bad a figured, I located a few manually but reached some that does my head in...... Out of the whole album there are two files "missing", the other ones play as they should. When I try and locate the missing files the folder comes up empty.....
    I have even checked the songs that do play in the same album....they dont show up either, even though they still play in iTunes (yes, they are all located at the same location). The album was originally ripped from a CD and I don't use iTunes Match or Genius.
    I have tried to find the files by:
    1."open in finder" - files missing / whole folder empty
    2."through finder and located the drive and folder" - files missing / folder empty
    3."copy file location from "get info" and paste into "go to folder" - the file temporarily appears in the finder window but dissapears shortly after / folder yet again empty.
    4. I check the folder "get info" from my finder and it says "zero bytes"
    5. I can't use Search because its on an external HDD and there fore not indexed
    6.I have tried to copy the folder to the desktop but still shows empty....
    7. I have tried to "organise" my library, still no change.
    What the..xxx..is happening..?
    From what I can gather, the files are actually there but not visible through the finder window (even though the folder appears to be 0 bytes).
    The problem being that I can't locate my missing files because I cant see them any more......
    Am I missing something (like show hidden folder on a Mac) or has it got to do with anything else...? How can I fix it..? I have found posts that relate to windows users forced their W7 to show hidden folders but nothing yet on Mac.....
    Help.
    //Fred

    I was lucky to be able to use a PC, that after trying numerous times actually read the external hdd, I quickly copied all files over to a backup hdd and recovered all files. After that I ended up in contact with Western Digital about the incident and they recommended to completely erase (7-pass erase) of the hdd, which ended up taking over 5 days to do. They gave me no reason as to "Why" it would have happened but if I erase and reformatted of the hdd and the problem reoccurred they recommended to get the unit replaced.
    I was lucky to recover all my files.....keep trying on different computers if you can, and copy what you can get hold of. The 7-pass erase will delete pretty much every trace of information on the hdd with no chance of recovery.
    So far since the incident its been running ok but I not longer trust the hdd to be stable. Not a simple nor quick process / solution I'm afraid.
    Good luck!
    Once you have recovered your files (or as many as you can get hold of) and ready to erase the hdd:
    (THIS WILL ERASE ALL YOUR DATA, MAKE SURE YOU HAVE A BACKUP BEFORE PROCEEDING)
    Connect the drive directly to the Mac, open Disk Utility.
    Select the drive and click on the "Erase" tab Select the "7-times zeros" to completely erase the drive.
    Once the erase have completed format the drive to your selection.

  • Trace file problem

    I got a tkprof trace file and found the following message at the top of the trace file:
    The following statement encountered a error during parse:
    SELECT INVOICE_ID FROM AP_PAYMENT_SCHEDULES WHERE INVOICE_ID = :b1 FOR UPDATE OF AP_PAYMENT_SCHEDULES NOWAIT
    Error encountered: ORA-00904
    Is this will affect the payment performance?
    Thanks
    Devon

    ORA-00904:     string: invalid identifier
    Cause:     The column name entered is either missing or invalid.
    Action:     Enter a valid column name. A valid column name must begin with a letter, be less than or equal to 30 characters, and consist of only alphanumeric characters and the special characters $, _, and #. If it contains other characters, then it must be enclosed in double quotation marks. It may not be a reserved word.
    This means that you are trying to put some thing which Oracle can't understand. I wouldn't be worried about the performance of the query since it would be a question once the query would run. So check the query why its throwing this error.
    Aman....

  • SQL Query taking longer time as seen from Trace file

    Below Query Execution timings:
    Any help will be benefitial as its affecting business needs.
    SELECT MATERIAL_DETAIL_ID
    FROM
    GME_MATERIAL_DETAILS WHERE BATCH_ID = :B1 FOR UPDATE OF ACTUAL_QTY NOWAIT
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.70 0 0 0 0
    Execute 2256 8100.00 24033.51 627 12298 31739 0
    Fetch 2256 900.00 949.82 0 12187 0 30547
    total 4513 9000.00 24984.03 627 24485 31739 30547
    Thanks and Regards

    Thanks Buddy.
    Data Collected from Trace file:
    SELECT STEP_CLOSE_DATE
    FROM
    GME_BATCH_STEPS WHERE BATCH_ID
    IN (SELECT
    DISTINCT BATCH_ID FROM
    GME_MATERIAL_DETAILS START WITH BATCH_ID = :B2 CONNECT BY PRIOR PHANTOM_ID=BATCH_ID)
    AND NVL(STEP_CLOSE_DATE, :B1) > :B1
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.54 0 0 0 0
    Execute 2256 800.00 1120.32 0 0 0 0
    Fetch 2256 9100.00 13551.45 396 77718 0 0
    total 4513 9900.00 14672.31 396 77718 0 0
    Misses in library cache during parse: 0
    Optimizer goal: CHOOSE
    Parsing user id: 66 (recursive depth: 1)
    Rows Row Source Operation
    0 TABLE ACCESS BY INDEX ROWID GME_BATCH_STEPS
    13160 NESTED LOOPS
    6518 VIEW
    6518 SORT UNIQUE
    53736 CONNECT BY WITH FILTERING
    30547 NESTED LOOPS
    30547 INDEX RANGE SCAN GME_MATERIAL_DETAILS_U1 (object id 146151)
    30547 TABLE ACCESS BY USER ROWID GME_MATERIAL_DETAILS
    23189 NESTED LOOPS
    53736 BUFFER SORT
    53736 CONNECT BY PUMP
    23189 TABLE ACCESS BY INDEX ROWID GME_MATERIAL_DETAILS
    23189 INDEX RANGE SCAN GME_MATERIAL_DETAILS_U1 (object id 146151)
    4386 INDEX RANGE SCAN GME_BATCH_STEPS_U1 (object id 146144)
    In the Package there are lots of SQL Statements using CONNECT BY CLAUSE.
    Does the use of CONNECT BY Clause degrades performance?
    As you can see the Rows Section is 0 but the Query and elapsed time is taking longer
    Regards

  • Lost time in trace file

    There is anonimous block:
    begin
      execute immediate 'alter session set tracefile_identifier = ''TS'''; 
      dbms_monitor.session_trace_enable;
      some_proc(true);
    end;Procedure some_proc consists following code
    loop
      select val into i from a where par = 'Bar';
      if i = 'EXIT' then
        exit;
      end if;
      for cur in (select fld from t order by r) loop
        processing(cur);
      end loop;
    end loop;Tables A and t is very small tables. So table t is empty.
    As you can see, expected than will be works loop and select from very small table.
    I have executed the block, and it works about 477 seconds.
       select value
      2      from v$sesstat s
      3   natural
      4      join v$statname n
      5     where sid = sys_context('USERENV', 'SID')
      6       and name = 'CPU used by this session';
         VALUE
             2
    declare
      2    t date;
      3  begin
      4    execute immediate 'alter session set tracefile_identifier = ''TS''';
      5    dbms_monitor.session_trace_enable;
      6    come_proc(true);
      7  end;
      8  /
    PL/SQL procedure successfully completed.
    Elapsed: 00:07:57.63
       select value
      2      from v$sesstat s
      3   natural
      4      join v$statname n
      5     where sid = sys_context('USERENV', 'SID')
      6       and name = 'CPU used by this session';
         VALUE
         45175But there is some strange moments:
    1. In tkprof report shows only 277.83 sec (whereas statistic "CPU usage" above is different and more appropriate, 451.75 sec.)
    declare
      t date;
    begin
      execute immediate 'alter session set tracefile_identifier = ''TS''';
      dbms_monitor.session_trace_enable;
      some_proc(true);
    end;
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        0      0.00       0.00          0          0          0           0
    Execute      1    260.95     277.83          0         64          0           1
    Fetch        0      0.00       0.00          0          0          0           0
    total        1    260.95     277.83          0         64          0           1
    Misses in library cache during parse: 0
    Misses in library cache during execute: 1
    Optimizer mode: FIRST_ROWS
    Parsing user id: 10757 
    Elapsed times include waiting on following events:
      Event waited on                             Times   Max. Wait  Total Waited
      ----------------------------------------   Waited  ----------  ------------
      SQL*Net message to client                       1        0.00          0.00
      SQL*Net message from client                     1       20.64         20.64
    SELECT VAL
    FROM
    A WHERE PAR = 'BAR'
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        1      0.01       0.00          0          0          0           0
    Execute 1782640     29.01      28.20          0          0          0           0
    Fetch   1782640     32.78      31.77          0    5347922          0     1782640
    total   3565281     61.80      59.97          0    5347922          0     1782640
    Misses in library cache during parse: 1
    Optimizer mode: FIRST_ROWS
    Parsing user id: 43     (recursive depth: 1)
    Rows     Row Source Operation
    1782640  INDEX RANGE SCAN A_UI (cr=5347922 pr=0 pw=0 time=31762812 us)(object id 530778)
    SELECT FLD
    FROM
    T ORDER BY R
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        1      0.01       0.01          0          0          0           0
    Execute 1782639     33.21      31.91          0          0          0           0
    Fetch   1782639     95.52      95.82          0   12478473          0           0
    total   3565279    128.74     127.75          0   12478473          0           0
    Misses in library cache during parse: 1
    Optimizer mode: FIRST_ROWS
    Parsing user id: 43     (recursive depth: 1)
    Rows     Row Source Operation
          0  SORT ORDER BY (cr=12478473 pr=0 pw=0 time=103178656 us)
          0   PARTITION RANGE SINGLE PARTITION: 1 1 (cr=12478473 pr=0 pw=0 time=92028737 us)
          0    TABLE ACCESS FULL T PARTITION: 1 1 (cr=12478473 pr=0 pw=0 time=86376673 us)2. In raw trace very many rows with c=0. And somtimes there is rows with c=1000
    EXEC #9:c=0,e=13,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912283
    FETCH #9:c=0,e=42,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912345
    EXEC #8:c=0,e=12,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912395
    FETCH #8:c=0,e=13,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451912427
    EXEC #9:c=0,e=14,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912475
    FETCH #9:c=0,e=37,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912534
    EXEC #8:c=0,e=11,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912580
    FETCH #8:c=0,e=12,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451912612
    EXEC #9:c=0,e=13,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912659
    FETCH #9:c=0,e=39,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912718
    EXEC #8:c=0,e=16,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912807
    FETCH #8:c=0,e=14,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451912865
    EXEC #9:c=0,e=14,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912916
    FETCH #9:c=0,e=46,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451912982
    EXEC #8:c=0,e=12,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913040
    FETCH #8:c=0,e=13,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451913148
    EXEC #9:c=0,e=14,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913197
    FETCH #9:c=0,e=40,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913256
    EXEC #8:c=0,e=11,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913302
    FETCH #8:c=0,e=12,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451913334
    EXEC #9:c=0,e=14,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913381
    FETCH #9:c=0,e=39,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913440
    EXEC #8:c=0,e=12,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913487
    FETCH #8:c=0,e=19,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451913525
    EXEC #9:c=0,e=18,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913590
    FETCH #9:c=0,e=36,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913661
    EXEC #8:c=10000,e=12,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913710
    FETCH #8:c=0,e=13,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451913742
    EXEC #9:c=0,e=13,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913790
    FETCH #9:c=0,e=37,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913846
    EXEC #8:c=0,e=11,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913893
    FETCH #8:c=0,e=12,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451913924
    EXEC #9:c=0,e=18,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451913996
    FETCH #9:c=0,e=51,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451914077
    EXEC #8:c=0,e=18,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451914149
    FETCH #8:c=0,e=17,p=0,cr=3,cu=0,mis=0,r=1,dep=1,og=2,tim=5857451914207
    EXEC #9:c=0,e=14,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451914284
    FETCH #9:c=0,e=37,p=0,cr=7,cu=0,mis=0,r=0,dep=1,og=2,tim=5857451914347Questions:
    1. How do you think, lost time is time spent
    a. in PLSQL engine during context switch,
    b. or lost time is time spent in SQL processing where CPU time is less than minimum accurancy (0.01s)
    c. or time lost during write in trace file (trace overhead)?
    2. Value c=10000 is accumulated value? I think no, may be I am wrong?
    But if I right, and time of processing was smaller than 0.01s, CPU time in tkprof will equal to zero, right?
    And from this point of view, strange that CPU time and elapsed time is near.
    3. Write in trace file is included into "elapsed time" in tracefile steps, e.g. "execute" and "fetch"?
    In other words I want more deeply understand process of SQL processing and trace.

    What version of Oracle are you using?
    Can you post the entire contents of the trace file?

  • I am not able to see the trace files for SQL query

    Hello, I am using windows vista OS.
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Prod
    PL/SQL Release 10.2.0.3.0 - Production
    CORE 10.2.0.3.0 Production
    TNS for 32-bit Windows: Version 10.2.0.3.0 - Production
    NLSRTL Version 10.2.0.3.0 - Production
    SQL>
    I enabled the trace as below
    alter system set timed_statistics=TRUE
    alter system set sql_trace=TRUE
    After this, I ran sql query from scott as below.
    select count(*) from emp;
    After this, i checked in user dump directory. The trace files are generating... But this sql code is not appearing in the trace files...
    Am i missing anything... Any help is appreciated.
    Thanks

    This may happen when the trace file is not completely closed.You may try again doing like this,
    alter session set sql_trace=true;
    select * from emp;
    alter session set sql_trace=false;After this,disconnect and exit from your session as well. This should close the file completely and you should be able to see your command in it.
    HTH
    Aman....

  • Interpreting Trace File.

    Hi i am using 10.2.0.4.0 version of oracle.
    I am having trace file info as below, for one of the query. So how should i interpret the trace file? What is the issue in the query, and the scope of improvement in the query? please note that , i have removed the query and its plans from the trace file, i have only posted the wait sections.
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        1      0.14       0.13          0          0          1           0
    Execute      1      6.63     162.12      33540      72921        383           0
    Fetch    17272    178.89    1933.95     274835    3147603         20      259063
    total    17274    185.66    2096.21     308375    3220524        404      259063
    Misses in library cache during parse: 1
    Optimizer mode: CHOOSE
    Parsing user id: 36 
    Elapsed times include waiting on following events:
      Event waited on                             Times   Max. Wait  Total Waited
      ----------------------------------------   Waited  ----------  ------------
      control file sequential read                    4        0.00          0.00
      db file sequential read                    302812        0.62       1913.89
      latch: cache buffers chains                     3        0.04          0.04
      direct path write temp                        501        0.01          0.30
      SQL*Net message to client                   17272        0.00          0.04
      db file scattered read                        120        0.02          0.63
      direct path read temp                         608        0.14          1.71
      SQL*Net message from client                 17272       44.81      31865.74
      SQL*Net more data to client                    15        0.00          0.00
      latch: object queue header operation            1        0.00          0.00
      latch: library cache                            3        0.03          0.04
      latch: library cache pin                        1        0.00          0.00
      latch: cache buffer handles                     1        0.00          0.00
    OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        1      0.14       0.13          0          0          1           0
    Execute      1      6.63     162.12      33540      72921        383           0
    Fetch    17272    178.89    1933.95     274835    3147603         20      259063
    total    17274    185.66    2096.21     308375    3220524        404      259063
    Misses in library cache during parse: 1
    Elapsed times include waiting on following events:
      Event waited on                             Times   Max. Wait  Total Waited
      ----------------------------------------   Waited  ----------  ------------
      SQL*Net message to client                   17275        0.00          0.04
      SQL*Net message from client                 17274       75.57      31941.39
      SQL*Net more data from client                   2        0.00          0.01
      db file sequential read                    302812        0.62       1913.89
      control file sequential read                    4        0.00          0.00
      latch: cache buffers chains                     3        0.04          0.04
      direct path write temp                        501        0.01          0.30
      db file scattered read                        120        0.02          0.63
      direct path read temp                         608        0.14          1.71
      SQL*Net more data to client                    15        0.00          0.00
      latch: object queue header operation            1        0.00          0.00
      latch: library cache                            3        0.03          0.04
      latch: library cache pin                        1        0.00          0.00
      latch: cache buffer handles                     1        0.00          0.00
    OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS
    call     count       cpu    elapsed       disk      query    current        rows
    Parse       11      0.02       0.01          0          0          0           0
    Execute    348      0.20       0.17          0          0          1           0
    Fetch      367      0.06       0.37         59       1187          0        3806
    total      726      0.28       0.56         59       1187          1        3806
    Misses in library cache during parse: 11
    Misses in library cache during execute: 10
    Elapsed times include waiting on following events:
      Event waited on                             Times   Max. Wait  Total Waited
      ----------------------------------------   Waited  ----------  ------------
      db file sequential read                        59        0.01          0.32
        1  user  SQL statements in session.
      348  internal SQL statements in session.
      349  SQL statements in session.
    ********************************************************************************

    below is the estimate and actual results.
    | Id  | Operation                              | Name                        | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads  | Writes |  OMem |  1Mem | Us
    ed-Mem | Used-Tmp|
    |*  1 |  COUNT STOPKEY                         |                             |  13475 |        |  13475 |00:01:32.33 |     134K|  11357 |      0 |       |       |
        |         |
    |   2 |   NESTED LOOPS                         |                             |  13475 |      2 |  13475 |00:01:31.66 |     134K|  11357 |      0 |       |       |
        |         |
    |   3 |    NESTED LOOPS                        |                             |  13475 |      1 |  13475 |00:01:29.22 |   94325 |  11357 |      0 |       |       |
        |         |
    |*  4 |     INDEX RANGE SCAN                   |                |  13475 |      1 |  13475 |00:00:26.63 |   40425 |   4014 |      0 |       |       |
        |         |
    |   5 |     TABLE ACCESS BY INDEX ROWID        | |  13475 |      1 |  13475 |00:01:02.46 |   53900 |   7343 |      0 |       |       |
        |         |
    |*  6 |      INDEX RANGE SCAN                  ||  13475 |      1 |  13475 |00:00:16.80 |   40425 |   2056 |      0 |       |       |
        |         |
    |*  7 |    TABLE ACCESS FULL                   | |  13475 |      2 |  13475 |00:00:02.26 |   40425 |      0 |      0 |       |       |
        |         |
    |   8 |  TABLE ACCESS BY INDEX ROWID           ||  94399 |      1 |  94399 |00:06:17.09 |     389K|  32207 |      0 |       |       |
        |         |
    |*  9 |   INDEX UNIQUE SCAN                    | |  94399 |      1 |  94399 |00:02:59.79 |     294K|  15488 |      0 |       |       |
        |         |
    |  10 |  TEMP TABLE TRANSFORMATION             |                             |      1 |        |    170K|00:35:11.08 |    1575K|    195K|   6158 |       |       |
        |         |
    |  11 |   LOAD AS SELECT                       |                             |      1 |        |      1 |00:04:49.06 |   53704 |  28653 |    264 |   525K|   525K|  5
    25K (0)|              |
    |  12 |    PARTITION RANGE ALL                 |                             |      1 |  55430 |  16097 |00:06:26.06 |   53433 |  28651 |      0 |       |       |
        |         |
    |  13 |     PARTITION HASH ALL                 |                             |     54 |  55430 |  16097 |00:09:20.69 |   53433 |  28651 |      0 |       |       |
        |         |
    |* 14 |      TABLE ACCESS BY LOCAL INDEX ROWID | INV                         |    432 |  55430 |  16097 |00:06:11.42 |   53433 |  28651 |      0 |       |       |
        |         |
    |* 15 |       INDEX SKIP SCAN                  | |    432 |    125K|  16097 |00:00:39.90 |    4642 |   4508 |      0 |       |       |
        |         |
    |  16 |   TABLE ACCESS BY INDEX ROWID          | |      1 |      2 |    170K|00:30:21.66 |    1522K|    166K|   5894 |       |       |
        |         |
    |  17 |    NESTED LOOPS                        |                             |      1 |     97 |    276K|34:55:49.92 |    1470K|    150K|   5894 |       |       |
        |         |
    |  18 |     NESTED LOOPS                       |                             |      1 |     55 |    105K|00:22:14.57 |    1128K|    134K|   5894 |       |       |
        |         |
    |  19 |      NESTED LOOPS OUTER                |                             |      1 |     52 |    105K|00:16:32.91 |     694K|    105K|   5894 |       |       |
        |         |
    |* 20 |       HASH JOIN                        |                             |      1 |     52 |    105K|00:16:19.68 |     402K|    102K|   5894 |  9641K|  2205K| 16
    27K (1)|        10240 |
    |  21 |        VIEW                            |                             |      1 |  65234 |    105K|00:16:16.46 |     402K|    101K|   4655 |       |       |
        |         |
    |  22 |         SORT UNIQUE                    |                             |      1 |  65234 |    105K|00:16:16.46 |     402K|    101K|   4655 |  8724K|  1161K| 61
    8K (48)|         9216 |
    |  23 |          UNION-ALL                     |                             |      1 |        |    105K|00:14:59.93 |     402K|  97342 |    252 |       |       |
        |         |
    |  24 |           NESTED LOOPS OUTER           |                             |      1 |  19975 |    105K|00:14:10.24 |     395K|  94655 |      0 |       |       |
        |         |
    |  25 |            NESTED LOOPS                |                             |      1 |  19975 |    105K|00:13:58.47 |     140K|  93616 |      0 |       |       |
        |         |
    |  26 |             VIEW                       |                             |      1 |  55430 |  16097 |00:00:00.43 |     270 |    531 |      0 |       |       |
        |         |
    |  27 |              TABLE ACCESS FULL         | |      1 |  55430 |  16097 |00:00:00.19 |     270 |    531 |      0 |       |       |
        |         |
    |* 28 |             TABLE ACCESS BY INDEX ROWID| |  16097 |      1 |    105K|00:13:59.70 |     140K|  93085 |      0 |       |       |
        |         |
    |* 29 |              INDEX RANGE SCAN          |     |  16097 |     10 |    145K|00:00:40.42 |   32685 |   8237 |      0 |       |       |
        |         |
    |  30 |            TABLE ACCESS BY INDEX ROWID | |    105K|      1 |  84716 |00:00:16.78 |     254K|   1039 |      0 |       |       |
        |         |
    |* 31 |             INDEX UNIQUE SCAN          | |    105K|      1 |  84716 |00:00:13.05 |     169K|    982 |      0 |       |       |
        |         |
    |  32 |           NESTED LOOPS                 |                             |      1 |  45259 |      0 |00:00:17.19 |    7336 |   2687 |    252 |       |       |
        |         |
    |* 33 |            HASH JOIN RIGHT OUTER       |                             |      1 |  45259 |      0 |00:00:17.19 |    7336 |   2687 |    252 |   884K|   884K|  3
    09K (0)|              |
    |  34 |             TABLE ACCESS FULL          | |      1 |   1673 |   1677 |00:00:00.01 |      24 |      8 |      0 |       |       |
        |         |
    |* 35 |             HASH JOIN                  |                             |      1 |  45259 |      0 |00:00:17.13 |    7310 |   2678 |    252 |  3318K|  1235K|  4
    47K (1)|         2048 |
    |* 36 |              TABLE ACCESS FULL         | |      1 |  45259 |  49043 |00:00:07.41 |    7043 |   2170 |      0 |       |       |
        |         |
    |  37 |              VIEW                      |                             |      1 |  55430 |  16097 |00:00:00.14 |     267 |    256 |      0 |       |       |
        |         |
    |  38 |               TABLE ACCESS FULL        ||      1 |  55430 |  16097 |00:00:00.12 |     267 |    256 |      0 |       |       |
        |         |
    |  39 |            TABLE ACCESS BY INDEX ROWID | |      0 |      1 |      0 |00:00:00.01 |       0 |      0 |      0 |       |       |
        |         |
    |* 40 |             INDEX UNIQUE SCAN          | |      0 |      1 |      0 |00:00:00.01 |       0 |      0 |      0 |       |       |
        |         |
    |  41 |        VIEW                            |                             |      1 |  55430 |  16097 |00:00:00.02 |     267 |      0 |      0 |       |       |
        |         |
    |  42 |         TABLE ACCESS FULL              | |      1 |  55430 |  16097 |00:00:00.01 |     267 |      0 |      0 |       |       |
        |         |
    |  43 |       TABLE ACCESS BY INDEX ROWID      | |    105K|      1 |  93385 |00:00:24.90 |     291K|   2104 |      0 |       |       |
        |         |
    |* 44 |        INDEX UNIQUE SCAN               | |    105K|      1 |  93385 |00:00:16.45 |     196K|   1405 |      0 |       |       |
        |         |
    |  45 |      TABLE ACCESS BY INDEX ROWID       | |    105K|      1 |    105K|00:05:49.82 |     434K|  29495 |      0 |       |       |
        |         |
    |* 46 |       INDEX UNIQUE SCAN                ||    105K|      1 |    105K|00:02:54.37 |     328K|  14644 |      0 |       |       |
        |         |
    |* 47 |     INDEX RANGE SCAN                   | |    105K|      2 |    170K|00:03:01.14 |     342K|  15690 |      0 |       |       |
        |         |
    Predicate Information (identified by operation id):
       1 - filter(1>=ROWNUM)
       4 - access("XS"."SITEPK"=:B1)
       6 - access("XS"."VENDORPK"="XB"."VENDORPK")
       7 - filter(("XB"."BUYERCOMPANYPK"="CC"."PARENTCOMPANYPK" OR "XB"."BUYERCOMPANYPK"="CC"."CHILDCOMPANYPK"))
       9 - access("INVOICEPK"=:B1 AND "LINENUM"=:B2)
      14 - filter(("IH"."INVOICEORIGIN"='APP' AND "IH"."PO_PK" IS NULL AND "IH"."ISPOSTED"='Y'))
      15 - access("IH"."PAYPK"=3914297352 AND "IH"."POSTDATE">=1338508800000 AND "IH"."POSTDATE"<1341014400000)
           filter(("IH"."POSTDATE">=1338508800000 AND "IH"."PAYPK"=3914297352 AND "IH"."POSTDATE"<1341014400000))
      20 - access("NEWVIEW"."PRIMARYKEY"="TAB"."INVOICEPK")
      28 - filter(TO_NUMBER("RAT"."AUDITTYPE")<2)
      29 - access("INNERTAB1"."INVOICEPK"="RAT"."INVOICEPK")
           filter("RAT"."INVOICEPK" IS NOT NULL)
      31 - access("RAT"."USERPK"="UR"."USERPK")
      33 - access("RA"."QUEUEPK"="Q"."QUEUEPK")
      35 - access("INNERTAB2"."INVOICEPK"="RA"."INVOICEPK")
      36 - filter(("RA"."INVOICEPK" IS NOT NULL AND "RA"."RECEIVERPK" IS NOT NULL))
      40 - access("RA"."RECEIVERPK"="UR"."USERPK")
      44 - access("TAB"."ENTEREDBY"="UR"."USERPK")
      46 - access("TAB"."INVOICEPK"="ISUM"."INVOICEPK")
      47 - access("IDD"."INVOICEPK"="TAB"."INVOICEPK")
    87 rows selected.
    Elapsed: 00:00:04.10
    SQL>Edited by: 930254 on Aug 7, 2012 9:33 AM

  • About Trace file

    Hi
    Can I create a trace file as my desire name in Udump folder? Because there are so many trc files in my udump folder. If I soft by date also, i can't recognize my trace file which is recently created.
    Please advise...!!
    Regards
    Arpitha

    Hi
    How to see the following output of TKPROF for a query? and also how to see the Wait events info? Please help me?
    My query
    SELECT * FROM emp, dept
    WHERE emp.deptno = dept.deptno;I would like to see the trace file output like this...
    call   count      cpu    elapsed     disk    query current    rows
    Parse     11     0.08      0.18        0       0       0         0
    Execute   11     0.23      0.66        0       3       6         0
    Fetch     35     6.70      6.83      100   12326       2       824
    total     57     7.01      7.67      100   12329       8       826
    Misses in library cache during parse: 0 Wait events info.
    Elapsed times include waiting on following events:
      Event waited on                             Times   Max. Wait  Total Waited
      ----------------------------------------   Waited  ----------  ------------
      db file sequential read                      8084        0.12          5.34
      direct path write                             834        0.00          0.00
      direct path write temp                        834        0.00          0.05
      db file parallel read                           8        1.53          5.51
      db file scattered read                       4180        0.07          1.45
      direct path read                             7082        0.00          0.05
      direct path read temp                        7082        0.00          0.44
      rdbms ipc reply                                20        0.00          0.01
      SQL*Net message to client                       1        0.00          0.00
      SQL*Net message from client                     1        0.00          0.00please help me in this regard..!!

  • How to find db file scatered read in trace file?

    Hi All,
    Was just going through basic concepts...
    1. Created table T1with 1000 rows in LMT of 8k block size.
    2. enabled tracing - alter session set events '10046 trace name context forever, level 12';
    3. performed - select * from T1;
    4. ALTER SYSTEM SET EVENTS '10046 trace name context off';
    Now i didnt found any db file scatered read in trace, as select is opting for full table scan...whats the problem here?
    I found only sql* net messages in trace file.
    -Yasser

    No luck..
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE    10.2.0.4.0      Production
    TNS for Solaris: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    SQL> create table tt1 as select * from dba_objects;
    Table created.
    SQL> alter system flush buffer_cache;
    System altered.
    SQL> ALTER SYSTEM SET EVENTS '10046 trace name context forever, level 12';
    System altered.
    SQL> select * from tt1;
    ------Excluded unwanted output---
    SQL> ALTER SYSTEM SET EVENTS '10046 trace name context off';
    System altered.
    Now content in trace file-
    /usr/local/opt/oracle/admin/mytest/udump/mytest1_ora_7053.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, Real Application Clusters, OLAP, Data Mining
    and Real Application Testing options
    ORACLE_HOME = /usr/local/opt/oracle/product/10.2.0
    System name:    SunOS
    Node name:      xxxxxxx
    Release:        5.10
    Version:        Generic_125100-06
    Machine:        sun4us
    Instance name: mytest1
    Redo thread mounted by this instance: 1
    Oracle process number: 24
    Unix process pid: 7053, image: oracle@xxxxxx (TNS V1-V3)
    *** 2009-10-14 03:39:06.573
    *** ACTION NAME:() 2009-10-14 03:39:06.572
    *** MODULE NAME:(sqlplus@xxxxxx (TNS V1-V3)) 2009-10-14 03:39:06.572
    *** SERVICE NAME:(SYS$USERS) 2009-10-14 03:39:06.572
    *** SESSION ID:(148.71) 2009-10-14 03:39:06.572
    WAIT #1: nam='SQL*Net message to client' ela= 2 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972153430324
    WAIT #1: nam='SQL*Net message from client' ela= 6241448 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159672267
    =====================
    PARSING IN CURSOR #1 len=16 dep=0 uid=0 oct=3 lid=0 tim=13972159673957 hv=2245880055 ad='c952ec28'
    select * from t1
    END OF STMT
    PARSE #1:c=0,e=1550,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=13972159673952
    BINDS #1:
    EXEC #1:c=0,e=59,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=13972159674104
    WAIT #1: nam='SQL*Net message to client' ela= 3 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159674145
    FETCH #1:c=0,e=84,p=0,cr=4,cu=0,mis=0,r=1,dep=0,og=1,tim=13972159674266
    WAIT #1: nam='SQL*Net message from client' ela= 224 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159674531
    WAIT #1: nam='SQL*Net message to client' ela= 0 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159674557
    FETCH #1:c=0,e=29,p=0,cr=1,cu=0,mis=0,r=15,dep=0,og=1,tim=13972159674580
    WAIT #1: nam='SQL*Net message from client' ela= 408 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159675013
    WAIT #1: nam='SQL*Net message to client' ela= 3 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159675167
    FETCH #1:c=0,e=86,p=0,cr=1,cu=0,mis=0,r=15,dep=0,og=1,tim=13972159675198
    WAIT #1: nam='SQL*Net message from client' ela= 427 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159675706
    WAIT #1: nam='SQL*Net message to client' ela= 0 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159675732
    FETCH #1:c=0,e=28,p=0,cr=1,cu=0,mis=0,r=15,dep=0,og=1,tim=13972159675754
    WAIT #1: nam='SQL*Net message from client' ela= 280 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159676056
    WAIT #1: nam='SQL*Net message to client' ela= 1 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=13972159676117
    FETCH #1:c=0,e=44,p=0,cr=1,cu=0,mis=0,r=15,dep=0,og=1,tim=13972159676144
    .................SAME MESSAGES.....................But i did not find any scattered read event.
    Seems like i am missing some thing.
    -Yasser
    Edited by: YasserRACDBA on Oct 15, 2009 12:00 PM
    Edited Node name

Maybe you are looking for