Create materialized view

Similar Questions

• Create Materialized view and Materialized view log.

  I wanted to create a materialized view with option "REFRESH QUICKLY YOU COMMIT".

  (1) table 1 - it is partitioned range + list - added primary key

  (2) View1 - having primary keys on the base table of view

  Steps to follow:

  (1) create the materialized on Table1; view journal -primary key by default

  (2) create the materialized on view1 view log.  -It gives below error.

  ORA-00942: table or view does not exist

  I wanted to create Materialized view as below

  create a materialized view

  Quickly REFRESH ON validation

  as

  Select...

  ........

  ... from table1

  where c1 (select c1 from View1 which...);

  
  

  Question:

  (1) because I am getting above error when creating journal of MV on the view. Can one create log view MV or we create a MV newspaper on the base table of view?

  (2) to create the MV with "REFRESH QUICKLY YOU COMMIT' option, we need to have the primary key on the main tables?

  
  

  Pointers on this will be really useful.
  

  
  

  Thank you

  Prasad

  "When a materialized view is maintained by the ON COMMIT method, the time required to perform the validation can be slightly longer than usual." This is because the refresh operation is performed as part of the validation process. This is why this method may not be suitable if many users at the same time change the tables on which is based the materialized view. »

  See: basis of materialized views (refreshment options) for all the other options and how they work.

• create materialized view log on the table without a primary key

  Hi all

  CREATE TABLE client_months 
  (
    SUBJ_CODE         NUMBER(4),
    SERV_CODE         NUMBER(4),
    DEBIT_CODE        NUMBER(4),
    PERIOD_NUM        NUMBER(2),
    PERIOD_NAME       VARCHAR2(40 CHAR),
    FIRST_MON_DAY     DATE,
    LAST_MON_DAY      DATE,
    VALUE_MON_DAY     DATE,
    MONTHES           NUMBER(4,2),
    GARDENING_WEIGHT  NUMBER(5,4),
    REASON_CODE       NUMBER(5),
    STAMP_ACTION      VARCHAR2(1 CHAR),
    STAMP_CDATE       DATE                        DEFAULT SYSDATE,
    STAMP_DATE        DATE,
    STAMP_USER        VARCHAR2(15 CHAR),
    REGION_CODE       NUMBER(9)
  )
  table created.
  
  CREATE UNIQUE INDEX client_months_UK  ON client_months 
  (SUBJ_CODE, SERV_CODE, DEBIT_CODE, PERIOD_NUM, REGION_CODE)
  index created.
  
  CREATE MATERIALIZED VIEW LOG ON client_months with rowid;
  
  CREATE MATERIALIZED VIEW client_months_mv 
  BUILD immediate 
  REFRESH FAST ON COMMIT 
  AS 
  SELECT * FROM client_months;
  
  ORA-12014: table 'CLIENT_MONTHS' does not contain a primary key constraint

  I don't want to refresh the mview when validation is performed on the base table.
  And I don't want to change the base table by adding a primary key.
  
  is it possible to create the mview journal using the unique index? or another solution?
  Please help
  Thanks in advance
  Naama

  Naamas wrote:
  No,
  I already read this post!

  Then you read wrong:

  SQL> CREATE TABLE client_months
    2  (
    3    SUBJ_CODE         NUMBER(4),
    4    SERV_CODE         NUMBER(4),
    5    DEBIT_CODE        NUMBER(4),
    6    PERIOD_NUM        NUMBER(2),
    7    PERIOD_NAME       VARCHAR2(40 CHAR),
    8    FIRST_MON_DAY     DATE,
    9    LAST_MON_DAY      DATE,
   10    VALUE_MON_DAY     DATE,
   11    MONTHES           NUMBER(4,2),
   12    GARDENING_WEIGHT  NUMBER(5,4),
   13    REASON_CODE       NUMBER(5),
   14    STAMP_ACTION      VARCHAR2(1 CHAR),
   15    STAMP_CDATE       DATE                        DEFAULT SYSDATE,
   16    STAMP_DATE        DATE,
   17    STAMP_USER        VARCHAR2(15 CHAR),
   18    REGION_CODE       NUMBER(9)
   19  )
   20  /
  
  Table created.
  
  SQL> CREATE UNIQUE INDEX client_months_UK  ON client_months
    2  (SUBJ_CODE, SERV_CODE, DEBIT_CODE, PERIOD_NUM, REGION_CODE)
    3  /
  
  Index created.
  
  SQL> CREATE MATERIALIZED VIEW LOG ON client_months with rowid
    2  /
  
  Materialized view log created.
  
  SQL> CREATE MATERIALIZED VIEW client_months_mv
    2  BUILD immediate
    3  REFRESH FAST WITH ROWID ON COMMIT -- pay attention to WITH ROWID
    4  AS
    5  SELECT * FROM client_months
    6  /
  
  Materialized view created.
  
  SQL>
  

  SY.

