About single-task message wait event

Hello
I have several active users, some of them from 2 an 3 days ago with single-task message wait event and their last_call was many time ago. One of users, blocked to other users just a little while ago and Concurrency grow up to 20 % and was on increase. i had to kill this user and all were well, concurrency dessapeared.
How could I avoid this behavior??
How could I kill these type of user by automatic way??
Thanks

Hi,
according to me active user is different
according to me active user is session or oracle process is doing something else like dml or ddl execution or select stmt else session is idel.
trace the session what is doing? is may be problem with dead connection
use oradebug and set the 10046 at level 12 and format it with tkprof utility.
paste it thread
Kind Regards,
Rakesh jayappa

Similar Messages

  • Single-Task Message Wait Event

    Discovered while researching some performance issues....
    A statspack report on the metadata repository is showing a lot of single-task message waits.
    Is this normal? What is the source of these waits?
    Per Oracle 8i documentation... "Oracle is diminishing the support of single-task mode."
    Why is this showing up in a 9.2.0.8 database???
    Any insights welcome...
    Thanks,
    Henry
    Edited by: OracleDBAinPA on Dec 8, 2009 6:56 AM

    As you can see, no one replied to the message...
    But, our performance issue was due to a memory leak in the listener (documented bug in 9.2.0.8).
    Restarting the listener, also reduced the wait...

  • Single-task message wating for 30 seconds

    Hi guys,
    I encountered some production issues: in some moments some random sql are taking a lot of time to excute.
    I enabled the sql_trace on the system and managed to catch an sql that raises issues. this is the trace parsed with tk prof:
    SELECT NVL(RUNNING_TOTALS_AMOUNT, 0)
    FROM
    ACT_TOTALS_TO_DATE WHERE ACCOUNT_NO = :B1
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        1      0.00      29.35          0          0          1           0
    Execute      2      0.00       0.00          0          0          1           0
    Fetch        2      0.00       0.00          0          4          0           0
    total        5      0.00      29.35          0          4          2           0
    Misses in library cache during parse: 0
    Optimizer mode: RULE
    Parsing user id: 158     (recursive depth: 2)
    Rows     Row Source Operation
          0  SORT GROUP BY (cr=4 pr=0 pw=0 time=62 us)
          0   MERGE JOIN OUTER (cr=4 pr=0 pw=0 time=38 us)
          0    TABLE ACCESS BY INDEX ROWID ACT_TOTALS_TO_DATE_MRC (cr=4 pr=0 pw=0 time=33 us)
          0     INDEX UNIQUE SCAN IDX_ATTDM_ACC_NO (cr=4 pr=0 pw=0 time=29 us)(object id 233866)
          0    REMOTE  ACT_TOTALS_TO_DATE_CALLS (cr=0 pr=0 pw=0 time=0 us)
    Elapsed times include waiting on following events:
      Event waited on                             Times   Max. Wait  Total Waited
      ----------------------------------------   Waited  ----------  ------------
      single-task message                             1       29.34         29.34
      SQL*Net message to dblink                       9        0.00          0.00
      SQL*Net message from dblink                     9        0.00          0.00
    ********************************************************************************usually this SQLs executes very good. the execution plan is what I expect. if I execute it on that machine it works fine.
    this SQL is executed by a pl/sql procedure. it ussualy works fine, but at that moment the entire procedure took around 30 seconds.
    ACT_TOTALS_TO_DATE is a view that uses table from another instance. the view uses db links.
    this problem appears on random SQLs and the parse time is huge.
    can you please tell me what is this wait?:
      Event waited on                             Times   Max. Wait  Total Waited
      ----------------------------------------   Waited  ----------  ------------
      single-task message                             1       29.34         29.34this is the wait line from raw trace file:
    WAIT #18: nam='single-task message' ela= 29347212 p1=0 p2=0 p3=0 obj#=-1 tim=1272918022974421
    I can admit that our code is not well build and it is not using BIND very good. I encountered a lot of hard parses and with this I have latches on shared pool.
    but can this explain this behavior?
    Thanks for your time.
    Edited by: alinux on Apr 22, 2011 6:03 PM

    Guys,
    how can a SQL wait 30 seconds in PARSE phase of its execution for:
    'single-task message' wait?
    or
    In my trace file I have other SQL that have long parsing time but no wait related to these:
    SELECT y, aG,b
    FROM
    xxx WHERE CONTRACT_ID = :B1
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        1      5.14       5.02          0          0          0           0
    Execute      2      1.41       1.37          0          0          0           0
    Fetch        2      0.00       0.00          0          6          0           2
    total        5      6.55       6.40          0          6          0           2
    Misses in library cache during parse: 0
    Optimizer mode: RULE
    Parsing user id: 158     (recursive depth: 2)
    Rows     Row Source Operation
          2  TABLE ACCESS BY INDEX ROWID xxx (cr=6 pr=0 pw=0 time=109 us)
          2   INDEX UNIQUE SCAN yyy (cr=4 pr=0 pw=0 time=63 us)(object id 234057)
    ********************************************************************************Thanks a lot
    Edited by: alinux on Apr 29, 2011 5:51 PM

  • Rdbms ipc message wait event

    When there is archiving done to the recovery area, there is "rdbms ipc message" wait event spike.
    What to conclude from it?
    Wait Class      Wait Event     P1 Text     P1     P2 Text     P2     P3 Text     P3     Wait Time (ms)
    System I/O     log file parallel write     files     2     blocks     4096     requests     2     10
    Idle     rdbms ipc message     timeout     150          0          0     90
    System I/O     log file parallel write     files     2     blocks     4096     requests     2     10
    Idle     rdbms ipc message     timeout     161          0          0     100
    System I/O     log file parallel write     files     2     blocks     4096     requests     2     10
    Idle     rdbms ipc message     timeout     181          0          0     190
    System I/O     log file parallel write     files     2     blocks     4096     requests     4     10
    Idle     rdbms ipc message     timeout     191          0          0     90
    System I/O     log file parallel write     files     2     blocks     4096     requests     2     10
    Idle     rdbms ipc message     timeout     201          0          0     90
    Thanks

    You can use the following details
    Wait Class      Wait Event               P1 Text          P1     P2     Wait Time(ms)
    System I/O     log file parallel write          files          2     4096     10
    Idle          rdbms ipc message          timeout          150     0     90
    System I/O     log file parallel write          files          2     4096     10
    Idle          rdbms ipc message          timeout          161     0     100
    System I/O     log file parallel write          files          2     4096     10
    Idle          rdbms ipc message          timeout          181     0     190
    System I/O     log file parallel write          files          2     4096     10
    Idle          rdbms ipc message          timeout          191     0     90
    System I/O     log file parallel write          files          2     4096     10
    Idle          rdbms ipc message          timeout          201     0 90

  • What is "reliable message" wait event in 10g??

    Hi, all.
    The database is 2 node RAC 10.2.0.2.0 on 32-bit windows 2003 EE SP1.
    From time to time, I see "reliable message" wait event on the
    "Top 5 Timed Events" section from AWR report.
    The wait class is "Other".
    There seems to be no manuals and html links explaining "reliable message"
    wait event.
    Thanks and Regards.
    Message was edited by:
    user507290
    Message was edited by:
    user507290

    Metalink Doc 461052.1 is a fairly lightweight walk-through of a system resource profiling tool called LTOM, the "Lite Onboard Monitor". It has an appendix in which it simply points out "The following events were considered idle and ignored... reliable message..."
    It also says that if you want to include something for wait analysis, just take it out of the list of idle and ignored events... so it's not exactly saying that the thing is an idle event, just that it was treated as such for the purposes of writing that document but that you might think differently.
    On the other hand, this page:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm
    ...is 10g Release 2's description of "wait events of greatest interest"... and "reliable message" isn't on it! From which one concludes, I suppose, that it isn't of great interest!

  • What is "reliable message" wait event?

    Hi, all.
    What is "reliable message" wait event?
    The wait class is "Other", not "Idle".
    From time to time, I can see "reliable message" wait event
    in the Top 5 Timed Events section from AWR reports.
    In addition, what is "CPU time" in the Top 5 Timed Events section?
    Thanks and Regards.
    Message was edited by:
    user507290

    Dear Yas.
    Thanks for your reply.
    The database is 2 node RAC database (10.2.0.2.0) on 32 bit windows 2003 EE SP1.
    Does "AQ" mean Streams AQ???
    Can I disable Streams AQ facility??
    Thanks and Regards.
    Message was edited by:
    user507290
    Message was edited by:
    user507290

  • My wait events - can anyone see a problem?

    hi,
    this is what i have, can anyone see a problem?
    thanks
    EVENT                               TOTAL_WAITS  PCT_WAITS TIME_WAIT_SEC PCT_TIME_WAITED TOTAL_TIMEOUTS PCT_TIMEOUTS AVERAGE_WAIT_SEC
    Streams AQ: qmn slave idle wait          148147         .3    4051461.88           38.04           3478          .07            27.35
    Streams AQ: qmn coordinator idle wa      291006        .59    3962890.53           37.21         148370         3.13            13.62
    it
    Streams AQ: waiting for time manage         948          0     2021434.2           18.98            948          .02          2132.31
    ment or cleanup tasks
    control file parallel write             1292057       2.64     266839.64            2.51              0            0              .21
    log file parallel write                28433394      58.02     134658.55            1.26              0            0                0
    db file sequential read                 8307195      16.95      69830.07             .66              0            0              .01
    free buffer waits                       3117839       6.36      43374.04             .41        3106093        65.55              .01
    log buffer space                          55520        .11       20810.2              .2          20235          .43              .37
    db file scattered read                   583604       1.19      18169.58             .17              0            0              .03
    write complete waits                      17946        .04      17536.66             .16          17941          .38              .98
    log file sync                            282268        .58      10005.35             .09           9369           .2              .04
    enq: RO - fast object reuse               26602        .05       6623.44             .06           2171          .05              .25
    enq: CF - contention                       1839          0       5178.14             .05           1723          .04             2.82
    Streams AQ: qmn coordinator waiting         999          0       4311.01             .04            883          .02             4.32
    for slave to start
    buffer busy waits                         32464        .07       3898.51             .04           3950          .08              .12
    control file sequential read            2199199       4.49       3558.34             .03              0            0                0
    SGA: MMAN sleep for component shrin      234330        .48       2523.65             .02         234216         4.94              .01
    k
    buffer exterminate                         1583          0       1539.72             .01           1573          .03              .97
    library cache pin                           317          0        927.71             .01            316          .01             2.93
    enq: CI - contention                       1829          0        570.84             .01            159            0              .31
    log file switch completion                 1658          0        517.18               0            425          .01              .31
    enq: TX - row lock contention               257          0         438.8               0            149            0             1.71
    read by other session                     27269        .06        355.17               0             52            0              .01
    os thread startup                          3869        .01        338.67               0             98            0              .09
    latch: shared pool                          760          0        285.87               0              0            0              .38
    latch: row cache objects                    664          0           250               0              0            0              .38
    Data file init write                      16324        .03        231.59               0              0            0              .01
    reliable message                          19189        .04        218.16               0            170            0              .01
    latch: library cache                        483          0        172.51               0              0            0              .36
    SQL*Net message from dblink             1143086       2.33        128.69               0              0            0                0
    latch free                                 6091        .01         121.1               0              0            0              .02
    library cache load lock                      90          0         89.48               0             18            0              .99
    log file single write                      1894          0         69.76               0              0            0              .04
    cursor: pin S wait on X                    5183        .01         55.87               0           5165          .11              .01
    local write wait                           6732        .01         42.58               0              2            0              .01
    log file switch (checkpoint incompl          95          0         42.11               0             30            0              .44
    ete)
    row cache lock                              119          0         30.96               0             10            0              .26
    SQL*Net more data from dblink             17198        .04         25.92               0              0            0                0
    log file switch (private strand flu          69          0         17.54               0              5            0              .25
    sh incomplete)
    enq: HW - contention                        180          0         16.53               0              5            0              .09
    enq: PR - contention                          9          0          14.5               0              2            0             1.61
    enq: JS - queue lock                         51          0         12.36               0              0            0              .24
    SQL*Net more data to client               48311         .1         11.66               0              0            0                0
    enq: TM - contention                         12          0         10.66               0              3            0              .89
    class slave wait                           3128        .01          7.03               0              1            0                0
    JS coord start wait                          68          0          6.42               0             68            0              .09
    direct path write                         92712        .19          6.06               0              0            0                0
    control file heartbeat                        1          0          3.91               0              1            0             3.91
    PX Deq: Par Recov Execute                   100          0           3.8               0              0            0              .04
    log file sequential read                   1900          0          2.88               0              0            0                0
    single-task message                          50          0          2.61               0              0            0              .05
    enq: TX - contention                         11          0          2.38               0              0            0              .22
    undo segment extension                  1181001       2.41          1.95               0        1180981        24.92                0
    db file single write                        165          0           1.3               0              0            0              .01
    enq: TX - index contention                   97          0          1.27               0              0            0              .01
    LGWR wait for redo copy                   20840        .04           .66               0              0            0                0
    JS kgl get object wait                        8          0           .63               0              8            0              .08
    SQL*Net message to dblink               1143086       2.33           .55               0              0            0                0
    kksfbc child completion                      14          0           .55               0             11            0              .04
    direct path read temp                    217237        .44           .41               0              0            0                0
    latch: cache buffers chains                2138          0           .37               0              0            0                0
    latch: messages                            1245          0           .27               0              0            0                0
    latch: redo writing                         786          0           .15               0              0            0                0
    PX Deq: Par Recov Reply                      65          0           .09               0              0            0                0
    latch: checkpoint queue latch               171          0           .09               0              0            0                0
    latch: redo allocation                     1029          0           .08               0              0            0                0
    latch: cache buffers lru chain              268          0           .07               0              0            0                0
    SGA: allocation forcing component g           5          0           .05               0              2            0              .01
    rowth
    db file parallel read                        83          0           .04               0              0            0                0
    latch: In memory undo latch                 558          0           .04               0              0            0                0
    latch: object queue header operatio         338          0           .04               0              0            0                0
    n
    direct path read                           5042        .01           .03               0              0            0                0
    PX Deque wait                                 7          0           .02               0              0            0                0
    direct path write temp                     4691        .01           .02               0              0            0                0
    enq: SQ - contention                          1          0           .02               0              0            0              .02
    latch: session allocation                   190          0           .02               0              0            0                0
    PX Deq: Join ACK                             15          0           .01               0              0            0                0
    cursor: pin S                               894          0           .01               0              0            0                0
    enq: TX - allocate ITL entry                 37          0           .01               0              0            0                0
    kkdlgon                                      15          0           .01               0              0            0                0
    latch: enqueue hash chains                   37          0           .01               0              0            0                0
    library cache lock                            1          0           .01               0              0            0              .01
    Log archive I/O                               1          0             0               0              0            0                0
    PX Deq: Par Recov Change Vector               2          0             0               0              0            0                0
    PX Deq: Signal ACK                            3          0             0               0              0            0                0
    PX Deq: Test for msg                          1          0             0               0              0            0                0
    PX qref latch                                 1          0             0               0              1            0                0
    SQL*Net break/reset to dblink                 5          0             0               0              0            0                0
    SQL*Net more data to dblink                   1          0             0               0              0            0                0
    buffer deadlock                              27          0             0               0             27            0                0
    checkpoint completed                          4          0             0               0              0            0                0
    cursor: mutex S                               3          0             0               0              0            0                0
    cursor: mutex X                               1          0             0               0              0            0                0
    enq: JS - q mem clnup lck                     1          0             0               0              0            0                0
    enq: PS - contention                          2          0             0               0              0            0                0
    enq: US - contention                          1          0             0               0              0            0                0
    instance state change                         2          0             0               0              0            0                0
    latch: library cache lock                     4          0             0               0              0            0                0
    latch: library cache pin                      1          0             0               0              0            0                0
    latch: object queue header heap               8          0             0               0              0            0                0
    latch: undo global data                       3          0             0               0              0            0                0
    recovery read                                39          0             0               0              0            0                0

    Hi,
    If its for a week than I won't bother. Probably you should try to get teh same report for these wait events in a much smaller period , like 20-30minutes of time period when your db is fully operational. If still at that time the wait events,these or any other, shoot up to high wait times, things can be investigated more deeply.
    HTH
    Aman....

  • Waiting event when execute my jdbc queries

    I write a simple multithread jdbc programme to connect to oracle, execute 10 time "select * from mytable" , when I start 2 threads, the time each thread use to complete queries is 9 second. when i start 3 threads, it become extremly slow.
    I notice there are serveral waiting event: resmgr:waiting in end wait, resmgr:waiting in actses run, and single-task message , they are waiting for as long as 4 seconds. they after my programm finished,
    could anyone tell me what are these event? do they affect the performance of my oracle?

    I write a simple multithread jdbc programme to connect to oracle, execute 10 time "select * from mytable" , when I start 2 threads, the time each thread use to complete queries is 9 second. when i start 3 threads, it become extremly slow.
    I notice there are serveral waiting event: resmgr:waiting in end wait, resmgr:waiting in actses run, and single-task message , they are waiting for as long as 4 seconds. they after my programm finished,
    could anyone tell me what are these event? do they affect the performance of my oracle? These wait events are associated with the Resource Manager which handles the Consumer Groups. Try changing your consumer group are shutting the Resource Manager off with
    alter system set resource_manager_plan='';
    then test your queries again.

  • Access method and wait event

    hi,
    i am confused about access method and wait event.
    is there any relation between access method and wait event?

    sb92075 wrote:
    is there any relation between access method and wait event?No relationI disagree. If access method is full table scan or fast full index scan, that's likely to cause db file scattered read waits, whereas an index driven access method such as index range scan will likely cause db file sequential read waits.
    -Mark

  • Question on Message Throw Event or Send Task

    Team,
    I saw a new BPM forum on our HPS Dev Site, I posted this question there so that we can discuss /answer/solve issues there.
    I am currently facing some issues in using Message throw event or Send task in my prototype model i am working on.
    References i used :
    Modeling and Implementation Guide for Oracle Business Section 19
    Platform:
    Orable BPM 11g/jdeveloper
    What i am trying to do here is i am trying to communicate with other BPMN processes. I saw from our Model guide we can either use Message Throw event or send and receive tasks to achieve this. But i see Message throw event can be used to invoke a synchronous or asynchronous BPMN process only through and interface like webservices. In my case , i want to just to start another task flow from another process. Can we use this without using webservices When i try to use Send Task to invoke another process i am not able to see the process name listed when i selected the properties , implementation tab.
    It would be great if anyone has any idea of ow to call or start another process from some other process.
    Thanks
    Sarath Surya

    your SSIS package will have following flow
    1. Create a Execute SQL Task which will have the below query
    SELECT EmailAddress
    FROM Table2 t
    WHERE EXISTS (
    SELECT 1
    FROM table1
    WHERE ID = t.ID
    AND (TotalCount < Min
    OR TotalCount > Max)
    Use Resultset option as Full resultset and map the resultset EmailAddress to a object variable (@[User::EmailAddressList]) created in SSIS
    2. Use a ForEach Loop with ADO enumerator which points to above variable
    Inside a loop add a variable [@User::EMailAddress]) to get iterated values
    3. Add a Sent Mail task inside loop and set an expression for ToLine property to point to the variable [@User::EMailAddress] so that it sents email to email address specified.
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • About wait events of awr

    is there anyone who can helip to advise me the meaning of
    1.SQL*Net break/reset to client
    2. Streams AQ: waiting for messages in the queue
    3. wait for unread message on broadcast channel
    we are processing a performence test , tks for your kind advise

    You can ignore these events as they are IDLE events, not WAIT events. In short, they mean user is connected but is not doing anything.

  • A clarification about block# wait event parameter ....

    Hi ,
    In Oracle Database Reference of 10g (Part Number B14237-02) about the block# wait event parameter is pointed out ... :
    This is the block number of the block for which Oracle needs to wait. The block number is relative to the start of the file. To find the object to which this block belongs, enter the following SQL statements:
    select name, kind
    from ext_to_obj_view
    where file# = file#
         and lowb <= block#
         and highb >= block#;Can you give me a simple example of using the above sql statement.... as ext_to_obj_view object does not exist.....
    Many thanks ,
    Simon

    This view is created by $ORACLE_HOME/rdbms/admin/catclust.sql script (to be run by sys user).
    http://download-uk.oracle.com/docs/cd/B19306_01/rac.102/b14197/monitor.htm#RACAD718
    Nicolas.

  • "lms flush message acks" wait event

    Dear All,
    We are load testing our application in 10.2.0.1 database with 2 node RAC, in the AWR report top 5 wait event, we are getting "lms flush message acks" 90%.
    I did search in google and metalink, but i could not able to find any related notes.
    Please help..
    Thanks,
    Anand.

    [email protected] wrote:
    We are load testing our application in 10.2.0.1 database with 2 node RAC, in the AWR report top 5 wait event, we are getting "lms flush message acks" 90%.
    Something is waiting for the "other" node to acknowledge a "flush" message - so you need to look at the other node to see if you can see anything that might cause the flush message to see a slow response.
    Of course, there may be congestion on the interconnect - but then various other RAC communications would also be slow - so it's more likely that the "flushing" is slow.
    Reasons for flushing - we are telling the other node to clear part of its buffer cache, this might be related to frequent truncate commands (as the top of a shortlist). If you truncate an object, any dirty blocks for that object have to be written to disc, and any clean blocks have to be flushed from the cache; in a RAC environment the other nodes have to be told to do the same and your session has to wait for them to complete the write and flush.
    In your case, you might check the code for frequency truncates - and check to see if you can see evidence for frequent slow write from dbwr (and also from lgwr) on the remote node.
    Since you're running an early version of 10.2, I think problems of this type can even be related to truncates on global temporary tables due to some bugs that weren't fixed until 10.2.0.3. (And I think there were some problems with dynamic remastering in that version too, which caused similar flushing issues).
    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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Find the Wait events for an objects.

    Hi Gurus.
    I need you help to find out the wait events for a particular table and index when batch export job running from the application. I have done some work around to to find out, but i am not able to figure out the issue or what are the wait events. i am working on linux 4node rac 11gR2.
    Below are the steps i have done.
    1. find object_id for a table finding the wait events to that object_id.
    SYS@ccmintpt1 SQL>select data_object_id from dba_objects where object_name='ACCOUNT_DETAIL_DENORM';
    DATA_OBJECT_ID
    82646
    88518
    84184
    SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=82646;
    no rows selected
    SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=88518;
    no rows selected
    SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=84184;
    no rows selected
    2. find the object id for the index of that table and finding the wait events to that object_id.
    SYS@ccmintpt1 SQL>select data_object_id from dba_objects where object_name='XAK2ACCOUNT_DETAIL_DENORM';
    DATA_OBJECT_ID
    88655
    SID EVENT WAIT_CLASS WAIT_CLASS#
    1 rdbms ipc message Idle 6
    2 heartbeat monitor sleep Idle 6
    3 rdbms ipc message Idle 6
    4 wait for unread message on broadcast channel Idle 6
    6 SQL*Net message from client Idle 6
    7 SQL*Net message from client Idle 6
    8 SQL*Net message from client Idle 6
    9 SQL*Net message from client Idle 6
    10 SQL*Net message from client Idle 6
    11 SQL*Net message from client Idle 6
    12 SQL*Net message from client Idle 6
    13 SQL*Net message from client Idle 6
    1876 SQL*Net message from client Idle 6
    1877 VKTM Logical Idle Wait Idle 6
    1878 rdbms ipc message Idle 6
    1879 rdbms ipc message Idle 6
    1880 rdbms ipc message Idle 6
    1881 SQL*Net message from client Idle 6
    3200 SQL*Net message from client Idle 6
    3210 SQL*Net message from client Idle 6
    3212 db file sequential read User I/O 8
    3213 SQL*Net message from client Idle 6
    3214 SQL*Net message from client Idle 6
    3216 SQL*Net message from client Idle 6
    3751 rdbms ipc message Idle 6
    3752 gcs remote message Idle 6
    3754 rdbms ipc message Idle 6
    3756 SQL*Net message from client Idle 6
    3757 SQL*Net message from client Idle 6
    1326 SQL*Net message from client Idle 6
    1876 Streams AQ: waiting for time management or cleanup tasks Idle 6
    1877 VKTM Logical Idle Wait Idle 6
    1878 rdbms ipc message Idle 6
    1879 rdbms ipc message Idle 6
    1880 rdbms ipc message Idle 6
    1882 SQL*Net message from client Idle 6
    3751 rdbms ipc message Idle 6
    3752 gcs remote message Idle 6
    3754 rdbms ipc message Idle 6
    3756 rdbms ipc message Idle 6
    3758 SQL*Net message from client Idle 6
    3759 PX Deq: Execution Msg Idle 6
    3200 SQL*Net message from client Idle 6
    3210 SQL*Net message from client Idle 6
    3212 db file sequential read User I/O 8
    3213 SQL*Net message from client Idle 6
    3214 SQL*Net message from client Idle 6
    3216 SQL*Net message from client Idle 6
    3751 rdbms ipc message Idle 6
    3752 gcs remote message Idle 6
    3754 rdbms ipc message Idle 6
    3756 SQL*Net message from client Idle 6
    3757 SQL*Net message from client Idle 6
    3786 SQL*Net message from client Idle 6
    3787 SQL*Net message from client Idle 6
    1 heartbeat monitor sleep Idle 6
    2 wait for unread message on broadcast channel Idle 6
    314 rdbms ipc message Idle 6
    315 Streams AQ: qmn coordinator idle wait Idle 6
    627 pmon timer Idle 6
    628 rdbms ipc message Idle 6
    629 Streams AQ: waiting for messages in the queue Idle 6
    940 Streams AQ: waiting for time management or cleanup tasks Idle 6
    941 VKTM Logical Idle Wait Idle 6
    942 rdbms ipc message Idle 6
    1253 rdbms ipc message Idle 6
    1254 rdbms ipc message Idle 6
    1256 Space Manager: slave idle wait Idle 6
    1566 DIAG idle wait Idle 6
    1567 rdbms ipc message Idle 6
    1568 Streams AQ: qmn slave idle wait Idle 6
    1879 rdbms ipc message Idle 6
    1880 smon timer Idle 6
    1881 rdbms ipc message Idle 6
    2192 PING Idle 6
    2193 rdbms ipc message Idle 6
    2194 rdbms ipc message Idle 6
    2505 rdbms ipc message Idle 6
    2506 rdbms ipc message Idle 6
    2818 rdbms ipc message Idle 6
    2819 rdbms ipc message Idle 6
    2821 PX Deq: reap credit Other 0
    3131 DIAG idle wait Idle 6
    3132 jobq slave wait Idle 6
    3444 rdbms ipc message Idle 6
    3445 jobq slave wait Idle 6
    3757 ges remote message Idle 6
    3758 rdbms ipc message Idle 6
    3759 VKRM Idle Idle 6
    4070 gcs remote message Idle 6
    4072 rdbms ipc message Idle 6
    4383 gcs remote message Idle 6
    4385 PX Deq: Execution Msg Idle 6
    4696 rdbms ipc message Idle 6
    4697 rdbms ipc message Idle 6
    1 rdbms ipc message Idle 6
    2 heartbeat monitor sleep Idle 6
    3 rdbms ipc message Idle 6
    4 wait for unread message on broadcast channel Idle 6
    6 SQL*Net message from client Idle 6
    From this output, what are the waits events i need to take into consideration.
    Is this the right approach to follow?
    Please let me know.
    Thanks in advance.

    user13162661 wrote:
    Hi Gurus.
    I need you help to find out the wait events for a particular table and index when batch export job running from the application. I have done some work around to to find out, but i am not able to figure out the issue or what are the wait events. i am working on linux 4node rac 11gR2.
    Below are the steps i have done.
    1. find object_id for a table finding the wait events to that object_id.
    SYS@ccmintpt1 SQL>select data_object_id from dba_objects where object_name='ACCOUNT_DETAIL_DENORM';
    DATA_OBJECT_ID
    82646
    88518
    84184
    SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=82646;
    no rows selected
    SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=88518;
    no rows selected
    SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=84184;
    no rows selected
    2. find the object id for the index of that table and finding the wait events to that object_id.
    SYS@ccmintpt1 SQL>select data_object_id from dba_objects where object_name='XAK2ACCOUNT_DETAIL_DENORM';
    DATA_OBJECT_ID
    88655
    SID EVENT WAIT_CLASS WAIT_CLASS#
    1 rdbms ipc message Idle 6
    2 heartbeat monitor sleep Idle 6
    3 rdbms ipc message Idle 6
    4 wait for unread message on broadcast channel Idle 6
    6 SQL*Net message from client Idle 6
    7 SQL*Net message from client Idle 6
    8 SQL*Net message from client Idle 6
    9 SQL*Net message from client Idle 6
    10 SQL*Net message from client Idle 6
    11 SQL*Net message from client Idle 6
    12 SQL*Net message from client Idle 6
    13 SQL*Net message from client Idle 6
    1876 SQL*Net message from client Idle 6
    1877 VKTM Logical Idle Wait Idle 6
    1878 rdbms ipc message Idle 6
    1879 rdbms ipc message Idle 6
    1880 rdbms ipc message Idle 6
    1881 SQL*Net message from client Idle 6
    3200 SQL*Net message from client Idle 6
    3210 SQL*Net message from client Idle 6
    3212 db file sequential read User I/O 8
    3213 SQL*Net message from client Idle 6
    3214 SQL*Net message from client Idle 6
    3216 SQL*Net message from client Idle 6
    3751 rdbms ipc message Idle 6
    3752 gcs remote message Idle 6
    3754 rdbms ipc message Idle 6
    3756 SQL*Net message from client Idle 6
    3757 SQL*Net message from client Idle 6
    1326 SQL*Net message from client Idle 6
    1876 Streams AQ: waiting for time management or cleanup tasks Idle 6
    1877 VKTM Logical Idle Wait Idle 6
    1878 rdbms ipc message Idle 6
    1879 rdbms ipc message Idle 6
    1880 rdbms ipc message Idle 6
    1882 SQL*Net message from client Idle 6
    3751 rdbms ipc message Idle 6
    3752 gcs remote message Idle 6
    3754 rdbms ipc message Idle 6
    3756 rdbms ipc message Idle 6
    3758 SQL*Net message from client Idle 6
    3759 PX Deq: Execution Msg Idle 6
    3200 SQL*Net message from client Idle 6
    3210 SQL*Net message from client Idle 6
    3212 db file sequential read User I/O 8
    3213 SQL*Net message from client Idle 6
    3214 SQL*Net message from client Idle 6
    3216 SQL*Net message from client Idle 6
    3751 rdbms ipc message Idle 6
    3752 gcs remote message Idle 6
    3754 rdbms ipc message Idle 6
    3756 SQL*Net message from client Idle 6
    3757 SQL*Net message from client Idle 6
    3786 SQL*Net message from client Idle 6
    3787 SQL*Net message from client Idle 6
    1 heartbeat monitor sleep Idle 6
    2 wait for unread message on broadcast channel Idle 6
    314 rdbms ipc message Idle 6
    315 Streams AQ: qmn coordinator idle wait Idle 6
    627 pmon timer Idle 6
    628 rdbms ipc message Idle 6
    629 Streams AQ: waiting for messages in the queue Idle 6
    940 Streams AQ: waiting for time management or cleanup tasks Idle 6
    941 VKTM Logical Idle Wait Idle 6
    942 rdbms ipc message Idle 6
    1253 rdbms ipc message Idle 6
    1254 rdbms ipc message Idle 6
    1256 Space Manager: slave idle wait Idle 6
    1566 DIAG idle wait Idle 6
    1567 rdbms ipc message Idle 6
    1568 Streams AQ: qmn slave idle wait Idle 6
    1879 rdbms ipc message Idle 6
    1880 smon timer Idle 6
    1881 rdbms ipc message Idle 6
    2192 PING Idle 6
    2193 rdbms ipc message Idle 6
    2194 rdbms ipc message Idle 6
    2505 rdbms ipc message Idle 6
    2506 rdbms ipc message Idle 6
    2818 rdbms ipc message Idle 6
    2819 rdbms ipc message Idle 6
    2821 PX Deq: reap credit Other 0
    3131 DIAG idle wait Idle 6
    3132 jobq slave wait Idle 6
    3444 rdbms ipc message Idle 6
    3445 jobq slave wait Idle 6
    3757 ges remote message Idle 6
    3758 rdbms ipc message Idle 6
    3759 VKRM Idle Idle 6
    4070 gcs remote message Idle 6
    4072 rdbms ipc message Idle 6
    4383 gcs remote message Idle 6
    4385 PX Deq: Execution Msg Idle 6
    4696 rdbms ipc message Idle 6
    4697 rdbms ipc message Idle 6
    1 rdbms ipc message Idle 6
    2 heartbeat monitor sleep Idle 6
    3 rdbms ipc message Idle 6
    4 wait for unread message on broadcast channel Idle 6
    6 SQL*Net message from client Idle 6
    From this output, what are the waits events i need to take into consideration.
    Is this the right approach to follow?
    Please let me know.
    Thanks in advance.what actual problem are you trying to solve?
    post SQL & results that have you concerned about wait events

  • Ca'nt ftp longer (i.e. 4 minutes) flv or f4v files (get error message "waiting for server")  I

    when I ftp(i.e. "put" or "upload) short flv or f4v files using dreamweaver cs4 the files upload easily and quickly. However, when I try to ftp ("put" or "upload" ) longer (i.e. 4 minutes or longer) flv or f4v files it goes through the ftp process (seeing it in background activity screen) but at the end I always get a message "waiting on server" and the longer files don't get onto hosting server.  Is there a setting I need to change or other method I need to use).  I have worked with my hosting support tech person but we could not solve this problem.

    I'd suggest that you try using a dedicated FTP program like Filezilla or SmartFTP.
    http://filezilla-project.org/
    Those programs give you much more feedback on what's happening as you attempt to upload files, including error messages, etc.
    There is really no difference between uploading large files and small files, the process on the server is exactly the same..UNLESS there are limits to file size or video duration set by your host. So dispite the fact that you have worked with your host support, I'd still say that the problem is server side or being limited by your Internet service provider... unless the video files you are attempting to upload are corrupted.
    You didn't say if any portion of the larger video files were uploaded...and FTP program will show you whether or not ANY of the file was uploaded and at what point it stopped. You also didn't mention how large the video files where.... sort of where the "tipping point" is in file size (video duration of course is no measure of file size).
    Just to reassure you, the file size of a video file will have no bearing on your ability to FTP unless your host or ISP is limiting you in some way.
    I regularly Live stream events and also record them. An 8 hr event will produce roughly 1.5GB of compressed video. I use SmartFTP, with a reputable host and can upload the entire set of 1.5GB of video files (each about 50MB) over a 1000kbps upload connection without problem. Recently during a movie production project, we uploaded a number of single video file which each where over 1GB a piece.
    So there is really no problem uploading video files unless there are restriction on you account from the host or the ISP.
    Best wishes,
    Adninjastrator

Maybe you are looking for