Rewrite Materialized View for quick update

Similar Questions

• term materialized view for update

  Hello

  Work on 10g

  I created a materialized as fast refresh view on commit.

  I need to know how long took for the update.

  I tried the below but could not get any results.

  SELECT increfreshtim FROM dba_mview_analysis, fullrefreshtim, last_refresh_date, mview_name

  Thanks in advance.

  It works for me. Post your MView definition and the output of queries, similar to what I posted.

  SQL > create table test_table as select level l, col of dbms_random.string ('A', 5) from dual connect by level<=>

  SQL > alter table test_table add constraint pk_test_table_l key (l) primary;

  SQL > create materialized view test_table; journal

  SQL > create a materialized view mv_all_objects cool off quickly in select * from test_table;

  Materialized view created.

  SQL > ed
  A written file afiedt.buf

  1. Select the owner, mview_name, last_refresh_date, refresh_method, fullrefreshtim, increfreshtim, query
  2 of dba_mview_analysis
  3 * where mview_name = 'MV_ALL_OBJECTS. '
  SQL > /.

  OWNER MVIEW_NAME REFRESH_ FULLREFRESHTIM INCREFRESHTIM QUERY LAST_REFR
  ------------------------------ ------------------------------ --------- -------- -------------- ------------- --------------------------------------------------------------------------------
  FDL_BAU MV_ALL_OBJECTS OCTOBER 8, 13 FAST 0 0 SELECT 'TEST_TABLE '. "' L ' 'L', 'TABLE_TEST '. «"COL" 'COL' OF 'TABLE_TEST' TEST_TAB «»

  -Insertion of data more

  SQL > insert test_table select 100000 + level l, col of dbms_random.string ('A', 5) from dual connect by level<=>

  SQL > exec dbms_mview.refresh ('MV_ALL_OBJECTS', 'F');

  PL/SQL procedure successfully completed.

  SQL > ed
  A written file afiedt.buf

  1. Select the owner, mview_name, last_refresh_date, refresh_method, fullrefreshtim, increfreshtim, query
  2 of dba_mview_analysis
  3 * where mview_name = 'MV_ALL_OBJECTS. '
  SQL > /.

  OWNER MVIEW_NAME REFRESH_ FULLREFRESHTIM INCREFRESHTIM QUERY LAST_REFR
  ------------------------------ ------------------------------ --------- -------- -------------- ------------- --------------------------------------------------------------------------------
  FDL_BAU MV_ALL_OBJECTS 8 OCTOBER 13 0 16 QUICK SELECT 'TEST_TABLE '. "' L ' 'L', 'TABLE_TEST '. «"COL" 'COL' OF 'TABLE_TEST' TEST_TAB «»

  SQL > drop materialized view log on test_table;

  Materialized view save ignored.

  SQL > drop mv_all_objects view materialized;

  Materialized view is deleted.

  SQL >

  The INCREFRESHTIM shows that it took 16 seconds to refresh the MView.