• 'Invalid metadata objects' when creating materialized views

  Hi experts,
  
  I ran into some trouble. I had an analytic workspace that has grown too quickly (see 11.2.0.2 size AW grows regularly with each generation of cube so I deleted and created a new.)
  
  He seemed to do very well with the tip David Greenfield, gave us in the mentioned forum post, but when I try to activate materialized views (that I had activated in the previous workspace) I am gettig the following error:
  
  -----
  Your metadata changes have been saved, with the following errors
  Invalid metadata objects:
  Invalid object "TABLESPACE. LECTURAS': 'CREATE A MATERIALIZED VIEW 'TABLESPACE' '. "CB$ LECTURAS.
  ORGANIZATION OF CUBE ON THE TABLESPACE. () TABLESPACE_AW
  MADE "LECTURAS_STORED"("LECTURAS_MEASURE_DIM" "LECTURA") IS "LECTURA"
  DIMENSION "TIEMPO" IS "TIEMPO", WITH THE HELP OF "TIEMPO_TIEMPO_HOUR_ID_UNIQUE_KEY."
  DIMENSION 'GEOGRAPHY' IS 'GEOGRAPHY' WITH THE HELP OF 'GEOGRAFIA_GEOGRAFIA_CONTADOR_ID_UNIQUE_KEY')
  POSTPONED BUILD
  UPDATE ON REQUEST
  FORCE
  WITH THE HELP OF CONSTRAINTS OF TRUST
  AS
  (
  SELECT
  TO_CHAR (T1." FEC_LECTURA', "dd/mm/yyyy hh24:mi:ss") "TIEMPO"
  T1. "" COD_METERID ""GEOGRAPHY. "
  SUM (T1." VAL_AI_HOR') "LECTURA".
  Of
  TABLESPACE. "' LECTURA_HORARIA_FINAL ' T1
  GROUP BY
  (TO_CHAR (T1." (FEC_LECTURA"," hh24:mi:ss dd/mm/yyyy '), T1. ("' COD_METERID")
  )
  ORA-00942: table or view does not exist
  "
  -----
  
  This same script running in SQLDeveloper gives the same error in line 17, which is the FROM clause. BUT I can run the select by itself and returns the expected result. If the table exists in the correct storage space.
  
  I must be missing something big...
  
  Thanks in advance.
  
  Joan
  
  P.S.: In the above code I use 'SPACE' to replace the real name from username and a tablespace (which is the same) for reasons of confidentiality.

  When you run the select statement, you connect to the same user you are trying to activate the VM?

  You can create a standard (No cube) MV with the same select statement? (Connected to the same user that you used in AWM).

  "CREATE MATERIALIZED VIEW "TABLESPACE"."MV_TEST"
    BUILD DEFERRED
    REFRESH ON DEMAND
    FORCE
    USING TRUSTED CONSTRAINTS
  AS
  (
    SELECT
     TO_CHAR(T1."FEC_LECTURA", 'dd/mm/yyyy hh24:mi:ss') "TIEMPO",
     T1."COD_METERID" "GEOGRAFIA",
     SUM(T1."VAL_AI_HOR") "LECTURA"
    FROM
     TABLESPACE."LECTURA_HORARIA_FINAL" T1
    GROUP BY
     (TO_CHAR(T1."FEC_LECTURA", 'dd/mm/yyyy hh24:mi:ss') , T1."COD_METERID")
  )
  {code}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            
  

• Cannot create Materialized View using the PL/SQL procedure

  Hello
  
  I have a question related to the creation of materialized view.
  I have a stored procedure that creates the materialized view. When you try to perform this procedure, I get not enough privileges error: ORA-01031.
  
  When I run the content of this procedure as a PL/SQL block anonymous their materialized view is created without any complications.
  Can you please advice me on this subject?
  It is even possible to create a materialized view in the stored procedure as I found no info on this subject.
  
  Thank you
  Petr

  Hi chudapet,

  Whenever you make in procedure, you must have direct subsidies and not through a role.

  Most likely the grant to create a materialized view is available via a role to your username.
  Assign a direct grant to the user:

  grant create materialized view to scott;
  {code}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
  

• Bug: Cannot create materialized view log on XE 11 G

  Hello
  
  I connect as try and HR user create materialized view log

  CREATE MATERIALIZED VIEW LOG ON HR.EMPLOYEES;

  I get the error
  >
  Error from the 1 in the command line:
  CREATE LOG VIEW MATERIALIZED ON HUMAN RESOURCES. EMPLOYEES
  Error in the command line: 1 column: 0
  Error report:
  SQL error: ORA-00439: feature not enabled not: Advanced replication
  00439 00000 - "function not enabled: %s."
  * Cause: The specified feature is not enabled.
  * Action: Try not to use this feature.
  >
  
  You can create a materialized view log on 10G XE with no problems.
  
  Kind regards
  Jari
  
  http://dbswh.webhop.NET/dbswh/f?p=blog:Home:0

  Is this a bug in 11g or 10g?

  It was reported earlier in the beta forum now archived. {: identifier of the thread = 2214092}

  The current doc lists the MV sites only (and 'No' to the function of replication advanced):
  http://download.Oracle.com/docs/CD/E17781_01/license.112/e18068/TOC.htm#BABDFDAI

• Create Materialized View ORA-01723: columns of length zero are not allowed

  I am trying to create a materialized view that derives from a column of a function and I get: ORA-01723: columns null are not allowed.
  
  I use 10 gr 2 with the following definition (simple version):
  
  CREATE MATERIALIZED VIEW ACES
  SELECT
  function_name (column_name) alias_de_colonne
  FROM table_name;
  
  I even tried to cast it as below:
  
  CREATE MATERIALIZED VIEW ACES
  SELECT
  Cast (function_name (column_name) AS VARCHAR2 (200)) alias_de_colonne
  FROM table_name;
  
  My function has an exception to return a value, even if no value are.
  
  I looked everywhere for the solution. Someone at - there a way around this problem? I really need my function to calculate the column because it has business rules that I can't join in my definition of the materialized view. My only hope around this is to insert values into a table and then create a materialized table view, I don't want to do that if someone has a solution around this.
  
  Any help would be greatly appreciated.
  
  Thank you
  
  Kyle
  
  Published by: Kyle Miller on April 19, 2011 08:28

  Have you tried to create a table with the correct structure and then by creating the view materialized, based on the predefined table as described here...

  http://www.oaktable.NET/content/ultra-fast-MV-alteration-using-prebuilt-table-option

  ?

  See you soon

  Ben

• With as subquery block in create MATERIALIZED view or bulk pl/sql

  Hi all
  
  Can I use the with as subquery block in create MATERIALIZED view?
  
  or in pl/sql
  
  
  
  -Thank you
  
  Published by: xwo0owx on March 31, 2011 11:23
  
  Published by: xwo0owx on March 31, 2011 11:23

  Have you tried to test it? :)

  SQL > SELECT * FROM V$VERSION;
  
  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
  PL/SQL Release 11.2.0.2.0 - Production
  CORE    11.2.0.2.0      Production
  TNS for 32-bit Windows: Version 11.2.0.2.0 - Production
  NLSRTL Version 11.2.0.2.0 - Production
  
  SQL > CREATE VIEW TEST_VIEW
    2  AS
    3  WITH d AS
    4  (
    5          SELECT * FROM DUAL
    6  )
    7  SELECT *
    8  FROM   d
    9  ;
  
  View created.
  
  SQL > SELECT * FROM test_view;
  
  D
  -
  X
  
  SQL > DECLARE
    2          x DUAL.DUMMY%TYPE;
    3  BEGIN
    4          WITH d AS
    5          (
    6                  SELECT * FROM DUAL
    7          )
    8          SELECT dummy
    9          INTO   x
   10          FROM   d
   11          ;
   12
   13          DBMS_OUTPUT.PUT_LINE(x);
   14  END;
   15  /
  X
  
  PL/SQL procedure successfully completed.
  

• Create table works, create materialized view only - long column names?

  Hello.
  
  I have no probs creating a table as well: -.
  CREATE TABLE blah
  (
  DEVICE_ID
  )
  in select
  "Device_ID" AS DEVICE_ID
  "of"sum" Device"@ed_link_3
  where "Device_ID" < 5;
  
  
  But when I try to create a materialized view:
  Blah1 CREATE MATERIALIZED VIEW
  (
  DEVICE_ID
  )
  < various materialized view parms >
  in select
  "Device_ID" AS DEVICE_ID
  "of"sum" Device"@ed_link_3
  where "Device_ID" < 5;
  
  It fails with errors: -.
  ORA-04052: error occurred when searching to the top of the remote object Aggregate.Device@ED_LINK_3
  ORA-01948: length of the name of the identifier (31) exceeds maximum (30)
  
  Is there a way to get around this?
  Is the problem with the columns of the remote table of device, which I do NOT need to import to have column names that are longer than 30 characters?
  
  For now, I want only the Device_ID column which is a simple 9 characters long.
  
  Oh, and the remote database is MySQL.
  I'm uncomfortable with the < parms of materialized view > as they work fine when I choose a different remote table with only short column names.
  
  Thank you.

  To my knowledge, you have the option
  (a) create view (with shortened column names or only with desired columns if they are already less than 30 char limit) side of mysql
  (b) use dbms_passthrough to force the analysis to be done on mysql (as in the example provided by SY here use dbms_passthrough to create a view )
  However, I prefer to stick to one), because with dbms_passtrhough, you retrieve row by row.

  Best regards

  Maxim

• is missing a closing parenthesis in create materialized view statement

  Hi, I am using oracle 10g R2 and try to create a view of materalized with the following statement:

  CREATE MATERIALIZED VIEW MVT_DEC_TAB USING INDEX REFRESH FAST ON COMMIT AS 
  select i.rowid as ind_rowid,c.rowid as indc_rowid,r.rowid as r_rowid,b.rowid as b_rowid,brk.rowid as brk_rowid,
  i.name,i.sname,i.address,i.tel,i.fax,i.email,
  DECODE(c.BRKNO,null,0,1) AS DEC_BRK,
  TO_TIMESTAMP(NVL(VEKDOV,'2001/01/01')||' 12:00:00','YYYY/MM/DD HH:MI:SS'),
  DECODE(c.brkno,null,DECODE(c.ncmpcode,null,c.vekdov,b.bcarddov),brk.validitydov)
  from indiv i,indivcoding c
  LEFT OUTER JOIN BROKER brk ON brk.brkno = c.brkno
  LEFT OUTER JOIN CORPORAT r
  ON c.ncmpcode=r.cmpcode INNER JOIN BCARD b ON b.bcardno=r.bcardno
  where c.typeact=2  
  and c.natcode=i.natcode
  and c.brkno is not null or c.ncmpcode is not null or c.nnatcode is not null

  but I get an error message:
  where c.typeact = 2
  ERROR on line 11:
  ORA-00907: lack of right parenthesis
  
  which makes no sense because if I run the sql code of the materialized view, it runs normally.
  I need to know what the causing this can someone help?

  Do not use the "LEFT OUTER JOIN" ANSI syntax in your CREATE MATERIALIZED VIEW definition.
  Specify

  FROM indiv i,indivcoding c, broker brk, corporat r
  WHERE brk.brkno(+) = c.brkno
  AND c.ncmpcode(+) = r.cmpcode
  

  OR

  FROM indiv i,indivcoding c, broker brk, corporat r
  WHERE c.brkno = brk.brkno(+)
  AND r.ncmpcode = c.cmpcode(+)
  

  (I find it more readable).

  Hemant K Collette

• Create materialized view at the trigger.

  Hello

  I use version below:

  Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production

  PL/SQL Release 11.2.0.1.0 - Production

  I created a materialized view query below:

  CREATE THE FSG1_FUND000 MATERIALIZED VIEW

  PCTUSED, PCTFREE 5 70

  Users TABLESPACE

  STORAGE (INITIAL 500K NEXT 500K)

  Refresh a start fast with (sysdate) next (sysdate + (1 / 1440))

  WITH rowid

  AS

  SELECT * FROM ABNDEV_T24. FSG1_FUND000@abndev;

  This Mview if any insert or update only (WITHOUT DELETING) are coming which should be copy to another table. But in mView trigger does not work.

  So pls advice me no alternative.

  Querys trigger:

  create or replace trigger trg_dummy

  after insert or update on FSG1_FUND000

  for each line

  Start

  If the insertion

  insert into FSG1_FUND001 (RECID, XMLRECORD) values (: new.) RECID,: new. XMLRECORD);

  elsif update then

  insert into FSG1_FUND001 (RECID, XMLRECORD) values (: new.) RECID,: new. XMLRECORD);

  end if;

  end;

  /

  Kind regards

  Villa

  Hello

  I learned and referred website as much as we can not able to create a trigger in MView (sorry we create trigger but none use of creation because in view no insert and update happened). So I drop completely the materialized view concepts and relaxation.

  Instead of, I have using the procedure to insert records in a table and then I created one by dbms_scheduler job.

  This discussion will be useful for any future reference.

  -procedure-

  create or replace procedure p2

  as

  Start

  INSERT / * + APPEND * / INTO FSG1_FUND000 SELECT * FROM FSG1_FUND000@remote;

  End; BluShadow

  /

  -----------------job--------------------

  Begin

  DBMS_SCHEDULER. () CREATE_JOB

  job_name-online "JOB4."

  job_type-online "PLSQL_BLOCK."

  JOB_ACTION => ' BEGIN p2; END;',

  start_date => SYSDATE,

  repeat_interval => ' FREQ = MINUTELY; INTERVAL = 5;',

  End_date => NULL,

  -Online TRUE, enabled

  comments => "Inserting a record in a table");

  end;

  /

