Re: view opaque and the materialized view

Similar Questions

• diff between the view and the materialized view

  Hi all
  
  Whats different between the view and the materialized view?
  
  could someone help me pls this topic
  
  thnks in advance

  See nothing else that a set is a set of sql statements that join the single or multiple tables and shows the data... However views do not have the data themselves but point to the data.

  Whereas the materialized view is a concept used primarily in the Datawarehousing... these views contain the data itself. Reason being, it is more easy/quick access to the data. The main objective of Materialized view is to perform calculations and display data from multiple tables by using joins.
  check out the link for more information below.
  http://www.geekinterview.com/question_details/29332

  rajeysh
  http://oracleinstance.blogspot.com

• The upper part of the page is not opaque, and the office is reflected. Thus, the menu bar is difficult to read. How to remedy this?

  The area behind the menu bar and the line above, all the way through to minimize, maximize, and close icons is not opaque and the desktop and the desktop icons appear through. There is nothing I can find in Firefox help to change this. In addition, it would be nice if the menu bar could be bigger and more visible - and if I could delete "Yahoo!" from the menu bar, leaving only the important items (File, Edit, View, history, Favorites, tools, help). Any suggestions?

  See:

  • [804050/questions/804050]

  Right-click in the free space on your desktop.
  
  Left click on personalization.
  
  There are four options in Windows 7 at the bottom of the screen, select 'window color and appearance '.
  
  Select a border color
  
  Uncheck the box: "enable transparency".

• Difference between the view and the materialized view

  Hi all
  
  Can someone tell me exactly the difference between the view and materialized views?

  Hello

  View:-this is a virtual table means table is there, but in fact is not there...
  see how to create a view...

   create or replace view aaa as select * from emp; 
  

  Now, when we choose the AAA, he will show me all the data that would be returned by running a query "Select * from emp"... Thus, all data will come from table iteself.
  View in itself is nothing but just a Sql statement that is used to create the view, in this case definition is "select * from emp.
  Any update in the database table Emp which is in our case, would automatically result in the view...
  Any changes (all dml) will actually update the base table (conditions apply *)

  Now the materialized view:-this is the same as except that it is not a virtual table... This will be created separately and it will acutally hold the result of the query that is used to create it. Any subsequent changes in the base table only will be included in the opinion of M M view is refreshed...

• I get "failed to set the refresh attribute COMMIT for the materialized view" when I try to create a MV using a table and another MV

  Experts,

  I'm trying to create a YOUNG refreshable ON COMMIT MV (xyz) using a table (circuit) and quickly updateable on validation MV (abc), but get an error:

  SQL error: ORA-12054: cannot set the attribute ON COMMIT refresh for the materialized view

  12054 00000 - "cannot set the refresh attribute COMMIT for the materialized view.

  * Cause: The materialized view did not meet the requirements for update to

  moment of validation.

  * Action: Specify only valid options.

  1] MV abc
  = MV abc defined as below =.

  CREATE MATERIALIZED view abc_MV

  Immediate CONSTRUCTION

  REFRESH QUICKLY YOU COMMIT using constraints of trust

  WITH ROWID AS SELECT n.*,.

  n.ROWID noderowid

  node n

  where n.nodetype in (1610000069,1610007267);

  
  

  -Above works OK and MV connect you on table node is created successfully

  =====================================================

  [ 2] Circuit Board

  ======================================================

  CREATE MATERIALIZED VIEW LOG ON Cramer.Circuit WITH SEQUENCE, ROWID ( ) -all columns of table ofcircut parentheses

  INCLUDING THE NEW VALUES;

  -More top works OK and MV connect you on table circuit is created successfully

  ======================================================
  

  
  

  
  

  [3] trying to create MV xyz
  

  ======================================================

  CREATE MATERIALIZED VIEW LOG ON cramer.abc_MV WITH SEQUENCE, ROWID ( ) -all columns of abc_MV brackets

  INCLUDING THE NEW VALUES;

  -Above works OK and log on ABC MV MV gets created successfully

  -Problematic step below

  Xyz_MV CREATE MATERIALIZED VIEW

  IMMEDIATE CONSTRUCTION

  REFRESH QUICKLY YOU COMMIT using constraints of trust

  AS

  SELECT c., c.rowid circuit_rowid, n.rowid tr_rowid

  the circuit c, abc_mv n

  where circuit2startnode = n.nodeid

  and c.rpplanId = n.rpplanId;
  ==========================================================

  Clues on how to solve this problem and make quickly updatable ON Commit MV xyz

  Thanks in advance.

  Chanchal,

  If you can read my original post carefully you may have noticed that all these restrictions will not apply in my case.

  All,

  In any case I found the solution to my problem.

  There are a few additional restrictions for materialized views multilayer

  Additional Restrictions for master materialized views

  The following types of materialized views may not be masters of editable materialized views:

  • ROWIDmaterialized views
  • Complex materialized views
  • Read-only materialized views

  I've updated the underlying MV abc below and everything worked like a charm

  CREATE MATERIALIZED view abc_MV

  Immediate CONSTRUCTION

  REFRESH QUICKLY YOU COMMIT using constraints of trust

  IN SELECT

  n.*, n.rowid noderowid, nt.rowid nodetyperowid

  the node n, nodetype_m nt

  where n.node2nodetype = nt.nodetypeid

  and nt.nodetypeid in (1610000069,1610007267);

  Note: To ADD a join without which I was getting error below (although had primary key on the table of the node)

  SQL error: ORA-23415: materialized view log for "NODE" does not save the primary key

  23415 00000 - "view the log for materialized \"%s\".\"%s\"does not save the primary key.

  * Cause: A primary key materialized view is refreshed quickly, but the

  The materialized view log does not record the primary key information.

  * Action: Use CREATING MATERIALIZED VIEW LOG... Command to add a PRIMARY KEY to

  start recording of the primary key information in the materialized view

  Newspaper.

