How to clear failed execution Plans?

Hello world

This should be an easy thing, but I can't seem to find a way to do it.

I created a custom implementation plan and added each financial area in the plan. Then I generated settings, you click on build and then he ran. Failed to run.

I noticed that there is a pre-configured with "R12 Financials_Oracle" execution plan and decided that I wanted to really run was Financials_Oracle R12 and not my personal plan. So I clicked on build for R12 Financials_Oracle plan of execution, and once it is finished, I clicked 'Run Now'. When you click Run now he told me that my custom implementation plan was completed with a failed State and until she is done correctly, no other plan could be run. I really don't want my custom plan completes successfully. I want to run the other plan instead.

How to remove/delete on my failure run data so I can start a new execution plan?

Thanks for the help!

-Joe

In DACS under the window RUN, do the following:
-Go to the tab "Run in progress".
-Highlight the execution plan has failed.
-Click right and selected 'Brand.' as completed
-Enter the number/text in the box.

Then:

-In the toolbar at the top of the page, select--> management ETL tools--> reset Data Sources
-Enter the number/text in the boox.

Now you are ready to start the new execution plan.

I hope this helps.

-Austin

Tags: Business Intelligence

1)

SQL> WITH CTATEL AS
  2  (SELECT A.CTA_FACTURAC, A.NUM_TELEFONO
  3  FROM PFA_CONTABON A, PGA_CTAFACTU B, PGA_ABONOS C
  4  WHERE B.CTA_FACTURAC=A.CTA_FACTURAC
  5  AND C.NUM_TELEFONO=A.NUM_TELEFONO)
  6  SELECT 71, A.CTA_FACTURAC, B.NUM_TELEFONO, A.COD_CONFACTU, SYSDATE, 0, A.TOT_IMPORTE*166.386, A.TOT_IMPORTE, 'E'
  7  FROM SOL_FICHERO a, CTATEL b
  8  WHERE ID_SOLICITUD=71
  9  AND A.CTA_FACTURAC=B.CTA_FACTURAC
 10  AND (A.NUM_TELEFONO IS NULL OR (A.NUM_TELEFONO <> '0' AND B.NUM_TELEFONO IS NOT NULL AND A.NUM_TELEFONO=B.NUM_TELEFONO))
 11  AND A.COD_CONFACTU IS NOT NULL AND  EXISTS (SELECT 1 FROM PGSM_CONFACTU WHERE COD_CONFACTU=A.COD_CONFACTU);

Execution Plan
----------------------------------------------------------
Plan hash value: 711563975

---------------------------------------------------------------------------------------------------
| Id  | Operation                       | Name            | Rows  | Bytes | Cost (%CPU)| Time     |
---------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                |                 |     1 |    64 |     6   (0)| 00:00:01 |
|   1 |  NESTED LOOPS                   |                 |     1 |    64 |     6   (0)| 00:00:01 |
|   2 |   NESTED LOOPS                  |                 |     1 |    54 |     5   (0)| 00:00:01 |
|   3 |    NESTED LOOPS                 |                 |     1 |    45 |     4   (0)| 00:00:01 |
|   4 |     NESTED LOOPS SEMI           |                 |     1 |    26 |     2   (0)| 00:00:01 |
|*  5 |      TABLE ACCESS BY INDEX ROWID| SOL_FICHERO     |     2 |    44 |     2   (0)| 00:00:01 |
|*  6 |       INDEX RANGE SCAN          | SOL_FICHERO_I01 |     6 |       |     1   (0)| 00:00:01 |
|*  7 |      INDEX UNIQUE SCAN          | PK_CONFACTU     |  5820 | 23280 |     0   (0)| 00:00:01 |
|*  8 |     INDEX RANGE SCAN            | PK_CONTABON     |     1 |    19 |     2   (0)| 00:00:01 |
|*  9 |    INDEX UNIQUE SCAN            | PK_CTAFACTU     |     1 |     9 |     1   (0)| 00:00:01 |
|* 10 |   INDEX UNIQUE SCAN             | PK_ABONOS       |     1 |    10 |     1   (0)| 00:00:01 |
---------------------------------------------------------------------------------------------------

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

   5 - filter("A"."COD_CONFACTU" IS NOT NULL)
   6 - access("ID_SOLICITUD"=71)
   7 - access("COD_CONFACTU"="A"."COD_CONFACTU")
   8 - access("A"."CTA_FACTURAC"="A"."CTA_FACTURAC")
       filter("A"."NUM_TELEFONO" IS NULL OR "A"."NUM_TELEFONO"="A"."NUM_TELEFONO" AND
              "A"."NUM_TELEFONO"<>'0')
   9 - access("B"."CTA_FACTURAC"="A"."CTA_FACTURAC")
  10 - access("C"."NUM_TELEFONO"="A"."NUM_TELEFONO")

