WAIT events in *.trc files

I am seeing the below messages in Oracle trace files in bdump directory and it is keep on appending trace files.
WAIT #0: nam='rdbms ipc message' ela= 2929698 timeout=300 p2=0 p3=0 obj#=-1 tim=2406524259034
WAIT #0: nam='rdbms ipc message' ela= 2929698 timeout=300 p2=0 p3=0 obj#=-1 tim=2406527188804
WAIT #0: nam='rdbms ipc message' ela= 2929700 timeout=300 p2=0 p3=0 obj#=-1 tim=2406530118570
Can somebosy help me to figureout what does it mean?.
Curently database is performing normaly and no erros reported.
Platform is :Oracle 10.2 on AIX 5.3
~Thanks

Here, I see my DBWR process does not have tracing enabled currently :
SQL> !ps -ef |grep dbw
2001      4051     1  0 22:11 ?        00:00:00 asm_dbw0_+ASM
ora10204  4101     1  0 22:12 ?        00:00:00 ora_dbw0_ORT24FS
ora10204  4157  4154  0 22:13 pts/1    00:00:00 /bin/sh -c ps -ef |grep dbw
ora10204  4159  4157  0 22:13 pts/1    00:00:00 grep dbw
SQL> select s.sid, s.serial#, s.sql_trace from v$session s, v$process p
  2  where s.paddr=p.addr
  3  and p.spid=4101;
       SID    SERIAL# SQL_TRAC
       167          1 DISABLEDNow, I enable tracing on DBWR :
SQL> exec dbms_monitor.session_trace_enable(167,1);
PL/SQL procedure successfully completed.
SQL> select s.sid, s.serial#, s.sql_trace from v$session s, v$process p
  2  where s.paddr=p.addr
  3  and p.spid=4101;
       SID    SERIAL# SQL_TRAC
       167          1 ENABLEDI can see a trace file being written to :
ora10204>pwd
/oracle_fs/ora10204/admin/ORT24FS/bdump
ora10204>ls -ltr|tail -3
-rw-r----- 1 ora10204 dba     900 Nov 27 22:12 ort24fs_lgwr_4103.trc
-rw-r----- 1 ora10204 dba 1659410 Nov 27 22:13 alert_ORT24FS.log
-rw-r----- 1 ora10204 dba    6457 Nov 27 22:18 ort24fs_dbw0_4101.trc
ora10204>cat ort24fs_dbw0_4101.trc |head -20
/oracle_fs/ora10204/admin/ORT24FS/bdump/ort24fs_dbw0_4101.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle_fs/ora10204/product/10.2.0.4
System name:    Linux
Node name:      linux64
Release:        2.6.18-53.el5
Version:        #1 SMP Sat Nov 10 19:37:22 EST 2007
Machine:        x86_64
Instance name: ORT24FS
Redo thread mounted by this instance: 1
Oracle process number: 5
Unix process pid: 4101, image: oracle@linux64 (DBW0)
*** 2008-11-27 22:15:20.886
*** SERVICE NAME:(SYS$BACKGROUND) 2008-11-27 22:15:20.866
*** SESSION ID:(167.1) 2008-11-27 22:15:20.866
WAIT #0: nam='rdbms ipc message' ela= 625573 timeout=64 p2=0 p3=0 obj#=-1 tim=1199018868033615
WAIT #0: nam='rdbms ipc message' ela= 2930717 timeout=300 p2=0 p3=0 obj#=-1 tim=1199018870984135
WAIT #0: nam='rdbms ipc message' ela= 2930648 timeout=300 p2=0 p3=0 obj#=-1 tim=1199018873915147
ora10204>I disable tracing :
SQL> exec dbms_monitor.session_trace_disable(167,1);
PL/SQL procedure successfully completed.
SQL> select s.sid, s.serial#, s.sql_trace from v$session s, v$process p
  2  where s.paddr=p.addr
  3  and p.spid=4101;
       SID    SERIAL# SQL_TRAC
       167          1 DISABLED
