What Plan to explain is better?

Dear Experts

I have a query which is almost similar to the query on the other but Query1 takes 530 milliseconds and 2 the query takes 370 milliseconds

Query with the explain plan command 1
SQL> select count(*) from (SELECT DISTINCT txitem1.account_id, txitem2.account_id, party.external_code,
  2                  mes.MESSAGE, txitem1.transfer_value, txheader.transfer_status,
  3                  txheader.service_type, txheader.transfer_date,
  4                  bank.embossing_name, txitem1.attr_1_value, txitem1.attr_2_value,
  5                  bank.created_on, mes.message_code
  6             FROM mtx_transaction_items txItem1, mtx_transaction_items txItem2,mbk_bank bank, mtx_transaction_header txHeader, mtx_party party,sys_messages mes,mtx_payment_methods pm
  7            WHERE txitem1.user_type = 'PAYEE'
  8              AND txitem2.user_type = 'PAYER'
  9              AND txheader.transfer_id = txitem1.transfer_id
 10              AND txitem1.transfer_id = txitem2.transfer_id
 11              AND txheader.service_type = 'FTOWN'
 12              AND TO_DATE(TO_CHAR(txHeader.transfer_Date,'DD/MM/YYYY'),'DD/MM/YYYY') BETWEEN TO_DATE ('01/01/2007', 'DD/MM/YYYY')
 13                                AND TO_DATE ('01/04/2009', 'DD/MM/YYYY')
 14              AND txitem1.party_id = party.user_id
 15              AND txitem1.account_id = bank.account_no
 16              AND mes.message_code = NVL (txheader.error_code, '200')
 17              AND mes.language_code = '01'
 18              AND pm.party_user_id = txitem1.party_id
 19              AND bank.account_no = pm.payment_method_number
 20               ORDER BY bank.created_on DESC);

  COUNT(*)
----------
     10382

Elapsed: 00:00:00.53

Execution Plan
----------------------------------------------------------
Plan hash value: 3804521013