• ORA-00957 double Materialized View name column (UPDATE: do not answer)

  Hi all.  I get this error when you try to create a materialized view.  I have several other MV I've created without problem, but I can not find the catch here, can anyone help?.  I can't find the duplicates. The only double I was although entered in the function Pipeline_Code and the column being called a column. To check, I have renamed the latter and still make me this question.

  Any help would be greatly appreciated.

  
  Thank you!

  The request is below:

  CREATE THE MV_TEST_STATION MATERIALIZED VIEW

  COMPLETE REFRESH

  START WITH TO_DATE (20-SEP-2013 00:00:00 "," dd-mon-yyyy hh24:mi:ss')

  NEXT (SYSDATE + 12/24)

  AS

  SELECT T.TEST_STATION_ID,

  -(SELECT TEST_STATION_TYPE. DESCRIPTION

  -FROM TEST_STATION_TYPE

  -WHERE TEST_STATION. TEST_STATION_TYPE =

  -TEST_STATION_TYPE. TEST_STATION_TYPE)

  -AS TEST_STATION_TYPE,

  TST. DESCRIPTION AS TEST_STATION_TYPE,

  T.SURVEY,

  T.STATUS,

  T.STATION,

  () F_TRUESTATION2

  T.STATION,

  T.PIPELINE_CODE,

  F_REROUTE_CODE (T.STATION,

  T.PIPELINE_CODE))

  AS TRUE_STATION,

  T.REQUIRED,

  --(SÉLECTIONNEZ PIPELINE_CODES.) PIPELINE_CODE_DESCRIPTION

  -FROM PIPELINE_CODES

  -WHERE TEST_STATION. PIPELINE_CODE = PIPELINE_CODES. PIPELINE_CODE)

  - AS PIPELINE_CODE.

  PC. PIPELINE_CODE_DESCRIPTION AS PC_PIPELINE_CODE,

  T.INSTALL_DATE,

  COMMENT BY T.FUNCTIONAL,

  TSR. TEST_STATION_READING_ID,

  TSR. TEST_DATE,

  TSR. SURVEYOR,

  TSR. ON_VOLTS,

  TSR. ON_BG,

  TSR. ON_AG,

  TSR. METER_UTC,

  TSR. METER_ID,

  TSR. IO_BG,

  TSR. IO_AG,

  TSR. INSTANT_OFF_VOLTS,

  TSR. FUNCTIONAL_DAMAGE_OUT,

  TSR. FUNCTIONAL_DAMAGE_IN,

  TSR. COSEMETIC_DAMAGE_OUT,

  TSR. COSEMETIC_DAMAGE_IN,

  TSR.COMMENTS,

  TSR. CASING_ON,

  TSR. CASING_OFF,

  TSR. CASING,

  TSR. CALIBRATION_DUE_DATE,

  TSR. ANODE_AMPS_ON,

  TSR. ANODE_AMPS_OFF,

  TSR. ANODE

  OF TEST_STATION T

  INNER JOIN TEST_STATION_TYPE ON T.TEST_STATION_TYPE = TST TST. TEST_STATION_TYPE

  INNER JOIN PIPELINE_CODES ON T.PIPELINE_CODE = PC PC. PIPELINE_CODE

  INNER JOIN TEST_STATION_READING ON T.TEST_STATION_ID = TSR TSR. TEST_STATION_ID

  WHERE T.TEST_STATION_ID = TSR. TEST_STATION_ID

  You have two COMMENTS:

  COMMENT BY T.FUNCTIONAL,

  ...

  TSR.COMMENTS,

• Materialized view automatically refresh? If the updating of the means how?

  Materialized view refresh automatically? If the updating of the means how?

  It is expected is not to ask questions of the basic documentation.

  Refresh Options

  When you define a materialized view, you can specify three update options: how to refresh, what kind of update and can trust constraints be used. If not specified, default values are considered as ON DEMAND , FORCE , and ENFORCED forced respectively.

  The two execution modes are ON COMMIT and ON DEMAND . According to the materialized view, you create, some options may be unavailable. Update modes are described in table 8-4 .

  Table 8-4 Modes of discount

  Refresh the Mode	Description
  ON COMMIT	Refresh product automatically when a transaction which changed one of the paintings of the materialized view's retail is committed. This can be specified as the materialized view is quickly updatable (in other words, no complex). The ON COMMIT privilege is required to use this mode.
  ON DEMAND	Refresh occurs when a user manually executes one of the procedures available refresh contained in the DBMS_MVIEW package ( REFRESH , REFRESH_ALL_MVIEWS , REFRESH_DEPENDENT ).

  http://docs.Oracle.com/CD/B28359_01/server.111/b28313/basicmv.htm#i1006193

