Why is LOWER function producing a cartesian merge join, when UPPER doesn't?

Hi there,
I have an odd scenario that I would like to understand correctly...
We have a query that is taking a long time to run on one of our databases, further investigation of the explain plan showed that the query was in fact producing a Cartesian merge join even though there is clearly join criteria specified. I know that the optimiser can and will do this if it is a more efficient way of producing the results, however in this scenario it is producing the Cartesian merge on two unrelated tables and seemingly ignoring the Join condition...
*** ORIGINAL QUERY ***
SELECT count(*)
FROM    srs_sce sce,
            srs_scj scj,
            men_mre mre,
            srs_mst mst,
            cam_smo cam,
            ins_spr spr,
            men_mua mua,
           temp_webct_users u
WHERE sce.sce_scjc = scj.scj_code
AND sce.sce_stuc = mre.mre_code
AND mst.mst_code = mre.mre_mstc
AND mre.mre_mrcc = 'STU'
AND mst.mst_code = mua.mua_mstc
AND cam.ayr_code = sce.sce_ayrc
AND cam.spr_code = scj.scj_sprc
AND spr.spr_code = scj.scj_sprc
-- Ignored Join Condition
AND LOWER(mua.mua_extu) = LOWER(u.login)
AND SUBSTR (sce.sce_ayrc, 1, 4) = '2008'
AND sce.sce_stac IN ('RCE', 'RLL', 'RPD', 'RIN', 'RSAS', 'RHL_R', 'RCO', 'RCI', 'RCA');
*** CARTESIAN EXPLAIN PLAN ***
SELECT STATEMENT  CHOOSECost: 83                                               
     20 NESTED LOOPS  Cost: 83  Bytes: 176  Cardinality: 1                                          
          18 NESTED LOOPS  Cost: 82  Bytes: 148  Cardinality: 1                                     
               15 NESTED LOOPS  Cost: 80  Bytes: 134  Cardinality: 1                                
                    13 NESTED LOOPS  Cost: 79  Bytes: 123  Cardinality: 1                           
                         10 NESTED LOOPS  Cost: 78  Bytes: 98  Cardinality: 1                      
                              7 NESTED LOOPS  Cost: 77  Bytes: 74  Cardinality: 1                 
NOTE: The Cartesian product is performed on the men_mre & temp_webct_users tables not the men_mua mua & temp_webct_users tables specified in the join condition.
                                   4 MERGE JOIN CARTESIAN  Cost: 74  Bytes: 32  Cardinality: 1            
                                        1 TABLE ACCESS FULL EXETER.TEMP_WEBCT_USERS Cost: 3  Bytes: 6  Cardinality: 1       
                                        3 BUFFER SORT  Cost: 71  Bytes: 1,340,508  Cardinality: 51,558       
                                             2 TABLE ACCESS FULL SIPR.MEN_MRE Cost: 71  Bytes: 1,340,508  Cardinality: 51,558 
                                   6 TABLE ACCESS BY INDEX ROWID SIPR.SRS_SCE Cost: 3  Bytes: 42  Cardinality: 1            
                                        5 INDEX RANGE SCAN SIPR.SRS_SCEI3 Cost: 2  Cardinality: 3       
                              9 TABLE ACCESS BY INDEX ROWID SIPR.SRS_SCJ Cost: 1  Bytes: 24  Cardinality: 1                 
                                   8 INDEX UNIQUE SCAN SIPR.SRS_SCJP1 Cardinality: 1            
                         12 TABLE ACCESS BY INDEX ROWID SIPR.INS_SPR Cost: 1  Bytes: 25  Cardinality: 1                      
                              11 INDEX UNIQUE SCAN SIPR.INS_SPRP1 Cardinality: 1                 
                    14 INDEX UNIQUE SCAN SIPR.SRS_MSTP1 Cost: 1  Bytes: 11  Cardinality: 1                           
               17 TABLE ACCESS BY INDEX ROWID SIPR.MEN_MUA Cost: 2  Bytes: 14  Cardinality: 1                                
                    16 INDEX RANGE SCAN SIPR.MEN_MUAI3 Cost: 2  Cardinality: 1                           
          19 INDEX RANGE SCAN SIPR.CAM_SMOP1 Cost: 2  Bytes: 28  Cardinality: 1                                     After speaking with data experts I realised one of the fields being LOWERed for the join condition generally always had uppercase values so I tried modifying the query to use the UPPER function rather than the LOWER one originally used, in this scenario the query executed in seconds and the Cartesian merge had been eradicated which by all accounts is a good result.
*** WORKING QUERY ***
SELECT count(*)
  FROM srs_sce sce,
       srs_scj scj,
       men_mre mre,
       srs_mst mst,
       cam_smo cam,
       ins_spr spr,
       men_mua mua,
       temp_webct_users u
WHERE sce.sce_scjc = scj.scj_code
   AND sce.sce_stuc = mre.mre_code
   AND mst.mst_code = mre.mre_mstc
   AND mre.mre_mrcc = 'STU'
   AND mst.mst_code = mua.mua_mstc
   AND cam.ayr_code = sce.sce_ayrc
   AND cam.spr_code = scj.scj_sprc
   AND spr.spr_code = scj.scj_sprc
-- Working Join Condition
   AND UPPER(mua.mua_extu) = UPPER(u.login)
   AND SUBSTR (sce.sce_ayrc, 1, 4) = '2008'
   AND sce.sce_stac IN ('RCE', 'RLL', 'RPD', 'RIN', 'RSAS', 'RHL_R', 'RCO', 'RCI', 'RCA');
*** WORKING EXPLAIN PLAN ***
SELECT STATEMENT  CHOOSECost: 13                                                    
     20 SORT AGGREGATE  Bytes: 146  Cardinality: 1                                               
          19 NESTED LOOPS  Cost: 13  Bytes: 146  Cardinality: 1                                          
               17 NESTED LOOPS  Cost: 12  Bytes: 134  Cardinality: 1                                     
                    15 NESTED LOOPS  Cost: 11  Bytes: 115  Cardinality: 1                                
                         12 NESTED LOOPS  Cost: 10  Bytes: 91  Cardinality: 1                           
                              9 NESTED LOOPS  Cost: 7  Bytes: 57  Cardinality: 1                      
                                   6 NESTED LOOPS  Cost: 6  Bytes: 31  Cardinality: 1                 
                                        4 NESTED LOOPS  Cost: 5  Bytes: 20  Cardinality: 1            
                                             1 TABLE ACCESS FULL EXETER.TEMP_WEBCT_USERS Cost: 3  Bytes: 6  Cardinality: 1       
                                             3 TABLE ACCESS BY INDEX ROWID SIPR.MEN_MUA Cost: 2  Bytes: 42  Cardinality: 3       
                                                  2 INDEX RANGE SCAN EXETER.TEST Cost: 1  Cardinality: 1 
                                        5 INDEX UNIQUE SCAN SIPR.SRS_MSTP1 Cost: 1  Bytes: 11  Cardinality: 1            
                                   8 TABLE ACCESS BY INDEX ROWID SIPR.MEN_MRE Cost: 2  Bytes: 26  Cardinality: 1                 
                                        7 INDEX RANGE SCAN SIPR.MEN_MREI2 Cost: 2  Cardinality: 1            
                              11 TABLE ACCESS BY INDEX ROWID SIPR.SRS_SCE Cost: 3  Bytes: 34  Cardinality: 1                      
                                   10 INDEX RANGE SCAN SIPR.SRS_SCEI3 Cost: 2  Cardinality: 3                 
                         14 TABLE ACCESS BY INDEX ROWID SIPR.SRS_SCJ Cost: 1  Bytes: 24  Cardinality: 1                           
                              13 INDEX UNIQUE SCAN SIPR.SRS_SCJP1 Cardinality: 1                      
                    16 INDEX RANGE SCAN SIPR.CAM_SMOP1 Cost: 2  Bytes: 19  Cardinality: 1                                
               18 INDEX UNIQUE SCAN SIPR.INS_SPRP1 Bytes: 12  Cardinality: 1                                     *** RESULT ***
COUNT(*)
83299I am still struggling to understand why this would have worked as to my knowledge the LOWER & UPPER functions are similar enough in function and regardless of that why would one version cause the optimiser to effectively ignore a join condition.
If anyone can shed any light on this for me it would be very much appreciated.
Regards,
Kieron
Edited by: Kieron_Bird on Nov 19, 2008 6:09 AM
Edited by: Kieron_Bird on Nov 19, 2008 6:41 AM