2)

SQL> WITH CTATEL AS
  2  (SELECT A.CTA_FACTURAC, A.NUM_TELEFONO
  3  FROM PFA_CONTABON A, PGA_CTAFACTU B, PGA_ABONOS C
  4  WHERE B.CTA_FACTURAC=A.CTA_FACTURAC
  5  AND C.NUM_TELEFONO=A.NUM_TELEFONO)
  6  SELECT 71, A.CTA_FACTURAC, NULL, A.COD_CONFACTU, SYSDATE, 0, A.TOT_IMPORTE*166.386, A.TOT_IMPORTE, 'E'
  7  FROM SOL_FICHERO a
  8  WHERE ID_SOLICITUD=71
  9  AND A.NUM_TELEFONO IS NOT NULL AND A.NUM_TELEFONO='0'
 10  AND EXISTS (SELECT 1 FROM CTATEL b WHERE A.CTA_FACTURAC=B.CTA_FACTURAC)
 11  AND A.COD_CONFACTU IS NOT NULL AND  EXISTS (SELECT 1 FROM PGSM_CONFACTU WHERE COD_CONFACTU=A.COD_CONFACTU);

Execution Plan
----------------------------------------------------------
Plan hash value: 3992598922

-------------------------------------------------------------------------------------------------
| Id  | Operation                     | Name            | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT              |                 |     1 |    26 |     7   (0)| 00:00:01 |
|*  1 |  FILTER                       |                 |       |       |            |          |
|   2 |   NESTED LOOPS SEMI           |                 |     1 |    26 |     2   (0)| 00:00:01 |
|*  3 |    TABLE ACCESS BY INDEX ROWID| SOL_FICHERO     |     1 |    22 |     2   (0)| 00:00:01 |
|*  4 |     INDEX RANGE SCAN          | SOL_FICHERO_I01 |     6 |       |     1   (0)| 00:00:01 |
|*  5 |    INDEX UNIQUE SCAN          | PK_CONFACTU     |  5820 | 23280 |     0   (0)| 00:00:01 |
|   6 |   NESTED LOOPS                |                 |     1 |    38 |     5   (0)| 00:00:01 |
|   7 |    NESTED LOOPS               |                 |     1 |    28 |     4   (0)| 00:00:01 |
|*  8 |     INDEX UNIQUE SCAN         | PK_CTAFACTU     |     1 |     9 |     2   (0)| 00:00:01 |
|*  9 |     INDEX RANGE SCAN          | PK_CONTABON     |     1 |    19 |     2   (0)| 00:00:01 |
|* 10 |    INDEX UNIQUE SCAN          | PK_ABONOS       |     1 |    10 |     1   (0)| 00:00:01 |
-------------------------------------------------------------------------------------------------

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

   1 - filter( EXISTS (SELECT /*+ */ 0 FROM "FACTMS"."PGA_ABONOS_1"
              "C","FACTMS"."PGA_CTAFACTU" "B","FACTMS"."PFA_CONTABON_1" "A" WHERE
              "B"."CTA_FACTURAC"="A"."CTA_FACTURAC" AND "A"."CTA_FACTURAC"=:B1 AND
              "B"."CTA_FACTURAC"=:B2 AND "C"."NUM_TELEFONO"="A"."NUM_TELEFONO"))
   3 - filter("A"."COD_CONFACTU" IS NOT NULL AND "A"."NUM_TELEFONO" IS NOT NULL AND
              "A"."NUM_TELEFONO"='0')
   4 - access("ID_SOLICITUD"=71)
   5 - access("COD_CONFACTU"="A"."COD_CONFACTU")
   8 - access("B"."CTA_FACTURAC"=:B1)
   9 - access("B"."CTA_FACTURAC"="A"."CTA_FACTURAC")
       filter("A"."CTA_FACTURAC"=:B1)
  10 - access("C"."NUM_TELEFONO"="A"."NUM_TELEFONO")