----------------------------------------------------------------------------------------------------------------------------------------
| Id  | Operation                                     | Name                   | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
----------------------------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                              |                        |     1 |     2 |   123   (2)| 00:00:02 |       |       |
|   1 |  SORT AGGREGATE                               |                        |     1 |     2 |            |          |       |       |
|   2 |   VIEW                                        |                        |     1 |     2 |   123   (2)| 00:00:02 |       |       |
|   3 |    HASH UNIQUE                                |                        |     1 |   836 |   123   (2)| 00:00:02 |       |       |
|   4 |     TABLE ACCESS BY INDEX ROWID               | MTX_TRANSACTION_ITEMS  |     9 |   459 |     2   (0)| 00:00:01 |       |       |
|   5 |      NESTED LOOPS                             |                        |     1 |   836 |   122   (1)| 00:00:02 |       |       |
|   6 |       NESTED LOOPS                            |                        |     1 |   785 |   120   (1)| 00:00:02 |       |       |
|   7 |        NESTED LOOPS                           |                        |     1 |   764 |   119   (1)| 00:00:02 |       |       |
|*  8 |         HASH JOIN                             |                        |     1 |   482 |   118   (1)| 00:00:02 |       |       |
|*  9 |          HASH JOIN                            |                        |    45 | 19710 |   113   (1)| 00:00:02 |       |       |
|  10 |           TABLE ACCESS BY INDEX ROWID         | MTX_TRANSACTION_ITEMS  |     6 |  2004 |     2   (0)| 00:00:01 |       |       |
|  11 |            NESTED LOOPS                       |                        |    38 | 14288 |   104   (0)| 00:00:02 |       |       |
|* 12 |             TABLE ACCESS BY GLOBAL INDEX ROWID| MTX_TRANSACTION_HEADER |     6 |   252 |    97   (0)| 00:00:02 | ROWID | ROWID |
|* 13 |              INDEX RANGE SCAN                 | IDX_MTH_SERVICE_TYPE   |  2500 |       |    19   (0)| 00:00:01 |       |       |
|* 14 |             INDEX RANGE SCAN                  | SYS_C00162170          |     1 |       |     1   (0)| 00:00:01 |       |       |
|  15 |           TABLE ACCESS FULL                   | MBK_BANK               |   734 | 45508 |     8   (0)| 00:00:01 |       |       |
|  16 |          TABLE ACCESS FULL                    | MTX_PAYMENT_METHODS    |   734 | 32296 |     5   (0)| 00:00:01 |       |       |
|  17 |         TABLE ACCESS BY INDEX ROWID           | SYS_MESSAGES           |     1 |   282 |     1   (0)| 00:00:01 |       |       |
|* 18 |          INDEX UNIQUE SCAN                    | SYS_C00163912          |     1 |       |     0   (0)| 00:00:01 |       |       |
|  19 |        TABLE ACCESS BY INDEX ROWID            | MTX_PARTY              |     1 |    21 |     1   (0)| 00:00:01 |       |       |
|* 20 |         INDEX UNIQUE SCAN                     | SYS_C00161984          |     1 |       |     0   (0)| 00:00:01 |       |       |
|* 21 |       INDEX RANGE SCAN                        | SYS_C00162170          |     1 |       |     1   (0)| 00:00:01 |       |       |
----------------------------------------------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   8 - access("PM"."PARTY_USER_ID"="TXITEM1"."PARTY_ID" AND "BANK"."ACCOUNT_NO"="PM"."PAYMENT_METHOD_NUMBER")
   9 - access("TXITEM1"."ACCOUNT_ID"="BANK"."ACCOUNT_NO")
  12 - filter(TO_DATE(TO_CHAR(INTERNAL_FUNCTION("TXHEADER"."TRANSFER_DATE"),'DD/MM/YYYY'),'DD/MM/YYYY')>=TO_DATE('2007-01-01
              00:00:00', 'yyyy-mm-dd hh24:mi:ss') AND TO_DATE(TO_CHAR(INTERNAL_FUNCTION("TXHEADER"."TRANSFER_DATE"),'DD/MM/YYYY'),'DD/MM/YYYY'
              )<=TO_DATE('2009-04-01 00:00:00', 'yyyy-mm-dd hh24:mi:ss'))
  13 - access("TXHEADER"."SERVICE_TYPE"='FTOWN')
  14 - access("TXHEADER"."TRANSFER_ID"="TXITEM1"."TRANSFER_ID" AND "TXITEM1"."USER_TYPE"='PAYEE')
       filter("TXITEM1"."USER_TYPE"='PAYEE')
  18 - access("MES"."MESSAGE_CODE"=NVL("TXHEADER"."ERROR_CODE",'200') AND "MES"."LANGUAGE_CODE"=1)
  20 - access("TXITEM1"."PARTY_ID"="PARTY"."USER_ID")
  21 - access("TXITEM1"."TRANSFER_ID"="TXITEM2"."TRANSFER_ID" AND "TXITEM2"."USER_TYPE"='PAYER')
       filter("TXITEM2"."USER_TYPE"='PAYER')

Note
-----
   - dynamic sampling used for this statement


Statistics
----------------------------------------------------------
          0  recursive calls
          0  db block gets
      44092  consistent gets
          0  physical reads
          0  redo size
        413  bytes sent via SQL*Net to client
        385  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          1  rows processed
