Solved

Insert is taking long time

Posted on 2009-04-10
3
1,303 Views
Last Modified: 2013-12-19
The insert procedure which is select all the row at this moment taking long time.

Select query is giving result in only minutes.

We are getting waits on
log file switch completion
log file switch (checkpoint incomplete)
Latch free

Size of redo log is 50MB.

Please have a look.


Query:
 
Insert Query:
INSERT /*+parallel(TB_DIM_ALL_CUST_ACCT,3)*/
INTO TB_DIM_ALL_CUST_ACCT
  (ALL_CUST_SKEY,
   CUST_SKEY,
   MDM_PARTY_ID,
   MDM_SRCE_ID,
   CUST_SSK,
   DDD_NUM,
   DDD_SUB_CAT_CD,
   HIN,
   DEA_NUM,
   SRCE_CUST_TYPE_CD,
   SRCE_MDM_CUST_TYPE_CD,
   SRCE_ORG_NAME,
   SRCE_FULL_NAME,
   STAT_CD,
   CUST_EXCPTN_FLG,
   EFF_END_DATE,
   MDM_INS_DATE,
   MDM_LAST_MOD_DATE,
   DW_INS_DATE,
   DW_LAST_MOD_DATE,
   DW_LAST_MOD_BY,
   DW_SRCE_ID,
   CURR_IND)
--  explain plan for
  SELECT B.ALL_CUST_SKEY,
         B.CUST_SKEY,
         B.MDM_PARTY_ID,
         B.MDM_SRCE_ID,
         B.CUST_SSK,
         B.DDD_NUM,
         B.DDD_SUB_CAT_CD,
         B.HIN,
         B.DEA_NUM,
         B.SRCE_CUST_TYPE_CD,
         B.SRCE_MDM_CUST_TYPE_CD,
         B.SRCE_ORG_NAME,
         B.SRCE_FULL_NAME,
         B.STAT_CD,
         B.CUST_EXCPTN_FLG,
         B.EFF_END_DATE,
         B.MDM_INS_DATE,
         B.MDM_LAST_MOD_DATE,
         SYSDATE,
         SYSDATE,
         B.DW_LAST_MOD_BY,
         B.DW_SRCE_ID,
         B.CURR_IND
    FROM TB_DIM_ALL_CUST_ACCT_HIST B
   WHERE (B.CDW_EFF_START_DATE = TO_DATE('2009-03-25', 'YYYY-MM-DD') + 1 OR
         B.CUST_EXCPTN_FLG = 'Y')
     AND B.CURR_IND = 'C'
            AND NOT EXISTS (SELECT 1
            FROM TB_DIM_ALL_CUST_ACCT A
           WHERE A.ALL_CUST_SKEY = B.ALL_CUST_SKEY)
 
Explain Plan:
 
 
SQL Statement which produced this data:
  select * from table(dbms_xplan.display())
 
PLAN_TABLE_OUTPUT
Plan hash value: 713779952
 
-------------------------------------------------------------------------------------------------------------------
| Id  | Operation             | Name                      | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
-------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT      |                           |  2513K|   431M|  8155   (2)| 00:02:27 |       |       |
|   1 |  NESTED LOOPS ANTI    |                           |  2513K|   431M|  8155   (2)| 00:02:27 |       |       |
|   2 |   PARTITION HASH ALL  |                           |  2513K|   400M|  8155   (2)| 00:02:27 |     1 |     3 |
|*  3 |    TABLE ACCESS FULL  | TB_DIM_ALL_CUST_ACCT_HIST |  2513K|   400M|  8155   (2)| 00:02:27 |     1 |     3 |
|*  4 |   INDEX FAST FULL SCAN| PK_TB_DIM_ALL_CUST_ACCT   |     1 |    13 |     0   (0)| 00:00:01 |       |       |
-------------------------------------------------------------------------------------------------------------------
 
Predicate Information (identified by operation id):
---------------------------------------------------
 
   3 - filter(("B"."CDW_EFF_START_DATE"=TO_DATE('2009-03-26 00:00:00', 'yyyy-mm-dd hh24:mi:ss') OR 
              "B"."CUST_EXCPTN_FLG"='Y') AND "B"."CURR_IND"='C')
   4 - filter("A"."ALL_CUST_SKEY"="B"."ALL_CUST_SKEY")