• Materialized views Refresh method and refresh option

  Hi Experts,

  According to the docs, If the MV contains the following, MV is considered complex. I wonder is there any view data dictionary that indicates the type of MV? Because is very easy to the candidate a complex type mv. Because many queries contains the properties below.

  http://docs.Oracle.com/CD/B28359_01/server.111/b28326/repmview.htm#i52501

  http://docs.Oracle.com/CD/B28359_01/server.111/b28313/basicmv.htm

  Specifically, a materialized view is considered complex if the materialized view definition query contains:

  • A CONNECT BY clause
  • An INTERSECT , MINUS , or UNION ALL operation
  • he DISTINCT or UNIQUE keyword
  • In some cases, an aggregate function, although it is possible to have an aggregation function in the query definition and always have a simple materialized view
  • In some cases, joins other than those in a subquery, although it is possible to have joins in the definition to interrogate and still have a simple materialized view
  • In some cases, a UNION operation

  
  

  After that I kept going to read that I learned that when a VM is created, the refresh mode is specified according to the type of the MV. That means, using ON-DEMAND refresh mode is widespread. The documentation mentions that there isa also refresh option. My question is, is it possible to specify

  ON REQUEST and FAST together?

  Also, what are the differences between FULL and FAST. Ends truncate the table and fill it up again?

  ON COMMIT

  Refresh product automatically when a transaction which changed one of the paintings of the materialized view's retail is committed. This can be specified as the materialized view is quickly updatable (in other words, not complex). The ON COMMIT privilege is required to use this mode.

  ON DEMAND

  Refresh occurs when a user manually executes one of the procedures available refresh contained in the DBMS_MVIEW package ( REFRESH , REFRESH_ALL_MVIEWS , REFRESH_DEPENDENT ).

  COMPLETE	Refreshes and recalculating the materialized view query definition.
  FAST	Applies incremental changes to refresh the materialized view using the information recorded in the papers of the materialized view, or an SQL * Loader direct-path access or a partition maintenance operation.

  FORCE

  Applies FAST update if possible; otherwise, it applies COMPLETE Refresh.

  NEVER

  Indicates that the materialized view will not be updated with updating mechanisms.

  Select * from version of v$.

  Oracle Database 11 g Release 11.2.0.4.0 - 64 bit Production

  Thank you

  Çaglar wrote:

  ...

  Also, what are the differences between FULL and FAST. Ends truncate the table and fill it up again?

  ...

  Thank you

  I just want to answer the truncated question. Seems that nobody covered that yet.

  Answer: It depends.

  If you do a full refresh, then the default is to use ATOMIC_REFRESH = TRUE.

  This means that the update is done via an insert, delete , and ... Select.

  You can change it to ATOMIC_REFRESH = FALSE (parameter dbms_mview.refresh).

  This means that is a TRUNCATE and insert a ... Select with APPEND peak (path direct insert).

  Refresh if Atomic = FALSE is considerably faster than the default. Also way less Archives of newspapers are written.

  The downside is however that, during the update the MV is empty, is no longer an atomar operation!

  See also Oracle documentation: http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_mview.htm#i997194

• Is it possible to limit registration of deletion in the MATERIALIZED VIEW UPDATE?

  Hello
  I have materialized view can be updated and I want to just limit the functionality of record deletion on this point of view.
  that is, the user should update the view but not able to delete the records.
  
  Is it possible if yes then please describe the steps.
  
  Kind regards
  Kam.

  If your point of view materialzed is editable, write a trigger and throw an exception on delete.

  for triggers on views materialzed see...

  http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:672989600346945045