• Generate the ddl to create materialized view log...

  Hi gurus...
  
  Oracle db: 11g
  
  I am trying to generate / excerpt from script MVIEW Logs from prod to be applied on the test.
  I tried
  < code >
  DBMS_METADATA. GET_DDL (decode(object_type,'materialized_view_log'), object_name, owner)
  from dba_objects
  where owner = < ABC >;
  < code >
  
  above fails, any ideas?
  
  Thank you

  >
  Oracle db: 11g

  I am trying to generate / excerpt from script MVIEW Logs from prod to be applied on the test.
  I tried
  
dbms_metadata.get_ddl(decode(object_type,'materialized_view_log'), object_name, owner)
from dba_objects
where owner=;


  above fails, any ideas?
  >
  Please try to use the tags in code, but you need to add.

   on the line before and the line after your code instead of what you are using.
  
  The object type names are case-sensitive so you need to use
  

  DBMS_METADATA. GET_DDL ('MATERIALIZED_VIEW_LOG', object_name, owner)

  Why are you using DECODE?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
  

• 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.

• Failed to create the fast refresh on the materialized view

  Hi, I am creating a materialized on the tables with fast refresh view on commit but I get an error message.

  I have created the following logs:

  Bonus CREATE MATERIALIZED VIEW LOG ON
  Users TABLESPACE
  WITH THE PRIMARY KEY
  INCLUDING THE NEW VALUES

  Used to CREATE MATERIALIZED VIEW LOG ON
  Users TABLESPACE
  WITH THE PRIMARY KEY
  INCLUDING THE NEW VALUES

  I then try to create the following:

  Test.BAM CREATE MATERIALIZED VIEW

  IMMEDIATE CONSTRUCTION
  COOL OFF QUICKLY ON COMMIT
  AS
  SELECT a.dept_no, SUM (a.salary)
  EMPLOYEE a, b bonus
  WHERE a.employee_id = b.employee_id
  GROUP BY dept_no

  When I do that, I get the following error:

  . ORA-12032: cannot use column rowid of materialized

  view log on 'test '. "" BONUS ".

  If I change to a full refresh, it works pretty well. If I create a MV with a fast refresh on a query just within the limits of the table bonus it also works very well, for example ' select * bonus where employee_id = 2'

  What I am doing wrong? Also when looking at the notes for MV connects in some places, he said using the primary key and others, he says to the sequence of use and row_id. Which is correct and what difference does it make?

  11.2 aix.

  Thank you very much

  I suggest that investigate you the reason why your MV is not quickly updatable with the following method:

  (1) create MV_CAPABILITIES_TABLE with @?/rdbms/admin/utlxmv.sql

  (2) exec ('BAM') dbms_mview.explain_mview

  3)

  column format a100 msgtxt

  column related_text format a20

  SELECT the possible, capability_name, related_text,

  msgtxt

  OF mv_capabilities_table;

  That should tell you the reason why he isn't yet quickly updatable.

  There was a popular quote on men and fishing, but I don't remember it for now :-)

  Kind regards

  Uwe Hesse