My mistake on the predicate information, was in a rush to run off to a meeting when I posted the entry...
*** UPPER Version of the Explain Plan ***
| Id  | Operation                     |  Name             | Rows  | Bytes | Cost  |  TQ    |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT              |                   |     1 |   146 |   736 |        |      |            |
|   1 |  SORT AGGREGATE               |                   |     1 |   146 |       |        |      |            |
|   2 |   SORT AGGREGATE              |                   |     1 |   146 |       | 86,10  | P->S | QC (RAND)  |
|*  3 |    HASH JOIN                  |                   |   241 | 35186 |   736 | 86,10  | PCWP |            |
|*  4 |     HASH JOIN                 |                   |   774 |   105K|   733 | 86,09  | P->P | HASH       |
|*  5 |      HASH JOIN                |                   | 12608 |  1489K|   642 | 86,08  | P->P | BROADCAST  |
|   6 |       NESTED LOOPS            |                   | 14657 |  1531K|   491 | 86,07  | P->P | HASH       |
|*  7 |        HASH JOIN              |                   | 14657 |  1359K|   490 | 86,07  | PCWP |            |
|*  8 |         HASH JOIN             |                   | 14371 |   996K|   418 | 86,06  | P->P | HASH       |
|*  9 |          TABLE ACCESS FULL    | SRS_SCE           |  3211 |   106K|   317 | 86,00  | S->P | BROADCAST  |
|* 10 |          HASH JOIN            |                   | 52025 |  1879K|   101 | 86,06  | PCWP |            |
|* 11 |           TABLE ACCESS FULL   | MEN_MRE           | 51622 |  1310K|    71 | 86,01  | S->P | HASH       |
|  12 |           INDEX FAST FULL SCAN| SRS_MSTP1         |   383K|  4119K|    30 | 86,05  | P->P | HASH       |
|  13 |         TABLE ACCESS FULL     | SRS_SCJ           |   114K|  2672K|    72 | 86,02  | S->P | HASH       |
|* 14 |        INDEX UNIQUE SCAN      | INS_SPRP1         |     1 |    12 |       | 86,07  | PCWP |            |
|  15 |       TABLE ACCESS FULL       | MEN_MUA           |   312K|  4268K|   151 | 86,03  | S->P | HASH       |
|  16 |      INDEX FAST FULL SCAN     | CAM_SMOP1         |   527K|  9796K|    91 | 86,09  | PCWP |            |
|  17 |     TABLE ACCESS FULL         | TEMP_WEBCT_USERS  | 33276 |   194K|     3 | 86,04  | S->P | HASH       |
Predicate Information (identified by operation id):
   3 - access(UPPER("MUA"."MUA_EXTU")=UPPER("U"."LOGIN"))
   4 - access("CAM"."AYR_CODE"="SCE"."SCE_AYRC" AND "CAM"."SPR_CODE"="SCJ"."SCJ_SPRC")
   5 - access("MST"."MST_CODE"="MUA"."MUA_MSTC")
   7 - access("SCE"."SCE_SCJC"="SCJ"."SCJ_CODE")
   8 - access("SCE"."SCE_STUC"="MRE"."MRE_CODE")
   9 - filter(SUBSTR("SCE"."SCE_AYRC",1,4)='2008' AND ("SCE"."SCE_STAC"='RCA' OR "SCE"."SCE_STAC"='RCE' OR
              "SCE"."SCE_STAC"='RCI' OR "SCE"."SCE_STAC"='RCO' OR "SCE"."SCE_STAC"='RHL_R' OR "SCE"."SCE_STAC"='RIN' OR
              "SCE"."SCE_STAC"='RLL' OR "SCE"."SCE_STAC"='RPD' OR "SCE"."SCE_STAC"='RSAS'))
  10 - access("MST"."MST_CODE"="MRE"."MRE_MSTC")
  11 - filter("MRE"."MRE_MRCC"='STU')
  14 - access("SPR"."SPR_CODE"="SCJ"."SCJ_SPRC")
Note: cpu costing is off
40 rows selected.*** LOWER Version of the Explain Plan ***
| Id  | Operation                     |  Name             | Rows  | Bytes | Cost  |  TQ    |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT              |                   |     1 |   146 |   736 |        |      |            |
|   1 |  SORT AGGREGATE               |                   |     1 |   146 |       |        |      |            |
|   2 |   SORT AGGREGATE              |                   |     1 |   146 |       | 88,10  | P->S | QC (RAND)  |
|*  3 |    HASH JOIN                  |                   |   257K|    35M|   736 | 88,10  | PCWP |            |
|*  4 |     HASH JOIN                 |                   |   774 |   105K|   733 | 88,09  | P->P | HASH       |
|*  5 |      HASH JOIN                |                   | 12608 |  1489K|   642 | 88,08  | P->P | BROADCAST  |
|   6 |       NESTED LOOPS            |                   | 14657 |  1531K|   491 | 88,07  | P->P | HASH       |
|*  7 |        HASH JOIN              |                   | 14657 |  1359K|   490 | 88,07  | PCWP |            |
|*  8 |         HASH JOIN             |                   | 14371 |   996K|   418 | 88,06  | P->P | HASH       |
|*  9 |          TABLE ACCESS FULL    | SRS_SCE           |  3211 |   106K|   317 | 88,00  | S->P | BROADCAST  |
|* 10 |          HASH JOIN            |                   | 52025 |  1879K|   101 | 88,06  | PCWP |            |
|* 11 |           TABLE ACCESS FULL   | MEN_MRE           | 51622 |  1310K|    71 | 88,01  | S->P | HASH       |
|  12 |           INDEX FAST FULL SCAN| SRS_MSTP1         |   383K|  4119K|    30 | 88,05  | P->P | HASH       |
|  13 |         TABLE ACCESS FULL     | SRS_SCJ           |   114K|  2672K|    72 | 88,02  | S->P | HASH       |
|* 14 |        INDEX UNIQUE SCAN      | INS_SPRP1         |     1 |    12 |       | 88,07  | PCWP |            |
|  15 |       TABLE ACCESS FULL       | MEN_MUA           |   312K|  4268K|   151 | 88,03  | S->P | HASH       |
|  16 |      INDEX FAST FULL SCAN     | CAM_SMOP1         |   527K|  9796K|    91 | 88,09  | PCWP |            |
|  17 |     TABLE ACCESS FULL         | TEMP_WEBCT_USERS  | 33276 |   194K|     3 | 88,04  | S->P | HASH       |
Predicate Information (identified by operation id):
   3 - access(LOWER("MUA"."MUA_EXTU")=LOWER("U"."LOGIN"))
   4 - access("CAM"."AYR_CODE"="SCE"."SCE_AYRC" AND "CAM"."SPR_CODE"="SCJ"."SCJ_SPRC")
   5 - access("MST"."MST_CODE"="MUA"."MUA_MSTC")
   7 - access("SCE"."SCE_SCJC"="SCJ"."SCJ_CODE")
   8 - access("SCE"."SCE_STUC"="MRE"."MRE_CODE")
   9 - filter(SUBSTR("SCE"."SCE_AYRC",1,4)='2008' AND ("SCE"."SCE_STAC"='RCA' OR "SCE"."SCE_STAC"='RCE' OR
              "SCE"."SCE_STAC"='RCI' OR "SCE"."SCE_STAC"='RCO' OR "SCE"."SCE_STAC"='RHL_R' OR "SCE"."SCE_STAC"='RIN' OR
              "SCE"."SCE_STAC"='RLL' OR "SCE"."SCE_STAC"='RPD' OR "SCE"."SCE_STAC"='RSAS'))
  10 - access("MST"."MST_CODE"="MRE"."MRE_MSTC")
  11 - filter("MRE"."MRE_MRCC"='STU')
  14 - access("SPR"."SPR_CODE"="SCJ"."SCJ_SPRC")
Note: cpu costing is off
40 rows selected.As you state something has obviously changed, but nothing obvious has been changed.
We gather statistics via...
exec dbms_stats.gather_schema_stats(ownname => 'USERNAME', estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE , degree => 4, granularity => ''ALL'', cascade => TRUE);
We run a script nightly which works out which indexes require a rebuild and rebuild those only it doesn;t just rebuild all indexes.
It would be nice to be able to use the 10g statistics history, but on this instance we aren't yet at that version, hopefully we will be there soon though.
Hope this helps,
Kieron