• Pivot can be used in fast refresh materialized view?

  Hi, I have a question about materialized view nested mode fast refresh on Oracle 11 g (It support function of pivot, but oracle 10 g doesn't support).
  
  When I created, he throws "ORA-12015: cannot create a view fast refresh materialized by a complex query.
  Then I used dbms_mview.explain_mview to see reason, and it tell me the following
  REFRESH_FAST_AFTER_INSERT ' view inline or subquery in LIST not supported for this type of MV.
  
  Can someone help me, any suggestions will be appreciated
  

  create table empX as select * from scott.emp;
  alter table empX add constraint PK_empX_empno primary key (empno);
  
  --drop  MATERIALIZED VIEW LOG ON empX;
  CREATE MATERIALIZED VIEW LOG ON empX with rowid, sequence(empno);
  
  --drop MATERIALIZED VIEW mv_empX;
  CREATE MATERIALIZED VIEW mv_empX
  REFRESH FAST START WITH SYSDATE
  NEXT  SYSDATE + 1/1440
  AS   
    select * from
    (
     select rowid emp_rowid, deptno, job, sal from empX
    )
    PIVOT( max(sal) for job IN ('ANALYST' job1, 'CLERK' job2, 'MANAGER' job3));
   
  --select * from mv_capabilities_table
  declare
    lv_sqltext varchar2(4000);
  begin
    execute immediate 'truncate table mv_capabilities_table';
    lv_sqltext := 'select * from
    (
     select deptno, job, sal from empX
    )
    PIVOT( max(sal) for job IN (''ANALYST'' job1, ''CLERK'' job2, ''MANAGER'' job3))
    ';  
    dbms_mview.explain_mview(lv_sqltext,'nested=>TRUE');
    commit;
  end;
  /

  Let me help you...
  I have done following and it run/view updated because I just replaced quickly with a complete word, because there are limitations for quickly updatable views:

  SQL> show user;
  USER is "SCOTT"
  SQL> create table empX as select * from scott.emp;
  
  Table created.
  
  SQL> alter table empX add constraint PK_empX_empno primary key (empno);
  
  Table altered.
  
  SQL>
  SQL> --drop  MATERIALIZED VIEW LOG ON empX;
  SQL> CREATE MATERIALIZED VIEW LOG ON empX with rowid, sequence(empno);
  
  Materialized view log created.
  
  SQL>
  SQL> --drop MATERIALIZED VIEW mv_empX;
  SQL> CREATE MATERIALIZED VIEW mv_empX
    2  REFRESH COMPLETE WITH rowid
    3  START WITH sysdate
    4  NEXT  SYSDATE + 1/1440
    5  AS
    6    select * from
    7    (
    8     select rowid emp_rowid, deptno, job, sal from empX
    9    )
   10    PIVOT( max(sal) for job IN ('ANALYST' job1, 'CLERK' job2, 'MANAGER' job3));
  
  Materialized view created.
  
  SQL> select * from mv_empx;
  
  EMP_ROWID              DEPTNO       JOB1       JOB2       JOB3
  ------------------ ---------- ---------- ---------- ----------
  AAAShcAAEAAAATTAAN         10                  1300
  AAAShcAAEAAAATTAAE         30
  AAAShcAAEAAAATTAAJ         30
  AAAShcAAEAAAATTAAC         30
  AAAShcAAEAAAATTAAA         20                   800
  AAAShcAAEAAAATTAAK         20                  1100
  AAAShcAAEAAAATTAAM         20       3000
  AAAShcAAEAAAATTAAD         20                             2975
  AAAShcAAEAAAATTAAB         30
  AAAShcAAEAAAATTAAI         10
  AAAShcAAEAAAATTAAL         30                   950
  
  EMP_ROWID              DEPTNO       JOB1       JOB2       JOB3
  ------------------ ---------- ---------- ---------- ----------
  AAAShcAAEAAAATTAAF         30                             2850
  AAAShcAAEAAAATTAAG         10                             2450
  AAAShcAAEAAAATTAAH         20       3000
  
  14 rows selected.
  
  SQL> begin
    2  dbms_mview.refresh('SCOTT.mv_empx');
    3  end;
    4  /
  
  PL/SQL procedure successfully completed.
  
  SQL> select * from mv_empx;
  
  EMP_ROWID              DEPTNO       JOB1       JOB2       JOB3
  ------------------ ---------- ---------- ---------- ----------
  AAAShcAAEAAAATTAAN         10                  1300
  AAAShcAAEAAAATTAAE         30
  AAAShcAAEAAAATTAAJ         30
  AAAShcAAEAAAATTAAC         30
  AAAShcAAEAAAATTAAA         20                   800
  AAAShcAAEAAAATTAAK         20                  1100
  AAAShcAAEAAAATTAAM         20       3000
  AAAShcAAEAAAATTAAD         20                             2975
  AAAShcAAEAAAATTAAB         30
  AAAShcAAEAAAATTAAI         10
  AAAShcAAEAAAATTAAL         30                   950
  
  EMP_ROWID              DEPTNO       JOB1       JOB2       JOB3
  ------------------ ---------- ---------- ---------- ----------
  AAAShcAAEAAAATTAAF         30                             2850
  AAAShcAAEAAAATTAAG         10                             2450
  AAAShcAAEAAAATTAAH         20       3000
  
  14 rows selected.
  
  SQL>
  

  So, the answer is Yes, we can use Pivot with Materialized view but:
  1 MV must be full refresh.
  2 oracle version should be 11 g; of course the pivot is available in Oracle 11 g.

  If this answers your question, please close the message, otherwise continue.

  These links may also be of interest:
  http://docs.Oracle.com/CD/B28359_01/server.111/b28313/basicmv.htm#i1007028
  http://docs.Oracle.com/CD/B28359_01/server.111/b28313/basicmv.htm#i1007007

  http://rwijk.blogspot.in/2009/06/fast-refreshable-MATERIALIZED-view.html

  And:

  Please see if (Note: 179466.1 - view to fast refresh materialized diagnose ORA-12015 / complex queries) help.

  Concerning
  Girish Sharma

• Creation of privilege to write to the database master materialized view?

  I would like to create materialized views for a few tables of a production Oracle database replication. I have only read access to the source database. I think I need additional privileges to create the journal for the quick update. Is this correct? Have no option if I can't get additional privileges and cannot get a DBA to help me?

  If you need to fast refresh to materialized view log, you will need help of DBA.

  Otherwise, you need to create complete refresh Mviews.

• Difference between the table and Materialized View

  Is there an advantage outside automatic synchronization (founded refresh selected type) using Materialized View?

  I came across this question as table and MV both store values, and we can also update table using the code what is the need of MV? Why not create a table instead of MV with the same definition and same charly?

  I need some explanation to force someone to convince himself.

  Thank you

  http://docs.Oracle.com/CD/B19306_01/server.102/b14223/basicmv.htm

  Sections that highlight its strengths:

  1. materialized views for data warehouses

  2. materialized views for distributed computing

  Query, re - write, features as Materialized view log files that can be used for replication between databases, etc...

• utlu112i_8.SQL: be refreshed materialized views

  Document 884522.1 said to run the script utlu112i_8.sql on my version 11 GR 1 material Vision 12.1 data base, to prepare for the upgrade of GR 11, 2

  The report indicates that it materialized views being updated is

  I was checking document 1526264.1 which explains how to check if this action is busy and with all the details... but, all the SELECT statements return: no line selected.

  And later, when I run utlu112i_8.sql again, he said: materialized views are being updated

  What's not here?

  In addition the report itself does not much tip how to solve the problem, how to fix the problem? Is the report correct?

  You can see the

  Doc - ID 1358698.1)

  Down

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