• The materialized view log and user...

  Hello
  Suppose a user, we will call him A has a table and another user B must create a log of materialized view on the table that a user has.
  While user B have all the privileges of object (direct priv insert, update, delete... not through a role) on the table to the user may not create a log of mv on this table on its schema...
  Thus, the insert/update/delete stmts on < table_name > are run successfully (after having logged on as user B).
  
  The error message ' ORA-00942: table or view does not exist ' appears when I run the command:
  Connect B/B;
  create log view materialized on table_name with sequence including new values;
  
  Note: I use ORADB 10.2.0.4 and it stands for table-name to user B (which tries to create the log of mv on)...
  
  The req. above is possible somehow?
  
  Thank you
  SIM

  The documentation says the following:

  The materialized view log is created in the same schema as the master of the target.

  HTH!

• Trigger on the materialized view

  Hello

  I have the scenario based (Database 11 g):

  There is a view materialized (PERSON), which contains the ID and NAME fields. This MV is update daily with a fast refresh.

  I have a second array (NAMES), with ID and NORM_NAME. This table contains the name of the person, without special characters.

  For example, for recording / * 1 BJORN * / in the PERSON table

  I would check * 1 BJORN * / in table NAMES.

  
  

  Problem is how to fill the NAME table after the filling of the materialized view.

  I used a trigger AFTER INSERT or update, as described below, but even if I update the master table (for this purpose, update the MV), I have only to trigger inserts.

  
  

  Is there a way to implement a trigger "after update" on a materialized view, or do I need another approach?
  

  
  

  /*

  
  

  create or replace TRIGGER TRG_TESTE_MV

  AFTER INSERT OR UPDATE ON THE PERSON

  REFERENCING OLD AS OLD AGAIN AS NEW

  FOR EACH LINE

  BEGIN

  IF THE INSERTION

  INSERT THE NAMES

  VALUES

  (: NEW.id,:NEW.NAME);

  END IF;

  IF THE UPDATE CAN

  UPDATE OF NAMES

  SET NAME =: NEW.NAME WHERE ID =: NEW.id;

  END IF;

  END;

  */

  Thanks for any help

  Your trigger fires, but I doubted that you will be satisfied with the results. You really need to understand how to refresh process works before you begin creating triggers of MV:

  SQL > create table emp1 in select * from EMP
  2.

  Table created.

  SQL > create materialized view emp1 with rowid journal
  2.

  Materialized view log that is created.

  SQL > create materialized view emp1_mv
  2 fast refresh
  3 on request
  4 with rowid
  5 as
  6 select * from emp1
  7.

  Materialized view created.

  SQL > create or replace
  trigger 2 emp1_mv_biudr
  3 before inserting
  4 or update
  5 or delete
  6 on emp1_mv
  7 for each line
  Start 8
  9 insert then dbms_output.put_line ('INSERT' |: new.ename); end if;
  10 if the deletion then dbms_output.put_line ('REMOVE' |: old.ename); end if;
  11 end;
  12.

  Trigger created.

  SQL > insert
  2 in emp1 (empno, ename, sal)
  3 values(1,'X',1000)
  4.

  1 line of creation.

  SQL > validation
  2.

  Validation complete.

  SQL > set serveroutput on
  SQL > exec dbms_mview.refresh ('emp1_mv', 'f');
  INSERTION OF X

  PL/SQL procedure successfully completed.

  SQL > update emp1
  2 set sal = sal + 1
  3 where ename ('King', 'JONES')
  4.

  2 lines to date.

  SQL > validation
  2.

  Validation complete.

  SQL > set serveroutput on
  SQL > exec dbms_mview.refresh ('emp1_mv', 'f');
  INSERTION OF JONES
  INSERTION OF KING

  PL/SQL procedure successfully completed.

  SQL > delete emp1
  2 where in ename ('ALLEN', 'SMITH')
  3.

  2 deleted rows.

  SQL > validation
  2.

  Validation complete.

  SQL > set serveroutput on
  SQL > exec dbms_mview.refresh ('emp1_mv', 'f');

  PL/SQL procedure successfully completed.

  SQL >

  As you can see, refresh MV updates ever. Results update underlying table to remove/insert in MV. That's why your trigger will not give the results that you expected.

  SY.