3)

  1  WITH CTATEL AS
  2  (SELECT A.CTA_FACTURAC, A.NUM_TELEFONO
  3  FROM PFA_CONTABON A, PGA_CTAFACTU B, PGA_ABONOS C
  4  WHERE B.CTA_FACTURAC=A.CTA_FACTURAC
  5  AND C.NUM_TELEFONO=A.NUM_TELEFONO)
  6  SELECT 71, A.CTA_FACTURAC, B.NUM_TELEFONO, A.COD_CONFACTU, SYSDATE, 0, A.TOT_IMPORTE*166.386, A.TOT_IMPORTE, 'E'
  7  FROM SOL_FICHERO a, CTATEL b
  8  WHERE ID_SOLICITUD=71
  9  AND A.CTA_FACTURAC=B.CTA_FACTURAC
 10  AND (A.NUM_TELEFONO IS NULL OR (A.NUM_TELEFONO <> '0' AND B.NUM_TELEFONO IS NOT NULL AND A.NUM_TELEFONO=B.NUM_TELEFONO))
 11  AND A.COD_CONFACTU IS NOT NULL AND  EXISTS (SELECT 1 FROM PGSM_CONFACTU WHERE COD_CONFACTU=A.COD_CONFACTU)
 12  UNION ALL
 13  SELECT 71, A.CTA_FACTURAC, NULL, A.COD_CONFACTU, SYSDATE, 0, A.TOT_IMPORTE*166.386, A.TOT_IMPORTE, 'E'
 14  FROM SOL_FICHERO a
 15  WHERE ID_SOLICITUD=71
 16  AND A.NUM_TELEFONO IS NOT NULL AND A.NUM_TELEFONO='0'
 17  AND EXISTS (SELECT 1 FROM CTATEL b WHERE A.CTA_FACTURAC=B.CTA_FACTURAC)
 18* AND A.COD_CONFACTU IS NOT NULL AND  EXISTS (SELECT 1 FROM PGSM_CONFACTU WHERE COD_CONFACTU=A.COD_CONFACTU)


Execution Plan
----------------------------------------------------------
Plan hash value: 3945970136

