2016-03-07 208 views
2

這種特殊的查詢工作正常,直到我們在11i的,但只要我們切換到12C查詢一直在做非常糟糕的Oracle查詢。 我試圖刪除提示,它似乎做得好一點,但我們的DBA希望我們刪除所有導致各個子步驟序列化的多個子查詢。我對如何改變它感到不知所措。 關於我能做什麼或開始的任何指針?需要幫助優化12C

 WITH 
     -- Get all active accounts that have not been suspended and the suspension rules 
     -- apply for the account 
     TT1 AS (SELECT 
         pl.employer_id, 
         ma.employee_id, 
         ma.member_account_id, 
         pl.plan_id 
       FROM sa_plans pl, 
         sa_accounts ma 
       WHERE TRUNC(SYSDATE) BETWEEN pl.start_date AND NVL(pl.end_date, TRUNC(SYSDATE)) 
        AND pl.employer_id = 23 
        AND pl.plan_type_id NOT IN (4 
               ,1) 
        AND pl.plan_id = ma.plan_id 
        AND sa_mc_info.fn_ee_susp_exempt(ma.employee_id, DECODE(pl.plan_type_id, 1, 6 ,5)) = 0 
        AND p_outstanding_threshold_perc > 0 
        AND NVL(ma.auto_suspension_flag, 0) = 0 
        AND TRUNC(SYSDATE) BETWEEN ma.account_effective_date AND NVL(ma.account_end_date, TRUNC(SYSDATE)) 
        AND ma.account_effective_date != NVL(ma.account_end_date, ma.account_effective_date + 1) 
      ), 
     -- Get all accounts that were active during the plan year for the current accounts 
     -- and the outstanding transactions 
     TT2 AS (SELECT /*+ MATERIALIZE */ 
         ma1.member_account_id, 
         ma1.plan_id, 
         ma1.employee_id , 
         wwsa.sa_mc_info.fn_acnt_unverified_txns(ma1.member_account_id) outstd_amount 
       FROM sa_accounts ma1, 
         TT1 ma 
       WHERE ma1.account_effective_date != NVL(ma1.account_end_date, ma1.account_effective_date + 1) 
        AND ma1.plan_id = ma.plan_id 
        AND ma1.employee_id = ma.employee_id 
        AND ma1.member_account_id = TT1.member_account_id), 
     -- Sum the outstanding transactions for the EE and plan 
     TT3 AS (SELECT /*+ MATERIALIZE ORDERED */ 
         TT1.member_account_id, 
         SUM(TT2.outstd_amount) outstd_amount 
       FROM TT1, 
         TT2 
       WHERE TT1.employee_id = TT2.employee_id 
        AND TT1.plan_id = TT2.plan_id 
       GROUP BY TT1.member_account_id 
       HAVING SUM(TT2.outstd_amount) > 0),    
     -- Get the current account balance for accounts with outstanding transactions 
     TT4 AS (SELECT /*+ MATERIALIZE ORDERED */ 
         TT1.*, 
         sa_bal_info.fn_account_balance(TT1.member_account_id) balance, 
         TT3.outstd_amount 
       FROM TT1, 
         TT3 
       WHERE TT1.member_account_id = TT3.member_account_id), 
     -- Get the list of accounts that need to be suspended 
     TT5 as (SELECT /*+ MATERIALIZE */ 
         member_account_id, 
         employee_id 
       FROM TT4 
       WHERE outstd_amount > balance * p_outstanding_threshold_perc 
        AND outstd_amount > NVL(p_minimum_threshold_amount, 0) ) 
SELECT * 
    FROM TT5 
ORDER BY employee_id; 

這是解釋計劃