Open in new window

0
Comment
Question by:sachin_dba
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 

Author Comment

by:sachin_dba
ID: 24115052
On the dev DB where there is only one partition, and insert is running in 10 mins.

Explain plan and waits on session attached.
Dev:
 
--------------------------------------------------------------------------------------------------------------------
| Id  | Operation              | Name                      | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
--------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT       |                           |     1 |   173 | 13889   (6)| 00:02:47 |       |       |
|   1 |  NESTED LOOPS ANTI     |                           |     1 |   173 | 13889   (6)| 00:02:47 |       |       |
|   2 |   PARTITION HASH SINGLE|                           |     1 |   167 | 13888   (6)| 00:02:47 |     1 |     1 |
|*  3 |    TABLE ACCESS FULL   | TB_DIM_ALL_CUST_ACCT_HIST |     1 |   167 | 13888   (6)| 00:02:47 |     1 |     1 |
|*  4 |   INDEX UNIQUE SCAN    | PK_TB_DIM_ALL_CUST_ACCT   |     1 |     6 |     1   (0)| 00:00:01 |       |       |
--------------------------------------------------------------------------------------------------------------------
 
Predicate Information (identified by operation id):
---------------------------------------------------
 
   3 - filter(("B"."CDW_EFF_START_DATE"=TO_DATE('2009-03-26 00:00:00', 'yyyy-mm-dd hh24:mi:ss') OR 
              "B"."CUST_EXCPTN_FLG"='Y') AND "B"."CURR_IND"='C')
   4 - access("A"."ALL_CUST_SKEY"="B"."ALL_CUST_SKEY")
 
Test:
 
-------------------------------------------------------------------------------------------------------------------
| Id  | Operation             | Name                      | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
-------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT      |                           |  2513K|   431M|  8155   (2)| 00:02:27 |       |       |
|   1 |  NESTED LOOPS ANTI    |                           |  2513K|   431M|  8155   (2)| 00:02:27 |       |       |
|   2 |   PARTITION HASH ALL  |                           |  2513K|   400M|  8155   (2)| 00:02:27 |     1 |     3 |
|*  3 |    TABLE ACCESS FULL  | TB_DIM_ALL_CUST_ACCT_HIST |  2513K|   400M|  8155   (2)| 00:02:27 |     1 |     3 |
|*  4 |   INDEX FAST FULL SCAN| PK_TB_DIM_ALL_CUST_ACCT   |     1 |    13 |     0   (0)| 00:00:01 |       |       |

Open in new window

sess-waits.JPG
0
 
LVL 3

Accepted Solution

by:
mganesh earned 500 total points
ID: 24121552
At first look, it looks you need to increase the redolog file size. 50MB is the default and is seldom enough for DMLs of decent weightage.

There are two things you can do initially:

1. Check the number of indexes on TB_DIM_ALL_CUST_ACCT and see if they are same in both your environments. Unwanted indexes slow down inserts.

2. I would suggest you to increase your redolog size to 256 MB at the minimum and observe the waits
0
 

Author Closing Comment

by:sachin_dba
ID: 31568859
No one looked at the explain plan.
0

Featured Post

Salesforce Has Never Been Easier

Improve and reinforce salesforce training & adoption using WalkMe's digital adoption platform. Start saving on costly employee training by creating fast intuitive Walk-Thrus for Salesforce. Claim your Free Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why doesn't the Oracle optimizer use my index? Querying too much data Most Oracle developers know that an index is useful when you can use it to restrict your result set to a small number of the total rows in a table. So, the obvious side…
Background In several of the companies I have worked for, I noticed that corporate reporting is off loaded from the production database and done mainly on a clone database which needs to be kept up to date daily by various means, be it a logical…
This video explains at a high level with the mandatory Oracle Memory processes are as well as touching on some of the more common optional ones.
This video shows setup options and the basic steps and syntax for duplicating (cloning) a database from one instance to another. Examples are given for duplicating to the same machine and to different machines

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question