-----------------------------------------------------------------------------------------------------------------------
| Id  | Operation                       | Name                        | Rows  | Bytes |TempSpc| Cost (%CPU)| Time     |
-----------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                |                             |  3351 |   127K|       |   776  (53)| 00:00:10 |
|   1 |  TEMP TABLE TRANSFORMATION      |                             |       |       |       |            |          |
|   2 |   LOAD AS SELECT                |                             |       |       |       |            |          |
|*  3 |    HASH JOIN                    |                             |   323K|    11M|    12M| 66832   (4)| 00:13:22 |
|*  4 |     HASH JOIN                   |                             |   338K|  9254K|  4176K| 39353   (3)| 00:07:53 |
|   5 |      INDEX FAST FULL SCAN       | PK_CTAFACTU                 |   203K|  1788K|       |   190   (4)| 00:00:03 |
|   6 |      INDEX FAST FULL SCAN       | PK_CONTABON                 |    16M|   300M|       | 13975   (4)| 00:02:48 |
|   7 |     INDEX FAST FULL SCAN        | PK_ABONOS                   |    15M|   150M|       |  9766   (5)| 00:01:58 |
|   8 |   UNION-ALL                     |                             |       |       |       |            |          |
|*  9 |    HASH JOIN                    |                             |  3350 |   127K|       |   388   (5)| 00:00:05 |
|  10 |     NESTED LOOPS SEMI           |                             |     1 |    26 |       |     2   (0)| 00:00:01 |
|* 11 |      TABLE ACCESS BY INDEX ROWID| SOL_FICHERO                 |     2 |    44 |       |     2   (0)| 00:00:01 |
|* 12 |       INDEX RANGE SCAN          | SOL_FICHERO_I01             |     6 |       |       |     1   (0)| 00:00:01 |
|* 13 |      INDEX UNIQUE SCAN          | PK_CONFACTU                 |  5820 | 23280 |       |     0   (0)| 00:00:01 |
|  14 |     VIEW                        |                             |   323K|  4112K|       |   379   (4)| 00:00:05 |
|  15 |      TABLE ACCESS FULL          | SYS_TEMP_0FD9D6621_1BE166BB |   323K|  6009K|       |   379   (4)| 00:00:05 |
|* 16 |    HASH JOIN SEMI               |                             |     1 |    33 |       |   388   (5)| 00:00:05 |
|  17 |     NESTED LOOPS SEMI           |                             |     1 |    26 |       |     2   (0)| 00:00:01 |
|* 18 |      TABLE ACCESS BY INDEX ROWID| SOL_FICHERO                 |     1 |    22 |       |     2   (0)| 00:00:01 |
|* 19 |       INDEX RANGE SCAN          | SOL_FICHERO_I01             |     6 |       |       |     1   (0)| 00:00:01 |
|* 20 |      INDEX UNIQUE SCAN          | PK_CONFACTU                 |  5820 | 23280 |       |     0   (0)| 00:00:01 |
|  21 |     VIEW                        |                             |   323K|  2214K|       |   379   (4)| 00:00:05 |
|  22 |      TABLE ACCESS FULL          | SYS_TEMP_0FD9D6621_1BE166BB |   323K|  6009K|       |   379   (4)| 00:00:05 |
-----------------------------------------------------------------------------------------------------------------------

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

   3 - access("C"."NUM_TELEFONO"="A"."NUM_TELEFONO")
   4 - access("B"."CTA_FACTURAC"="A"."CTA_FACTURAC")
   9 - access("A"."CTA_FACTURAC"="B"."CTA_FACTURAC")
       filter("A"."NUM_TELEFONO" IS NULL OR "A"."NUM_TELEFONO"="B"."NUM_TELEFONO" AND "A"."NUM_TELEFONO"<>'0')
  11 - filter("A"."COD_CONFACTU" IS NOT NULL)
  12 - access("ID_SOLICITUD"=71)
  13 - access("COD_CONFACTU"="A"."COD_CONFACTU")
  16 - access("A"."CTA_FACTURAC"="B"."CTA_FACTURAC")
  18 - filter("A"."COD_CONFACTU" IS NOT NULL AND "A"."NUM_TELEFONO" IS NOT NULL AND "A"."NUM_TELEFONO"='0')
  19 - access("ID_SOLICITUD"=71)
  20 - access("COD_CONFACTU"="A"."COD_CONFACTU")

I use this WITH clausule in the query above:

operating system

WITH CTATEL AS 
(SELECT A.CTA_FACTURAC, A.NUM_TELEFONO 
FROM PFA_CONTABON A, PGA_CTAFACTU B, PGA_ABONOS C 
WHERE B.CTA_FACTURAC=A.CTA_FACTURAC 
AND C.NUM_TELEFONO=A.NUM_TELEFONO)