Query 2 with explain plan
SQL> select count(*) from (SELECT DISTINCT txitem1.account_id, txitem2.account_id, party.external_code,
  2                  mes.MESSAGE, txitem1.transfer_value, txheader.transfer_status,
  3                  txheader.service_type, txheader.transfer_date,
  4                  bank.embossing_name, txitem1.attr_1_value, txitem1.attr_2_value,
  5                  bank.created_on, mes.message_code
  6             FROM sys_messages mes,mbk_bank bank,mtx_party party,mtx_payment_methods pm,mtx_transaction_header txheader,mtx_transaction_items txitem1,
  7                  mtx_transaction_items txitem2
  8            WHERE  Trunc(txHeader.transfer_Date)  BETWEEN TO_DATE ('01/01/2007', 'DD/MM/YYYY')
  9              AND TO_DATE ('01/04/2009', 'DD/MM/YYYY')
 10         and txitem1.user_type = 'PAYEE'
 11              AND txitem2.user_type = 'PAYER'
 12              AND mes.language_code = '01'
 13              AND txheader.service_type = 'FTOWN'
 14         and txheader.transfer_id = txitem1.transfer_id
 15         AND txitem1.transfer_id = txitem2.transfer_id
 16              AND txitem1.party_id = party.user_id
 17              AND txitem1.account_id = bank.account_no
 18         AND bank.account_no = pm.payment_method_number
 19              AND mes.message_code = NVL (txheader.error_code, '200')
 20              AND pm.party_user_id = txitem1.party_id
 21              ORDER BY bank.created_on DESC);

  COUNT(*)
----------
     10382

Elapsed: 00:00:00.37

Execution Plan
----------------------------------------------------------
Plan hash value: 2305733494

--------------------------------------------------------------------------------------------------------------------------------------------
| Id  | Operation                                 | Name                   | Rows  | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Pstop |
--------------------------------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                          |                        |     1 |     2 |       |   344   (3)| 00:00:05 |   |        |
|   1 |  SORT AGGREGATE                           |                        |     1 |     2 |       |            |          |   |        |
|   2 |   VIEW                                    |                        |   251 |   502 |       |   344   (3)| 00:00:05 |   |        |
|   3 |    HASH UNIQUE                            |                        |   251 |   204K|   456K|   344   (3)| 00:00:05 |   |        |
|   4 |     TABLE ACCESS BY INDEX ROWID           | MTX_TRANSACTION_ITEMS  |     9 |   459 |       |     2   (0)| 00:00:01 |   |        |
|   5 |      NESTED LOOPS                         |                        |   251 |   204K|       |   296   (3)| 00:00:04 |   |        |
|*  6 |       HASH JOIN                           |                        |    29 | 22765 |       |   238   (3)| 00:00:03 |   |        |
|   7 |        NESTED LOOPS                       |                        |    29 | 14587 |       |   232   (3)| 00:00:03 |   |        |
|*  8 |         HASH JOIN                         |                        |    29 | 13369 |       |   203   (3)| 00:00:03 |   |        |
|*  9 |          HASH JOIN                        |                        |    29 | 12760 |       |   198   (3)| 00:00:03 |   |        |
|* 10 |           HASH JOIN                       |                        |   886 | 93916 |       |    14   (8)| 00:00:01 |   |        |
|  11 |            TABLE ACCESS FULL              | MTX_PAYMENT_METHODS    |   734 | 32296 |       |     5   (0)| 00:00:01 |   |        |
|  12 |            TABLE ACCESS FULL              | MBK_BANK               |   734 | 45508 |       |     8   (0)| 00:00:01 |   |        |
|* 13 |           TABLE ACCESS FULL               | MTX_TRANSACTION_ITEMS  | 14429 |  4706K|       |   183   (2)| 00:00:03 |   |        |
|  14 |          TABLE ACCESS FULL                | MTX_PARTY              |   468 |  9828 |       |     5   (0)| 00:00:01 |   |        |
|* 15 |         TABLE ACCESS BY GLOBAL INDEX ROWID| MTX_TRANSACTION_HEADER |     1 |    42 |       |     1   (0)| 00:00:01 | ROWID | ROWID |
|* 16 |          INDEX UNIQUE SCAN                | SYS_C00166115          |     1 |       |       |     0   (0)| 00:00:01 |   |        |
|* 17 |        TABLE ACCESS FULL                  | SYS_MESSAGES           |   253 | 71346 |       |     5   (0)| 00:00:01 |   |        |
|* 18 |       INDEX RANGE SCAN                    | SYS_C00162170          |     1 |       |       |     1   (0)| 00:00:01 |   |        |
--------------------------------------------------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   6 - access("MES"."MESSAGE_CODE"=NVL("TXHEADER"."ERROR_CODE",'200'))
   8 - access("TXITEM1"."PARTY_ID"="PARTY"."USER_ID")
   9 - access("TXITEM1"."ACCOUNT_ID"="BANK"."ACCOUNT_NO" AND "PM"."PARTY_USER_ID"="TXITEM1"."PARTY_ID")
  10 - access("BANK"."ACCOUNT_NO"="PM"."PAYMENT_METHOD_NUMBER")
  13 - filter("TXITEM1"."USER_TYPE"='PAYEE')
  15 - filter("TXHEADER"."SERVICE_TYPE"='FTOWN' AND TRUNC(INTERNAL_FUNCTION("TXHEADER"."TRANSFER_DATE"))>=TO_DATE('2007-01-01
              00:00:00', 'yyyy-mm-dd hh24:mi:ss') AND TRUNC(INTERNAL_FUNCTION("TXHEADER"."TRANSFER_DATE"))<=TO_DATE('2009-04-01 00:00:00',
              'yyyy-mm-dd hh24:mi:ss'))
  16 - access("TXHEADER"."TRANSFER_ID"="TXITEM1"."TRANSFER_ID")
  17 - filter("MES"."LANGUAGE_CODE"=1)
  18 - access("TXITEM1"."TRANSFER_ID"="TXITEM2"."TRANSFER_ID" AND "TXITEM2"."USER_TYPE"='PAYER')
       filter("TXITEM2"."USER_TYPE"='PAYER')