• The Materialized View - ORA-12052: is unable to fast refresh materialized view

  Hello

  I was hitting my head all day trying to create materialized views. I have made some progress, but have hit a brick wall, unfortunately!

  Basically, I have been invited to take a view and see if I can get the benefits of performance by transforming all or part of it in materialized views. Because the underlying tables of the config is updated quite frequently, I want to fast refresh materialized views on commit. However, when I try to create a materialized view containing an outer join in an aggregated materialized view table, I get ORA-12052: is unable to fast refresh materialized view.

  I went through the documentation and also Rob van Wijkvery useful series of blogs on the topic (especially http://rwijk.blogspot.co.uk/2009/09/fast-refreshable-materialized-view.html) but have not found anything that matches. Maybe I missed something somewhere along the line, or maybe I'm asking just something completely impossible?

  My db is 11.2.0.2.

  Here's the test scripts, I've worked with that:

  drop materialized view test1_test2_mv;
  Drop materialized view test2 journal;
  drop table test2;
  Drop materialized view test1_mv newspaper;
  drop materialized view test1_mv;
  Drop materialized view test1 journal;
  drop table test1;

  create table test1 (identification number,
  type varchar2 (10),
  number of Val,
  update_time date,
  constraint t1_pk primary key (id, type, val));
  
  Insert into test1
  Select 1, 'a', 1001, sysdate - 10/24 Union double all the
  Select 1, 'b', 1003, sysdate - 9/24 Union double all the
  Select 1, 'c', 1002, sysdate - 8/24 Union double all the
  Select 1, had ', 1004, sysdate - 7/24 Union double all the
  Select 1, 'e', 1005, sysdate - 6/24 Union double all the
  Select 1, 'c', 1006, sysdate - 5/24 Union double all the
  Select 2, 'a', 1002, sysdate - 4/24 Union double all the
  Select 2, 'b', 1005, sysdate - 3/24 Union double all the
  Select 3, 'a', 1001, sysdate - 2/24 Union double all the
  Select 3, 'c', 1006, sysdate - 1/24 Union double all the
  Select 3, 'e', 1008, sysdate - 2/24 Union double all the
  Select option 4, has ', 1004, sysdate - 3/24 Union double all the
  Select 5, 'b', 1002, sysdate - 4/24 Union double all the
  Select 5, 'g', 1001, sysdate - 5/24 Union double all the
  Select 6, 'h', 1004, sysdate - 6/24 Union double all the
  Select 7, 'b', 1007, sysdate - 7/24 Union double all the
  Select 7, had ', 1001, sysdate - 8/24 double;

  commit;

  Select * from test1;

  
  CREATE MATERIALIZED VIEW LOG ON test1
  WITH rowid, primary key (update_time)
  including the new values;

  
  Test1_mv CREATE MATERIALIZED VIEW
  IMMEDIATE CONSTRUCTION
  COOL OFF QUICKLY ON COMMIT
  Did YOU SELECT id,
  MAX (case when type = "there" end of val) THAT col_a,.
  MAX (case when type = 'b', then val end) AS col_b,.
  MAX (case when type = 'c' then end val) AS col_c,.
  MAX (case when type = ' then end of val) AS col_d,
  MAX (update_time) AS update_time
  OF test1
  WHERE TYPE in ('a',
  « b »,
  « c »,
  a ')
  GROUP BY id;

  CREATE MATERIALIZED VIEW LOG ON test1_mv
  WITH rowid
  including the new values;

  
  create table test2 (identification number,
  col2 number,
  COL3 varchar2 (10),
  number of COL4,
  constraint t2_pk primary key (id));
  
  Insert into test2
  Select 1, 1, 'bob', 1 double Union all
  Select 2, 1, "sue", 1 double Union all
  Select 3, 1, 'tom', 1 double Union all
  Select 4, 1, 'jay', 1 double Union all
  Select 5, 1, 'art', 1 double Union all
  Select 6, 1, 'kay', 1 double Union all
  Select 7, 1, 'max', 1 double Union all
  Select 8, 1, 'tim', 1 double Union all
  Select 9, 1, "liz", 1 from dual;

  commit;

  
  CREATE MATERIALIZED VIEW LOG ON test2
  WITH rowid, primary key
  including the new values;

  
  Test1_test2_mv CREATE MATERIALIZED VIEW
  IMMEDIATE CONSTRUCTION
  COOL OFF QUICKLY ON COMMIT
  LIKE SOME t2.rowid,.
  T1.ID,
  T1.col_a,
  T1.col_b,
  T1.col_c,
  T1.col_d,
  T1.update_time,
  T2.col2,
  T2. COL3
  OF test1_mv t1,.
  Test2 t2
  WHERE (+) t1.id = t2.id; -symbol of outer join is not correctly displayed on the forums without space, grr!

  ORA-12052: is unable to fast refresh materialized view TEST1_TEST2_MV

  Y at - it any way I can get the materialized view fast refresh on commit or I asking the impossible?

  Add t1.rowid:

  SQL > CREATE MATERIALIZED VIEW test1_test2_mv

  2 BUILD IMMEDIATE

  3 QUICK REFRESH YOU COMMIT

  4 AS t2.rowid SELECT rid2,

  5 t1.rowid rid1,

  6 t1.id

  T1.col_a 7,.

  T1.col_b 8,.

  T1.col_c 9,.

  T1.col_d 10,

  T1.update_time 11,

  T2.col2 12,

  13 t2.col3

  14 OF test1_mv t1,

  15 test2 T2

  16 WHERE t1.id = t2.id

  17.

  Materialized view created.

  SQL > select * from test1_test2_mv

  2.

  RID2 RID1 ID COL_A, COL_B, COL_C COL_D UPDATE_TIME COL2 COL3

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

  AAAYB6AANAAAANDAAA AAAYB/AANAAAAN/AAA 1 1001 1003 1006 1004 25 / 06 / 2014 12:54:16 1 bob

  AAAYB6AANAAAANDAAB AAAYB/AANAAAAN/AAB 2 1002 1005 25 / 06 / 2014 1 sue 14:54:16

  AAAYB6AANAAAANDAAC AAAYB/AANAAAAN/AAC 3 1001 1006 25 / 06 / 2014 16:54:16 1 tom

  AAAYB/AANAAAAN/AAD AAAYB6AANAAAANDAAD 4 1004 25/06/2014 14:54:16 1 jay

  AAAYB6AANAAAANDAAE AAAYB / AANAAAAN / AAE 5 1002 2014/06/25 13:54:16 1 art

  AAAYB6AANAAAANDAAF AAAYB/AANAAAAN/AAG 7 1007 1009 25 / 06 / 2014 10:54:16 max 1

  AAAYB/AANAAAAN/AAH                                                                                                        1 tim

  AAAYB/AANAAAAN/AAF                                                                                                        1 kay

  AAAYB/AANAAAAN/AAI                                                                                                        1 liz

  9 selected lines.

  SQL > update of test2

  2 set col3 = "fly."

  3 where id = 7

  6 m

  1 line update.

  SQL > validation

  2.

  Validation complete.

  SQL > select * from test1_test2_mv

  2.

  RID2 RID1 ID COL_A, COL_B, COL_C COL_D UPDATE_TIME COL2 COL3

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

  AAAYB6AANAAAANDAAA AAAYB/AANAAAAN/AAA 1 1001 1003 1006 1004 25 / 06 / 2014 12:54:16 1 bob

  AAAYB6AANAAAANDAAB AAAYB/AANAAAAN/AAB 2 1002 1005 25 / 06 / 2014 1 sue 14:54:16

  AAAYB6AANAAAANDAAC AAAYB/AANAAAAN/AAC 3 1001 1006 25 / 06 / 2014 16:54:16 1 tom

  AAAYB/AANAAAAN/AAD AAAYB6AANAAAANDAAD 4 1004 25/06/2014 14:54:16 1 jay

  AAAYB6AANAAAANDAAE AAAYB / AANAAAAN / AAE 5 1002 2014/06/25 13:54:16 1 art

  AAAYB/AANAAAAN/AAH                                                                                                        1 tim

  AAAYB/AANAAAAN/AAF                                                                                                        1 kay

  AAAYB/AANAAAAN/AAI                                                                                                        1 liz

  AAAYB6AANAAAANDAAF AAAYB/AANAAAAN/AAG 7 1007 1009 25 / 06 / 2014 10:54:16 1 rob

  9 selected lines.

• Do not to use the materialized view

  I wonder if we've already created a materialized view, can we prefer not to use this point of view, materialized for a query? I want to say can we determine if a query uses MV and other queries don't use MV?  Thank you.

  Hello Indra,

  I'm not completely sure about that, but you can read (with examples) concerning the indications- NO_REWRITE and REWRITE

  Text over the doc links:

  Council of REWRITING:

  The REWRITE Council instructs the optimizer to rewrite a query regarding the materialized views when possible, regardless of cost. Use the REWRITE trick with or without a display list. If you use REWRITE with a view list and the list contains an eligible materialized view, then Oracle uses this view regardless of its cost.

  Tip NO_REWRITE:

  The NO_REWRITE Council tells the optimizer to disable the rewrite of the query to the query block, of the substitution of the definition of the parameter QUERY_REWRITE_ENABLED .

  Be aware! -The NOREWRITE suspicion has been deprecated. Use the NO_REWRITE hint instead.

  Read here: setting QUERY_REWRITE_ENABLED

  -Nordine

• Change the definition of the materialized view while maintaining access for users uninteruupted

  Hello

  We have a system report and the need to change the report definition mv access - like to do it without interruption.

  Is this possible?

  the sql behind mv was change picks up so column of another table.

  Have you heard but not used for dbms_redefinition tables

  Thank you

  It is built in the Oracle solution for this one, where you can edit the definition WITHOUT interruption. You can drop the materialized view existing with the clause "save table" and rebuilt the view materialized on 'predefined table'. I googled this example for you

  create materialized view mv1 as select dept , count(*) as cnt from scott.emp;

  We want to change the statement so that only dept more 5 will be calculated

  drop materialized view mv1 preserve table;
  

  Notice that PRESERVE TABLE clause - mv1 table is not droped - single layer mview.

  desc mv1
  

  now, we create the mview with a different query on top of the existing table

  create materialized view mv1 on prebuilt table as  select dept , count(*) as cnt from scott.emp where dept > 5;
  

  Notice that on prebuilt table the mview uses the existing object clause.

  exec dbms_mview.refresh_mview('mv1');
  

  http://StackOverflow.com/questions/18085894/redefine-MATERIALIZED-view-with-no-downtime

  http://Arup.blogspot.com/2009/01/ultra-fast-MV-alteration-using-prebuilt.html

• PX Deq Credit: send blkd hang while the materialized view Refresh

  Hi all
  
  When we are materialized view refreshing. It takes more than 2.30 minutes. Initially, it took 1.40 minutes.
  
  We use parallel and base are partitioned. When I checked the tkprof report I see a lot of insert query expects especially PX Deq Credit: send blkd event. When I check the ASH report that I find not just any question about MV was running but always refresh MV was going on
  
  
  

  TKPROF: Release 11.2.0.1.0 - Development on Wed Jun 5 16:27:29 2013
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
  
  Trace file: CHDFCI_p001_43384918_PARALLEL.trc
  Sort options: exeela  prsela  fchela  
  ********************************************************************************
  count    = number of times OCI procedure was executed
  cpu      = cpu time in seconds executing 
  elapsed  = elapsed time in seconds executing
  disk     = number of physical reads of buffers from disk
  query    = number of buffers gotten for consistent read
  current  = number of buffers gotten in current mode (usually for update)
  rows     = number of rows processed by the fetch or execute call
  ********************************************************************************
  
  
  EXPLAIN PLAN option disabled.
  ********************************************************************************
  
  SQL ID: 2x210q5g30m4t
  Plan Hash: 2058446196
  INSERT /*+ BYPASS_RECURSIVE_CHECK APPEND  */ INTO 
    "APPS"."GL_BAL_MV" SELECT * FROM 
    GL_BAL_V
  
  
  call     count       cpu    elapsed       disk      query    current        rows
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  Parse        1      0.00       0.00          0          0          0           0
  Execute      1    362.20    9372.04    1158765          0          0           0
  Fetch        0      0.00       0.00          0          0          0           0
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  total        2    362.20    9372.04    1158765          0          0           0
  
  Misses in library cache during parse: 0
  Optimizer mode: ALL_ROWS
  Parsing user id: 175     (recursive depth: 1)
  
  Rows     Row Source Operation
  -------  ---------------------------------------------------
        0  LOAD AS SELECT  (cr=0 pr=0 pw=0 time=0 us)
        0   PX COORDINATOR  (cr=0 pr=0 pw=0 time=0 us)
        0    PX SEND QC (RANDOM) :TQ10003 (cr=0 pr=0 pw=0 time=0 us cost=1041298 size=389555904 card=2028937)
  78448967     HASH JOIN BUFFERED (cr=0 pr=1158765 pw=1158765 time=276842112 us cost=1041298 size=389555904 card=2028937)
   410944      BUFFER SORT (cr=0 pr=0 pw=0 time=492466 us)
   410944       PX RECEIVE  (cr=0 pr=0 pw=0 time=34526636 us cost=64715 size=147944250 card=1643825)
        0        PX SEND HASH :TQ10001 (cr=0 pr=0 pw=0 time=0 us cost=64715 size=147944250 card=1643825)
        0         PARTITION RANGE ALL PARTITION: 1 39 (cr=0 pr=0 pw=0 time=0 us cost=64715 size=147944250 card=1643825)
        0          TABLE ACCESS FULL GL_CODE_COMBINATIONS PARTITION: 1 39 (cr=0 pr=0 pw=0 time=0 us cost=64715 size=147944250 card=1643825)
  78448967      PX RECEIVE  (cr=0 pr=0 pw=0 time=2453949696 us cost=976582 size=395060280 card=3873140)
        0       PX SEND HASH :TQ10002 (cr=0 pr=0 pw=0 time=0 us cost=976582 size=395060280 card=3873140)
        0        HASH JOIN  (cr=0 pr=0 pw=0 time=0 us cost=976582 size=395060280 card=3873140)
        0         BUFFER SORT (cr=0 pr=0 pw=0 time=0 us)
        0          PX RECEIVE  (cr=0 pr=0 pw=0 time=0 us cost=32 size=133920 card=2480)
        0           PX SEND BROADCAST :TQ10000 (cr=0 pr=0 pw=0 time=0 us cost=32 size=133920 card=2480)
        0            HASH JOIN  (cr=0 pr=0 pw=0 time=0 us cost=32 size=133920 card=2480)
        0             TABLE ACCESS FULL GL_SETS_OF_BOOKS (cr=0 pr=0 pw=0 time=0 us cost=7 size=108 card=6)
        0             TABLE ACCESS FULL GL_PERIODS (cr=0 pr=0 pw=0 time=0 us cost=24 size=44640 card=1240)
        0         PX BLOCK ITERATOR PARTITION: 1 39 (cr=0 pr=0 pw=0 time=0 us cost=976550 size=30099548160 card=627073920)
        0          TABLE ACCESS FULL GL_BALANCES PARTITION: 1 39 (cr=0 pr=0 pw=0 time=0 us cost=976550 size=30099548160 card=627073920)
  
  
  Elapsed times include waiting on following events:
    Event waited on                             Times   Max. Wait  Total Waited
    ----------------------------------------   Waited  ----------  ------------
    PX Deq: Execution Msg                           3        0.16          0.17
    PX Deq Credit: send blkd                  1061004        1.99       5084.61
    PX Deq: Table Q Normal                     250856        2.00       2306.87
    asynch descriptor resize                        1        0.00          0.00
    Disk file operations I/O                       10        0.23          0.26
    direct path write temp                       3608        1.20        958.39
    latch free                                     26        0.02          0.19
    PX qref latch                             7647924        0.05         11.85
    direct path read temp                         578        0.43         35.19
    PX Deq Credit: need buffer                   4037        0.08          5.84
  
  
  
  ********************************************************************************
  
  OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS
  
  call     count       cpu    elapsed       disk      query    current        rows
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  Parse        0      0.00       0.00          0          0          0           0
  Execute      0      0.00       0.00          0          0          0           0
  Fetch        0      0.00       0.00          0          0          0           0
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  total        0      0.00       0.00          0          0          0           0
  
  Misses in library cache during parse: 0
  
  Elapsed times include waiting on following events:
    Event waited on                             Times   Max. Wait  Total Waited
    ----------------------------------------   Waited  ----------  ------------
    PX Deq: Execution Msg                           3        0.47          0.75
    PX Deq: Slave Session Stats                     1        0.15          0.15
  
  
  OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS
  
  call     count       cpu    elapsed       disk      query    current        rows
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  Parse        1      0.00       0.00          0          0          0           0
  Execute      1    362.20    9372.04    1158765          0          0           0
  Fetch        0      0.00       0.00          0          0          0           0
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  total        2    362.20    9372.04    1158765          0          0           0
  
  Misses in library cache during parse: 0
  
  Elapsed times include waiting on following events:
    Event waited on                             Times   Max. Wait  Total Waited
    ----------------------------------------   Waited  ----------  ------------
    PX Deq: Execution Msg                           3        0.16          0.17
    PX Deq Credit: send blkd                  1061004        1.99       5084.61
    PX Deq: Table Q Normal                     250856        2.00       2306.87
    asynch descriptor resize                        1        0.00          0.00
    Disk file operations I/O                       10        0.23          0.26
    direct path write temp                       3608        1.20        958.39
    latch free                                     26        0.02          0.19
    PX qref latch                             7647924        0.05         11.85
    direct path read temp                         578        0.43         35.19
    PX Deq Credit: need buffer                   4037        0.08          5.84
  
      1  user  SQL statements in session.
      0  internal SQL statements in session.
      1  SQL statements in session.
      0  statements EXPLAINed in this session.
  ********************************************************************************
  Trace file: CHDFCI_p001_43384918_PARALLEL.trc
  Trace file compatibility: 11.1.0.7
  Sort options: exeela  prsela  fchela  
         1  session in tracefile.
         1  user  SQL statements in trace file.
         0  internal SQL statements in trace file.
         1  SQL statements in trace file.
         1  unique SQL statements in trace file.
   8986825  lines in trace file.
      9372  elapsed seconds in trace file.

  When I checked the ASH report during this period. I don't see anything related to MV running.
  I use parallel degree 8 to GL_BALANCES.
  Please suggest.

  Sarah wrote:
  Hi all

  When we are materialized view refreshing. It takes more than 2.30 minutes. Initially, it took 1.40 minutes.

  You are showing much more than 2.30 minutes in this result tkprof - did you mean hours?

  We use parallel and base are partitioned. When I checked the tkprof report I see a lot of insert query expects especially PX Deq Credit: send blkd event.

  In your case, it seems as if the "PX Deq Credit: send blkd" is an inactive waiting (despite comments in the manual, which is not always true).
  Plan execution tells you that you are not loading in the GL_BAL_MV at the same time (even if you select it in parallel). This means a single process must collect all the data of all the slaves of PX to insert it, so anytime 7 slaves will wait for you "PX Deq Credit: send blkd" while the eighth sends data to the query Coordinator to write to the table. (The timeout on these waiting 2 seconds - which is consistent with the max wait the values you see.)

  If you can ensure that the MV and its index is declared as parallel, and you can enable parallel DML for updating, you may find that things go a lot faster.

  When I check the ASH report that I find not just any question about MV was running but always refresh MV was going on

  Ash can be a bit flakey with some of its reports in 11.2.0.1 - perhaps you were simply unlucky.

  >

  call     count       cpu    elapsed       disk      query    current        rows
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  Parse        1      0.00       0.00          0          0          0           0
  Execute      1    362.20    9372.04    1158765          0          0           0
  Fetch        0      0.00       0.00          0          0          0           0
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  total        2    362.20    9372.04    1158765          0          0           0
  

  It is possible, moreover, that your plan has changed over time - there are a couple of "HASH JOIN TAMPONNÉE" in the plan, which means that the table "probe" the hash join arrives on the assembling process and is dumped to disk (if it does not fit in memory) to be reread and joined. This can consume a lot of IO and the time - as seen by the "pr = 1158765 pw = 1158765" on line 4 of your plan. It is possible that a previous plan has used a method of dissemination for the table of 'building' avoid this overload - but that the optimizer has switched plans as all data has increased.

  Concerning
  Jonathan Lewis

  Published by: Jonathan Lewis on June 5, 2013 16:20 (formatting)

• Elapsed time for the materialized view vs Master table query

  Hello all;
  
  Small confusion about time up for the vs Master materialized view table query
  
  

  SQL > select count (*), sum (quan_sold), sum (amt_sold) of the sale;

  COUNT (*) SUM (QUAN_SOLD) SUM (AMT_SOLD)
  6000000 12000000 720480000
  Elapsed time: 00:00:30.54
  

  SQL > create materialized view mv1
  2 activate the rewrite of the query as
  3. select count (*), sum (quan_sold), sum (amt_sold) of the sale;

  Materialized view created.
  Elapsed time: 00:00:01.45
  

  SQL > select count (*), sum (quan_sold), sum (amt_sold) of the sale;

  COUNT (*) SUM (QUAN_SOLD) SUM (AMT_SOLD)
  6000000 12000000 720480000
  Elapsed time: 00:00:00.01
  
  Please see the three cases "Elapsed Time"...
  
  When comparing other cases.
  1. my query takes long time (30.54), extraction of data from the sale
  2. create a materialized view takes less time (01:45) why?
  
  Source: http://uhesse.com/2009/07/08/brief-introduction-into-materialized-views/

  >
  Small confusion about elapsed time for the materialized view vs Master table query

  SQL > select count (*), sum (quan_sold), sum (amt_sold) from the sale.

  COUNT (*) SUM (QUAN_SOLD) SUM (AMT_SOLD)
  6000000 12000000 720480000
  Elapsed time: 00:00:30.54

  SQL > create materialized view mv1
  2 activate the rewrite of the query as
  3. select count (*), sum (quan_sold), sum (amt_sold) of the sale;
  Materialized view created.
  Elapsed time: 00:00:01.45

  SQL > select count (*), sum (quan_sold), sum (amt_sold) from the sale.

  COUNT (*) SUM (QUAN_SOLD) SUM (AMT_SOLD)
  6000000 12000000 720480000
  Elapsed time: 00:00:00.01

  Please see the three cases "Elapsed Time"...

  When comparing other cases.
  1. my query takes long time (30.54), extraction of data from the sale
  2. create a materialized view takes less time (01:45) why?
  >
  Many queries take less time the second time you run them. After the first performance, there may be many, if not all, lines in the buffer cache. Then the second round will not make any or all e/s physical but will obtain data from the buffer cache.

  Also, you haven't checked that the MV was even used for the second run.

  Drop the MV and make the query several times and means of the time. Then create the MV and do the same thing.

• performance of the queries on the main tables of the materialized view vs

  Hello
  
  I'm afraid of strange behavior in db, on my paintings of master UDBMOVEMENT_ORIG (26mil.rows) and UDBIDENTDATA_ORIG (18mil.rows) is created the materialized view TMP_MS_UDB_MV (UDBMOVEMENT stands for this object) that meets certain default conditions and the join on these paintings of master condition. MV got on the lines of 12milions. I created MV for poll not so huge objects, MV got 3GB, paintings of master toghether 12 GB. But I don't understand that physical reads and becomes compatible is less on MV that on the main tables, the final execution time is shorter on the master tables. See my journal below.
  
  Why?
  
  Thanks for the replies.
  
  
  SQL > set echo on
  SQL > @flush
  SQL > alter system flush buffer_cache;
  
  Modified system.
  
  Elapsed time: 00:00:00.20
  SQL > alter system flush shared_pool;
  
  Modified system.
  
  Elapsed time: 00:00:00.65
  SQL > SELECT
  UDBMovement.zIdDevice 2, UDBMovement.sDevice, UDBMovement.zIdLocal, UDBMovement.sComputer, UDBMovement.tActionTime, UDBIdentData.sCardSubType, UDBIdentData.sCardType, UDBMovement.cEpan, UDBMovement.cText, UDBMovement.lArtRef, UDBMovement.sArtClassRef, UDBMovement.lSequenz, UDBMovement.sTransMark, UDBMovement.lBlock, UDBMovement.sTransType, UDBMovement.lGlobalID, UDBMovement.sFacility, UDBIdentData.sCardClass, UDBMovement.lSingleAmount, UDBMovement.sVAT, UDBMovement.lVATTot, UDBIdentData.tTarifTimeStart, UDBIdentData.tTarifTimeEnd, UDBIdentData.cLicensePlate, UDBIdentData.lMoneyValue, UDBIdentData.lPointValue, UDBIdentData.lTimeValue, UDBIdentData.tProdTime, UDBIdentData.tExpireDate
  UDBMOVEMENT_orig UDBMovement 3, Udbidentdata_orig UDBIdentData
  4. WHERE
  5 UDBMovement.lGlobalId = UDBIdentData.lGlobalRef (+) AND UDBMovement.sComputer = UDBIdentData.sComputer (+)
  6 AND UDBMovement.sTransType > 0 AND UDBMovement.sDevice < 1000 AND UDBMovement.sDevice > = 0 AND UDBIdentData.sCardType IN (2) AND (bitand(UDBMovement.sSaleFlag,1) = 0 AND bitand(UDBMovement.sSaleFlag,4) = 0) AND UDBMovement.sArtClassRef < 100
  7 AND UDBMovement.tActionTime > = TO_DATE (May 5, 2011 00:00:00 ',' dd/mm/yyyy hh24:mi:ss') + 0.25 AND UDBMovement.tActionTime < TO_DATE (May 5, 2011 00:00:00 ',' dd/mm/yyyy hh24:mi:ss') + 0.5
  8 ORDER BY tActionTime, lBlock, lSequenz;
  
  4947 selected lines.
  
  Elapsed time: 00:00:15.84
  
  Execution plan
  ----------------------------------------------------------
  Hash value of plan: 1768406139
  
  ------------------------------------------------------------------------------------------------------------
  | ID | Operation | Name | Lines | Bytes | TempSpc | Cost (% CPU). Time |
  ------------------------------------------------------------------------------------------------------------
  | 0 | SELECT STATEMENT | 7166 | 1238K | 20670 (1) | 00:04:09 |
  | 1. SORT ORDER BY | 7166 | 1238K | 1480K | 20670 (1) | 00:04:09 |
  | 2. NESTED LOOPS |
  | 3. NESTED LOOPS | 7166 | 1238K | 20388 (1) | 00:04:05 |
  |* 4 | TABLE ACCESS BY INDEX ROWID | UDBMOVEMENT_ORIG | 7142 | 809K | 7056 (1) | 00:01:25 |
  |* 5 | INDEX RANGE SCAN | IDX_UDBMOVARTICLE | 10709. 61 (0) | 00:00:01 |
  |* 6 | INDEX UNIQUE SCAN | UDBIDENTDATA_PRIM | 1 | | | 1 (0) | 00:00:01 |
  |* 7 | TABLE ACCESS BY INDEX ROWID | UDBIDENTDATA_ORIG | 1. 61. 2 (0) | 00:00:01 |
  ------------------------------------------------------------------------------------------------------------
  
  Information of predicates (identified by the operation identity card):
  ---------------------------------------------------
  
  4 - filter("UDBMOVEMENT".") STRANSTYPE"> 0 AND 'UDBMOVEMENT '. "" SDEVICE ' < 1000 AND
  BITAND ("SSALEFLAG", 1) = 0 AND "UDBMOVEMENT". "" SDEVICE ' > = 0 AND BITAND ("UDBMOVEMENT". "SSALEFLAG «(, 4) = 0)" "
  5 - access("UDBMOVEMENT".") TACTIONTIME' > = TO_DATE (' 2011-05-05 06:00 ',' syyyy-mm-jj)
  ('HH24:mi:SS) AND "UDBMOVEMENT". "' TACTIONTIME ', TO_DATE (' 2011-05-05 12:00 ',' syyyy-mm-jj)
  ('HH24:mi:SS) AND "UDBMOVEMENT". ("' SARTCLASSREF" < 100)
  filter ("UDBMOVEMENT". "SARTCLASSREF" < 100)
  6 - access("UDBMOVEMENT".") LGLOBALID "=" UDBIDENTDATA. " "" LGLOBALREF "AND
  'UDBMOVEMENT '. "' SCOMPUTER"="UDBIDENTDATA." ("' SCOMPUTER")
  7 - filter("UDBIDENTDATA".") SCARDTYPE "= 2)
  
  
  Statistics
  ----------------------------------------------------------
  543 recursive calls
  0 db block Gets
  84383 compatible Gets
  4485 physical reads
  0 redo size
  533990 bytes sent via SQL * Net to client
  3953 bytes received via SQL * Net from client
  331 SQL * Net back and forth to and from the client
  kinds of 86 (memory)
  0 sorts (disk)
  4947 lines processed
  
  SQL > @flush
  SQL > alter system flush buffer_cache;
  
  Modified system.
  
  Elapsed time: 00:00:00.12
  SQL > alter system flush shared_pool;
  
  Modified system.
  
  Elapsed time: 00:00:00.74
  SQL > SELECT UDBMovement.zIdDevice, UDBMovement.sDevice, UDBMovement.zIdLocal, UDBMovement.sComputer, UDBMovement.tActionTime, UDBMovement.sCardSubType, UDBMovement.sCardType, UDBMovement.cEpan, UDBMovement.cText, UDBMovement.lArtRef, UDBMovement.sArtClassRef, UDBMovement.lSequenz, UDBMovement.sTransMark, UDBMovement.lBlock, UDBMovement.sTransType, UDBMovement.lGlobalID, UDBMovement.sFacility, UDBMovement.sCardClass, UDBMovement.lSingleAmount, UDBMovement.sVAT, UDBMovement.lVATTot, UDBMovement.tTarifTimeStart, UDBMovement.tTarifTimeEnd, UDBMovement.cLicensePlate, UDBMovement.lMoneyValue, UDBMovement.lPointValue, UDBMovement.lTimeValue, UDBMovement.tProdTime
  2. OF UDBMOVEMENT WHERE
  3 UDBMovement.sTransType > 0 AND UDBMovement.sDevice < 1000 AND UDBMovement.sDevice > = 0 AND UDBMovement.sCardType IN (2) AND (bitand(UDBMovement.sSaleFlag,1) = 0 AND bitand(UDBMovement.sSaleFlag,4) = 0) AND UDBMovement.sArtClassRef < 100
  4. AND UDBMovement.tActionTime > = TO_DATE (May 5, 2011 00:00:00 ',' the hh24: mi: ss' dd/mm/yyyy) + 0.25
  5 AND UDBMovement.tActionTime < TO_DATE (May 5, 2011 00:00:00 ',' the hh24: mi: ss' dd/mm/yyyy) + 0.5 ORDER BY tActionTime, lBlock, lSequenz;
  
  4947 selected lines.
  
  Elapsed time: 00:00:26.46
  
  Execution plan
  ----------------------------------------------------------
  Hash value of plan: 3648898312
  
  -----------------------------------------------------------------------------------------------------------
  | ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time |
  -----------------------------------------------------------------------------------------------------------
  | 0 | SELECT STATEMENT | 2720 | 443K | 2812 (1) | 00:00:34 |
  | 1. SORT ORDER BY | 2720 | 443K | 2812 (1) | 00:00:34 |
  |* 2 | MAT_VIEW ACCESS BY INDEX ROWID | TMP_MS_UDB_MV | 2720 | 443K | 2811 (1) | 00:00:34 |
  |* 3 | INDEX RANGE SCAN | EEETMP_MS_ACTTIMEDEVICE | 2732 | 89 (0) | 00:00:02 |
  -----------------------------------------------------------------------------------------------------------
  
  Information of predicates (identified by the operation identity card):
  ---------------------------------------------------
  
  2 - filter("UDBMOVEMENT".") STRANSTYPE"> 0 AND BITAND ("UDBMOVEMENT". "SSALEFLAG «(, 4) = 0 AND" "
  BITAND ("SSALEFLAG", 1) = 0 AND "UDBMOVEMENT". ("' SARTCLASSREF" < 100)
  3 - access("UDBMOVEMENT".") TACTIONTIME' > = TO_DATE (' 2011-05-05 06:00 ',' syyyy-mm-jj)
  ('HH24:mi:SS) AND "UDBMOVEMENT". "" SDEVICE ' > = 0 AND "UDBMOVEMENT". ' SCARDTYPE ' = 2 AND ".
  'UDBMOVEMENT '. "" TACTIONTIME "< TO_DATE(' 2011-05-05 12:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
  'UDBMOVEMENT '. ("' SDEVICE ' < 1000)
  filter ("UDBMOVEMENT". "SCARDTYPE"= 2 AND "UDBMOVEMENT"." SDEVICE' < 1000 AND
  'UDBMOVEMENT '. ("' SDEVICE ' > = 0)
  
  
  Statistics
  ----------------------------------------------------------
  449 recursive calls
  0 db block Gets
  6090 gets coherent
  2837 physical reads
  0 redo size
  531987 bytes sent via SQL * Net to client
  3953 bytes received via SQL * Net from client
  331 SQL * Net back and forth to and from the client
  168 sorts (memory)
  0 sorts (disk)
  4947 lines processed
  
  SQL > spool off
  
  Published by: MattSk on February 4, 2013 14:20

  >
  The second query makes a full table of materialized view scan.
  >
  What you base that statement on?

  I do not see any table full scan in terms of the second query. All I see is
  >
  * 2 MAT_VIEW ACCESS BY INDEX ROWID TMP_MS_UDB_MV 2720 443K 2811 (1) 00:00:34

• Refresh the Materialized View constructed from an external table commit?

  Is it possible to create a materialized with Refresh view on commit built from an external table?
  
  I think the answer is "no, because there is no way for the outer table report to the view materialized it has been changed," but I would like to be sure before I tell my client who has requested the opportunity to do this (or, Alternatively, to learn how Oracle hoops I have to cross in order to operate).
  
  I can create a Refresh on demand, it is not a question of not having the necessary permissions to create the materialized view itself.

  No, you can't. The outer table is not modified in a transactional way and there no materialized view logs, so there is no event to hang in and no delta to apply.

  However, you can use dbms_scheduler observer file that will ask for the presence of a file and load the data in a table or refresh a materialized view based on the external table.

  Justin

• question on the materialized view unregistered on the main site

  Hello
  
  you know how one knows, on the main site, on the existence of a materialized view another site referring to other tables to a primary site. It seems registration is not required.
  
  the site main orcl1: I have a table, and a materialized view log defined on A table.
  another site orcl2: have a link db orcl1 and rapid updatable view SCOTT materialized. A_MVW (create a materialized view A_MVW cool off quickly in select * from A@orcl1)
  
  on orcl1 I perform: exec DBMS_MVIEW. UNREGISTER_MVIEW (mviewowner = > 'SCOTT', mviewname = > mviewsite, 'A_MVW' = > 'ORCL2');
  so the materialized view seems to be correctly set aside (because it no longer appears in: select * from DBA_REGISTERED_MVIEWS ;))
  But, to my surprise, I can still perform refreshes fast on A_MVW, which also remove rows from the materialized view log. So how is site orcl1 always aware of the existence of the materialized view?
  
  It seems that, registered or not to the main site, a materialized view has the same... or is not? where is it stored, on the main site, information about materialized views (especially those of quickly updatable) as local tables reffer?
  
  Thank you

  See DocIDs 258634.1, 67371.1, 1031924.6
  on Oracle's Support website.

  Hemant K Collette