Why 3) plan is so bad? (In any case, it's like "UNION ALL" of 1) and 2).

Thanks in advance,

Jose Luis

We do not know if one of them is 'bad' plans.

In fact, there is no such thing as a bad plan, one or several inaccurate estimates.

To determine whether a plan is 'bad', you really see who believes are inaccurate - and which means the time of execution of the execution plans and runtime enforcement measures.

Please take a look at the notice in the following thread:

HOW to: Validate a query of SQL statement tuning - model showing

What happens in the third SQL, is that because you referenced the subquery WITH twice, Oracle decides to materialise it in a temporary table for the reason that it is cheaper that to do the same thing one subquery normally twice - a reasonable approach.

It is probably more likely that the third query estimates are more accurate than the other two.

Star_transformation not shoiwng in the execution plan
Hello

We have a data warehouse and processing star not no projection in the execution plan.

STAR_TRANSFORMATION_ENABLED at the database level.

With the help of 11.2.0.3 on AIX

The fact table has index bitmap and fks to keys on tables dimesnion dimesnion.

Example query
```
select *
from media m, retailer_transaction rt
, retailer r
where m.dimension_key = rt.plant_issue_id
and rt.outlet_id = r.dimension_key
and prod_num = 600
```
Anthing we are ' % s '?

Found how interrogate more selective cause said to use star_transformation

added and plis_handled_year = 2013
and out_num 123423

Why is this good?

Is there a rule such as only highly selective queries will use transformation star?

Thank you

Published by: user5716448 on February 15, 2013 04:10
Transformation of Star I it'sactually one expensive thing to do. So, the optimizer plans an ABC on this subject. This quote comes from a piece on the blog of optimizer Oracle [url https://blogs.oracle.com/optimizer/entry/star_transformation]:

"The transformation is performed based on cost - when the cost of the transformed plan is lower than that of the unprocessed plan. If dimension filters do not significantly reduce the amount of data to be extracted from the fact table, and then a full table scan is more effective. »

Cheers, APC

How to clear forecasts already generated Demantra
Hi all

We are new demantra organization of the user. Recently after Go-live we decided to not to generate forecasts for a bunch of items. As a result, we turned off the indicator 'not' forecast and restart the engine. However, our horizon is 102 weeks. Thus, in previous weeks of engine, we had planned already apply to these shipments of 100 weeks.

Now, after turning off this flag and re-run the engine, demantra does not generate new forecast for them. But the old forecasts remain in the system. How to clear these forecasts?

Any help will be appreciated.

Thank you

Roger
Hello

You have two options here:
1 consider to change the flag 'Make zero forecast', forcing the engine generates a forecast of ZERO for these old/inactive/disabled. You will need to also get rid of substitutions of forecasts of manual that you have in other series to completely reduce the final forecast to ZERO.

2 see parameter 'ResetForeVals' in the system settings > engine > tab Shell shape business. You can set this parameter to the value "Yes" or "All". Remember that a setting of 'All' will affect the engine time, mainly the time engine would take to clean the column FORE_X before generating a new forecast.

Thank you
REDA

Get the SQL execution plan that is currently running in 9i
Hello

Apologies for the magnitude of this issue, but I was wondering if someone could help me to the more accurate/efficient way to get a piece of running Oracle 9i SQL execution plan.

in 10g and 11g of course dbms_xplan.display_cursor (sql_id) can be used.

How can this be achieved in 9i, currently I am just get the SQL_TEXT and then executing a plan to explain ("EXPLAIN PLAN for.") - I think that this is not neccesserally the same plan to explain that will be used for the sql code that runs if

Any help would be appreciated.

Thank you
The plan exists after analysis difficult.
Statistics of actual execution will require a completed.
That is why sql followed in real time is so great in 11g.
In 9i, difficult.

How to clear failed execution Plans?

Similar Questions

1)

2)

3)

Maybe you are looking for