Query waiting for objects...

Hi,
I have a Pl/Sql query which when run is taking a long time to execute.
When i put a trace on it, i found that it is waiting for 2 objects and as soon as the wait is over the query produces the output immediately.
I tried puuting index on tables which had large records as i thought initially that it might be waiting due to full table scan, but its not of much help.
Earlier this query used to run within 5 minutes some 3 months back, but now it is taking about 1 hour daily and when the trace is on, it shows again it is waiting for 2 objects.
What im thinking is that, earlier when the query used to run within 5 minutes the data involved was not that heavy, but since the last 2 months the data is in millions every month.
Could you suggest me a possible solution to this problem of waiting for objects.
Thanks.
Database version being used - Oracle 10g

Hi,
When i put a trace on it, i found that it is waiting for 2 objects and as soon as the wait is over the query produces the output immediately.'it is waiting for 2 objects?' What exactly do you mean by that?
If you've done a trace then why didn't you post the tkprof output?
Please post the tkprof output (including wait events) and your PL/SQL procedure (or a representative piece of sample code)
Put this tag => before and after your tkprof output/code examples, so it says readable.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • Insert query waiting for in-definite time.

    Hi all,
    I had a serious problem in my system.
    My application gets stuck when trying to insert a huge xml message in a table blob. Usually there is no problem, the insert query goes into wait state just around or after the gather stats running on this table ends.
    The table is partitioned one and around 150Gb in size.
    I have seen in toad the wait event for this insert query is SQL* net more data from client.
    This might be something related to RBS usage of this stuck insert query - in toad the RBS usage start time is same as the end time of gather stats.
    But i m unable to figure out why the insert is stuck just after the gather stats ends, i have simulated this issue many times. My oracle version is 9.0.8.
    Could somebody help to figure out why this is happening...?

    My oracle version is 9.0.8.I doubt this is correct.
    Post Operating System (OS) name & version for DB server system.
    Post results of SELECT * from v$version.
    Now CUT the commands & results & PASTE (post) them back here.
    ALTER SESSION SET SQL_TRACE=TRUE;
    -- invoke the problem SQL here
    ALTER SESSION SET SQL_TRACE=FALSE;
    now find the trace file within ./udump folder
    tkprof <trace_file.trc> trace_results.txt explain=<username>/<password>
    post the contents of trace_results.txt back here
    when application "gets stuck" run the following SQL from different session
    SELECT DECODE(request,0,'Holder: ','Waiter: ')||sid sess,
    id1, id2, lmode, request, type
    FROM V$LOCK
    WHERE (id1, id2, type) IN
    (SELECT id1, id2, type FROM V$LOCK WHERE request>0)
    ORDER BY id1, request
    /

  • Getting deadlock detected while waiting for resource error for select Query.....

    Hi all,
    i am getting a below error whenever executing the below select query....
    some times it will show dead lock detected while waiting for resource and terminated...
    some times it executes and gives result..
    but all the time it writes an alert to alert log
    Plesae suggest how to resolve the issue..........
    Thanks in advance
    Env: Linux / Oracle 11.2.0.3.3
    Error from alert log:
    Errors in file /u01/oracle/oracle/diag/rdbms/bdrdb/bdrdb/trace/bdrdb_p017_6076.trc:
    ORA-00060: deadlock detected while waiting for resource
    ORA-10387: parallel query server interrupt (normal)
    Trace file info... bdrdb_p017_6076.trc:
    Trace file /u01/oracle/oracle/diag/rdbms/bdrdb/bdrdb/trace/bdrdb_p017_6076.trc
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORACLE_HOME = /u01/oracle/oracle/product/11.2.0/dbhome_1
    System name:    Linux
    Node name:      bdrdb.cteplindia.com
    Release:        2.6.18-308.el5PAE
    Version:        #1 SMP Fri Jan 27 17:40:09 EST 2012
    Machine:        i686
    Instance name: bdrdb
    Redo thread mounted by this instance: 1
    Oracle process number: 92
    Unix process pid: 6076, image: [email protected] (P017)
    *** 2013-11-04 23:18:57.915
    *** SESSION ID:(423.59970) 2013-11-04 23:18:57.915
    *** CLIENT ID:() 2013-11-04 23:18:57.915
    *** SERVICE NAME:(bdrdb) 2013-11-04 23:18:57.915
    *** MODULE NAME:() 2013-11-04 23:18:57.915
    *** ACTION NAME:() 2013-11-04 23:18:57.915
    *** 2013-11-04 23:18:57.915
    DEADLOCK DETECTED ( ORA-00060 )
    [Transaction Deadlock]
    Deadlock graph:
                           ---------Blocker(s)--------  ---------Waiter(s)---------
    Resource Name          process session holds waits  process session holds waits
    PS-00000001-00000011        92     423     S             33     128     S     X
    BF-2ed08c01-00000000        33     128     S             92     423     S     X
    session 423: DID 0001-005C-00081126     session 128: DID 0001-0021-00067D23
    session 128: DID 0001-0021-00067D23     session 423: DID 0001-005C-00081126
    DEADLOCK DETECTED ( ORA-00060 )
    [Transaction Deadlock]
    Deadlock graph:
                           ---------Blocker(s)--------  ---------Waiter(s)---------
    Resource Name          process session holds waits  process session holds waits
    PS-00000001-00000011        92     423     S             33     128     S     X
    BF-2ed08c01-00000000        33     128     S             92     423     S     X
    session 423: DID 0001-005C-00081126     session 128: DID 0001-0021-00067D23
    session 128: DID 0001-0021-00067D23     session 423: DID 0001-005C-00081126
    Rows waited on:
      Session 423: no row
      Session 128: obj - rowid = 00021DC1 - AAAh3BAAVAAAQL/AAA
      (dictionary objn - 138689, file - 21, block - 66303, slot - 0)
    ----- Information for the OTHER waiting sessions -----
    Session 128:
      sid: 128 ser: 46176 audsid: 1836857 user: 102/DBLOCAL
        flags: (0x8000041) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
        flags2: (0x40009) -/-/INC
      pid: 33 O/S info: user: oracle, term: UNKNOWN, ospid: 31611
        image: [email protected]
      client details:
        O/S info: user: masked, term: masked, ospid: 5924:568
        machine: masked program: Toad.exe
        application name: TOAD background query session, hash value=526966934
      current SQL:
        application name: TOAD background query session, hash value=526966934
      current SQL:
      SELECT  DISTINCT B_FP_TEST.TEST_ID
      FROM B_FP_TEST,
           B_USER_INFO,
           J_FP_INVESTIGATOR,
           L_TEST_STATUS,
           L_ATMS_TEST_TYPE,
           j_op_test_anml
    WHERE     B_FP_TEST.TEST_ID = J_FP_INVESTIGATOR.TEST_ID
           AND B_FP_TEST.TEST_TYPE_ID = L_ATMS_TEST_TYPE.ATMS_TEST_TYPE_ID
           AND B_USER_INFO.B_USER_INFO_ID = J_FP_INVESTIGATOR.INVESTIGATOR_ID
           AND B_FP_TEST.STATUS_ID = L_TEST_STATUS.STATUS_ID
           AND B_FP_TEST.IS_DELETED = :"SYS_B_00"
           AND B_FP_TEST.TEST_NUM NOT IN (:"SYS_B_01", :"SYS_B_02", :"SYS_B_03")
           AND L_ATMS_TEST_TYPE.IS_DELETED = :"SYS_B_04"
           AND J_FP_INVESTIGATOR.is_pi = :"SYS_B_05"
           AND L_TEST_STATUS.STATUS IN (:"SYS_B_06", :"SYS_B_07", :"SYS_B_08")
           AND j_op_test_anml.test_id = B_FP_TEST.TEST_ID
    ----- End of information for the OTHER waiting sessions -----
    *** 2013-11-04 23:18:57.916
    dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=3, mask=0x0)
    ----- Error Stack Dump -----
    ORA-00060: deadlock detected while waiting for resource
    ORA-10387: parallel query server interrupt (normal)
    ----- SQL Statement (None) -----
    Current SQL information unavailable - no cursor.
    ----- Call Stack Trace -----
    calling              call     entry                argument values in hex
    location             type     point                (? means dubious value)
    More......
    Query:
    SELECT DISTINCT B_FP_TEST.TEST_ID
      FROM B_FP_TEST,
           B_USER_INFO,
           J_FP_INVESTIGATOR,
           L_TEST_STATUS,
           L_ATMS_TEST_TYPE,
           j_op_test_anml
    WHERE     B_FP_TEST.TEST_ID = J_FP_INVESTIGATOR.TEST_ID
           AND B_FP_TEST.TEST_TYPE_ID = L_ATMS_TEST_TYPE.ATMS_TEST_TYPE_ID
           AND B_USER_INFO.B_USER_INFO_ID = J_FP_INVESTIGATOR.INVESTIGATOR_ID
           AND B_FP_TEST.STATUS_ID = L_TEST_STATUS.STATUS_ID
           AND B_FP_TEST.IS_DELETED = 0
           AND B_FP_TEST.TEST_NUM NOT IN (1, 2, 99)
           AND L_ATMS_TEST_TYPE.IS_DELETED = 0
           AND J_FP_INVESTIGATOR.is_pi = 1
           AND L_TEST_STATUS.STATUS IN ('Scheduled', 'In-Progress', 'Completed')
           AND j_op_test_anml.test_id = B_FP_TEST.TEST_ID
           AND (   (j_op_test_anml.end_date BETWEEN TO_DATE ('28-Oct-2013') - 1
                                                AND TO_DATE ('04-Nov-2013') + 1)
                OR (j_op_test_anml.start_date BETWEEN TO_DATE ('28-Oct-2013') - 1
                                                  AND TO_DATE ('04-Nov-2013') + 1)
                OR (TO_DATE ('28-Oct-2013') BETWEEN j_op_test_anml.start_date
                                                AND j_op_test_anml.end_date)
                OR (TO_DATE ('04-Nov-2013') BETWEEN j_op_test_anml.start_date
                                                AND j_op_test_anml.end_date))
           AND L_ATMS_TEST_TYPE.IS_DELETED = 0
           AND B_FP_TEST.DATASOURCE_ID = 9
    Query Exp plan:
    Plan hash value: 3398228788
    | Id  | Operation                                          | Name                | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |    TQ  |IN-OUT| PQ Distrib |
    |   0 | SELECT STATEMENT                                   |                     |  1501 |   102K|  1929   (1)| 00:00:24 |       |       |        |      |            |
    |   1 |  HASH UNIQUE                                       |                     |  1501 |   102K|  1929   (1)| 00:00:24 |       |       |        |      |            |
    |   2 |   CONCATENATION                                    |                     |       |       |            |          |       |       |        |      |            |
    |   3 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
    |   4 |     PX SEND QC (RANDOM)                            | :TQ30005            |   241 | 16870 |   800   (1)| 00:00:10 |       |       |  Q3,05 | P->S | QC (RAND)  |
    |*  5 |      HASH JOIN                                     |                     |   241 | 16870 |   800   (1)| 00:00:10 |       |       |  Q3,05 | PCWP |            |
    |   6 |       PX RECEIVE                                   |                     |   246 | 15990 |   797   (1)| 00:00:10 |       |       |  Q3,05 | PCWP |            |
    |   7 |        PX SEND HASH                                | :TQ30004            |   246 | 15990 |   797   (1)| 00:00:10 |       |       |  Q3,04 | P->P | HASH       |
    |*  8 |         HASH JOIN                                  |                     |   246 | 15990 |   797   (1)| 00:00:10 |       |       |  Q3,04 | PCWP |            |
    |   9 |          PX RECEIVE                                |                     |   573 | 29223 |   793   (1)| 00:00:10 |       |       |  Q3,04 | PCWP |            |
    |  10 |           PX SEND HASH                             | :TQ30003            |   573 | 29223 |   793   (1)| 00:00:10 |       |       |  Q3,03 | P->P | HASH       |
    |* 11 |            HASH JOIN                               |                     |   573 | 29223 |   793   (1)| 00:00:10 |       |       |  Q3,03 | PCWP |            |
    |  12 |             BUFFER SORT                            |                     |       |       |            |          |       |       |  Q3,03 | PCWC |            |
    |  13 |              PX RECEIVE                            |                     |       |       |            |          |       |       |  Q3,03 | PCWP |            |
    |  14 |               PX SEND BROADCAST                    | :TQ30000            |       |       |            |          |       |       |        | S->P | BROADCAST  |
    |  15 |                NESTED LOOPS                        |                     |       |       |            |          |       |       |        |      |            |
    |  16 |                 NESTED LOOPS                       |                     |   485 | 20855 |   781   (0)| 00:00:10 |       |       |        |      |            |
    |  17 |                  TABLE ACCESS BY GLOBAL INDEX ROWID| J_OP_TEST_ANML      |   485 | 10185 |   296   (0)| 00:00:04 | ROWID | ROWID |        |      |            |
    |* 18 |                   INDEX RANGE SCAN                 | IDX$$_2D190001      |   485 |       |     4   (0)| 00:00:01 |       |       |        |      |            |
    |* 19 |                  INDEX UNIQUE SCAN                 | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
    |* 20 |                 TABLE ACCESS BY GLOBAL INDEX ROWID | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
    |  21 |             PX BLOCK ITERATOR                      |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       |  Q3,03 | PCWC |            |
    |* 22 |              TABLE ACCESS FULL                     | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       |  Q3,03 | PCWP |            |
    |  23 |          BUFFER SORT                               |                     |       |       |            |          |       |       |  Q3,04 | PCWC |            |
    |  24 |           PX RECEIVE                               |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       |  Q3,04 | PCWP |            |
    |  25 |            PX SEND HASH                            | :TQ30001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
    |* 26 |             TABLE ACCESS FULL                      | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
    |  27 |       BUFFER SORT                                  |                     |       |       |            |          |       |       |  Q3,05 | PCWC |            |
    |  28 |        PX RECEIVE                                  |                     |    30 |   150 |     3   (0)| 00:00:01 |       |       |  Q3,05 | PCWP |            |
    |  29 |         PX SEND HASH                               | :TQ30002            |    30 |   150 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
    |* 30 |          TABLE ACCESS FULL                         | L_ATMS_TEST_TYPE    |    30 |   150 |     3   (0)| 00:00:01 |       |       |        |      |            |
    |  31 |    NESTED LOOPS                                    |                     |       |       |            |          |       |       |        |      |            |
    |  32 |     NESTED LOOPS                                   |                     |     3 |   210 |   329   (1)| 00:00:04 |       |       |        |      |            |
    |  33 |      NESTED LOOPS                                  |                     |     3 |   195 |   329   (1)| 00:00:04 |       |       |        |      |            |
    |* 34 |       HASH JOIN                                    |                     |     2 |   114 |   325   (1)| 00:00:04 |       |       |        |      |            |
    |  35 |        NESTED LOOPS                                |                     |       |       |            |          |       |       |        |      |            |
    |  36 |         NESTED LOOPS                               |                     |     6 |   258 |   322   (1)| 00:00:04 |       |       |        |      |            |
    |  37 |          PARTITION RANGE SINGLE                    |                     |     6 |   126 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
    |* 38 |           TABLE ACCESS FULL                        | J_OP_TEST_ANML      |     6 |   126 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
    |* 39 |          INDEX UNIQUE SCAN                         | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
    |* 40 |         TABLE ACCESS BY GLOBAL INDEX ROWID         | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
    |* 41 |        TABLE ACCESS FULL                           | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
    |* 42 |       TABLE ACCESS BY INDEX ROWID                  | J_FP_INVESTIGATOR   |     1 |     8 |     2   (0)| 00:00:01 |       |       |        |      |            |
    |* 43 |        INDEX RANGE SCAN                            | FI_TEST_ID_PK       |     1 |       |     1   (0)| 00:00:01 |       |       |        |      |            |
    |* 44 |      INDEX UNIQUE SCAN                             | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
    |* 45 |     TABLE ACCESS BY INDEX ROWID                    | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       |        |      |            |
    |  46 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
    |  47 |     PX SEND QC (RANDOM)                            | :TQ20003            |       |       |            |          |       |       |  Q2,03 | P->S | QC (RAND)  |
    |  48 |      NESTED LOOPS                                  |                     |       |       |            |          |       |       |  Q2,03 | PCWP |            |
    |  49 |       NESTED LOOPS                                 |                     |    33 |  2310 |   399   (2)| 00:00:05 |       |       |  Q2,03 | PCWP |            |
    |* 50 |        HASH JOIN                                   |                     |    33 |  2145 |   397   (2)| 00:00:05 |       |       |  Q2,03 | PCWP |            |
    |  51 |         PX RECEIVE                                 |                     |    78 |  3978 |   393   (1)| 00:00:05 |       |       |  Q2,03 | PCWP |            |
    |  52 |          PX SEND HASH                              | :TQ20002            |    78 |  3978 |   393   (1)| 00:00:05 |       |       |  Q2,02 | P->P | HASH       |
    |* 53 |           HASH JOIN                                |                     |    78 |  3978 |   393   (1)| 00:00:05 |       |       |  Q2,02 | PCWP |            |
    |  54 |            BUFFER SORT                             |                     |       |       |            |          |       |       |  Q2,02 | PCWC |            |
    |  55 |             PX RECEIVE                             |                     |       |       |            |          |       |       |  Q2,02 | PCWP |            |
    |  56 |              PX SEND BROADCAST                     | :TQ20000            |       |       |            |          |       |       |        | S->P | BROADCAST  |
    |  57 |               NESTED LOOPS                         |                     |       |       |            |          |       |       |        |      |            |
    |  58 |                NESTED LOOPS                        |                     |    66 |  2838 |   382   (1)| 00:00:05 |       |       |        |      |            |
    |  59 |                 PARTITION RANGE SINGLE             |                     |    66 |  1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
    |* 60 |                  TABLE ACCESS FULL                 | J_OP_TEST_ANML      |    66 |  1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
    |* 61 |                 INDEX UNIQUE SCAN                  | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
    |* 62 |                TABLE ACCESS BY GLOBAL INDEX ROWID  | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
    |  63 |            PX BLOCK ITERATOR                       |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       |  Q2,02 | PCWC |            |
    |* 64 |             TABLE ACCESS FULL                      | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       |  Q2,02 | PCWP |            |
    |  65 |         BUFFER SORT                                |                     |       |       |            |          |       |       |  Q2,03 | PCWC |            |
    |  66 |          PX RECEIVE                                |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       |  Q2,03 | PCWP |            |
    |  67 |           PX SEND HASH                             | :TQ20001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
    |* 68 |            TABLE ACCESS FULL                       | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
    |* 69 |        INDEX UNIQUE SCAN                           | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       |  Q2,03 | PCWP |            |
    |* 70 |       TABLE ACCESS BY INDEX ROWID                  | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       |  Q2,03 | PCWP |            |
    |  71 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
    |  72 |     PX SEND QC (RANDOM)                            | :TQ10003            |       |       |            |          |       |       |  Q1,03 | P->S | QC (RAND)  |
    |  73 |      NESTED LOOPS                                  |                     |       |       |            |          |       |       |  Q1,03 | PCWP |            |
    |  74 |       NESTED LOOPS                                 |                     |    33 |  2310 |   399   (2)| 00:00:05 |       |       |  Q1,03 | PCWP |            |
    |* 75 |        HASH JOIN                                   |                     |    34 |  2210 |   397   (2)| 00:00:05 |       |       |  Q1,03 | PCWP |            |
    |  76 |         PX RECEIVE                                 |                     |    78 |  3978 |   393   (1)| 00:00:05 |       |       |  Q1,03 | PCWP |            |
    |  77 |          PX SEND HASH                              | :TQ10002            |    78 |  3978 |   393   (1)| 00:00:05 |       |       |  Q1,02 | P->P | HASH       |
    |* 78 |           HASH JOIN                                |                     |    78 |  3978 |   393   (1)| 00:00:05 |       |       |  Q1,02 | PCWP |            |
    |  79 |            BUFFER SORT                             |                     |       |       |            |          |       |       |  Q1,02 | PCWC |            |
    |  80 |             PX RECEIVE                             |                     |       |       |            |          |       |       |  Q1,02 | PCWP |            |
    |  81 |              PX SEND BROADCAST                     | :TQ10000            |       |       |            |          |       |       |        | S->P | BROADCAST  |
    |  82 |               NESTED LOOPS                         |                     |       |       |            |          |       |       |        |      |            |
    |  83 |                NESTED LOOPS                        |                     |    66 |  2838 |   382   (1)| 00:00:05 |       |       |        |      |            |
    |  84 |                 PARTITION RANGE SINGLE             |                     |    66 |  1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
    |* 85 |                  TABLE ACCESS FULL                 | J_OP_TEST_ANML      |    66 |  1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
    |* 86 |                 INDEX UNIQUE SCAN                  | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
    |* 87 |                TABLE ACCESS BY GLOBAL INDEX ROWID  | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
    |  88 |            PX BLOCK ITERATOR                       |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       |  Q1,02 | PCWC |            |
    |* 89 |             TABLE ACCESS FULL                      | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       |  Q1,02 | PCWP |            |
    |  90 |         BUFFER SORT                                |                     |       |       |            |          |       |       |  Q1,03 | PCWC |            |
    |  91 |          PX RECEIVE                                |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       |  Q1,03 | PCWP |            |
    |  92 |           PX SEND HASH                             | :TQ10001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
    |* 93 |            TABLE ACCESS FULL                       | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
    |* 94 |        INDEX UNIQUE SCAN                           | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       |  Q1,03 | PCWP |            |
    |* 95 |       TABLE ACCESS BY INDEX ROWID                  | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       |  Q1,03 | PCWP |            |
    Predicate Information (identified by operation id):
       5 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
       8 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
      11 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
      18 - access("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05
                  00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
      19 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
      20 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
                  "B_FP_TEST"."TEST_NUM"<>99)
      22 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
      26 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
      30 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
      34 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
      38 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05
                  00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
                  LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
      39 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
      40 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
                  "B_FP_TEST"."TEST_NUM"<>99)
      41 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
      42 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
      43 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
      44 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
      45 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
      50 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
      53 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
      60 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-04
                  00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
                  LNNVL("J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27
                  00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
      61 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
      62 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
                  "B_FP_TEST"."TEST_NUM"<>99)
      64 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
      68 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
      69 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
      70 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
      75 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
      78 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
      85 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-28 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-10-28
                  00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
                  LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27
                  00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND
                  (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05
                  00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
      86 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
      87 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
                  "B_FP_TEST"."TEST_NUM"<>99)
      89 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
      93 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
      94 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
      95 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)

    Excellent piece of follow-up on my first suggestion.
    I nearly made a comment about how the plan doesn't show Bloom filter pruning either - and then I realised why not. The plan you've shown us comes from Explain Plan with literal values present; the trace file shows bind variables with names that are generated when cursor_sharing is set to force or similar - so the run-time plan and the plan from explain plan are almost guaranteed to be different.
    Oracle support will need you to supply the plan you get from trying to run the query and then making a call to dbms_xplan.display_cursor() - dbms_xplan in 10g | Oracle Scratchpad If you do this I think you'll find that the pstart/pstop columns contain entries like :BF0000, and you may even find operations link PX JOIN FILTER CREATE / PX JOIN FILTER USE
    A couple of generic notes:
    if a query does sufficient work to merit parallel execution, then it's usually better to supply the best possible information to the optimizer, which means using literals rather than bind variables - you could try executing the query with the hint /*+ cursor_sharing_exact */ to stop Oracle from turning your literals into binds; it might be the presence of bind variables that's making the optimizer choose a path that has to include bloom filter pruning in your case.
    Where you have the to_date() call you've used a four-digit year - which is a very good thing and helps the optimizer - but it's also a good idea to include an explicit format string as well: with a four-digit year this probably won't make any difference, but it avoids any risk of ambiguity for the optimizer.
    I made a comment about the P->S stage and bottlenecks - I spent a couple more minutes looking at the plan, and I see the optimizer has used concatentation: in effect it has run three query blocks one after the other and fed the results to the query co-ordinator - in this case the P->S would make no difference to the end-user response time there's always a final P->S to the coordinator, you just happen to have three of them.
    Regards
    Jonathan Lewis

  • Keep getting this prompt when I close a tab: ASSERT: Giving up waiting for the tab closing animation to finish (bug 608589) Stack Trace: 0:([object XULElement],[object XULElement],0) How do I get rid of it?

    ASSERT: Giving up waiting for the tab closing animation to finish (bug 608589)
    Stack Trace:
    0:([object XULElement],[object XULElement],0)
    Happening since I went to the 4.0b9 beta. Thanks for any help in getting rid of it.

    They're still working on fixing that Bug - https://bugzilla.mozilla.org/show_bug.cgi?id=608589 - a fix for another Bug - https://bugzilla.mozilla.org/show_bug.cgi?id=613888 - landed earlier this week which might have fixed it. Unless you are willing to install a nightly Trunk which has the latest fixes, you'll have to wait for 4.0b10 for the fix.

  • Query "Stuck" in CXPacket wait with no other waits for that session id in the blocking session id of sys.dm_os_waiting_tasks

    So I have a query that is running with a large number of CXPacket waits.  There are no other tasks in the sys.dm_os_waiting_tasks that are blocking this session id with a wait other than CXPacket Wait.  This is taking place on a SQL Server 2008
    R2 machine.  My question is there something else to look at?  I've gone ahead and posted the output of the entire sys.dm_os_waiting_tasks.  Any thoughts?
    waiting_task_address    session_id    exec_context_id    wait_duration_ms    wait_type    resource_address    blocking_task_address    blocking_session_id  
     blocking_exec_context_id    resource_description
    0x0000000004E88988    NULL    NULL    13525    FT_IFTS_SCHEDULER_IDLE_WAIT    NULL    NULL    NULL    NULL    NULL
    0x0000000004E89288    NULL    NULL    64128606    DISPATCHER_QUEUE_SEMAPHORE    NULL    NULL    NULL    NULL    NULL
    0x0000000004ED6748    2    0    19502    XE_TIMER_EVENT    NULL    NULL    NULL    NULL    NULL
    0x0000000004450508    3    0    2779501    XE_DISPATCHER_WAIT    NULL    NULL    NULL    NULL    NULL
    0x000000000446A748    4    0    838    LAZYWRITER_SLEEP    NULL    NULL    NULL    NULL    NULL
    0x000000000448E508    5    0    438    REQUEST_FOR_DEADLOCK_SEARCH    0x000000000B9301F8    NULL    NULL    NULL    NULL
    0x0000000004E88508    6    0    1304946379    KSOURCE_WAKEUP    NULL    NULL    NULL    NULL    NULL
    0x0000000004484508    7    0    146961    LOGMGR_QUEUE    0x0000000003597248    NULL    NULL    NULL    NULL
    0x00000000804942C8    9    0    3366    SQLTRACE_INCREMENTAL_FLUSH_SLEEP    NULL    NULL    NULL    NULL    NULL
    0x000000000448E748    10    0    929    SLEEP_TASK    NULL    NULL    NULL    NULL    NULL
    0x0000000004450988    11    0    26214727    BROKER_EVENTHANDLER    NULL    NULL    NULL    NULL    NULL
    0x0000000004EBC508    12    0    1304959888    ONDEMAND_TASK_QUEUE    0x0000000003575508    NULL    NULL    NULL    NULL
    0x0000000004EA2508    13    0    146959    CHECKPOINT_QUEUE    0x0000000003590C70    NULL    NULL    NULL    NULL
    0x0000000004EA2748    14    0    1304947282    BROKER_TRANSMITTER    NULL    NULL    NULL    NULL    NULL
    0x0000000004484988    16    0    1304947282    BROKER_TRANSMITTER    NULL    NULL    NULL    NULL    NULL
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x0000000255EFEBC8    154    19    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x0000000258D26748    154    17    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x0000000258DB0E08    154    18    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x000000025A392748    154    21    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x0000000258DB2E08    154    20    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x000000025C694508    154    23    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x000000025A675708    154    24    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x000000000446AE08    154    0    19974433    CXPACKET    0x0000000804ECC1D0    0x00000001D3F902C8    154    22    exchangeEvent
    id=Port80263100 WaitType=e_waitPortOpen nodeId=4
    0x0000000004EBCE08    154    1    18269246    CXPACKET    0x000000080C705200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6220e00 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004485288    154    2    18269246    CXPACKET    0x000000080CD4F200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6220f00 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004EA3B88    154    3    18269246    CXPACKET    0x000000080CCDD200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6221000 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004ED7948    154    4    18269246    CXPACKET    0x000000080CC8B200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6220f80 WaitType=e_waitPipeGetRow nodeId=33
    0x000000000448F708    154    5    18269242    CXPACKET    0x000000080CD41200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6220e80 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004451B88    154    6    18269245    CXPACKET    0x000000080CE31200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6221080 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000004E89048    154    7    18269246    CXPACKET    0x000000080D12B200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6221100 WaitType=e_waitPipeGetRow nodeId=33
    0x000000000446ABC8    154    8    18269243    CXPACKET    0x000000080CE7D200    0x000000000448FB88    154    13    exchangeEvent
    id=Pipe2f6221200 WaitType=e_waitPipeGetRow nodeId=33
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258D26748    154    17    18270546    CXPACKET    0x000000025C763020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247880 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB0E08    154    18    19974425    CXPACKET    0x00000008064DD020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247900 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000255EFEBC8    154    19    18269474    CXPACKET    0x0000000806355020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247800 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x0000000258DB2E08    154    20    18270502    CXPACKET    0x0000000805CC1020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247a00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322346    CXPACKET    0x0000000806395020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A392748    154    21    18322347    CXPACKET    0x0000000806395020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247980 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x00000001D3F902C8    154    22    18270621    CXPACKET    0x000000025CE67020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247c00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025C694508    154    23    18270541    CXPACKET    0x000000025C75D020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247a80 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004EBCE08    154    1    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x000000000448F708    154    5    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004485288    154    2    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004ED7948    154    4    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004EA3B88    154    3    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004451B88    154    6    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x0000000004E89048    154    7    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17
    0x000000025A675708    154    24    18269840    CXPACKET    0x000000025C767020    0x000000000446ABC8    154    8    exchangeEvent
    id=Pipe9c247b00 WaitType=e_waitPipeGetRow nodeId=17

    Hello,
    First, I would take a look at what your MAXDOP setting is, that's seems a bit high unless you have around 80 processors - stick to multiples of the number of processors in a single numa node and don't go over half of the numa nodes if this is for an OLTP
    system. If it's for a DSS or DW system then having a very high maxdop should be fine.
    When dealing with CXPACKET the wait means that it's waiting for all of the parallel threads to complete before it can merge the results and move on. If any single thread has to process more than any other (or waits longer for data) the whole process has
    to wait. I would investigate to see if there is a large skew in statistics and one thread is processing much more than another. I'd also try creating an extended events session to grab all of the waitinfo for that session.
    Sean Gallardy | Blog |
    Twitter

  • Update query is waiting for async descriptor resize

    Hi All,
    One of the update query which was completing in 1-2 mins. Suddenly today it started taking more than 3-4 hours and still it is running.
    Below is the query, I can see the explain plain. I can see the query is waiting for async descriptor resize wait event
    UPDATE AP_INVOICE_DISTRIBUTIONS SET POSTED_FLAG = 'N' WHERE POST
    ED_FLAG = 'S' AND (ACCOUNTING_DATE >= :B2 OR :B2 IS NULL) AND (A
    CCOUNTING_DATE <= :B1 OR :B1 IS NULL)
    when i checked the P1text, P2text columns of v$session, it is showing outstanding #aio,current ai0 limit respectively.
    Explan plan
    CODEPLAN_TABLE_OUTPUT
    | Id  | Operation                      | Name                         | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | UPDATE STATEMENT               |                              |       |       |   250 (100)|          |
    |   1 |  UPDATE                        | AP_INVOICE_DISTRIBUTIONS_ALL |       |       |            |          |
    |   2 |   NESTED LOOPS                 |                              |       |       |            |          |
    |   3 |    NESTED LOOPS                |                              |    39 | 12480 |   250   (0)| 05:14:02 |
    |*  4 |     TABLE ACCESS BY INDEX ROWID| AP_ACCOUNTING_EVENTS_ALL     |    39 |   624 |   145   (0)| 03:02:09 |
    |*  5 |      INDEX RANGE SCAN          | AP_ACCOUNTING_EVENTS_N2      |  3954 |       |    14   (0)| 00:17:36 |
    |*  6 |     INDEX RANGE SCAN           | AP_INVOICE_DISTRIBUTIONS_N18 |     4 |       |     2   (0)| 00:02:31 |
    PLAN_TABLE_OUTPUT
    |*  7 |    TABLE ACCESS BY INDEX ROWID | AP_INVOICE_DISTRIBUTIONS_ALL |     1 |   304 |     4   (0)| 00:05:02 |
    CODE
    Please help me on this.
    Env Details --
    DB version -- 11.2.0.1
    OS - IBM AIX.
    Thanks in advance...

    This could be this bug
    Bug 9829397 - Excessive CPU and many "asynch descriptor resize" waits for SQL using Async IO (Doc ID 9829397.8)

  • Significant time waiting for User I/O on the hot object

    How to correct this warnings shone in enterprise manager's top most poor sql's in performance analysis ;
    The SQL statement with SQL_ID "dnpdchg674nrr" spent significant time waiting for User I/O on the hot object.
    Texto SQLSELECT COUNT(*) AS QTDCTA FROM CONTAS WHERE SITUACAOCT = 0 AND TIPOCT = 0 AND MA...
    Fowards Thanks
    Marcos Ortega
    Brasil

    Thanks, for so fast answers;
    Just one doubt; Significant user I/O; I thought to be related to many rows beeing request, or some like that;
    here is the plan ( contas is a huge table , more than 40 millions rows )
    SELECT COUNT(*) AS QTDCTA
    FROM CONTAS
    WHERE SITUACAOCT = 0 AND TIPOCT = 0 AND MATRICULA = :pMATRICULA
    SELECT STATEMENT, GOAL = ALL_ROWS                    5     1     26     
    SORT AGGREGATE                         1     26     AGGREGATE
    TABLE ACCESS BY INDEX ROWID     EOS     CONTAS          5     1     26     BY INDEX ROWID
    INDEX RANGE SCAN     EOS     I_LOCALIZ     2     4     3          RANGE SCAN

  • Cannot get a connection, pool error Timeout waiting for idle object

    my connection pool setting is
      maxActive="3" minIdle="2"                maxWait="10000"              removeAbandoed="true" logAbandoned="true"         removeAbandonedTimeout="30"         autoreconnection="true" 
    we have 7 people hitting the group of search functions ,
    about 3 minutes I get
    I got error like
    org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object         at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:104)         at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)         at Deferment.showResult.checStudent(showResult.java:135)         at Deferment.showResult.doPost(showResult.java:99)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)         at org.apache.catalina.servlets.InvokerServlet.serveRequest(InvokerServlet.java:402)         at org.apache.catalina.servlets.InvokerServlet.doPost(InvokerServlet.java:170)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    I just wonder
    1) Cannot get a connection, pool error Timeout waiting for idle object-> cause by connection pool leaking or other problem.
    2) Setting the maxactive to -1 ( suggestion from Google) , if I set my connection to ulimit , waht should I put on minIdle="2"
    3) How can I test my connection pool have problem or not ? is
    SHOW PROCESSLIST; tolding me someinformation? I use Mysql
    Thank you!

    I try something like ps2 = conn.prepareStatement(target);
                ps2.setString(1, UNumber); // set input parameter
                rs = ps2.executeQuery();
                sendMail = 0;//how many rows we can find.
                while (rs.next()) {
                    sendMail++;
                ps2.close();
                rs.close();
                conn.close();
      if ((count1 == 0) || (count2 == 0)) {
                    conn.rollback();
                } else {
                    conn.commit();
                    conn.setAutoCommit(true);
                ps.close();
                calstat2.close();
                conn.close();
    calstat = (CallableStatement) conn.prepareCall("{call findStudent}");
                calstat.executeQuery();
                calstat.close();
                conn.close();is that enought? what else I should do to make sure I did close all the connection, after I use it ?
    thank you

  • Can't close tab. Don't get an X in tab.ASSERT: Giving up waiting for the tab closing animation to finish (bug 608589) Stack Trace: 0:([object XULElement],[object XULElement],0)

    error msg: ASSERT: Giving up waiting for the tab closing animation to finish (bug 608589)
    Stack Trace:
    0:([object XULElement],[object XULElement],0)

    A work around is goto about:config
    toggle the following line so that it is set to false.
    browser.tabs.animate

  • How do i query the module object for the interface of the module-specific interface I require

    Hi there.
    Currently using LabVIEW 2012/TestStand 2012.
    I am attempting to edit the LabVIEW Text Sequence Translator, and in the CreateStep.vi I am trying to create a step that is of type WIS_Sequence_Call (a custom version of NI_Types.ini-->SequenceCall).
    I need to set the file pathname, sequence name and parameter values in the step.  I believe I need to get access to the SequenceCallModule class to do this.
    This help file SequenceCallModule states in the description: "To access the properties and methods of a specific module class, query the Module object for the interface of the module-specific interface you want to acquire.".
    What exactly is meant by "query" here?  It looks like "Specify" might be what I am after, but I want this done programmatically, ie no dialog boxes.
    See my snippet below.
    Thanks.

    Thanks for the reply Charles.
    I have been using the 2012 version of the poster.
    I can get access to the Module class from the Step Class as shown in the snippet above, but I can't see how to get to SequenceCallModule? The "To more specific class" VI doesn't seem to work for TS refs. Is there no way to derive the SequenceCallModule from this?
    Also I can use the TSAdp.SequenceCallModule reference, but I need to link this to the relevant step that I've just created.  Can NI please provide me with a link to any examples on this?
    Thanks

  • How do i query the module object for the interface of the module-spe​cific interface I require

    Hi there.
    Currently using LabVIEW 2012/TestStand 2012.
    I am attempting to edit the LabVIEW Text Sequence Translator, and in the CreateStep.vi I am trying to create a step that is of type WIS_Sequence_Call (a custom version of NI_Types.ini-->SequenceCall).
    I need to set the file pathname, sequence name and parameter values in the step.  I believe I need to get access to the SequenceCallModule class to do this.
    This help file SequenceCallModule states in the description: "To access the properties and methods of a specific module class, query the Module object for the interface of the module-specific interface you want to acquire.".
    What exactly is meant by "query" here?  It looks like "Specify" might be what I am after, but I want this done programmatically, ie no dialog boxes.
    See my snippet below.
    Thanks.
    Christopher Farmer
    Certified LabVIEW Architect
    Certified TestStand Developer
    http://wiredinsoftware.com.au
    Solved!
    Go to Solution.

    Thanks for the reply Charles.
    I have been using the 2012 version of the poster.
    I can get access to the Module class from the Step Class as shown in the snippet above, but I can't see how to get to SequenceCallModule? The "To more specific class" VI doesn't seem to work for TS refs. Is there no way to derive the SequenceCallModule from this?
    Also I can use the TSAdp.SequenceCallModule reference, but I need to link this to the relevant step that I've just created.  Can NI please provide me with a link to any examples on this?
    Thanks
    Christopher Farmer
    Certified LabVIEW Architect
    Certified TestStand Developer
    http://wiredinsoftware.com.au

  • Query on Using fork with wait for event

    Hi All,
    I have a scenario in which a fork has two branches and one branch has the multiple steps along the line and also calls a subworkflow in one of the steps.
    The second branch has a single wait for event to complete the workflow in case of a cancel event.
    My understanding is that when the branch one executes and is on a single step decision or have gone inside a subworkflow and wating for user decision on the workitem created
    Whenever the wait event is triggered on the main workflow the second branch gets executed completing the workflow and all the branch one steps and the subworkflow gets logically deleted removing all the workitem from the inbox.
    Do I have to do any specific process control in main workflow to make sure that the subworkflow is deleted .
    Please clarify on this.
    Thanks,
    Charan.

    It should be taken care by itself. No additional steps required.
    Regards, IA

  • Query with links to 'services for object'

    Hi everybody
    I need your help
    We have pictures (jpg, pdf, tif) linked to materials in material master (in transaction mm02 – services for object). Sometthing like this - but form materials:
    http://www.le.ac.uk/mis/docs/sapdocs/ug/UG5-1%20Services.doc
    We would like to create the "stock report" with links to these attachments. Can anyone tell me if it is possible to create these links in the report?
    I would like the report to look something like this:
    material_number1; stock1; link_to_picture_on_material_number1
    material_number2; stock2; link_to_picture_on_material_number2
    the user should be able to open the attached picture (if it exists) by clicking the link at each material number (even better if the pictures were already displayed in the report)
    Thank you very much in advance
    BR,
    Jana

    There are a number of classes with methods for accessing objects saved using services for object - look for classes starting CL_GOS*
    Help for GOS is available at
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/f5/e16f3a53dee246e10000000a11402f/frameset.htm">Generic Object Services (BC-SRV-GBT)</a>
    In your report you could link to the relevant code to display the image based on an event like at line selection / at user command or using hotspots or similar in an ALV based report
    Andrew

  • How to make my object to wait for server response

    Hi ,
    I need some one suggestions on thread concepts.
    First Let me know my scenario is fit for thread concept.
    is it possible then how I can reach to solution.
    I have scenario like
    I send a request to server and server is taking some time to process the request.
    if I am calling the method on server it showing no results bez i know server takes some time.
    for that my calling method has to be wait for some time.
    Thanks
    Babu H

    Hi ,
    Let me give more information about that between my java class and server
    i have the bridge library which is also written in other than java.
    for that i used the njawin tool make as java wrapper class and accessing the java wrapper class(Bridge Server).
    the java wrapper class has post_request and poll_response methods so that why i 'm using only these methods in my java class to access the server.
    exactly I don't which technology is resided in Brdige server and actual Server bez that has been developed some one.
    poll_respnse means server has posted the response to client.
    Thanks
    Babu H

  • Wait for MTTR advisory state object

    Hello I am running a snapshot in 10g and the MMon slave process is waiting for the MTTR advisory for over 2hrs now. Does anyone know what the issue is?

    If one takes the time to read the OP's question, you can see that he states the version: 10.1. Anyway, one can infer that the question is about 10g, since enq: WF - contention is a new 10g wait event.
    But I'm curious about this event too. None of my Milsap or Lewis books mentions it, and neither does the excellent Shee/Deshpande/Gopalakrishnan. The event does not merit a mention on Metalink, nor can you find it in the 10g or 11g online docs.
    According to the naming convention of other enqueue wait events, WF would be the type of lock that is being waited on. But I have never heard of a WF lock. What could it mean?
    All I can find out about this event is that it has one parameter, name|mode.
    I am seeing it in the context of running a SQL Tuning Set cursor cache capture operation. A quick cruise through DBA_HIST_SYSTEM_EVENT tells me that this event has (almost) never arisen before on my system.
    This is my first experience with STS, which is why I'm curious about new things that come my way. Is this event causing a problem? I'm not sure. It has only been experiencing about 8 seconds of wait per 10 minute snapshot since I started running my STS capture. Nobody is complaining, yet. But as they say, Knowledge is power.
    So does anyone have insight into this mysterious wait event?
    Thanks.

Maybe you are looking for

  • Why is the App Store telling me to repurchase apps?

    So, I recently got an iPad 2, and I was wanting to download some universal apps I had bought for my iPhone (GTA 3 and GarageBand, for example), but the app store is telling me that I need to buy the apps, again. My iPad is associated with the same Ap

  • Editable field gives wrong value in report.

    Hi, I have report with some editable fields. I am using apex_item for one editable select list. I gave functionality to update row by providing go button. when user clicks on go button, I sends page by using javascript dosubmit which updates values i

  • RMAN Restore From External System

    I have been asked to restore a database from a different company onto our system. I was given a CD with the RMAN backup that they took. It's the same Oracle 9i database and we are both on Windows 2003. I've never done a restore this way before. I wou

  • Apache Proxy Plug-in with multiple clusters?

    We are using the Apache Proxy Plug-in , the           basic question is if we can place multiple cluster           IP's in the same Location definition or do we have           to have a different definition for each cluster?           Currently we ha

  • Help recover a deleted calendar

    Deleted a calendar called "Master" in iCal because it was not syncing with Outlook properly.  Now it removed all entries from Outlook and I can't recover any files.  Can anyone help?  Unfortunately I can't click on "undo" as I made additional clicks.