Similar Messages

  • Why are calculation functions lost from Reader Extended PDF when downloaded from website?

    I am creating PDF forms with most fields performing calculations. I am saving the forms out as Reader Extended PDF> Enable Additional Features. When I email the form there is no problem with the person using the form, all calculations work. The person is able to save the form and all info is present.
    However, when the same file is posted on a website with a clickable link to download, once downloaded, all the calculation functions are missing from the fields. Additionally, when the user fills the form out anyway, the info in the fields is invisible.
    I am on a MAC OS 10 using Acrobat X Pro. The majority of the people going to the website and using the forms are on Windows. What am I doing wrong?

    It sounds like you're actually using the Preview application when viewing the form on your Mac. It does not support JavaScript, which is how the automatic calculations are implemented. It also corrupts forms when it saves them. A result of this corruption is when the form is subsequently opened in Acrobat/Reader, the fields are blank unless a field has the focus. For more information, see: http://kb2.adobe.com/community/publishing/885/cpsid_88564.html

  • MERGE JOIN CARTESIAN

    Hi,
    I have a query which is using MERGE JOIN CARTESIAN (see step 4 and 11 in execution plan bellow) and i believe this is the culprit and query is never returning. Stats are up to date on all tables. This query involves two remote databases which are accessed using VIEWs from local database. Is there any hint which i can use here to avoid merge join Cartesian and test. Thanks. Also pasting query if any one can have any idea.
        Select  distinct
         substr(Revenue.FKDAT,5,2) || '/' || substr(Revenue.FKDAT,7,2) || '/' || substr(Revenue.FKDAT,1,4) INVOICE_DATE
        , Revenue.VBELN INVOICE_NR
        , Revenue.ARKTX CUSTDEVICE
        , (case Revenue.ZU_LOTID
        when null then hstg_partinfo_cust_dw.CUSTPARTOUT
        when '' then hstg_partinfo_cust_dw.CUSTPARTOUT
        Else
        (case decode(trim(zodss1b2.biztype),'TNR-E330-BAKE','TNR','')
        when 'TNR' then
        (case when (select CUSTPARTOUT from hstg_partinfo_cust_dw Where lotid = 'U' || substr(Revenue.ZU_LOTID,2,7) || '.' || substr(Revenue.ZU_LOTID,9) and stage = 'T998-TFIN' and rownum = 1)
         is null then (select CUSTPARTOUT from hstg_partinfo_cust_dw Where lotid = (select parentid from hstg_partinfo_cust_dw where lotid = 'U' || substr(Revenue.ZU_LOTID,2,7) || '.' || substr(Revenue.ZU_LOTID,9) and stage = 'E330-BAKE' and rownum = 1) and stage = 'T998-TFIN' and rownum = 1)
        else (select CUSTPARTOUT from hstg_partinfo_cust_dw Where lotid = 'U' || substr(Revenue.ZU_LOTID,2,7) || '.' || substr(Revenue.ZU_LOTID,9) and stage = 'T998-TFIN' and rownum = 1)
        end)
        else hstg_partinfo_cust_dw.CUSTPARTOUT
        end)
        end) CUSTPARTOUT
        , Revenue.PONUM DO_NR
        , Revenue.BSTKD PO_NR
        , Revenue.FKIMG GD_QTY
        , Revenue.zkbetr GD_PRICE
        , Revenue.NETWR GD_AMT
        , '' REJ_QTY
        , '' REJ_PRICE
        , '' REJ_AMT
        , Revenue.ZU_LOTID LOTTYPE
        ,(case Revenue.ZU_LOTID
        when null then substr(Revenue.ZU_PRTID,1,instr(Revenue.ZU_PRTID,'.') -1)
        when '' then substr(Revenue.ZU_PRTID,1,instr(Revenue.ZU_PRTID,'.') -1)
        Else
        (case decode(trim(zodss1b2.biztype),'TNR-E330-BAKE','TNR','')
        when 'TNR' then
       (case when (select substr(PARTID,1,instr(PARTID,'.') -1) from hstg_partinfo_cust_dw Where lotid = 'U' || substr(Revenue.ZU_LOTID,2,7) || '.' || substr(Revenue.ZU_LOTID,9) and stage = 'T998-TFIN' and  rownum = 1)
         is null then (select substr(PARTID,1,instr(PARTID,'.') -1) from hstg_partinfo_cust_dw Where lotid = (select parentid from hstg_partinfo_cust_dw where lotid = 'U' || substr(Revenue.ZU_LOTID,2,7) || '.' || substr(Revenue.ZU_LOTID,9) and stage = 'E330-BAKE' and rownum = 1) and stage = 'T998-TFIN' and rownum = 1)
        else (select substr(PARTID,1,instr(PARTID,'.') -1) from hstg_partinfo_cust_dw Where lotid = 'U' || substr(Revenue.ZU_LOTID,2,7) || '.' || substr(Revenue.ZU_LOTID,9) and stage = 'T998-TFIN' and rownum = 1)
        end)
        else substr(Revenue.ZU_PRTID,1,instr(Revenue.ZU_PRTID,'.') -1)
        end)
        end) PARTID
        , '' TESTER
        , substr(zodss1b2.BSTDK,5,2) || '/' || substr(zodss1b2.BSTDK,7,2) || '/' || substr(zodss1b2.BSTDK,1,4) DO_DATE
        , hstg_partinfo_cust_dw.package package
        , hstg_partinfo_cust_dw.pincount pincount
        , (select c.catg07 from ops$ods_adm.catg c where c.partid=revenue.zu_prtid) as package_size
        , (select c.catg09 from ops$ods_adm.catg c where c.partid=revenue.zu_prtid) as wafer_size
        , decode(trim(zodss1b2.biztype),'TNR-E330-BAKE','TNR','') BIZTYPE
         --from revenue, zodss1b2,dim_partinfo
         from revenue, zodss1b2,hstg_partinfo_cust_dw
         where Revenue.Remarks <> 'CANCELLED'
         and Revenue.FKART in ('ZUF2')
         and Revenue.KUNNR in ('BC1001','BC1002','BC1003')
         and Revenue.FKDAT like '201008%'
         and Revenue.FKIMG > 0
         and Revenue.kpein > 0
         and Revenue.ZU_LOTID = zodss1b2.charg
         and Revenue.MATNR = zodss1b2.matnr
         --and Revenue.ZU_PRTID = dim_partinfo.partid
         and hstg_partinfo_cust_dw.lotid='U' || substr(Revenue.ZU_LOTID,2,7) || '.' || substr(Revenue.ZU_LOTID,9)
        Union all
         Select distinct
         substr(Revenue.FKDAT,5,2) || '/' || substr(Revenue.FKDAT,7,2) || '/' || substr(Revenue.FKDAT,1,4) INVOICE_DATE
        , Revenue.VBELN INVOICE_NR
        , Revenue.ARKTX CUSTDEVICE
        , hstg_partinfo_cust_dw.CUSTPARTOUT CUSTPARTOUT
        , Revenue.PONUM DO_NR
        , Revenue.BSTKD PO_NR
        , Revenue.FKIMG GD_QTY
        , Revenue.zkbetr GD_PRICE
        , Revenue.NETWR GD_AMT
        , '' REJ_QTY
        , '' REJ_PRICE
        , '' REJ_AMT
        , Revenue.ZU_LOTID LOTTYPE
        , substr(Revenue.ZU_PRTID,1,instr(Revenue.ZU_PRTID,'.') -1) PARTID
        , '' TESTER
        , substr(zodsscrap.BSTDK,5,2) || '/' || substr(zodsscrap.BSTDK,7,2) || '/' || substr(zodsscrap.BSTDK,1,4) DO_DATE
        , hstg_partinfo_cust_dw.package package
        , hstg_partinfo_cust_dw.pincount pincount
        , (select c.catg07 from ops$ods_adm.catg c where c.partid=revenue.zu_prtid) as package_size
        , (select c.catg09 from ops$ods_adm.catg c where c.partid=revenue.zu_prtid) as wafer_size
         --from revenue, zodsscrap,dim_partinfo
         from revenue, zodsscrap,hstg_partinfo_cust_dw
         where Revenue.Remarks <> 'CANCELLED'
         and Revenue.FKART in ('ZUF2')
         and Revenue.KUNNR in ('BC1001','BC1002','BC1003')
         and Revenue.FKDAT like '201008%'
         and Revenue.FKIMG > 0
         and Revenue.kpein > 0
         and Revenue.ZU_LOTID = zodsscrap.charg
         --and Revenue.ZU_PRTID = dim_partinfo.partid
         and hstg_partinfo_cust_dw.lotid='U' || substr(Revenue.ZU_LOTID,2,7) || '.' || substr(Revenue.ZU_LOTID,9);hstg_partinfo_cust_dw is a view which is on remote database USGDWDBP and is queried using synonym in the local database.
    revenue is also a view which is in another remote database which is queried using synonym in local database.
    ODS Plan
    | Id  | Operation               |  Name       | Rows  | Bytes | Cost  | Inst   |IN-OUT|
    |   0 | SELECT STATEMENT        |             |     2 |  8532 |   999 |        |      |
    |   1 |  UNION-ALL              |             |       |       |       |        |      |
    |   2 |   SORT UNIQUE           |             |     1 |  4277 |   985 |        |      |
    |   3 |    NESTED LOOPS         |             |     1 |  4277 |   983 |        |      |
    |   4 |     MERGE JOIN CARTESIAN|             |     1 |  4107 |   980 |        |      |
    |   5 |      REMOTE             |             |     1 |  4076 |     2 | USGDW~ | R->S |
    |   6 |      BUFFER SORT        |             |   918K|    27M|   978 |        |      |
    |   7 |       TABLE ACCESS FULL | ZODSS1B2    |   918K|    27M|   978 |        |      |
    |   8 |     REMOTE              |             |     1 |   170 |     3 | SAPP0~ | R->S |
    |   9 |   SORT UNIQUE           |             |     1 |  4255 |    14 |        |      |
    |  10 |    NESTED LOOPS         |             |     1 |  4255 |    12 |        |      |
    |  11 |     MERGE JOIN CARTESIAN|             |     1 |  4096 |     9 |        |      |
    |  12 |      REMOTE             |             |     1 |  4076 |     2 | USGDW~ | R->S |
    |  13 |      BUFFER SORT        |             |  1755 | 35100 |     7 |        |      |
    |  14 |       TABLE ACCESS FULL | ZODSSCRAP   |  1755 | 35100 |     7 |        |      |
    |  15 |     REMOTE              |             |     1 |   159 |     3 | SAPP0~ | R->S |
    ---------------------------------------------------------------------------------------Thanks in advance
    Salman

    Dear Salman Qureshi,
    First of all please see Jonathan Lewis' post about the merge join cartesian;
    http://jonathanlewis.wordpress.com/2006/12/13/cartesian-merge-join/
    You may also check the Thomas Kyte's thread;
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4105951726381
    You merge join cartesian cost is so low that the impact will not be that high.
    Yes, there are ways to avoid the merge join cartesian. First you have to check the where conditions. Merge join cartesian steps are happening because of the bad SQL algorithm OR sometimes Oracle needs to have a merge join cartesian. At the end, it is up to your SQL.
    After than that, you can also use the ORDERED CBO hint to avoid the merge join cartesian.
    Please add below line after the SELECT clause and see the new execution plan;
    /*+ ORDERED */I hope your problem will be fixed when you show the CBO to use the ORDERED Oracle hint.
    About the ORDERED Oracle hint, please check it out;
    http://download.oracle.com/docs/cd/B14117_01/server.101/b10752/hintsref.htm#5555
    ORDERED
    The ORDERED hint causes Oracle to join tables in the order in which they appear in the FROM clause.
    If you omit the ORDERED hint from a SQL statement performing a join, then the optimizer chooses the order in which to join the tables. You might want to use the ORDERED hint to specify a join order if you know something about the number of rows selected from each table that the optimizer does not. Such information lets you choose an inner and outer table better than the optimizer could.Hope That Helps.
    Ogan

  • Is merge join cartesian more cpu intensibe than nested loop ?

    Hi,
    just wonderning which access method is more cpu intensive , lets supposed we got 2 the same row sources and doing joing via merge join cartesian and next case is nested loop .
    I know NL can be cpu intensive because of tight loop access , but what abour MJC ?
    I can see bufferd sort but not sure is that cpu friendly ?
    Regards
    GregG

    Hi,
    I think in your case it's more accurate to compare a NESTED LOOP (NL) to a MERGE JOIN (MJ), because CARTESIAN MERGE JOIN is a rather special case of MJ.
    Merge join sorts its inputs before combining them, and it could be efficient when one or both of inputs are already sorted.
    Regarding your question (which is more CPU intensive):
    1) if MERGE JOIN involves disk spills, then CPU is probably irrelevant, because disk operations are much more expensive
    2) the amount of work to combine rowsources via a MJ depends on how well they are aligned with respect to each other, so I don't think it can be expressed via a simple formula.
    For nested loops, the situation is much more simple: you don't need to do any special work do combine the rowsource, so the cost is just the sum of the cost acquiring the outer rowsource plus the number of iterations times the cost of one iteration. If the data is read from disk, then CPU probably won't matter much, if most of reads are logical ones than CPU becomes of a factor (it's hard to tell how much work CPU will have to do per one logical read because there are two many factors here -- how many columns are accessed, how they are located within the block, are there any expensive math functions applied to any of them etc.)
    Best regards,
    Nikolay

  • Why Merge join Cartesion

    hi can any one please help me understand why this simple query is doing merge cartesion join , but not equi join
    i have two table with column name id on both the tables.
    CREATE TABLE id_a (ID VARCHAR2(10), description VARCHAR2(100));
    CREATE TABLE id_b (ID VARCHAR2(10), long_description VARCHAR2(100),short_description VARCHAR2(100));
    /* Formatted on 2010/01/13 12:16 (Formatter Plus v4.8.8) */
    SET DEFINE OFF;
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0001'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0002'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0003'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0004'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0005'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0006'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0007'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0008'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0009'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0010'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0011'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0012'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0013'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0014'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0015'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0016'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0017'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0018'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0019'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0020'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0021'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0022'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0023'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0024'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0025'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0026'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0027'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0028'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0029'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0030'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0031'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0032'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0033'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0034'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0035'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0036'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0037'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC0038'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC8000'
    INSERT INTO id_a
                (ID, description
         VALUES ('10ACCC', '10ACCC9998'
    COMMIT ;
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('10ACCC', NULL, NULL);
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('20LNDM', NULL, NULL);
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('10NQWR', NULL, NULL);
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('40KKRA ', NULL, NULL);
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('10VUIU', NULL, NULL);
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('10NCMM', NULL, NULL);
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('10EAQL', NULL, NULL);
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('10BLGP', NULL, NULL);
    Insert into ID_B
       (ID, LONG_DESCRIPTION, SHORT_DESCRIPTION)
    Values
       ('10LWGV', NULL, NULL);
    commit;
    select a.description from id_a a , id_b b where
    a.id = '10ACCC'
    and a.id = b.id ;

    these are the stats that accurately reflect the data. if i use exist clause for each table i can avoid the merge cartesion, but is it a better way to rewrite the query. please suggest.
    And one more thing is that i read the article http://jonathanlewis.wordpress.com/2006/12/13/cartesian-merge-join/ in this article it clearly says that i need to set the parameter
    optimizertransitivity_retain to true . but how do i do that?
    SQL> show parameter user_dump_dest
    NAME                                 TYPE        VALUE
    user_dump_dest                       string      /u01/app/oracle/admin/dnsprx/u
                                                     dump
    SQL> show parameter optimizer
    NAME                                 TYPE        VALUE
    optimizer_dynamic_sampling           integer     2
    optimizer_features_enable            string      10.1.0.5
    optimizer_index_caching              integer     0
    optimizer_index_cost_adj             integer     100
    optimizer_mode                       string      ALL_ROWS
    SQL> show parameter db_file_multi
    NAME                                 TYPE        VALUE
    db_file_multiblock_read_count        integer     16
    SQL> show parameter db_block_size
    NAME                                 TYPE        VALUE
    db_block_size                        integer     8192
    SQL> show parameter cursor_sharing
    NAME                                 TYPE        VALUE
    cursor_sharing                       string      EXACT
    SQL> column sname format a20
    SQL> column pname format a20
    SQL> column pval2 format a20
    SQL>
    SQL> select
      2  sname
      3  , pname
      4  , pval1
      5  , pval2
      6  from
      7  sys.aux_stats$;
    SNAME                PNAME                     PVAL1 PVAL2
    SYSSTATS_INFO        STATUS                          COMPLETED
    SYSSTATS_INFO        DSTART                          02-21-2006 12:14
    SYSSTATS_INFO        DSTOP                           02-21-2006 12:14
    SYSSTATS_INFO        FLAGS                         1
    SYSSTATS_MAIN        CPUSPEEDNW           604.316547
    SYSSTATS_MAIN        IOSEEKTIM                    10
    SYSSTATS_MAIN        IOTFRSPEED                 4096
    SYSSTATS_MAIN        SREADTIM
    SYSSTATS_MAIN        MREADTIM
    SYSSTATS_MAIN        CPUSPEED
    SYSSTATS_MAIN        MBRC
    SYSSTATS_MAIN        MAXTHR
    SYSSTATS_MAIN        SLAVETHR
    13 rows selected.
    Elapsed: 00:00:00.09
    SQL>
    SQL> --============================================================================
    SQL> ----------------- put your sql statement here---------------------------------
    SQL> explain plan for
      2   SELECT DISTINCT b.sub_nasp_id
      3            FROM r_ref_cust_status_unmnpip_nasp a,
      4                 ref_nasp_eref b,
      5                 ref_garm_naspid c
      6              WHERE a.nasp_id = '10ACCC'
      7             AND a.nasp_id = b.nasp_id
      8             AND a.nasp_id = SUBSTR (c.ID, 1, 6)
      9             AND NVL (INSTR ('1', NVL (c.sensitivity_level, '@!')), 1) != 0;
    Explained.
    Elapsed: 00:00:00.07
    SQL>
    SQL>
    SQL> ---------------------- end of  sql statement ---------------------------------
    SQL> --============================================================================
    SQL>
    SQL> select * from table(dbms_xplan.display);
    PLAN_TABLE_OUTPUT
    Plan hash value: 3987722552
    | Id  | Operation                      | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT               |                    |     6 |   192 |  3578   (2)| 00:00:43 |
    |   1 |  SORT UNIQUE                   |                    |     6 |   192 |  3578   (2)| 00:00:43 |
    |   2 |   MERGE JOIN CARTESIAN         |                    |  3105 | 99360 |  3577   (2)| 00:00:43 |
    |   3 |    MERGE JOIN CARTESIAN        |                    |   528 |  8448 |  1991   (4)| 00:00:24 |
    |*  4 |     TABLE ACCESS FULL          | REF_GARM_NASPID    |   528 |  4752 |  1990   (3)| 00:00:24 |
    |   5 |     BUFFER SORT                |                    |     1 |     7 |     1 (100)| 00:00:01 |
    |*  6 |      INDEX RANGE SCAN          | UNMNPIP_NASP_INDX  |     1 |     7 |     0   (0)| 00:00:01 |
    |   7 |    BUFFER SORT                 |                    |     6 |    96 |  3577   (2)| 00:00:43 |
    |   8 |     TABLE ACCESS BY INDEX ROWID| REF_NASP_EREF      |     6 |    96 |     3   (0)| 00:00:01 |
    |*  9 |      INDEX RANGE SCAN          | REF_NASP_EREF_INDX |     6 |       |     2   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       4 - filter(SUBSTR("C"."ID",1,6)='10ACCC' AND
                  NVL(INSTR('1',NVL("C"."SENSITIVITY_LEVEL",'@!')),1)<>0)
       6 - access("A"."NASP_ID"='10ACCC')
       9 - access("B"."NASP_ID"='10ACCC')
    24 rows selected.
    Elapsed: 00:00:00.23
    SQL> rollback;
    Rollback complete.
    Elapsed: 00:00:00.04
    SQL>
    SQL> -- rem Set the ARRAYSIZE according to your application
    SQL> set autotrace traceonly arraysize 100
    SQL>
    SQL> alter session set tracefile_identifier = 'mytrace1';
    Session altered.
    Elapsed: 00:00:00.04
    SQL> alter session set events '10046 trace name context forever, level 8';
    Session altered.
    Elapsed: 00:00:00.04
    SQL>
    SQL> --============================================================================
    SQL> ----------------- put your sql statement here---------------------------------
    SQL> explain plan for
      2  SELECT DISTINCT b.sub_nasp_id
      3            FROM r_ref_cust_status_unmnpip_nasp a,
      4                 ref_nasp_eref b,
      5                 ref_garm_naspid c
      6              WHERE a.nasp_id = '10ACCC'
      7             AND a.nasp_id = b.nasp_id
      8             AND a.nasp_id = SUBSTR (c.ID, 1, 6)
      9             AND NVL (INSTR ('1', NVL (c.sensitivity_level, '@!')), 1) != 0;
    Explained.
    Elapsed: 00:00:00.06
    SQL>
    SQL> ---------------------- end of  sql statement ---------------------------------
    SQL> --============================================================================
    SQL>
    SQL>
    SQL> ----------------------------- Step 2 ------------------------------------------
    SQL> --============================================================================
    SQL>
    SQL> -- if you're on 10g or later
    SQL> -- get the row source statistics
    SQL> -- if the SQL is sensitive
    SQL> -- don't switch on the ECHO
    SQL> -- set echo off
    SQL>
    SQL> set echo on
    SQL>
    SQL> ---set timing on trimspool on linesize 250 pagesize 999
    SQL> set arraysize 100 termout off
    SQL> -- alter system flush buffer_cache;
    SQL> -- spool off
    SQL>
    SQL> -- put your statement here
    SQL> -- use the GATHER_PLAN_STATISTICS hint
    SQL> -- if you're not using STATISTICS_LEVEL = ALL
    SQL>
    SQL>  SELECT /*+ gather_plan_statistics */     DISTINCT b.sub_nasp_id
      2            FROM r_ref_cust_status_unmnpip_nasp a,
      3                 ref_nasp_eref b,
      4                 ref_garm_naspid c
      5              WHERE a.nasp_id = '10ACCC'
      6             AND a.nasp_id = b.nasp_id
      7             AND a.nasp_id = SUBSTR (c.ID, 1, 6)
      8             AND NVL (INSTR ('1', NVL (c.sensitivity_level, '@!')), 1) != 0;
    40 rows selected.
    Elapsed: 00:00:04.65
    Execution Plan
    Plan hash value: 3987722552
    | Id  | Operation                      | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT               |                    |     6 |   192 |  3578   (2)| 00:00:43 |
    |   1 |  SORT UNIQUE                   |                    |     6 |   192 |  3578   (2)| 00:00:43 |
    |   2 |   MERGE JOIN CARTESIAN         |                    |  3105 | 99360 |  3577   (2)| 00:00:43 |
    |   3 |    MERGE JOIN CARTESIAN        |                    |   528 |  8448 |  1991   (4)| 00:00:24 |
    |*  4 |     TABLE ACCESS FULL          | REF_GARM_NASPID    |   528 |  4752 |  1990   (3)| 00:00:24 |
    |   5 |     BUFFER SORT                |                    |     1 |     7 |     1 (100)| 00:00:01 |
    |*  6 |      INDEX RANGE SCAN          | UNMNPIP_NASP_INDX  |     1 |     7 |     0   (0)| 00:00:01 |
    |   7 |    BUFFER SORT                 |                    |     6 |    96 |  3577   (2)| 00:00:43 |
    |   8 |     TABLE ACCESS BY INDEX ROWID| REF_NASP_EREF      |     6 |    96 |     3   (0)| 00:00:01 |
    |*  9 |      INDEX RANGE SCAN          | REF_NASP_EREF_INDX |     6 |       |     2   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       4 - filter(SUBSTR("C"."ID",1,6)='10ACCC' AND
                  NVL(INSTR('1',NVL("C"."SENSITIVITY_LEVEL",'@!')),1)<>0)
       6 - access("A"."NASP_ID"='10ACCC')
       9 - access("B"."NASP_ID"='10ACCC')
    Statistics
              1  recursive calls
              0  db block gets
           8836  consistent gets
           5736  physical reads
              0  redo size
            855  bytes sent via SQL*Net to client
            243  bytes received via SQL*Net from client
              2  SQL*Net roundtrips to/from client
              3  sorts (memory)
              0  sorts (disk)
             40  rows processed
    SQL> set termout on
    SQL> select * from table(dbms_xplan.display_cursor(null, null, 'ALLSTATS LAST'));
    Elapsed: 00:00:00.26
    Execution Plan
    Plan hash value: 3602215112
    | Id  | Operation                         | Name           | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT                  |                |  8168 | 16336 |    24   (0)| 00:00:01 |
    |   1 |  COLLECTION ITERATOR PICKLER FETCH| DISPLAY_CURSOR |       |       |            |          |
    Statistics
             11  recursive calls
              0  db block gets
            108  consistent gets
              0  physical reads
              0  redo size
            304  bytes sent via SQL*Net to client
            243  bytes received via SQL*Net from client
              2  SQL*Net roundtrips to/from client
              0  sorts (memory)
              0  sorts (disk)
              1  rows processed
    SQL>
    SQL>
    SQL>
    SQL>
    SQL>
    SQL> disconnect
    Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - 64bit Production
    With the Partitioning, Real Application Clusters, OLAP and Data Mining options
    SQL> spool off

  • Group by causing merge join cartesian?

    Hi All,
    Database Version: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
    Database Version: PL/SQL Release 10.2.0.5.0 - ProductionI've written a query which runs in under a second and produces a few hundred rows (as you can see below). I only wanted to find the number of distinct incident ID's returned so I put a group by at the end and it ran for ever.
    I produced an explain plan (as shown below) for the query with the group by in it and it is trying to perform a cartesian join!
    WTF is going on? I've never known a group by statement to do that before.
    basic structure of the tables is as follows:
    SQL> desc answer_master
    Name                                                                     Null?    Type
    ANSWER_ID                                                                NOT NULL NUMBER(12)
    INCIDENT_ID                                                              NOT NULL NUMBER(12)
    PLAN_ID                                                                  NOT NULL NUMBER(12)
    QUESTION_ID                                                              NOT NULL NUMBER(12)
    SQL> desc question_master
    Name                                                                     Null?    Type
    QUESTION_PLAN_ID                                                         NOT NULL NUMBER(12)
    QUESTION_ID                                                              NOT NULL NUMBER(12)
    QUESTION_TYPE                                                            NOT NULL NUMBER(2)
    QUESTION_TEXT                                                            NOT NULL VARCHAR2(255)
    QUESTION_PARENT_ID                                                                NUMBER(12)the offending SQL statement
    SQL> explain plan for
      2  select incident_id
      3    from answer_master am
      4   where exists (select 'x'
      5                   from answer_master am1
      6                  where question_id in (select question_id
      7                               from question_master qms
      8                              where question_plan_id = 1477
      9                                and question_parent_id = 69067
    10                                and substr(question_text,-3) = 'PDF')
    11                    and am1.incident_id = am.incident_id)
    12    and exists (select 'x'
    13                   from answer_master am1
    14                  where question_id in (select question_id
    15                               from question_master qms
    16                              where question_plan_id = 1477
    17                                and question_parent_id = 69067
    18                                and substr(question_text,-3) != 'PDF')
    19                    and am1.incident_id = am.incident_id);
    Explained.
    Elapsed: 00:00:00.01
    SQL> set linesize 132;
    SQL> select plan_table_output from table(dbms_xplan.display('plan_table',null,'serial'));
    PLAN_TABLE_OUTPUT                                                                                                                  
    Plan hash value: 1710257923                                                                                                        
    | Id  | Operation                        | Name                  | Rows  | Bytes | Cost (%CPU)| Time     |                         
    |   0 | SELECT STATEMENT                 |                       |     1 |    32 |   171   (6)| 00:00:01 |                         
    |*  1 |  HASH JOIN RIGHT SEMI            |                       |     1 |    32 |   171   (6)| 00:00:01 |                         
    |   2 |   VIEW                           | VW_SQ_2               |    71 |   923 |    70   (5)| 00:00:01 |                         
    |   3 |    NESTED LOOPS                  |                       |    71 |  3266 |    70   (5)| 00:00:01 |                         
    |*  4 |     TABLE ACCESS BY INDEX ROWID  | QUESTION_MASTER       |     1 |    35 |     2   (0)| 00:00:01 |                         
    |*  5 |      INDEX RANGE SCAN            | QUESTION_MASTER_IX1   |     3 |       |     1   (0)| 00:00:01 |                         
    |*  6 |     INDEX RANGE SCAN             | ANSWER_MASTER_QID_IX2 | 18731 |   201K|    68   (5)| 00:00:01 |                         
    |   7 |   NESTED LOOPS                   |                       |   304 |  5776 |   100   (5)| 00:00:01 |                         
    |   8 |    VIEW                          | VW_SQ_1               |    14 |   182 |    70   (5)| 00:00:01 |                         
    |   9 |     HASH UNIQUE                  |                       |    14 |   644 |            |          |                         
    |  10 |      NESTED LOOPS                |                       |    14 |   644 |    70   (5)| 00:00:01 |                         
    |* 11 |       TABLE ACCESS BY INDEX ROWID| QUESTION_MASTER       |     1 |    35 |     2   (0)| 00:00:01 |                         
    |* 12 |        INDEX RANGE SCAN          | QUESTION_MASTER_IX1   |     3 |       |     1   (0)| 00:00:01 |                         
    |* 13 |       INDEX RANGE SCAN           | ANSWER_MASTER_QID_IX2 | 18731 |   201K|    68   (5)| 00:00:01 |                         
    |* 14 |    INDEX RANGE SCAN              | ANSWER_MASTER_QID_IX3 |    22 |   132 |     2   (0)| 00:00:01 |                         
    Predicate Information (identified by operation id):                                                                                
       1 - access("ITEM_2"="AM"."INCIDENT_ID")                                                                                         
       4 - filter("QUESTION_PLAN_ID"=1477 AND SUBSTR("QUESTION_TEXT",-3)!='PDF')                                                       
       5 - access("QUESTION_PARENT_ID"=69067)                                                                                          
       6 - access("QUESTION_ID"="QUESTION_ID")                                                                                         
      11 - filter("QUESTION_PLAN_ID"=1477 AND SUBSTR("QUESTION_TEXT",-3)='PDF')                                                        
      12 - access("QUESTION_PARENT_ID"=69067)                                                                                          
      13 - access("QUESTION_ID"="QUESTION_ID")                                                                                         
      14 - access("ITEM_1"="AM"."INCIDENT_ID")                                                                                         
    33 rows selected.
    Elapsed: 00:00:00.06
    SQL> explain plan for
      2  select incident_id
      3    from answer_master am
      4   where exists (select 'x'
      5                   from answer_master am1
      6                  where question_id in (select question_id
      7                               from question_master qms
      8                              where question_plan_id = 1477
      9                                and question_parent_id = 69067
    10                                and substr(question_text,-3) = 'PDF')
    11                    and am1.incident_id = am.incident_id)
    12    and exists (select 'x'
    13                   from answer_master am1
    14                  where question_id in (select question_id
    15                               from question_master qms
    16                              where question_plan_id = 1477
    17                                and question_parent_id = 69067
    18                                and substr(question_text,-3) != 'PDF')
    19                    and am1.incident_id = am.incident_id)
    20  group by incident_id;
    Explained.
    Elapsed: 00:00:00.00
    SQL> select plan_table_output from table(dbms_xplan.display('plan_table',null,'serial'));
    PLAN_TABLE_OUTPUT                                                                                                                  
    Plan hash value: 1433543102                                                                                                        
    | Id  | Operation                         | Name                  | Rows  | Bytes | Cost (%CPU)| Time     |                        
    |   0 | SELECT STATEMENT                  |                       |     1 |    98 |    77   (6)| 00:00:01 |                        
    |   1 |  HASH GROUP BY                    |                       |     1 |    98 |    77   (6)| 00:00:01 |                        
    |   2 |   NESTED LOOPS                    |                       |     1 |    98 |    76   (4)| 00:00:01 |                        
    |   3 |    NESTED LOOPS                   |                       |     1 |    87 |    74   (5)| 00:00:01 |                        
    |   4 |     NESTED LOOPS                  |                       |     1 |    81 |    72   (5)| 00:00:01 |                        
    |   5 |      MERGE JOIN CARTESIAN         |                       |     1 |    70 |     4   (0)| 00:00:01 |                        
    |*  6 |       TABLE ACCESS BY INDEX ROWID | QUESTION_MASTER       |     1 |    35 |     2   (0)| 00:00:01 |                        
    |*  7 |        INDEX RANGE SCAN           | QUESTION_MASTER_IX1   |     3 |       |     1   (0)| 00:00:01 |                        
    |   8 |       BUFFER SORT                 |                       |     1 |    35 |     2   (0)| 00:00:01 |                        
    |*  9 |        TABLE ACCESS BY INDEX ROWID| QUESTION_MASTER       |     1 |    35 |     2   (0)| 00:00:01 |                        
    |* 10 |         INDEX RANGE SCAN          | QUESTION_MASTER_IX1   |     3 |       |     1   (0)| 00:00:01 |                        
    |* 11 |      INDEX RANGE SCAN             | ANSWER_MASTER_QID_IX2 | 18731 |   201K|    68   (5)| 00:00:01 |                        
    |* 12 |     INDEX RANGE SCAN              | ANSWER_MASTER_QID_IX3 |    22 |   132 |     2   (0)| 00:00:01 |                        
    |* 13 |    INDEX RANGE SCAN               | ANSWER_MASTER_QID_IX2 |     1 |    11 |     2   (0)| 00:00:01 |                        
    Predicate Information (identified by operation id):                                                                                
       6 - filter("QUESTION_PLAN_ID"=1477 AND SUBSTR("QUESTION_TEXT",-3)='PDF')                                                        
       7 - access("QUESTION_PARENT_ID"=69067)                                                                                          
       9 - filter("QUESTION_PLAN_ID"=1477 AND SUBSTR("QUESTION_TEXT",-3)!='PDF')                                                       
      10 - access("QUESTION_PARENT_ID"=69067)                                                                                          
      11 - access("QUESTION_ID"="QUESTION_ID")                                                                                         
      12 - access("AM1"."INCIDENT_ID"="AM"."INCIDENT_ID")                                                                              
      13 - access("QUESTION_ID"="QUESTION_ID" AND "AM1"."INCIDENT_ID"="AM"."INCIDENT_ID")                                              
    31 rows selected.
    Elapsed: 00:00:00.00
    SQL> spool offedit: changing greater-than/less-than signs to != so it displays on forum
    Edited by: WhiteHat on Feb 11, 2011 9:37 AM

    The "Cartesian" product is nothing "wrong", if (!) the optimizer is right and the number or rows it's picking for that part of the execution plan is really 1. And that can be true, as ORACLE also changed from HASH join to NL. So that NL might be the cause of your performance issue not the Cartesian.
    The performance of IN, EXISTS and SUBQUERIES got better over the versions, but I still see no reason in most cases to use them for good readable and performing code.
    What you do think about this:
    WITH my_selection As
    (SELECT incident_id
    from question_master qms
       where question_plan_id = 1477
       and question_parent_id = 69067
       and (substr(question_text,-3) = 'PDF'
            or and substr(question_text,-3) != 'PDF')
       GROUP BY incident_id
       HAVING COUNT(*) >1)
    SELECT am.incident_id
      FROM answer_master am
         INNER JOIN my_selection s
          ON am.incident_id = s.incident_id
    group by am.incident_id;

  • WHERE clauses and Merge Join Cartesian?

    For some reason, Siebel is generating queries like this:
                        AND CONCAT (CONCAT (t41828.lvl8anc_postn, '-'),
                                    t41828.lvl8_emp_full_name
                                   ) = 'GEO-SMITH, BILL'
                        AND CONCAT (CONCAT (t41828.lvl6anc_postn, '-'),
                                    t41828.lvl6_emp_full_name
                                   ) = 'GROUP1-DOE, JOHN'and this ends up with 3 merge join cartesian in autotrace and this query takes several hours.
    However, by rewriting just those 2 clauses to:
                        AND (t41828.lvl8anc_postn = 'GEO' and
                                    t41828.lvl8_emp_full_name = 'SMITH, BILL')
                        AND (t41828.lvl6anc_postn = 'GROUP1' and
                                    t41828.lvl6_emp_full_name = 'DOE, JOHN')the merge join cartesians go away, and it runs in 7 seconds.
    However, since Siebel is generating the query, and we are having issues, we decided to add columns for testing that is equivalent to the concatenation of the two columns above. After doing this, and creating indexes on the new columns, it is now back to the merge join cartesian and I cannot get rid of it.
    So:
    1. How can rewriting the WHERE (not adding or deleting anything here, just rewriting it in a different way) clause eliminate the merge join cartesian?
    I'm guessing by understanding that single question, I will be able to come up with a better solution to this.

    Note we made two additional columns:
    CONCAT (CONCAT (t41828.lvl8anc_postn, '-'), t41828.lvl8_emp_full_name) => col1 CONCAT (CONCAT (t41828.lvl6anc_postn, '-'), t41828.lvl6_emp_full_name) => col2
    When I created indexes on col1 and col2 and used them in the query, the cartesians returned, and I cannot figure out why. So, I'm still confused why:
    In the original query:
    1. Using CONCAT, and thus no indexes => cartesian
    2. No CONCAT, and indexes => no cartesian
    With the new columns, col1 and col2:
    1. No CONCAT needed, full table scan or indexes => cartesian

  • Photomerge panorama produces an empty merge file from two images; how can I fix this? Thanks

    Photomerge panorama produces an empty merge file from two images; how can I fix this? Thanks

    If you did not create this swf yourself then you won't be able to do what I am suggesting.  If you did, then open the fla in Flash and go into the Publish Settings and select the option to publish an html file as an output.  That will create an html page that embeds the Flash file.  Test that file in your browser and see if it plays properly.  IF so, then copy that code in place of whatever Dreamweaver did to embed the Flash.
    Dreamweaver is not a reliable tool for embedding Flash content... why it does not do it the same way Flash does it is anyone's guess.

  • Shutterfly requests 10.6 or lower to produce a video with flash player what can I DO?

    SHUTTERFLY  requests 10.6 or lower to produce a video with flash player what can I DO?

    Install 10.6 or lower.  http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html

  • Merge Join Cartesian performing bad on 10g

    Hello All,
    I have a merge join cartesian query that took seconds in 8i. Once the database was upgraded to 10g, the same query is taking hours. In looking at the explain plans, it looks like the access paths are identical.
    Has anyone encountered this issue?
    Thanks.

    Sometimes the cost-based optimizer will do cartesian joins to optimize a query. Seeing the word "cartesian" in a query plan is still a major red flag to my eyes. Also, performance changes between versions are usually expected, though most people complain about 9i to 10g results these days :)
    Are you sure you need to be doing a cartesian join at all? As Fly pointed out they have a bad reputation, and yours must be running badly as per your post. I personally get more efficient results from hash joins over sort merges these days so that's something you can look at.
    Try variations on your query to generate execution plans to see if you can get better results. Don't forget to actually time results since plan statistics have been known to be out-of-touch with actual run performance.
    Good luck!

  • MERGE JOIN cartesian help

    Hi All,
    I have a problem in writing the below query. The below query always shows an MERGE JOIN CARTESIAN in the explain plan due to which the query execution takes lot of time(close to 2 hour for 1000 records).
    I'm using "Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi". Please advice if I need to provide more information on this.
    Select to_char(a.amnt_date,'DD-MON-YYYY') amnt_date,
           SUM(a.AMNT_CON) amount
    from amount a,
         (SELECT area_no 
             FROM (SELECT *
                      FROM area_usage
                      WHERE area_hier_no = '201064')
          CONNECT BY area_par_no = PRIOR area_no
          START WITH area_no in (SELECT area_no
                                    FROM area
                                    WHERE area_code in ('EQ'))) b,
         (SELECT acc_no
             FROM (SELECT *
                     FROM acc_usage
                    WHERE acc_hier_no = '1')
          CONNECT BY acc_par_no = PRIOR acc_no
          START WITH acc_no = 202917) c --  Account Hierarchy
    where a.area_no = b.area_no
       AND a.acc_no = c.acc_no
    GROUP BY a.amnt_date-----
    PLAN_TABLE_OUTPUT
    PLAN_TABLE_OUTPUT
    Plan hash value: 2492729134
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop |
    | 0 | SELECT STATEMENT | | 692 | 22144 | 3327 (32)| 00:00:40 | | |
    | 1 | HASH GROUP BY | | 692 | 22144 | 3327 (32)| 00:00:40 | | |
    | 2 | TABLE ACCESS BY LOCAL INDEX ROWID | AMOUNT | 138 | 2898 | 3326 (32)| 00:00:40 | | |
    | 3 | NESTED LOOPS | | 692 | 22144 | 3326 (32)| 00:00:40 | | |
    | 4 | MERGE JOIN CARTESIAN | | 5 | 55 | 13 (0)| 00:00:01 | | |
    | 5 | VIEW | | 1 | 5 | 5 (0)| 00:00:01 | | |
    |* 6 | CONNECT BY WITH FILTERING | | | | | | | |
    | 7 | TABLE ACCESS BY INDEX ROWID | ACC_USAGE | 1 | 24 | 2 (0)| 00:00:01 | | |
    |* 8 | INDEX UNIQUE SCAN | ACU_PK | 1 | | 1 (0)| 00:00:01 | | |
    | 9 | NESTED LOOPS | | | | | | | |
    | 10 | CONNECT BY PUMP | | | | | | | |
    |* 11 | TABLE ACCESS BY INDEX ROWID | ACC_USAGE | 1 | 14 | 5 (0)| 00:00:01 | | |
    |* 12 | INDEX RANGE SCAN | ACU_AH_HAVE_AS_PARENT_FK_I | 4 | | 1 (0)| 00:00:01 | | |
    | 13 | BUFFER SORT | | 5 | 30 | 13 (0)| 00:00:01 | | |
    | 14 | VIEW | | 5 | 30 | 8 (0)| 00:00:01 | | |
    |* 15 | CONNECT BY WITH FILTERING | | | | | | | |
    |* 16 | TABLE ACCESS BY INDEX ROWID | AREA_USAGE | | | | | | |
    | 17 | NESTED LOOPS | | 1 | 32 | 2 (0)| 00:00:01 | | |
    | 18 | TABLE ACCESS BY INDEX ROWID| AREA | 1 | 21 | 2 (0)| 00:00:01 | | |
    |* 19 | INDEX UNIQUE SCAN | AR_AR2_UK | 1 | | 1 (0)| 00:00:01 | | |
    |* 20 | INDEX UNIQUE SCAN | AU_PK | 8608 | 94688 | 0 (0)| 00:00:01 | | |
    | 21 | NESTED LOOPS | | | | | | | |
    | 22 | CONNECT BY PUMP | | | | | | | |
    |* 23 | TABLE ACCESS BY INDEX ROWID | AREA_USAGE | 5 | 85 | 8 (0)| 00:00:01 | | |
    |* 24 | INDEX RANGE SCAN | ARU_APN_FKI | 8 | | 1 (0)| 00:00:01 | | |
    | 25 | PARTITION RANGE ALL | | | | | | 1 | 60 |
    | 26 | BITMAP CONVERSION TO ROWIDS | | | | | | | |
    | 27 | BITMAP AND | | | | | | | |
    | 28 | BITMAP CONVERSION FROM ROWIDS | | | | | | | |
    |* 29 | INDEX RANGE SCAN | A_ARH_FK_I | 194K| | 134 (7)| 00:00:02 | 1 | 60 |
    | 30 | BITMAP CONVERSION FROM ROWIDS | | | | | | | |
    |* 31 | INDEX RANGE SCAN | A_AH_FK_I | 194K| | 488 (41)| 00:00:06 | 1 | 60 |
    Predicate Information (identified by operation id):
    6 - access("ACC_USAGE"."ACC_PAR_NO"=PRIOR "ACC_USAGE"."ACC_NO")
    8 - access("ACC_USAGE"."ACC_NO"=202917 AND "ACC_HIER_NO"=1)
    11 - filter("ACC_HIER_NO"=1)
    12 - access("ACC_USAGE"."ACC_PAR_NO"=PRIOR "ACC_USAGE"."ACC_NO")
    15 - access("AREA_USAGE"."AREA_PAR_NO"=PRIOR "AREA_USAGE"."AREA_NO")
    16 - filter("AREA_HIER_NO"=201064)
    19 - access("AREA_CODE"='EQ')
    20 - access("AREA_HIER_NO"=201064 AND "AREA_USAGE"."AREA_NO"="AREA_NO")
    23 - filter("AREA_HIER_NO"=201064)
    24 - access("AREA_USAGE"."AREA_PAR_NO"=PRIOR "AREA_USAGE"."AREA_NO")
    29 - access("A"."AREA_NO"="B"."AREA_NO")
    31 - access("A"."ACC_NO"="C"."ACC_NO")
    54 rows selected.
    Edited by: Harinath Arasu on Oct 14, 2010 5:31 AM

    That's a very small difference, and I wouldn't expect that to cause huge shifts in an execution plan. Either way to gather statistics you would use the DBMS_STATS package.
    By the way, your "formatted" execution plan isn't exactly readable in your post.
    Looking at your query a little more closely I do recommend you remove the SELECT * from the subqueries. Something like this may suffice:
    Select to_char(a.amnt_date,'DD-MON-YYYY') amnt_date,
           SUM(a.AMNT_CON) amount
    from amount a,
         (SELECT area_no 
             FROM (SELECT area_no
                        , area_par_no
                      FROM area_usage
                      WHERE area_hier_no = '201064')
          CONNECT BY area_par_no = PRIOR area_no
          START WITH area_no in (SELECT area_no
                                    FROM area
                                    WHERE area_code in ('EQ'))) b,
         (SELECT acc_no
             FROM (SELECT acc_no
                        , acc_par_no
                     FROM acc_usage
                    WHERE acc_hier_no = '1')
          CONNECT BY acc_par_no = PRIOR acc_no
          START WITH acc_no = 202917) c --  Account Hierarchy
    where a.area_no = b.area_no
       AND a.acc_no = c.acc_no
    GROUP BY a.amnt_dateUsing a SELECT * and not subsequently using all the columns is hiding valuable information from Oracle. If you provide only the columns used Oracle may be able to find a better execution plan.
    Granted I don't know the table structures so you could actually be using all the columns. I still recommend the change because I think it makes the code easier to understand.

  • Why does Merge Join needs its sources to be sorted

    Hi,
    Can anyone explain why Merge Join needs its sources to be sorted ?
    I saw an explanation in another thread that this is the way to not load all the data to memory, but isnt the data that is about to be merged already all in memory becuase the SORT component waits for all the rows to arrive ?
    Why are there no options for Full cache, Partial Cache and No Cache like in the Lookup component ?

    MERGE Join is one of Join algorithms in SQL Server needs sorted inputs and efficient for large set of records.
    You may refer the below(Craig
    Freedman) link to understand the MERGE JOIN algorithm in details.
    http://blogs.msdn.com/b/craigfr/archive/2006/08/03/merge-join.aspx
    http://technet.microsoft.com/en-us/library/ms137653.aspx
    Nope
    This is SSIS forum and I guess poster is asking about MERGE JOIN transformation in SSIS
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Why the italic function doesn't works in my Pages? I have already installed the actualization and it keeps not working...

    Why the italic function doesn't works in my Pages? I have already installed the actualization and it keeps not working...

    drag the other clip 'over' the main clip
    the 2nd clip has to be selected/yellow border...
    then you're prompted in the Inspector with the several options...

  • Why we use function module u0091SSF_FUNCTION_MODULE_NAMEu0092 in smartform driver p

    Why we use function module ‘SSF_FUNCTION_MODULE_NAME’ in smartform driver program?

    Forum Search
    Use the form below to search the forum content. You can choose to search all content or restrict it to certain forums or dates. Also, you can filter the results by a username or user ID.
    Search Forum Content
    Search Terms:        Search Tips
    Category or Forum:      
    Date Range:      
    Results Per Page:      
    Welcome, Clemens Li      Help
    Your Control Panel      Your Control Panel
    Your Reward Points      Your Reward Points
    Your Questions      Your Questions
    Search Results » Messages: 271 - Search Terms: why we require ‘form interface’ section in smartform?      Sort by:
    Pages: 19 1 2 3 4 5 6 7 8 9 10
       1. Why we require ‘FORM INTERFACE’ section in smartform?
          Posted on: Sep 12, 2007 10:47 PM, by user: p d -- Relevance: 100% -- Show all results within this thread
          Why we require ‘FORM INTERFACE’ section in smartform?
       2. What is the driver program & why we require driver program?
          Posted on: Sep 12, 2007 10:48 PM, by user: p d -- Relevance: 17% -- Show all results within this thread
          What is the driver program & why we require driver program?
       3. Re: form interface in smartform
          Posted on: Feb 21, 2006 11:51 AM, by user: Hasmath -- Relevance: 14% -- Show all results within this thread
          hard-coded driver program in the tables section. for this u have to define the same structure in the form interface of the smartforms and can use the same structure for sending the data to the smartform ...
       4. Smartform: Form Interface
          Posted on: Aug 24, 2007 2:34 PM, by user: vivek pandey -- Relevance: 13% -- Show all results within this thread
          Hi, If we want to use a workarea/internaltable in the form interface of Smartform of a user defined structure ...
       5. Form Interface in Smartforms ?
          Posted on: Oct 27, 2006 5:32 PM, by user: SAP BEE -- Relevance: 12% -- Show all results within this thread
          ztest ) on the table and print the value : &gs_vbap-total&. I activate the form ...it is fine ...as well as program !! Now , when i do the print preview of the form , It gives an error : Reference ...
       6. SmartForms form interface - tables
          Posted on: May 18, 2005 2:44 PM, by user: Diliip Gupchup -- Relevance: 12% -- Show all results within this thread
          Hi All, In smart forms how to declare our internal table in form interface? By using types in global itried but it is ...
       7. Calling thru Form Interface of Smartforms
          Posted on: May 4, 2007 3:03 AM, by user: Subhasish Ganguly -- Relevance: 11% -- Show all results within this thread
          In a Smartforms, how can I call a internal table thru 'Form interface' which has been declared in the driver program? ...
       8. Form Interface in SMARTFORMS
          Posted on: Jun 1, 2006 10:56 AM, by user: Rams V -- Relevance: 11% -- Show all results within this thread
          Hi There, Is it mandatory to create a custom structure in ABAP dictionary to use it in SMARTFORM interface? regards, Rams. ...
       9. Line Types and Table types & Smartform form interface
          Posted on: Sep 21, 2005 3:38 PM, by user: Aadarsh K -- Relevance: 10% -- Show all results within this thread
          types ?? 2. In smartforms form interface, in the importing parameter, can tables be passed ?? [we use tables parameter generally, but even if passed in export parameter, no error is being given and ...
      10. regarding complex section in smartforms
          Posted on: Aug 25, 2007 7:49 AM, by user: ravi -- Relevance: 10% -- Show all results within this thread
          learning smartforms on 5.0ecc and i got the documents which is showing the complex section but in 5.0 ecc we have no complex section cud u plz let me know where sud i add the contents of the complex section ...
      11. why is it that some function module require an endselect
          Posted on: Aug 8, 2007 3:40 PM, by user: mathias Mbizvo -- Relevance: 10% -- Show all results within this thread
          why is it that some function module require an endselect and some can work without the endselect...
      12. Complex section in smartforms
          Posted on: Aug 11, 2007 7:29 PM, by user: narendra veduru -- Relevance: 9% -- Show all results within this thread
          Hi I am practicing smartforms in 4.7. I have a tutorial based on 4.6c and they have complex section in the nodes. How do i ...
      13. form interface using currency fields - smartforms urgent!!!!
          Posted on: Aug 17, 2005 1:11 AM, by user: skmysore -- Relevance: 9% -- Show all results within this thread
          called function module. what is the error here? How can i correct this to display data into the form? Please help me it is urgent!!! Thanks Santhosh ...
      14. why do we activate a program
          Posted on: Feb 28, 2007 5:50 AM, by user: Rose -- Relevance: 8% -- Show all results within this thread
          hi, why do we activate a program or tables in sap.Though there is a option known as save why do we activate? ...
      15. Re: what is form interface and global definitions
          Posted on: Jun 5, 2007 8:25 AM, by user: Venkatesh -- Relevance: 8% -- Show all results within this thread
          Function modules. and global definitions are the variable or tables declared with in the smartform. we can pass values to the smartform from the driver programme through the form interface. if helpful ...
    Pages: 19 [ 1 2 3 4 5 6 7 8 9 10 | Next

  • Why Data Sort is required for Merge Join Transformation

    hi,
    In my understanding Merge Join works very similar to T SQL joins. But I am trying to understand why Sort is a compulsory requirement? I have looked into following article but not helpful
    http://technet.microsoft.com/en-us/library/ms137653(v=sql.105).aspx
    aamertaimor
    aamertaimor

    Merge Join is going to walk through two sets in the order that you gave in your input or using the Sort transformation. So, it loads one record from one input and one record from the second input.  If the keys match, it will output the row with information
    from both inputs.  If the left input has a value that is less than the value in right input, then either the row from the left input is sent out with no right input information (if there is an outer join) or if the join is an inner join, the
    Merge Join component will get the next row from Left input.  If the right input has a value that is less than the value that in the left input, then if there is a full outer join, output the right input with no left input information otherwise, get the
    next row from the right input.
    Here is the beauty, SSIS only needs to retain a couple rows in memory.
    What if Microsoft decided that there is no requirement for sorting?  Then in order for the Merge join to work is that it would load all of the rows from one input into memory and then the Merge Join would look up the row in memory.  That means
    a large amount of memory would be needed.
    By the way, if you want Merge Join behavior without the sort, use a Lookup component.
    Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com

Maybe you are looking for

  • Mac Mini 2012 Poor Wifi

    Hi All, I've had my 2012 Mac Mini (the basis of my home music recording setup) about 9-10 months and always had poor wifi connection. Download speeds are terrible and it can take hours to download a few MBs My provider is Sky Fibre Broadband with the

  • Need help in uploading an excel file into SAP

    Hi All, I got a requirement to upload an excel file to SAP. But When i tried with the FM "ALSM_EXCEL_TO_INTERNAL_TABLE" , file  not getting uploaded to internal table. Getting expection 2, UPLOAD_OLE... I think the problem is with the file... the fol

  • [SOLVED] Windows lag when moved...?

    Using Xfce, with and without composite, the windows lag when being moved. It's like the whole window isn't held together properly; the window movement is kind of choppy, but still smooth, if that makes any sense. This makes for a rather bad experienc

  • Repeated kernel error

    After mounting any AFP volume, the system log show these errors (repeated three times). I have fixed permissions and verified the drive with DiskUtility/fsck. What is causing this and what are the likely consequences? Apr 8 13:43:52 c-imac kernel[0]:

  • Config required for Imports in IMG

    Dear All, Please provide me with some information related to the configuration required for the imports in IMG. What are the settings to be made in Foriegn Trade/Customs. Regards, Venkat.