SQL> and see that the trace file is no longer being updated. (Unfortunately, stopping tracing on a process does NOT write any message like "tracing stopped" to the trace file, you have to watch the trace file or run an "fuser" command on Unix/Linux to see if it is still being wrttien to (on Windows, I guess the file would be locked by the process if tracing hasn't been disabled).
Hemant K Chitale
http://hemantoracledba.blogspot.com

Similar Messages

  • Performance Issue: Wait event "log file sync" and "Execute to Parse %"

    In one of our test environments users are complaining about slow response.
    In statspack report folowing are the top-5 wait events
    Event Waits Time (cs) Wt Time
    log file parallel write 1,046 988 37.71
    log file sync 775 774 29.54
    db file scattered read 4,946 248 9.47
    db file parallel write 66 248 9.47
    control file parallel write 188 152 5.80
    And after runing the same application 4 times, we are geting Execute to Parse % = 0.10. Cursor sharing is forced and query rewrite is enabled
    When I view v$sql, following command is parsed frequently
    EXECUTIONS PARSE_CALLS
    SQL_TEXT
    93380 93380
    select SEQ_ORDO_PRC.nextval from DUAL
    Please suggest what should be the method to troubleshoot this and if I need to check some more information
    Regards,
    Sudhanshu Bhandari

    Well, of course, you probably can't eliminate this sort of thing entirely: a setup such as yours is inevitably a compromise. What you can do is make sure your log buffer is a good size (say 10MB or so); that your redo logs are large (at least 100MB each, and preferably large enough to hold one hour or so of redo produced at the busiest time for your database without filling up); and finally set ARCHIVE_LAG_TARGET to something like 1800 seconds or more to ensure a regular, routine, predictable log switch.
    It won't cure every ill, but that sort of setup often means the redo subsystem ceases to be a regular driver of foreground waits.

  • Wait Events "log file parallel write" / "log file sync" during CREATE INDEX

    Hello guys,
    at my current project i am performing some performance tests for oracle data guard. The question is "How does a LGWR SYNC transfer influences the system performance?"
    To get some performance values, that i can compare i just built up a normal oracle database in the first step.
    Now i am performing different tests like creating "large" indexes, massive parallel inserts/commits, etc. to get the bench mark.
    My database is an oracle 10.2.0.4 with multiplexed redo log files on AIX.
    I am creating an index on a "normal" table .. i execute "dbms_workload_repository.create_snapshot()" before and after the CREATE INDEX to get an equivalent timeframe for the AWR report.
    After the index is built up (round about 9 GB) i perform an awrrpt.sql to get the AWR report.
    And now take a look at these values from the AWR
                                                                       Avg
                                                 %Time  Total Wait    wait     Waits
    Event                                 Waits  -outs    Time (s)    (ms)      /txn
    log file parallel write              10,019     .0         132      13      33.5
    log file sync                           293     .7           4      15       1.0
    ......How can this be possible?
    Regarding to the documentation
    -> log file sync: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3120
    Wait Time: The wait time includes the writing of the log buffer and the post.-> log file parallel write: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3104
    Wait Time: Time it takes for the I/Os to complete. Even though redo records are written in parallel, the parallel write is not complete until the last I/O is on disk.This was also my understanding .. the "log file sync" wait time should be higher than the "log file parallel write" wait time, because of it includes the I/O and the response time to the user session.
    I could accept it, if the values are close to each other (maybe round about 1 second in total) .. but the different between 132 seconds and 4 seconds is too noticeable.
    Is the behavior of the log file sync/write different when performing a DDL like CREATE INDEX (maybe async .. like you can influence it with the initialization parameter COMMIT_WRITE??)?
    Do you have any idea how these values come about?
    Any thoughts/ideas are welcome.
    Thanks and Regards

    Surachart Opun (HunterX) wrote:
    Thank you for Nice Idea.
    In this case, How can we reduce "log file parallel write" and "log file sync" waited time?
    CREATE INDEX with NOLOGGINGA NOLOGGING can help, can't it?Yes - if you create index nologging then you wouldn't be generating that 10GB of redo log, so the waits would disappear.
    Two points on nologging, though:
    <ul>
    it's "only" an index, so you could always rebuild it in the event of media corruption, but if you had lots of indexes created nologging this might cause an unreasonable delay before the system was usable again - so you should decide on a fallback option, such as taking a new backup of the tablespace as soon as all the nologging operatons had completed.
    If the database, or that tablespace, is in +"force logging"+ mode, the nologging will not work.
    </ul>
    Don't get too alarmed by the waits, though. My guess is that the +"log file sync"+ waits are mostly from other sessions, and since there aren't many of them the other sessions are probably not seeing a performance issue. The +"log file parallel write"+ waits are caused by your create index, but they are happeninng to lgwr in the background which is running concurrently with your session - so your session is not (directly) affected by them, so may not be seeing a performance issue.
    The other sessions are seeing relatively high sync times because their log file syncs have to wait for one of the large writes that you have triggered to complete, and then the logwriter includes their (little) writes with your next (large) write.
    There may be a performance impact, though, from the pure volume of I/O. Apart from the I/O to write the index you have LGWR writting (N copies) of the redo for the index and ARCH is reading and writing the completed log files caused by the index build. So the 9GB of index could easily be responsible for vastly more I/O than the initial 9GB.
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk
    To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}{noformat} (lowercase, curly brackets, no spaces) so that the text appears in fixed format.
    "Science is more than a body of knowledge; it is a way of thinking"
    Carl Sagan                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • No wait events info in trace file?

    A very good day to all experts,
    I am tracing a session using the below procedure.
    dbms_system.set_ev(12,13,EV=>10046,LE=>12,NM=>'');
    I am just displaying the following information in trace file.Trace file is not displaying any wait events even when i am doing level 12 tracing.How i can see the wait event information in trace files?
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.00 0 0 0 0
    Execute 1 0.01 0.01 0 0 0 0
    Fetch 2 0.00 0.05 2 2 0 1
    total 4 0.01 0.07 2 2 0 1
    Misses in library cache during parse: 1
    Optimizer mode: CHOOSE
    Parsing user id: 55
    Rows Row Source Operation
    1 TABLE ACCESS BY INDEX ROWID aaa_USERS (cr=2 pr=2 pw=0 time=58806 us)
    1 INDEX UNIQUE SCAN SYS_C004271 (cr=1 pr=1 pw=0 time=42773 us)(object id 47506)
    Thank you....

    Your post is without version information up to 4 digits.
    You post tkprof output.
    Not all version of Oracle have tkprof post wait event info.
    IIRC. this started in Oracle 9iR2.
    You would need to look in the raw trace file to find out whether this information is actually available. You will find it is.
    This could likely being caused by using 8i, which doesn't have this facility.
    But as you don't post a version, your question can not be answered.
    Sybrand Bakker
    Senior Oracle DBA

  • Log file sync wait event advise?

    Due to business needs, Apps has been designed to do every single transaction commit and coming to infrastructure, db Datafiles and redo logs are in faster disk (FC) and archive logs are placed in slower speed disk(SATA). We are seeing the log file sync wait event in the top events and symptoms for this waitevent is either disk speed is slow or doing frequent commit. In my scenario i guess 99% this wait event happening due to frequent commits. Can i assume archive log slower disk will not be root cause for this (my understanding this waitevent occurs on redo log writing area and not in archive log writing area) ? Please confirm.

    user530956 wrote:
    We are seeing the log file sync wait event in the top events and symptoms for this waitevent is either disk speed is slow or doing frequent commit.As Hemant has pointed out, this could also be due to CPU overload.
    I note you say the event is IN the top events - this tells us virtually nothing; an event might be IN the top 5 while being responsible for less than 1% of the total recorded wait time; it could be IN the top 5 but explained as a side effect of something that appeared above it in the Top 5. Why not just show us a typical Top 5 (along with a typical Load Profile it you want to be really helpful).
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk
    To post code, statspack/AWR report, execution plans or trace files from text files, START and END the text with the tag {noformat}{noformat} (the word "code" in lowercase, curly brackets, no spaces) so that the text appears in fixed format. This won't be sufficient if you try to cut and paste from an HTML report, which will need further editing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • How do I the interpret "Disk file operations I/O" wait event?

    I have a large and very busy batch database. All of a sudden the "Disk file operations I/O" wait event is in the top 5 in AWR.
    The manual page isn't very helpful:
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/waitevents003.htm#insertedID40
    Disk file operations I/O
    This event is used to wait for disk file operations (for example, open, close, seek, and resize). It is also used for miscellaneous I/O operations such as block dumps and password file accesses.
    So here is my question: What exactly is going on when I see this wait event? Why doesn't it show up as one of the other I/O events? Can I make it go away? Should I make it go away?
    DR

    sb92075 wrote:
    All of a sudden the "Disk file operations I/O" wait event is in the top 5 in AWR.Top wait event
    In EVERY Top Wait Event list, one wait event will ALWAYS be on top as #1; by definition of the list.
    Simply because any item, even #1, appears on this list does not mean this is a problem & needs to be fixed.
    If the Top Wait Event accounts for only 5 seconds out of a 1 hour sample,
    then reducing it to ZERO won't measurably improve overall application performance.
    The actual Time Waited is required to determine if it is a problem or not.It's taking 20% of time in a 15 minute sample. Anything that takes 20% of deserves to be understood....So: What actually causes it?
    DR

  • Wait events "db file scatter read"

    I have a continuous wait event in my production database...*"db file scatter read"* can any one tell me the reason behind that..

    i want perfect answer not google search..google produce lot of options ..i know that.Where is perfect answer? In documentation, books, expert's blog, forum right? And how to find them, i think from google and/or search in net. Simple to admit, but hard to follow....
    I really appreciate that you are seeking "perfect answer", but i am sure for that you have to use "search tech" as well.
    As Sidhu has already given you the perfect link, Aman has asked you statspack info, now i hope you are addressing your question in a well manner. Let us work on the issue with great experts.
    Regards
    Girish Sharma

  • How to see the wait events info. after excute a select query

    Hi
    How to see the wait events info. after execute a select query. Are there any parameter to set for this option?
    And also wanna see the follwing info. in trace file. For this what are the parameters I have to set right?
    SELECT * FROM emp, dept
    WHERE emp.deptno = dept.deptno;
    call   count      cpu    elapsed     disk    query current    rows
    Parse      1     0.16      0.29         3       13       0       0
    Execute    1     0.00      0.00         0        0       0       0
    Fetch      1     0.03      0.26         2        2       4      14
    Misses in library cache during parse: 1
    Parsing user id: (8) SCOTT Regards
    Arpitha

    $ sqlplus scott/tiger
    SQL*Plus: Release 10.2.0.2.0 - Production on Wed Apr 20 15:29:33 2011
    Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> SHOW PARAMETER dump
    NAME                                 TYPE        VALUE
    background_core_dump                 string      partial
    background_dump_dest                 string      /user/oracle/app/oracle/admin/
                                                     orclsb/bdump
    core_dump_dest                       string      /user/oracle/app/oracle/admin/
                                                     orclsb/cdump
    max_dump_file_size                   string      UNLIMITED
    shadow_core_dump                     string      partial
    user_dump_dest                       string      /user/oracle/app/oracle/admin/
                                                     orclsb/udump
    SQL> ALTER SESSION SET EVENTS='10046 trace name context forever, level 12';
    Session altered.
    SQL> SELECT * FROM emp WHERE deptno=20;
         EMPNO ENAME      JOB              MGR HIREDATE         SAL       COMM
        DEPTNO
          7369 SMITH      CLERK           7902 17-DEC-80        800
            20
          7566 JONES      MANAGER         7839 02-APR-81       2975
            20
          7788 SCOTT      ANALYST         7566 19-APR-87       3000
            20
         EMPNO ENAME      JOB              MGR HIREDATE         SAL       COMM
        DEPTNO
          7876 ADAMS      CLERK           7788 23-MAY-87       1100
            20
          7902 FORD       ANALYST         7566 03-DEC-81       3000
            20Now
    $ pwd
    /user/oracle/app/oracle/admin/orclsb/udump
    $ ls -ltr|tail -5
    -rw-r-----   1 oracle   oinstall     622 Apr 20 11:35 orclsb_ora_949.trc
    -rw-r-----   1 oracle   oinstall     651 Apr 20 11:35 orclsb_ora_976.trc
    -rw-r-----   1 oracle   oinstall    1982 Apr 20 11:35 orclsb_ora_977.trc
    -rw-r-----   1 oracle   oinstall    1443 Apr 20 15:29 orclsb_ora_1251.trc
    -rw-r-----   1 oracle   oinstall  279719 Apr 20 15:30 orclsb_ora_1255.trc
    $ tkprof  orclsb_ora_1255.trc  orclsb_ora_1255.txt
    TKPROF: Release 10.2.0.2.0 - Production on Wed Apr 20 15:32:17 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    $ ls -ltr|tail -5
    -rw-r-----   1 oracle   oinstall     651 Apr 20 11:35 orclsb_ora_976.trc
    -rw-r-----   1 oracle   oinstall    1982 Apr 20 11:35 orclsb_ora_977.trc
    -rw-r-----   1 oracle   oinstall    1443 Apr 20 15:29 orclsb_ora_1251.trc
    -rw-r-----   1 oracle   oinstall  279719 Apr 20 15:30 orclsb_ora_1255.trc
    -rw-r--r--   1 oracle   oinstall   26872 Apr 20 15:32 orclsb_ora_1255.txtThis orclsb_ora_1255.txt contains the required information.

  • What is "KJC: Wait for msg .." wait event in 10g??

    Hi, all.
    The database is 2 node RAC database (10.2.0.2.0)
    on 32-bit windows 2003 EE SP1.
    I found "KJC: Wait for msg sends to complete" wait event in
    "Top 5 Timed Event" Section from AWR report.
    What is "KJC: Wait for msg sends to complete" wait event??
    The following is from UDUMP.
    Dump file d:\oracle\product\10.2.0\admin\rac\udump\rac2_ora_5656.trc
    Mon Sep 24 00:04:40 2007
    ORACLE V10.2.0.2.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
    With the Real Application Clusters, OLAP and Data Mining options
    Windows Server 2003 Version V5.2 Service Pack 1
    CPU : 4 - type 586, 2 Physical Cores
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:5278M/8190M, Ph+PgF:6596M/10041M, VA:316M/2047M
    Instance name: rac2
    Redo thread mounted by this instance: 2
    Oracle process number: 64
    Windows thread id: 5656, image: ORACLE.EXE (SHAD)
    *** 2007-09-24 00:04:40.156
    *** ACTION NAME:() 2007-09-24 00:04:40.156
    *** MODULE NAME:(OEM.SystemPool) 2007-09-24 00:04:40.156
    *** SERVICE NAME:(RAC.world) 2007-09-24 00:04:40.156
    *** CLIENT ID:() 2007-09-24 00:04:40.156
    *** SESSION ID:(486.53) 2007-09-24 00:04:40.156
    IPCSendMsg: could not initiate send on conn 0x5b0d3e98 to node [rac1 : 696 : 3996 : 359937], err 10054
    IPCGetRequestInfo: failed a request rqh(0x5b060db8), type(6), status(2), bytes(0)
    Thanks and Regards.
    Message was edited by:
    user507290
    Message was edited by:
    user507290

    This might have something to do with bug 5075434 - Small performance overhead in RAC (waits for "KJC: Wait for msg sends to complete").
    Check metalink for further details.

  • Tkprof unable to read the .trc file

    hi all,
    i got the dead lock error on one of my TEST databse.
    i want to find out what are the sql queries causing that deadlock error.
    for that purpose i want to analyze the already generated .trc file to get that particular queries.
    for that purpose i used the fallowing commands .
    c:>set oracle_home='e:\ora9i'
    c:>tkprof tracefilename file1.txt print=10 record=deadlocksql.txt
    for the above commands i am getting the fallowing error
    could not open trace file tracefilename(that was generated due to dead lock error)
    please give your valuable comments to make this workable.
    thanks,

    tracefilename is not an option of tkprof. try to remove it from the command line.
    [data/ora/adm/H90UDEMO/udump i05c09 : oracle : H89UCBAC ]> tkprof
    Usage: tkprof tracefile outputfile [explain= ] [table= ]
                  [print= ] [insert= ] [sys= ] [sort= ]
      table=schema.tablename   Use 'schema.tablename' with 'explain=' option.
      explain=user/password    Connect to ORACLE and issue EXPLAIN PLAN.
      print=integer    List only the first 'integer' SQL statements.
      aggregate=yes|no
      insert=filename  List SQL statements and data inside INSERT statements.
      sys=no           TKPROF does not list SQL statements run as user SYS.
      record=filename  Record non-recursive statements found in the trace file.
      waits=yes|no     Record summary for any wait events found in the trace file.
      sort=option      Set of zero or more of the following sort options:
        prscnt  number of times parse was called
        prscpu  cpu time parsing
        prsela  elapsed time parsing
        prsdsk  number of disk reads during parse
        prsqry  number of buffers for consistent read during parse
        prscu   number of buffers for current read during parse
        prsmis  number of misses in library cache during parse
        execnt  number of execute was called
        execpu  cpu time spent executing
        exeela  elapsed time executing
        exedsk  number of disk reads during execute
        exeqry  number of buffers for consistent read during execute
        execu   number of buffers for current read during execute
        exerow  number of rows processed during execute
        exemis  number of library cache misses during execute
        fchcnt  number of times fetch was called
        fchcpu  cpu time spent fetching
        fchela  elapsed time fetching
        fchdsk  number of disk reads during fetch
        fchqry  number of buffers for consistent read during fetch
        fchcu   number of buffers for current read during fetch
        fchrow  number of rows fetched
        userid  userid of user that parsed the cursorNicolas.

  • Need help to analysis "foreground and background wait events" on statspack report for oracle database 11.2.0.4 on AIX

    Hi: I'm analyzing this STATSPACK report: it is "volume test" on our UAT server, so most input is from 'bind variables'.  Our shared pool is well utilized in oracle.  Oracle redo logs is not appropriately configured on this server, as in 'Top 5 wait events' there are 2 for redos.
    I need to know what else information can be dig-out from 'foreground wait events' & 'background wait events', and what can assist us to better understanding, in combination of 'Top 5 wait event's, that how the server/test went?  it could be overwelming No. of wait events, so appreciate any helpful diagnostic or analysis.  Database is oracle 11.2.0.4 upgraded from 11.2.0.3, on IBM AIX power system 64bit, level 6.x
    STATSPACK report for
    Database    DB Id    Instance     Inst Num  Startup Time   Release     RAC
    ~~~~~~~~ ----------- ------------ -------- --------------- ----------- ---
    700000XXX   XXX              1 22-Apr-15 12:12 11.2.0.4.0  NO
    Host Name             Platform                CPUs Cores Sockets   Memory (G)
    ~~~~ ---------------- ---------------------- ----- ----- ------- ------------
         dXXXX_XXX    AIX-Based Systems (64-     2     1       0         16.0
    Snapshot       Snap Id     Snap Time      Sessions Curs/Sess Comment
    ~~~~~~~~    ---------- ------------------ -------- --------- ------------------
    Begin Snap:       5635 22-Apr-15 13:00:02      114       4.6
      End Snap:       5636 22-Apr-15 14:00:01      128       8.8
       Elapsed:      59.98 (mins) Av Act Sess:       0.6
       DB time:      35.98 (mins)      DB CPU:      19.43 (mins)
    Cache Sizes            Begin        End
    ~~~~~~~~~~~       ---------- ----------
        Buffer Cache:     2,064M              Std Block Size:         8K
         Shared Pool:     3,072M                  Log Buffer:    13,632K
    Load Profile              Per Second    Per Transaction    Per Exec    Per Call
    ~~~~~~~~~~~~      ------------------  ----------------- ----------- -----------
          DB time(s):                0.6                0.0        0.00        0.00
           DB CPU(s):                0.3                0.0        0.00        0.00
           Redo size:          458,720.6            8,755.7
       Logical reads:           12,874.2              245.7
       Block changes:            1,356.4               25.9
      Physical reads:                6.6                0.1
    Physical writes:               61.8                1.2
          User calls:            2,033.7               38.8
              Parses:              286.5                5.5
         Hard parses:                0.5                0.0
    W/A MB processed:                1.7                0.0
              Logons:                1.2                0.0
            Executes:              801.1               15.3
           Rollbacks:                6.1                0.1
        Transactions:               52.4
    Instance Efficiency Indicators
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                Buffer Nowait %:  100.00       Redo NoWait %:  100.00
                Buffer  Hit   %:   99.98  Optimal W/A Exec %:  100.00
                Library Hit   %:   99.77        Soft Parse %:   99.82
             Execute to Parse %:   64.24         Latch Hit %:   99.98
    Parse CPU to Parse Elapsd %:   53.15     % Non-Parse CPU:   98.03
    Shared Pool Statistics        Begin   End
                 Memory Usage %:   10.50   12.79
        % SQL with executions>1:   69.98   78.37
      % Memory for SQL w/exec>1:   70.22   81.96
    Top 5 Timed Events                                                    Avg %Total
    ~~~~~~~~~~~~~~~~~~                                                   wait   Call
    Event                                            Waits    Time (s)   (ms)   Time
    CPU time                                                       847          50.2
    enq: TX - row lock contention                    4,480         434     97   25.8
    log file sync                                  284,169         185      1   11.0
    log file parallel write                        299,537         164      1    9.7
    log file sequential read                           698          16     24    1.0
    Host CPU  (CPUs: 2  Cores: 1  Sockets: 0)
    ~~~~~~~~              Load Average
                          Begin     End      User  System    Idle     WIO     WCPU
                           1.16    1.84     19.28   14.51   66.21    1.20   82.01
    Instance CPU
    ~~~~~~~~~~~~                                       % Time (seconds)
                         Host: Total time (s):                  7,193.8
                      Host: Busy CPU time (s):                  2,430.7
                       % of time Host is Busy:      33.8
                 Instance: Total CPU time (s):                  1,203.1
              % of Busy CPU used for Instance:      49.5
            Instance: Total Database time (s):                  2,426.4
      %DB time waiting for CPU (Resource Mgr):       0.0
    Memory Statistics                       Begin          End
    ~~~~~~~~~~~~~~~~~                ------------ ------------
                      Host Mem (MB):     16,384.0     16,384.0
                       SGA use (MB):      7,136.0      7,136.0
                       PGA use (MB):        282.5        361.4
        % Host Mem used for SGA+PGA:         45.3         45.8
    Foreground Wait Events  DB/Inst: XXXXXs  Snaps: 5635-5636
    -> Only events with Total Wait Time (s) >= .001 are shown
    -> ordered by Total Wait Time desc, Waits desc (idle events last)
                                                                 Avg          %Total
                                              %Tim Total Wait   wait    Waits   Call
    Event                               Waits  out   Time (s)   (ms)     /txn   Time
    enq: TX - row lock contentio        4,480    0        434     97      0.0   25.8
    log file sync                     284,167    0        185      1      1.5   11.0
    Disk file operations I/O            8,741    0          4      0      0.0     .2
    direct path write                  13,247    0          3      0      0.1     .2
    db file sequential read             6,058    0          1      0      0.0     .1
    buffer busy waits                   1,800    0          1      1      0.0     .1
    SQL*Net more data to client        29,161    0          1      0      0.2     .1
    direct path read                    7,696    0          1      0      0.0     .0
    db file scattered read                316    0          1      2      0.0     .0
    latch: shared pool                    144    0          0      2      0.0     .0
    CSS initialization                     30    0          0      3      0.0     .0
    cursor: pin S                          10    0          0      9      0.0     .0
    row cache lock                         41    0          0      2      0.0     .0
    latch: row cache objects               19    0          0      3      0.0     .0
    log file switch (private str            8    0          0      7      0.0     .0
    library cache: mutex X                 28    0          0      2      0.0     .0
    latch: cache buffers chains            54    0          0      1      0.0     .0
    latch free                            290    0          0      0      0.0     .0
    control file sequential read        1,568    0          0      0      0.0     .0
    log file switch (checkpoint             4    0          0      6      0.0     .0
    direct path sync                        8    0          0      3      0.0     .0
    latch: redo allocation                 60    0          0      0      0.0     .0
    SQL*Net break/reset to clien           34    0          0      1      0.0     .0
    latch: enqueue hash chains             45    0          0      0      0.0     .0
    latch: cache buffers lru cha            7    0          0      2      0.0     .0
    latch: session allocation               5    0          0      1      0.0     .0
    latch: object queue header o            6    0          0      1      0.0     .0
    ASM file metadata operation            30    0          0      0      0.0     .0
    latch: In memory undo latch            15    0          0      0      0.0     .0
    latch: undo global data                 8    0          0      0      0.0     .0
    SQL*Net message from client     6,362,536    0    278,225     44     33.7
    jobq slave wait                     7,270  100      3,635    500      0.0
    SQL*Net more data from clien        7,976    0         15      2      0.0
    SQL*Net message to client       6,362,544    0          8      0     33.7
    Background Wait Events  DB/Inst: XXXXXs  Snaps: 5635-5636
    -> Only events with Total Wait Time (s) >= .001 are shown
    -> ordered by Total Wait Time desc, Waits desc (idle events last)
                                                                 Avg          %Total
                                              %Tim Total Wait   wait    Waits   Call
    Event                               Waits  out   Time (s)   (ms)     /txn   Time
    log file parallel write           299,537    0        164      1      1.6    9.7
    log file sequential read              698    0         16     24      0.0    1.0
    db file parallel write              9,556    0         13      1      0.1     .8
    os thread startup                     146    0         10     70      0.0     .6
    control file parallel write         2,037    0          2      1      0.0     .1
    Log archive I/O                        35    0          1     30      0.0     .1
    LGWR wait for redo copy             2,447    0          0      0      0.0     .0
    db file async I/O submit            9,556    0          0      0      0.1     .0
    db file sequential read               145    0          0      2      0.0     .0
    Disk file operations I/O              349    0          0      0      0.0     .0
    db file scattered read                 30    0          0      4      0.0     .0
    control file sequential read        5,837    0          0      0      0.0     .0
    ADR block file read                    19    0          0      4      0.0     .0
    ADR block file write                    5    0          0     15      0.0     .0
    direct path write                      14    0          0      2      0.0     .0
    direct path read                        3    0          0      7      0.0     .0
    latch: shared pool                      3    0          0      6      0.0     .0
    log file single write                  56    0          0      0      0.0     .0
    latch: redo allocation                 53    0          0      0      0.0     .0
    latch: active service list              1    0          0      3      0.0     .0
    latch free                             11    0          0      0      0.0     .0
    rdbms ipc message                 314,523    5     57,189    182      1.7
    Space Manager: slave idle wa        4,086   88     18,996   4649      0.0
    DIAG idle wait                      7,185  100      7,186   1000      0.0
    Streams AQ: waiting for time            2   50      4,909 ######      0.0
    Streams AQ: qmn slave idle w          129    0      3,612  28002      0.0
    Streams AQ: qmn coordinator           258   50      3,612  14001      0.0
    smon timer                             43    2      3,605  83839      0.0
    pmon timer                          1,199   99      3,596   2999      0.0
    SQL*Net message from client        17,019    0         31      2      0.1
    SQL*Net message to client          12,762    0          0      0      0.1
    class slave wait                       28    0          0      0      0.0
    thank you very much!

    Hi: just know it now: it is a large amount of 'concurrent transaction' designed in this "Volume Test" - to simulate large incoming transaction volme, so I guess wait in eq:TX - row is expected.
    The fact: (1) redo logs at uat server is known to not well-tune for configurations (2) volume test slow 5%, however data amount in its test is kept the same by each time import  production data, by the team. So why it slowed 5% this year?
    The wait histogram is pasted below, any one interest to take a look?  any ideas?
    Wait Event Histogram  DB/Inst: XXXX/XXXX  Snaps: 5635-5636
    -> Total Waits - units: K is 1000, M is 1000000, G is 1000000000
    -> % of Waits - column heading: <=1s is truly <1024ms, >1s is truly >=1024ms
    -> % of Waits - value: .0 indicates value was <.05%, null is truly 0
    -> Ordered by Event (idle events last)
                               Total ----------------- % of Waits ------------------
    Event                      Waits  <1ms  <2ms  <4ms  <8ms <16ms <32ms  <=1s   >1s
    ADR block file read          19   26.3   5.3  10.5  57.9
    ADR block file write          5                     40.0        60.0
    ADR file lock                 6  100.0
    ARCH wait for archivelog l   14  100.0
    ASM file metadata operatio   30  100.0
    CSS initialization           30              100.0
    Disk file operations I/O   9090   97.2   1.4    .6    .4    .2    .1    .1
    LGWR wait for redo copy    2447   98.5    .5    .4    .2    .2    .2    .1
    Log archive I/O              35   40.0         8.6  25.7   2.9        22.9
    SQL*Net break/reset to cli   34   85.3   8.8         5.9
    SQL*Net more data to clien   29K  99.9    .0    .0    .0          .0    .0
    buffer busy waits          1800   96.8    .7    .7    .6    .3    .4    .5
    control file parallel writ 2037   90.7   5.0   2.1    .8   1.0    .3    .1
    control file sequential re 7405  100.0                      .0
    cursor: pin S                10   10.0                    90.0
    db file async I/O submit   9556   99.9    .0                .0          .0
    db file parallel read         1  100.0
    db file parallel write     9556   62.0  32.4   1.7    .8   1.5   1.3    .1
    db file scattered read      345   72.8   3.8   2.3  11.6   9.0    .6
    db file sequential read    6199   97.2    .2    .3   1.6    .7    .0    .0
    direct path read           7699   99.1    .4    .2    .1    .1    .0
    direct path sync              8   25.0  37.5  12.5  25.0
    direct path write            13K  97.8    .9    .5    .4    .3    .1    .0
    enq: TX - row lock content 4480     .4    .7   1.3   3.0   6.8  12.3  75.4    .1
    latch free                  301   98.3    .3    .7    .7
    latch: In memory undo latc   15   93.3   6.7
    latch: active service list    1              100.0
    latch: cache buffers chain   55   94.5                     3.6   1.8
    latch: cache buffers lru c    9   88.9                    11.1
    latch: call allocation        6  100.0
    latch: checkpoint queue la    3  100.0
    latch: enqueue hash chains   45   97.8                     2.2
    latch: messages               4  100.0
    latch: object queue header    7   85.7        14.3
    latch: redo allocation      113   97.3               1.8    .9
    latch: row cache objects     19   89.5                           5.3   5.3
    latch: session allocation     5   80.0              20.0
    latch: shared pool          147   90.5   1.4   2.7   1.4    .7   1.4   2.0
    latch: undo global data       8  100.0
    library cache: mutex X       28   89.3         3.6         3.6         3.6
    log file parallel write     299K  95.6   2.6   1.0    .4    .3    .2    .0
    log file sequential read    698   29.5    .1               4.6  46.8  18.9
    log file single write        56  100.0
    log file switch (checkpoin    4               25.0  50.0  25.0
    log file switch (private s    8         12.5        37.5  50.0
    log file sync               284K  93.3   3.7   1.4    .7    .5    .3    .1
    os thread startup           146                                      100.0
    row cache lock               41   85.4   9.8               2.4         2.4
    DIAG idle wait             7184                                      100.0
    SQL*Net message from clien 6379K  86.6   5.1   2.9   1.3    .7    .3   2.8    .3
    SQL*Net message to client  6375K 100.0    .0    .0    .0    .0    .0    .0
    Wait Event Histogram  DB/Inst: XXXX/xxxx  Snaps: 5635-5636
    -> Total Waits - units: K is 1000, M is 1000000, G is 1000000000
    -> % of Waits - column heading: <=1s is truly <1024ms, >1s is truly >=1024ms
    -> % of Waits - value: .0 indicates value was <.05%, null is truly 0
    -> Ordered by Event (idle events last)
                               Total ----------------- % of Waits ------------------
    Event                      Waits  <1ms  <2ms  <4ms  <8ms <16ms <32ms  <=1s   >1s
    SQL*Net more data from cli 7976   99.7    .1    .1    .0                      .1
    Space Manager: slave idle  4086     .1    .2    .0    .0    .3         3.2  96.1
    Streams AQ: qmn coordinato  258   49.2                .8                    50.0
    Streams AQ: qmn slave idle  129                                            100.0
    Streams AQ: waiting for ti    2   50.0                                      50.0
    class slave wait             28   92.9   3.6   3.6
    jobq slave wait            7270     .0                               100.0
    pmon timer                 1199                                            100.0
    rdbms ipc message           314K  10.3   7.3  39.7  15.4  10.6   5.3   8.2   3.3
    smon timer                   43                                            100.0

  • Problem identifying db object for "buffer busy waits" event.

    10.2.0.3
    AIX 64
    SELECT username, a.p1text, a.p1, a.p2text, a.p2, a.p3text, a.p3, event FROM v$session a WHERE
    a.status='ACTIVE'
    AND a.event = 'buffer busy waits'
    Query reports about 40 active sessions with this information:
    file# 3746
    block# 2
    class# 13
    select
    owner,
    segment_name,
    segment_type
    from
    dba_extents
    where
    file_id = 3746
    and
    2 between block_id and block_id + blocks -1;
    no rows returned
    SELECT MAX(a.file#) FROM sys.file$ a
    3535
    This was only a temporary situation when after couple of minutes(7) wait event "buffer busy waits" dissapeared completely.
    Any ideas?
    Thank you,
    Daniel.

    http://perfvision.com/papers/06_buffer_cache.ppt
    Slide 80-81 points at increasing the size of the initial and next extent for File Header Block buffer busy waits
    Side 85 points at high extent allocation for File Header Block buffer busy waits
    http://perfvision.com/ftp/hotsos/aas.ppt
    Side 55 points at extent allocation too small/too many extents being allocated for File Header Block buffer busy waits
    A couple hints from the documentation:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/instance_tune.htm
    "To determine the possible causes [of buffer busy waits], first query V$SESSION to identify the value of ROW_WAIT_OBJ# when the session waits for buffer busy waits."
    "To identify the object and object type contended for, query DBA_OBJECTS using the value for ROW_WAIT_OBJ# that is returned from V$SESSION."
    "V$SEGMENT_STATISTICS - This is a user-friendly view of statistic values. In addition to all the columns of V$SEGSTAT, it has information about such things as the segment owner and table space name. It makes the statistics easy to understand, but it is more costly."
    You may want to query DBA_TEMP_FILES for the specific FILE_ID identified by the V$SESSION. Taking a look at V$SEGMENT_STATISTICS might also be helpful.
    Are you using dictionary managed tablespaces, locally managed tablespaces with manual extent size management, ASSM with manual extent size management, or ASSM with automatic extent size management?
    Charles Hooper
    IT Manager/Oracle DBA
    K&M Machine-Fabricating, Inc.

  • Wait events - how to read it

    Hi frnds,
    As, I'm beginner to performance tuning I dont know
    What action do i need to take?
    I mean how to read the output which I given below.
    this is the output suffering buffer busy waits.
    Could anyone please tell me
    CLASS TOTAL_WAITS TOTAL_TIME
    data block 93303 58711
    unused 0 0
    system undo header 12 232
    undo header 7847 6636
    3rd level bmb 0 0
    save undo header 0 0
    bitmap index block 0 0
    file header block 0 0
    free list 0 0
    undo block 68 207
    segment header 422 399
    extent map 0 0
    2nd level bmb 0 0
    system undo block 0 0
    sort block 0 0
    save undo block 0 0
    1st level bmb 1 17
    bitmap block 0 0
    Thanks, Muhammed Thameem. S

    Hello,
    "Buffer busy waits" is contention for a buffer (representing a specific
    version of a database block) within the Buffer Cache. So, in essence
    it is block contention and thus it is most likely something to do with
    the design of the tables and indexes supporting the application. A
    built-in bottleneck. On indexes, it could be the age-old problem of
    insertions into an index on a column with a monotonically-ascending
    data value (i.e. timestamps or sequence numbers) which tends to cause
    contention on the highest leaf node of the index. On tables, it might
    have to do with many concurrent insertions into a table in a
    freelist-managed tablespace where the table has only one freelist. It
    could also be due to a home-grown implementation of sequence-number
    generators (i.e. small table with one row, one column in which contains
    the "last value" of a sequence, etc) which lots of people use to avoid
    not being "portable across databases" which they think means not using
    Oracle sequences (yadda yadda yadda).
    I'd look for any SQL statement in the "SQL sorted by Elapsed Time"
    section of the AWR report which exhibits high elapsed time but
    relatively low CPU time, indicating a lot of wait time. Of course,
    there are something like 800 possible wait events in current releases
    of Oracle, of which "buffer busy waits" is only one, so this is just
    inference and not a direct causal connection to your problem. But,
    once I find such statements I'd check to see if they are
    accessing/manipulating tables within the CUBS_DATA tablespace, and then
    use "select * from table(dbms_xplan.display_awr('sql-id'))" to
    get the execution plan(s), and then look for something ineffective
    within the execution plan. You might find the script "sqlhistory.sql" helpful
    here as well, to get a "historical perspective" on the execution of the
    SQL statements over time, in case the buffer busy waits peaked at some
    point in the past
    Please refer to:
    http://www.pubbs.net/201003/oracle/51925-understanding-awr-buffer-waits.html
    Also
    http://www.remote-dba.net/oracle_10g_tuning/t_buffer_busy_waits.htm
    kind regards
    Mohamed

  • Error shown in t1.trc file

    Hello all,
    i am working on EDI X12 over Internet transaction given in user guide.after completing everything in B2B UI tool on both acme and globalchips servers.i ran deq.bat file on both servers giving s*ubscriber=b2berroruser* and wait=1 in ipdequeue.properties file and there was nothing in t1.trc file generated.so i ran enq_850.bat on acme side and enq_855.bat on globalchips side and on both sides Action=Null.and i got the below message in t1.trc file on acme server.
    so can anyone please suggest what should i do next and what is the actual problem.
    MsgID = C0A8010111EAD13D58B00000DADA4C00-1
    ReplyToMsgID = null
    FromParty = GlobalChips
    ToParty = Acme
    EventName = Exception
    DoctypeName = Exception
    DoctypeRevision = 1.0
    MsgType = 3
    payload length = 8063
    *&lt;Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt;*
    *&lt;correlationId&gt;null&lt;/correlationId&gt;*
    *&lt;b2bMessageId&gt;C0A8010111EAD13D58B00000DADA4C00-1&lt;/b2bMessageId&gt;*
    *&lt;errorCode&gt;AIP-50034&lt;/errorCode&gt;*
    *&lt;errorText&gt;Validation error and cannot create Functional Acknowledgment&lt;/errorText&gt;*
    *&lt;errorDescription&gt;*
    *&lt;![CDATA[Machine Info: (mcity94)*
    *Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.*
    *Error Brief :*
    *5082: XEngine error - Guideline look-up failed.*
    *iAudit Report :*
    *&lt;?xml version="1.0" encoding="UTF-16"?&gt;&lt;AnalyzerResults Guid="{C4E22FFB-856B-4C67-BC08-6383C138EFBD}" InterchangeReceived="1" InterchangeProcessed="1" InterchangeAccepted="0"&gt; &lt;ExecutionDate&gt;Tuesday, January 06, 2009&lt;/ExecutionDate&gt; &lt;ExecutionTime&gt;11:23:24 PM (India Standard Time)&lt;/ExecutionTime&gt; &lt;AnalyzerReturn&gt;Failed&lt;/AnalyzerReturn&gt; &lt;NumberOfErrors&gt;1&lt;/NumberOfErrors&gt; &lt;ErrorByCategory&gt; &lt;Category Name="Rejecting"&gt; &lt;Severity Name="Normal"&gt;1&lt;/Severity&gt; &lt;/Category&gt; &lt;/ErrorByCategory&gt; &lt;Status&gt;Finished&lt;/Status&gt; &lt;DataFile&gt; &lt;FilePath&gt;D:\oracle\OraJ2EE\ip&lt;/FilePath&gt; &lt;FileName/&gt; &lt;LastModified/&gt; &lt;FileSize/&gt; &lt;DataURL&gt;file:\\D:\oracle\OraJ2EE\ip&lt;/DataURL&gt; &lt;/DataFile&gt; &lt;Interchange Guid="{CCCD3245-D8CC-4126-8C87-F1FA258BB076}" InterchangeAckCode="R" FunctionalGroupReceived="1" FunctionalGroupProcessed="1" FunctionalGroupAccepted="0" RError="1" NError="0" OtherWI="0"&gt; &lt;DataXPointer&gt; &lt;StartPos&gt;0&lt;/StartPos&gt; &lt;Size&gt;28433&lt;/Size&gt; &lt;/DataXPointer&gt; &lt;NodeInfo&gt; &lt;Links&gt; &lt;Link Name="InterchangeSenderQual"&gt;ZZ&lt;/Link&gt; &lt;Link Name="InterchangeSenderID"&gt;GlobalChips &lt;/Link&gt; &lt;Link Name="InterchangeReceiverQual"&gt;ZZ&lt;/Link&gt; &lt;Link Name="InterchangeReceiverID"&gt;Acme &lt;/Link&gt; &lt;Link Name="InterchangeControlVersion"&gt;00200&lt;/Link&gt; &lt;Link Name="Standard"&gt;X12&lt;/Link&gt; &lt;/Links&gt; &lt;Properties&gt; &lt;Property Name="InterchangeAuthorizationInfoQual"&gt;00&lt;/Property&gt; &lt;Property Name="InterchangeAuthorizationInfo"&gt; &lt;/Property&gt; &lt;Property Name="InterchangeSecurityInfoQual"&gt;00&lt;/Property&gt; &lt;Property Name="InterchangeSecurityInfo"&gt; &lt;/Property&gt; &lt;Property Name="InterchangeSenderQual"&gt;ZZ&lt;/Property&gt; &lt;Property Name="InterchangeSenderID"&gt;GlobalChips &lt;/Property&gt; &lt;Property Name="InterchangeReceiverQual"&gt;ZZ&lt;/Property&gt; &lt;Property Name="InterchangeReceiverID"&gt;Acme &lt;/Property&gt; &lt;Property Name="InterchangeDate"&gt;090106&lt;/Property&gt; &lt;Property Name="InterchangeTime"&gt;1009&lt;/Property&gt; &lt;Property Name="InterchangeControlStandard_RepeatingSeparator"&gt;U&lt;/Property&gt; &lt;Property Name="InterchangeControlVersion"&gt;00200&lt;/Property&gt; &lt;Property Name="InterchangeControlNumber"&gt;000001005&lt;/Property&gt; &lt;Property Name="InterchangeAckRequested"&gt;0&lt;/Property&gt; &lt;Property Name="InterchangeUsageIndicator"&gt;P&lt;/Property&gt; &lt;Property Name="InterchangeComponentElementSep"&gt;0x2b&lt;/Property&gt; &lt;Property Name="DecimalSeparator"/&gt; &lt;Property Name="ElementDelimiter"&gt;0x7e&lt;/Property&gt; &lt;Property Name="ReleaseCharacter"/&gt; &lt;Property Name="RepeatingSeparator"/&gt; &lt;Property Name="SegmentDelimiter"&gt;0x27&lt;/Property&gt; &lt;Property Name="SubelementDelimiter"&gt;0x2b&lt;/Property&gt; &lt;Property Name="InterchangeChildCount"&gt;1&lt;/Property&gt; &lt;Property Name="InterchangeTrailerControlNumber"&gt;000001005&lt;/Property&gt; &lt;/Properties&gt; &lt;/NodeInfo&gt; &lt;FunctionalGroup Guid="{46DA7B93-2365-4704-8156-A0FF38B242E2}" FunctionalGroupAckCode="R" TransactionSetsIncluded="1" TransactionSetsReceived="1" TransactionSetsProcessed="1" TransactionSetsAccepted="0" RError="0" NError="0" OtherWI="0"&gt; &lt;DataXPointer&gt; &lt;StartPos&gt;106&lt;/StartPos&gt; &lt;Size&gt;28311&lt;/Size&gt; &lt;/DataXPointer&gt; &lt;NodeInfo&gt; &lt;Links&gt; &lt;Link Name="GroupSenderID"&gt;GlobalChips&lt;/Link&gt; &lt;Link Name="GroupReceiverID"&gt;Acme&lt;/Link&gt; &lt;Link Name="GroupVersionNumber"&gt;004010&lt;/Link&gt; &lt;/Links&gt; &lt;Properties&gt; &lt;Property Name="GroupID"&gt;PR&lt;/Property&gt; &lt;Property Name="GroupSenderID"&gt;GlobalChips&lt;/Property&gt; &lt;Property Name="GroupReceiverID"&gt;Acme&lt;/Property&gt; &lt;Property Name="GroupDate"&gt;20090106&lt;/Property&gt; &lt;Property Name="GroupTime"&gt;1009&lt;/Property&gt; &lt;Property Name="GroupControlNumber"&gt;1005&lt;/Property&gt; &lt;Property Name="GroupAgencyCode"&gt;X&lt;/Property&gt; &lt;Property Name="GroupVersionNumber"&gt;004010&lt;/Property&gt; &lt;Property Name="GroupChildCount"&gt;1&lt;/Property&gt; &lt;Property Name="GroupTrailerControlNumber"&gt;1005&lt;/Property&gt; &lt;/Properties&gt; &lt;/NodeInfo&gt; &lt;Transaction Guid="{660C36B3-D2FD-4F7A-AE2A-3CE953611D55}" TransactionAckCode="R" RError="0" NError="0" OtherWI="0"&gt; &lt;DataXPointer&gt; &lt;StartPos&gt;157&lt;/StartPos&gt; &lt;Size&gt;28250&lt;/Size&gt; &lt;/DataXPointer&gt; &lt;NodeInfo&gt; &lt;Links&gt; &lt;Link Name="TransactionID"&gt;855&lt;/Link&gt; &lt;/Links&gt; &lt;Properties&gt; &lt;Property Name="TransactionID"&gt;855&lt;/Property&gt; &lt;Property Name="TransactionControlNumber"&gt;1005&lt;/Property&gt; &lt;Property Name="TransactionImplementationReference"/&gt; &lt;Property Name="TransactionChildCount"&gt;170&lt;/Property&gt; &lt;Property Name="TransactionTrailerControlNumber"&gt;1005&lt;/Property&gt; &lt;/Properties&gt; &lt;/NodeInfo&gt; &lt;/Transaction&gt; &lt;/FunctionalGroup&gt; &lt;InterchangeErrors&gt; &lt;Error ErrorCode="{3F43BFA3-7899-445C-A5B8-867089B8D4B2}" Severity="Normal" Category="Rejecting" Index="1" ID="50820000"&gt; &lt;ErrorBrief&gt;5082: XEngine error - Guideline look-up failed.&lt;/ErrorBrief&gt; &lt;ErrorMsg&gt;Failed guideline look-up.&lt;/ErrorMsg&gt; &lt;ErrorObjectInfo&gt; &lt;Parameter Name="ErrorLevel"&gt;0&lt;/Parameter&gt; &lt;Parameter Name="InterchangeControlVersion"&gt;00200&lt;/Parameter&gt; &lt;Parameter Name="InterchangeReceiverID"&gt;Acme &lt;/Parameter&gt; &lt;Parameter Name="InterchangeReceiverQual"&gt;ZZ&lt;/Parameter&gt; &lt;Parameter Name="InterchangeSenderID"&gt;GlobalChips &lt;/Parameter&gt; &lt;Parameter Name="InterchangeSenderQual"&gt;ZZ&lt;/Parameter&gt; &lt;Parameter Name="Name"&gt;XEngine&lt;/Parameter&gt; &lt;Parameter Name="Standard"&gt;X12&lt;/Parameter&gt; &lt;Parameter Name="_ec_dn_guid_"&gt;{CCCD3245-D8CC-4126-8C87-F1FA258BB076}&lt;/Parameter&gt; &lt;Parameter Name="_ec_index"&gt;0&lt;/Parameter&gt; &lt;Parameter Name="ec_error_scope"&gt;Interchange&lt;/Parameter&gt; &lt;/ErrorObjectInfo&gt; &lt;ErrorDataInfo&gt; &lt;Part1/&gt; &lt;ErrData/&gt; &lt;Part3/&gt; &lt;DataXPointer&gt; &lt;StartPos&gt;0&lt;/StartPos&gt; &lt;Size&gt;0&lt;/Size&gt; &lt;/DataXPointer&gt; &lt;/ErrorDataInfo&gt; &lt;/Error&gt; &lt;/InterchangeErrors&gt; &lt;/Interchange&gt;&lt;/AnalyzerResults&gt; ]]&gt;*
    *&lt;/errorDescription&gt;*
    *&lt;errorSeverity&gt;2&lt;/errorSeverity&gt;*
    *&lt;errorDetails&gt;*
    *&lt;parameter name="InterchangeControlStandard_RepeatingSeparator" value="U"/&gt;*
    *&lt;parameter name="InterchangeTrailerControlNumber" value="000001005"/&gt;*
    *&lt;parameter name="InterchangeChildCount" value="1"/&gt;*
    *&lt;parameter name="InterchangeTime" value="1009"/&gt;*
    *&lt;parameter name="InterchangeUsageIndicator" value="P"/&gt;*
    *&lt;parameter name="ErrorScope" value="Interchange"/&gt;*
    *&lt;parameter name="SubelementDelimiter" value="+"/&gt;*
    *&lt;parameter name="RepeatingSeparator" value=""/&gt;*
    *&lt;parameter name="InterchangeSecurityInfo" value=" "/&gt;*
    *&lt;parameter name="InterchangeReceiverQual" value="ZZ"/&gt;*
    *&lt;parameter name="DecimalSeparator" value=""/&gt;*
    *&lt;parameter name="InterchangeAuthorizationInfoQual" value="00"/&gt;*
    *&lt;parameter name="ElementDelimiter" value="~"/&gt;*
    *&lt;parameter name="InterchangeComponentElementSep" value="+"/&gt;*
    *&lt;parameter name="InterchangeControlVersion" value="00200"/&gt;*
    *&lt;parameter name="InterchangeAckRequested" value="0"/&gt;*
    *&lt;parameter name="InterchangeSenderQual" value="ZZ"/&gt;*
    *&lt;parameter name="InterchangeReceiverID" value="Acme "/&gt;*
    *&lt;parameter name="ReleaseCharacter" value=""/&gt;*
    *&lt;parameter name="InterchangeDate" value="090106"/&gt;*
    *&lt;parameter name="SegmentDelimiter" value="'"/&gt;*
    *&lt;parameter name="InterchangeControlNumber" value="000001005"/&gt;*
    *&lt;parameter name="InterchangeAuthorizationInfo" value=" "/&gt;*
    *&lt;parameter name="InterchangeSenderID" value="GlobalChips "/&gt;*
    *&lt;parameter name="InterchangeSecurityInfoQual" value="00"/&gt;*
    *&lt;/errorDetails&gt;*
    *&lt;/Exception&gt;*
    thanks
    sunny

    Hello Prasanna,
    Thanks for your reply,i have checked the parameters with the document protocol parameters,when i have compared i have noticed that some parameters given in the error are not there in the B2B UI and some parameters present in B2B UI are not shown in error part of t1.trc file i am providing the details below
    Not there in the b2b ui_
    &lt;parameter name="InterchangeTrailerControlNumber" value="000001014"/&gt;
    &lt;parameter name="InterchangeChildCount" value="1"/&gt;
    &lt;parameter name="ErrorScope" value="Interchange"/&gt;
    &lt;parameter name="RepeatingSeparator" value=""/&gt;
    &lt;parameter name="InterchangeAckRequested" value="0"/&gt;
    &lt;parameter name="InterchangeControlNumber" value="000001014"/&gt;
    Not there in the t1.trc file_
    Responsible Agency Code =X
    Replacement Character = 0*7c
    Security Information = " "
    Functional Group Time = system time
    Interchange ecs file = " " Browse
    group ecs file = " " Browse
    ImplementationClass = oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin
    Functional Group Date = system date
    Application Receiver's Code
    Application Sender's Code
    Tag Delimiter = 0*3d
    Having different values in the b2b ui_
    &lt;parameter name="SubelementDelimiter" value="+"/&gt; , value in the b2b ui is 0*2b
    &lt;parameter name="DecimalSeparator" value=""/&gt; , value in b2b ui is 0*2e
    &lt;parameter name="ElementDelimiter" value="~"/&gt; , value in b2b ui is 0*7e
    &lt;parameter name="InterchangeComponentElementSep" value="+"/&gt; , value in b2b ui is 0*2b
    &lt;parameter name="SegmentDelimiter" value=" ' "/&gt; , value in b2b ui is 0*27
    I have changed the values in B2B UI according to the values shown in the trace file,i changed 0*2b to "+" , 0*27 to" ' " , 0 * 7e to "~" and 0*2e to " "
    but it generated another error i.e
    5097: Invalid delimiter settings
    So i have replaced the overridden values with original values except the DecimalSeparator and restared the whole B2B instance and ran the bat files but the result is still the same it is showing the old error again i.e
    5082: XEngine error - Guideline look-up failed.
    So can anyone please suggest me a solution for this problem as it is very urgent and if this error is resolved then i can successfully finish all the remaining scenarios as the same error is persisting in the EDI EDIFACT scenario as well
    Thanx
    Sunny

  • Wait events 'direct path write'  and 'direct path read'

    Hi,
    We have a query which is taking more that 2 min. It's a 9.2.0.7 database. We took the trace/tkprof of the query,and identified that there are so manay 'direct path write' and 'direct path read' wait events in the trace file.
    WAIT #3: nam='direct path write' ela= 5 p1=201 p2=70710 p3=15
    WAIT #3: nam='direct path read' ela= 170 p1=201 p2=71719 p3=15
    In the above, "p1=201" is a file_id, but we could not find any data file, temp file, control file with that id# 201.
    Can you please let us know what's "p1=201" here, how to identify the file which is causing the issue.
    Thanks
    Sravan

    What does:
    show parameter db_filesreturn? My guess, is that it returns 200.
    The direct file read and direct file write events are reads and writes to TEMP tablespace. In those wait events, the file# is reported as db_files+temp file id. So, 201 means temp file #1.
    Now, as to your actual performance problem.
    Without seeing the SQL and the corresponding execution plan, it's impossible to be sure. However, the most common causes of temp writes are sort operations and group by operations.
    If you decide to post your SQL and execution plan, please be sure to make it readable by formatting it. Information on how to do so can be found here.
    Hope that helps,
    -Mark
    Edited by: mbobak on May 1, 2011 1:50 AM

Maybe you are looking for

  • How to get the recipient and Note for recipient in Medium 7 Simple Mail?

    Dear friends, I'm trying to send the shipment in the form of PDF attachment to the assigned user. I'm wondering how can I get the receiver and the note(which should be the content of the email) which can be configured in the "Communication Method"? T

  • Custom Master Page for Cases in eDiscovery

    We are creating eDicovery site using custom site template. Site gets created using custom master page that we have set. Now, there are two option to create New Case. #1. Use "Create New Case" button on Right Top Corner on home page #2. OR Go to cases

  • Why doesn't adobe reader print

    Adobe Reader has stopped printing for me. I don't recall when the problem started, but until recently I could print easily. Now, every time I try to print any PDF file (old or new, including files I've printed before), I get his message: "The documen

  • Avoid Duplicate IDOC :

    Hi All, I need to code for avoid duplicate IDOC when my program convert one idoc to another IDOC. The Code is written below..   LOOP  AT  t_seldoc.     SELECT SINGLE * FROM  edidc           WHERE docnum  EQ t_seldoc-idoc.     REFRESH: t_idocst,      

  • Premiere pro will not import .mov files

    Premiere pro CS3 running on Vista 64 bit will not import .mov files. After Effects CS4 has the same problem, it says I don't have the correct version of Quick Time installed. I'm using the 64 bit version 7.6.4 for Vista. Any help would be appreciated