• Creating a discount on commit Materialized view

  Hello

  I am trying to create a refresh materialized view validation so that whenever I run followed by DML commit on Master he table should get quickly reflect in my view materialized.

  I gave SELECT on table privilege to the user where this point of view will be created

  The master:

  GRANT SELECT ON HR. EMPLOYEES AT SCOTT.

  Scott:

  Scott.hremp CREATE MATERIALIZED VIEW

  COOL OFF QUICKLY ON COMMIT

  AS

  SELECT * FROM HR. EMPLOYEES;

  ERROR on line 4:

  ORA-01031: insufficient privileges

  Then I Grant all on the table EMPLOYEES at SCOTT.

  GRANT ALL ON hr. EMPLOYEES AT SCOTT;

  Then got following error when creating view materilized:

  SQL > CREATE MATERIALIZED VIEW scott.hremp

  2 QUICK REFRESH YOU COMMIT

  3 AS

  4. SELECT * HR. EMPLOYEES;

  SELECT * FROM HR. EMPLOYEES

  *

  ERROR on line 4:

  ORA-23413: table 'HR '. "" EMPLOYEES "do not have a materialized view log

  I create materialized view Master journal:

  SQL > CREATE MATERIALISEE NEWSPAPER VIEW on human resources. EMPLOYEES;

  Materialized view log that is created.

  Even after this, that I'm not able to create not Exist Error in materialized view Table and now:

  SQL > CREATE MATERIALIZED VIEW scott.hremp

  2 QUICK REFRESH YOU COMMIT

  3 AS

  4. SELECT * HR. EMPLOYEES;

  SELECT * FROM HR. EMPLOYEES

  *

  ERROR on line 4:

  ORA-12018: following error occurred during the generation of code for 'SCOTT '. "" HREMP ".

  ORA-00942: table or view does not exist

  Kindly guide me.

  Also, I want to know why I needed to GRANT ALL HR for the creation of this point of view, materialized.

  You also need a (selection) grant on the MV newspaper created for master during an attempt to build a quickly updatable MV.

  ISSUE: Permissions problem making fast refresh

  See you soon,.