Note
-----
   - dynamic sampling used for this statement


Statistics
----------------------------------------------------------
          0  recursive calls
          0  db block gets
      48293  consistent gets
          0  physical reads
          0  redo size
        413  bytes sent via SQL*Net to client
        385  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          1  rows processed
Here I am confused explain query plan 1 seems better but performace wise query 2 is better. Please, help me choose the best query.

Thanks and greetings
Saurabh Sharma

Egovcoe_In wrote:
Thanks BluShadow

I executed the following command and I got the same execution plan for both queries, but again time required differs

exec DBMS_Stats.Gather_Schema_Stats('BROWSER_UAT', estimate_percent => 10, degree=> 6,cascade => true);

If you gathered stats. Large.
What to clear the memory cache and also given that Randolf said above.

The reason why I m worried about MS is I want to write a query to listen for in the circumstances. I read a lot of material on query tuning n somewhere it is written order of the tables in the clause and order of conditions in where would adopt when we use the CBO but somewhere it is written that it affects.

The order of tables and where clauses are unlikely to have any impact on performance (unless you write really bad SQL with a lot of subqueries, nested etc) as the CBO will optimize the query to join the tables and filter records in the best conditions, according to the statistics that he knows the tables. So no matter if you join A before B from B to C in your syntax or C to B, then B to A. It will 99% of the time has come out with the same execution plan.

A matter of milliseconds is nothing and can easily vary from a running query to another, even if the query does not change. Things that can affect the duration of this small amount are things like the disk IO and network traffic and the speed with which the application of the 'front end' can retrieve and display information (which could be slowed by other applications).

WHERE CAN I FIND INFORMATION OF PERFECT WRITING SQL QUERY?

If there is information written for the perfect SQL queries then it would be have been developed in the SQL engine and the optimizer so that any query could be rewritten automatically, or the SQL engine could report to you what changes you must make to improve your query.

A perfect SQL query is simply one that returns the correct data in a period, accounting for a reasonable future data growth.