• Prob of materialized view

  Hi all
  
  
  I have problem with Mview when you perform dml operations.
  
  I'm trying to insert or update on the materialized view, then I am getting below error.
  
  ORA-01732: operation non-legal data manipulation on this point of view
  
  Please can you me cant we do on the materialized view dml operations?
  
  My version of DB is 10g.
  

  DESC SUNITHA;
  
  Name     Null?     Type
  NAME          VARCHAR2(10)
  ID     NOT NULL     NUMBER(2)

  create  MATERIALIZED  view maview as select * from sunitha;

  I'm trying to insert into maview
  

  insert into maview values('c',4);
  
  ORA-01732: data manipulation operation not legal on this view

  Please notify.
  
  
  Thank you
  Miriam.

  Here is an excerpt of the document.

  Updatable Materialized Views
  
  You can make a materialized view updatable during creation by including the FOR UPDATE
  clause or enabling the equivalent option in the Replication Management tool. For changes
  made to an updatable materialized view to be pushed back to the master during refresh,
  the updatable materialized view must belong to a materialized view group.
  
  Updatable materialized views enable you to decrease the load on master sites because users
  can make changes to the data at the materialized view site. The following is an example of
  an updatable materialized view:
  
  CREATE MATERIALIZED VIEW hr.departments FOR UPDATE AS
    SELECT * FROM [email protected];
  
  The following statement creates a materialized view group:
  
  BEGIN
     DBMS_REPCAT.CREATE_MVIEW_REPGROUP (
        gname => 'hr_repg',
        master => 'orc1.world',
        propagation_mode => 'ASYNCHRONOUS');
  END;
  /
  
  The following statement adds the hr.departments materialized view to the materialized
  view group, making the materialized view updatable:
  
  BEGIN
     DBMS_REPCAT.CREATE_MVIEW_REPOBJECT (
        gname => 'hr_repg',
        sname => 'hr',
        oname => 'departments',
        type => 'SNAPSHOT',
        min_communication => TRUE);
  END;
  
  /
  
  You can also use the Replication Management tool to create a materialized view group
  and add a materialized view to it.
  