----------------------------------------------------------------------------------------------------------------------- 
| Id | Operation        | Name      | Rows | Bytes | Cost (%CPU)| Time  | 
----------------------------------------------------------------------------------------------------------------------- 
| 0 | SELECT STATEMENT      |        |  1 | 26 | 8622 (1)| 00:00:01 | 
| 1 | TEMP TABLE TRANSFORMATION    |        |  |  |   |    | 
| 2 | LOAD AS SELECT      | SYS_TEMP_0FD9D666F_DCBC1560 |  |  |   |    | 
| 3 | NESTED LOOPS       |        |  4 | 252 | 8600 (1)| 00:00:01 | 
| 4 |  NESTED LOOPS      |        | 1707 | 252 | 8600 (1)| 00:00:01 | 
|* 5 |  TABLE ACCESS BY INDEX ROWID BATCHED| SA_PLANS     |  3 | 84 | 8452 (1)| 00:00:01 | 
| 6 |  INDEX FULL SCAN     | SA_PLANS_PK     | 19218 |  | 75 (2)| 00:00:01 | 
|* 7 |  INDEX RANGE SCAN     | SA_ACCOUNTS_N03    | 569 |  |  2 (0)| 00:00:01 | 
|* 8 |  TABLE ACCESS BY INDEX ROWID   | SA_ACCOUNTS     |  1 | 35 | 67 (0)| 00:00:01 | 
| 9 | LOAD AS SELECT      | SYS_TEMP_0FD9D6670_DCBC1560 |  |  |   |    | 
| 10 | NESTED LOOPS       |        |  3 | 177 |  8 (0)| 00:00:01 | 
| 11 |  NESTED LOOPS      |        |  3 | 177 |  8 (0)| 00:00:01 | 
| 12 |  VIEW        |        |  1 | 26 |  2 (0)| 00:00:01 | 
| 13 |  TABLE ACCESS FULL     | SYS_TEMP_0FD9D666F_DCBC1560 |  1 | 22 |  2 (0)| 00:00:01 | 
|* 14 |  INDEX RANGE SCAN     | SA_ACCOUNTS_N01    |  3 |  |  2 (0)| 00:00:01 | 
|* 15 |  TABLE ACCESS BY INDEX ROWID   | SA_ACCOUNTS     |  3 | 99 |  6 (0)| 00:00:01 | 
| 16 | LOAD AS SELECT      | SYS_TEMP_0FD9D6671_DCBC1560 |  |  |   |    | 
|* 17 | FILTER        |        |  |  |   |    | 
| 18 |  HASH GROUP BY      |        |  1 | 41 |  5 (20)| 00:00:01 | 
|* 19 |  HASH JOIN       |        |  1 | 41 |  4 (0)| 00:00:01 | 
| 20 |  VIEW        |        |  1 | 17 |  2 (0)| 00:00:01 | 
| 21 |  TABLE ACCESS FULL    | SYS_TEMP_0FD9D666F_DCBC1560 |  1 | 22 |  2 (0)| 00:00:01 | 
| 22 |  VIEW        |        |  1 | 24 |  2 (0)| 00:00:01 | 
| 23 |  TABLE ACCESS FULL    | SYS_TEMP_0FD9D6670_DCBC1560 |  1 | 30 |  2 (0)| 00:00:01 | 
| 24 | LOAD AS SELECT      | SYS_TEMP_0FD9D6672_DCBC1560 |  |  |   |    | 
|* 25 | HASH JOIN       |        |  1 | 78 |  4 (0)| 00:00:01 | 
| 26 |  VIEW        |        |  1 | 52 |  2 (0)| 00:00:01 | 
| 27 |  TABLE ACCESS FULL     | SYS_TEMP_0FD9D666F_DCBC1560 |  1 | 22 |  2 (0)| 00:00:01 | 
| 28 |  VIEW        |        |  1 | 26 |  2 (0)| 00:00:01 | 
| 29 |  TABLE ACCESS FULL     | SYS_TEMP_0FD9D6671_DCBC1560 |  1 | 19 |  2 (0)| 00:00:01 | 
| 30 | LOAD AS SELECT      | SYS_TEMP_0FD9D6673_DCBC1560 |  |  |   |    | 
|* 31 | VIEW         |        |  1 | 52 |  2 (0)| 00:00:01 | 
| 32 |  TABLE ACCESS FULL     | SYS_TEMP_0FD9D6672_DCBC1560 |  1 | 48 |  2 (0)| 00:00:01 | 
| 33 | SORT ORDER BY       |        |  1 | 26 |  3 (34)| 00:00:01 | 
| 34 | VIEW         |        |  1 | 26 |  2 (0)| 00:00:01 | 
| 35 |  TABLE ACCESS FULL     | SYS_TEMP_0FD9D6673_DCBC1560 |  1 | 12 |  2 (0)| 00:00:01 | 
----------------------------------------------------------------------------------------------------------------------- 
+0

什麼是在以前的版本計劃(11i的是Oracle應用的版本,我相信你的意圖是在這裏說,這在以前的版本一樣11g中的Oracle數據庫的運行良好)?您發佈的查詢仍然有一些提示,但在問題的文本中說,您刪除了令人困惑的「提示」。您發佈的查詢計劃是否來自包含所有提示的查詢版本?或提示刪除的那個? –

+1

缺少「謂詞信息」 - 它打印在計劃表下,你可以用它補充計劃嗎? – krokodilko

+0

我會拿出具體化,並下令提示,(甲骨文將決定他應該怎麼使用),我會嘗試並行(8)提示來代替。優化其關於「瞄準射擊 - 瞄準 - 射擊......」,因爲它取決於事情 – Thomas

回答

0

嘗試執行TT1和評估的執行時間。如果沒有問題,則繼續使用TT1 + TT2等。你需要了解問題出在解決之前。

0

我會假設你的問題是直接關係到一個不錯的計劃。

所以,如你所說,它表現得很好的11g數據庫所以有基本的兩件事情你可以做來嘗試解決一個短期的方式你的問題:

  1. 檢查OPTIMIZER_FEATURES_ENABLE參數在12c版本。如果它設置爲12. *或較高版本,請嘗試將正在運行查詢的會話降級到舊數據庫的11. *版本。

  2. 假設你有優化包(許可問題 - 照顧)使能爲您的生產環境中,你可以使用SQL配置文件。怎麼樣?您可以手動將您的計劃從11g複製並導入到12c數據庫。看看dbms_sqltune.import_sql_profile。 https://oracle-randolf.blogspot.com.br/2009/03/plan-stability-in-10g-using-existing.html

正如我前面所說,這些都是短期行爲。評估你的SQL會更好。