Tags: Database

Similar Questions

  • What is this new SQL Beta - 1z1 - 071 - 2 SQL - Oracle Database SQL 12 c

    Hello

    It's confusing.

    This looks like a 2nd review SQL for Oracle 12 c.

    What is this new SQL Beta - 1z1 - 071 - 2 SQL - Oracle Database SQL 12 c

    Can someone explain.

    Roger

    OK - I guess I should have held off a few hours before my previous answer.  I just got an email in the Certification of Oracle program manager. Now, I have inside information.

    1Z0-071 is a SQL new test and the role it plays is between that of the review of databases SQL and SQL Expert.  Specifically, unlike review of databases SQL, passing it will give proof of the OCA for people who spend. I don't know more than that yet.  The review details page is not available and if the subjects are currently a grey area for me.  I'll probably create a blog on the review, if I can get a few details about it.

  • How to make a Plan to explain on PL - SQL?

    Hey guys, it's Xev, I'm back with a whole new positive attitude . I am very happy now that I got my cluster (11.2) 2-node RAC 11 GR 2 installed and working properly

    I'm doing a plan to explain some pl - sql, I wrote, but I'm having a hard time trying to figure out how to make it work.

    The catplan.sql has been performed and I a plan_table ready and waiting for me.

    Here's the full code as well as the two tables table that I use, just as I'm supposed to display.

    This is the first table

    and Yes, I only want a single folder in there...

    CREATE TABLE FILLER

    ("DATA_PACKED" VARCHAR2 (75 BYTE)

    )

    Insert in FILLING (DATA_PACKED) values ('KICKKKKKKKKK');

    commit;

    Then at the top on the list is the table of the HAMMER, I will insert all the data once the pl/sql program runs...

    This table is supposed to be empty...

    CREATE TABLE HAMMER

    ('H1' VARCHAR2 (100 BYTE),

    "H2" VARCHAR2 (100 BYTE)

    )

    and now, the CODE... Now, it is a very small version of my load of GR 11, 2 test scripts that I wrote, but I need to see execution plan behind this logic.

    I can even make a plan to explain on this code, or do I have to use something else?

    ---------------------------------------------------------------------------------------------------------

    declare

    Table type is table of the varchar2 (30) index directory.

    Table Z_STUFF.

    Start

    Select * BULK COLLECT into Z_STUFF of filling;

    because me in 1... 100

    loop

    for zoo in 1... Z_STUFF. Count

    loop

    Insert into HAMMER (H1, H2)

    values (Z_STUFF (zoo), Z_STUFF (zoo));

    end loop;

    end loop;

    end;

    /

    ----------------------------------------------------------------------------------------------------

    All comments are welcome, I just need to see what makes this logic behind the scenes...

    Thank you

    Xev.

    A query plan refers to an SQL statement.  A PL/SQL block can have 0 or more SQL statements.  It is, therefore, unnecessary to speak to generate a query plan for a PL/SQL block.  Your PL/SQL block happens to contain two different SQL statements.  You might get two different query plans, one for each statement.  Given how trivial statements are, however, I'm not sure that query plans would give you a lot of information.

    What is the problem you're trying to solve?  If you try to set the PL/SQL, you probably want to look into various profilers of PL/SQL.  For example, the DBMS_PROFILER package or the package DBMS_HPROF.

    Justin

  • plan_table is necessary so that a plan to explain?

    Hi, I noticed that a plan to explain to a query can be obtained by defining autotrace on. However, when I get a result of the autotrace, it shows no record in the plan_table table. I just want to check with others to ensure that it is clear that a plan_table table is not necessary to obtain a plan for a query to explain. I also noticed that when I hit the button explain plan in sql developer, there is no record in the plan_table table.

    arizona9952 wrote:
    Hi, I noticed that a plan to explain to a query can be obtained by defining autotrace on. However, when I get a result of the autotrace, it shows no record in the plan_table table. I just want to check with others to ensure that it is clear that a plan_table table is not necessary to obtain a plan for a query to explain. I also noticed that when I hit the button explain plan in sql developer, there is no record in the plan_table table.

    What is your version of sql developer? If it's 3.0 cancellations, then the developer sql lines after extraction of the plan for the display. If you must rely on the result Autotrace or Plan to explain tabs.

    Similar description below thread:
    Choose specific SQL Developer 2 plan_table +?

    Concerning
    Girish Sharma

  • filter (NULL IS NOT NULL) plan to explain?

    Hi all

    Can someone please explain what this explain plan statement means? I see a (NULL IS NOT NULL) filter as first statement - could not understand why it came so Googling.

    My query is used:
    EXPLAIN PLAN FOR
    MERGE INTO summary_bysrccd
    USING
    (SELECT LAST_DAY(TRUNC(to_timestamp(os.requestdatetime, 'yyyymmddhh24:mi:ss.ff4'))) AS SUMMARY_DATE,
    os.acctnum,
    ol.sourcecode AS sourcecode,
    ol.sourcename AS sourcename,
    count(1) cnt_articleview
    FROM article_views os , master_sourcecode ol
    where os.sourcecode = ol.sourcecode
    AND os.acctnum IS NOT NULL
    AND ol.sourcecode IS NOT NULL
    AND os.requestdatetime IS NOT NULL
    AND UPPER(os.success_ind) = 'S'
         AND (
              ('INCR'  = 'FULL'
              AND  (get_date_timestamp(os.requestdatetime) BETWEEN TO_DATE('23-AUG-2011 00:00:00','DD-MON-YYYY HH24:MI:SS') AND TO_DATE('27-AUG-2011 23:59:59','DD-MON-YYYY HH24:MI:SS')
              AND   os.entry_CreatedDate BETWEEN TO_DATE('22-AUG-2011 00:00:00','DD-MON-YYYY HH24:MI:SS') AND TO_DATE('28-AUG-2011 00:00:00','DD-MON-YYYY HH24:MI:SS')
              ))
              OR ('INCR' = 'FULL'
              AND os.entry_createddate BETWEEN TO_DATE('23-AUG-2011 00:00:00','DD-MON-YYYY HH24:MI:SS') AND TO_DATE('27-AUG-2011 23:59:59','DD-MON-YYYY HH24:MI:SS') )
         )
    group by LAST_DAY(TRUNC(to_timestamp(os.requestdatetime, 'yyyymmddhh24:mi:ss.ff4'))),
    os.acctnum,ol.sourcecode,ol.sourcename) mrg_query
    ON (ods_av_summary_bysrccd.acctnum = mrg_query.acctnum AND
    ods_av_summary_bysrccd.summary_date=mrg_query.summary_date AND
    ods_av_summary_bysrccd.sourcecode=mrg_query.sourcecode)
    WHEN NOT MATCHED THEN
    INSERT (SUMMARY_date,ACCTNUM,SOURCECODE,SOURCENAME,CNT_ARTICLEVIEW,ENTRY_LASTUPDATEDDATE)
    VALUES(mrg_query.summary_date,mrg_query.acctnum,mrg_query.sourcecode,mrg_query.sourcename,
    mrg_query.cnt_articleview,sysdate)
    WHEN MATCHED THEN
    UPDATE SET ods_av_summary_bysrccd.cnt_articleview=
    CASE WHEN NVL('INCR','INCR') = 'FULL' THEN mrg_query.cnt_articleview
    ELSE ods_av_summary_bysrccd.cnt_articleview+mrg_query.cnt_articleview
    END,
    ods_av_summary_bysrccd.entry_lastupdateddate=sysdate;
    My Plan to explain:
    SQL> select * from table(dbms_xplan.display);
    
    PLAN_TABLE_OUTPUT
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Plan hash value: 268591246
    
    -----------------------------------------------------------------------------------------------------------------------------------------------
    | Id  | Operation                                 | Name                      | Rows  | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Pstop |
    -----------------------------------------------------------------------------------------------------------------------------------------------
    |   0 | MERGE STATEMENT                           |                           |     1 |   456 |       |     3   (0)| 00:00:01 |       |       |
    |   1 |  MERGE                                    | ODS_AV_SUMMARY_BYSRCCD    |       |       |       |            |          |       |       |
    |   2 |   VIEW                                    |                           |       |       |       |            |          |       |       |
    |   3 |    NESTED LOOPS OUTER                     |                           |     1 |   417 |       |     3   (0)| 00:00:01 |       |       |
    |   4 |     VIEW                                  |                           |     1 |   360 |       |     5 (100)| 00:00:01 |       |       |
    |   5 |      SORT GROUP BY                        |                           |     1 |    73 |   595M|            |          |       |       |
    
    PLAN_TABLE_OUTPUT
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    |*  6 |       FILTER                              |                           |       |       |       |            |          |       |       |
    |*  7 |        HASH JOIN                          |                           |  6975K|   485M|  3944K| 17594   (1)| 00:03:32 |       |       |
    |   8 |         TABLE ACCESS FULL                 | ODS_MASTER_SOURCECODE     | 84021 |  2953K|       |   273   (1)| 00:00:04 |       |       |
    |*  9 |         TABLE ACCESS BY GLOBAL INDEX ROWID| ODS_ARTICLE_VIEWS         |  7007K|   247M|       |   826   (0)| 00:00:10 |    33 |    33 |
    |* 10 |          INDEX FULL SCAN                  | IDX_AV_ACCTNUM            |    25M|       |       |    26   (0)| 00:00:01 |       |       |
    |  11 |     TABLE ACCESS BY GLOBAL INDEX ROWID    | ODS_AV_SUMMARY_BYSRCCD    |     1 |    57 |       |     3   (0)| 00:00:01 | ROWID | ROWID |
    |* 12 |      INDEX UNIQUE SCAN                    | ODS_AV_SUMMARY_BYSRCCD_PK |     1 |       |       |     2   (0)| 00:00:01 |       |       |
    -----------------------------------------------------------------------------------------------------------------------------------------------
    
    Predicate Information (identified by operation id):
    ---------------------------------------------------
    
    PLAN_TABLE_OUTPUT
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    
       6 - filter(NULL IS NOT NULL)
       7 - access("OS"."SOURCECODE"="OL"."SOURCECODE")
       9 - filter("OS"."REQUESTDATETIME" IS NOT NULL AND "OS"."ENTRY_CREATEDDATE">=TO_DATE(' 2011-08-23 00:00:00', 'syyyy-mm-dd
                  hh24:mi:ss') AND "OS"."ENTRY_CREATEDDATE"<=TO_DATE(' 2011-08-27 23:59:59', 'syyyy-mm-dd hh24:mi:ss') AND UPPER("OS"."SUCCESS_IND")='S')
      10 - filter("OS"."ACCTNUM" IS NOT NULL)
      12 - access("ODS_AV_SUMMARY_BYSRCCD"."SUMMARY_DATE"(+)=INTERNAL_FUNCTION("MRG_QUERY"."SUMMARY_DATE") AND
                  "ODS_AV_SUMMARY_BYSRCCD"."ACCTNUM"(+)="MRG_QUERY"."ACCTNUM" AND "ODS_AV_SUMMARY_BYSRCCD"."SOURCECODE"(+)="MRG_QUERY"."SOURCECODE")
    
    Note
    -----
    
    PLAN_TABLE_OUTPUT
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
       - dynamic sampling used for this statement

    This filter appears usually when the CBO has found a conflict between your predicates WHERE clause and declarative constraints on the tables involved.

    For example, suppose that the EMP table had this constraint:

    CHECK(empno > 0)
    

    And you were to interrogate the EMP with this query:

    select *
    from emp
    where empno <  0
    

    You will find that the NULL value is NOT NULL filter in the execution plan.

  • When I connect to Facebook, everything is huge. What have I done? Better yet how can I fix it? HP DV6 Pav

    When I connect to Facebook, everything is huge. What have I done? Better yet how can I fix it? HP Pav DV

    Try and clickCtr and to reduce it and see if that helps. CTRL it dilates. CTRL should reset back to normal

    In addition, if you have a wheel mouse, you can click Ctrl while you scroll the wheel to change the zoom

  • What plan should I buy?

    I need only PS, Dw and Acrobat pro, I don't need all of the CC programs. What plan should I buy?

    There is no specific plan for this combination. Just buy the full CC.

    Mylenium

  • Should what plan I choose?

    Should what plan I choose?  I am a photographer non-profit looking to change my photos.  I only use lightroom and bridge, NOT photoshop.  I will buy as an "individual".  Photography package for looks good, but I didn't see listed bridge.  I ' n not trying to pay more $ $20 per month.  Any help is appreciated, and once more the BRIDGE and LIGHTROOM are required.  Thank you.

    Hi Braden,

    IF you purchase the plan of photography for $9.99 / month, this will include photoshop lightroom and bridge, so you can get this plan.

    See also:-fact Adobe Bridge come with creative photography Plan Cloud?

    For Plans: CC price and membership plans | Adobe Creative Cloud

  • Hi, I'm on cloud creative $49.99 for the month of subscription and I am told it includes Typekit, but when I try to log it asks what plan I want to?

    Hi, I'm on cloud creative $49.99 for the month of subscription and I am told it includes Typekit, but when I try to log it asks what plan I want to?

    Please see

    Hope this will help you to use typekit.

    Kind regards

    Hervé Khare

  • I need flash builder. What plan should I choose?

    I need flash builder. What plan should I choose? I need iosmetric engine too

    FB is a separate product, not associated with any plan of cloud.

    Mylenium

  • What plan I currently have.  I think that the credit card has expired.

    I don't remember what plan I had

    You have an incomplete CC of edition Creative Cloud schoolgirl and her teacher, the payment is not yet spent.

    Concerning

    Baudier

  • How keep the formatting of a plan to explain in the forum.

    Hi all

    I would like to know how to keep the formatting of a plan to explain in the new forum. I used to use {} code in the old forum, but it no longer works. I used '-' in the new forum, but apparently not worked either.

    An example would be greatly appreciated!

    Thank you very much.

    You can try to use the font "Courier New" for the explain plan command part. That would make it readable.

    HTH,

    Joy

  • What plans are available for the use of the storage cloud at adobe. What is the authorized space if I free plan.

    What plans are available for the use of the storage cloud at adobe. What is the authorized space if I free plan.

    Thank you

    Agoutin

    Hi rajthkr,

    Acrobat.com offers free online storage for up to 5 GB of data (there are on the plans at this time to provide additional storage for a fee).

    Best,

    Sara

  • What Plan of observations

    Hello

    Currently I have membership creative cloud and I believe that the BC plan, it comes with is Webbasics, I don't have that Webforms and 1 another option.

    What plan BC I need access comments?  I checked the front page of pricing in British Colombia, but I see nothing definitive about the 'comments '.

    Thanks in advance

    Michel

    Hello

    You will need at least a Web marketing plan or higher.  Two webBasic plans offer no comments module.

    For more details on which features are included in each plan, please see below.

    - http://helpx.adobe.com/business-catalyst/kb/detailed-plan-breakdown.html

    I hope this helps!

    -Sidney

  • What Plan does the creative cloud comes with?

    The creative cloud says he understands 5 sites hosted in British Colombia. is nayone knows what plan are these sites? webBasic? Web marketing?

    Web Basics... the lowest plan available.

Maybe you are looking for