• Oracle Warehouse builder or materialized views

  I have a requirement as follows:
  
  Requirement:
  We must create a Reporting DB to be used for information and a transactional database will be in separate host. Fundamentally, he need to extract data from a set of transactional DB tables and move to the Reporting DB schema at adequate intervals.
  
  We may have to get a different column data in different tables and store it in a single table / several reports DB tables.
  
  
  Can someone whether to go with Oracle Warehouse builder or the materialized views for this offer please?
  Or use OWB to create and maintain the MVs.
  
  Also please me a link point to what features are available with OWB
  
  Our Oracle is installed in Solaris 10 and one who is perfect either generator warehouse Oracle or materialized views
  
  Thank you
  APPU
  
  Published by: user12094414 on October 25, 2009 21:52
  
  Published by: user12094414 on October 25, 2009 22:17

  user12094414 wrote:
  Can someone whether to go with Oracle Warehouse builder or the materialized views for this offer please?
  Or use OWB to create and maintain the MVs.

  The two are not exclusive. OWB is a tool for designing the data movement and implement updates to the warehouse.

  MVs are a tool integrated into the database in support of materialization of the current request to speed up some types of applications related to data that is availoable, perhaps after transport OWB.

  >

  Also please me a link point to what features are available with OWB

  Normal (to allow the future of mutual aid) access is

  http://OTN.Oracle.com
  -> Products (perma menu on the left): database (link)
  -> Warehouseing Bi & data (link in the middle section)
  -> Related products (product menu on the right): Warehouse Builder
  where you can get a Viewlet, whitepapers, docs, demos, tutorials, etc.

  Direct access to the page above is http://www.oracle.com/technology/products/warehouse/index.html

• Problem with the materialized view

  Hello
  
  I encountered a problem...
  
  I have a materialized view which I update via a button in my application. I used the following code to do this:
  DBMS_REFRESH. Refresh (the "SCHEME".) "MY_MV" ');
  
  As you can see the pattern, I have included in the appeal, and which worked fine until now.
  
  We have now 2 apps. in the same PB. Its actually the same app... Only for the development and the other for testing. The app development uses a different schema and this effect cannot use the call above, it seems.
  
  I offcause want to ommit using the schema in the call, because otherwise I would have to change every time I move to App Development to test the app. But when I ommit it I get the following error:
  
  ORA-23404: refresh, group "APEX_PUBLIC_USER". "' MY_MV ' does not exist
  
  How to solve this?
  
  And another thing... My selection around the application does not use the scheme, then how does apex know what sound scheme when his choice, but he does not know when its doing a dbms_refresh?
  
  Hope someone is smarter than me :)
  
  Bjarke

  Hello
  Try this way

  declare
  my_schema varchar2(10);
  begin
  select owner into my_schema from apex_applications where application_id=:APP_ID;
  dbms_refresh.refresh( my_schema || '.'|| 'MY_MV');
  end;
  

  CITY

• Materialized view questions...

  Hi all..
  
  Please help me with the following question on the materialized view.
  I need to create a MV on my LOCAL_DB on a table that is located on REMOTE_DB.
  Should I created the log of the view materialized in the '' REMOTE_DB".
  
  1)
  
  Are there disadvantages in using materialized views? I mean, there is no maintenance required
  When the database has stopped or
  
  2)
  «I create view materliazied as "" select * from table_name "»»
  If the base table changes, influence my materialized view.
  
  I have the following sqls to create the mv, please let me know if that is correct.
  
  
  -LOCAL_DATABASE
  Plates_mv CREATE MATERIALIZED VIEW
  REFRESH quickly
  START BY SYSDATE
  NEXT SYSDATE + 1
  AS SELECT * FROM plates@home_dmv.world;
  
  
  -REMOTE_DATABASE or LOCAL_DATABASE?
  CREATE MATERIALIZED VIEW LOG ON plates;
  
  I thank in advance.