Are materialized views in Oracle OLAP licenses. ?

Similar Questions

• How to check the table have are all views in oracle

  Hello
  How to check the table have are all views in oracle

  SELECT * FROM user_dependencies
  WHERE type='VIEW'
  AND referenced_type='TABLE'
  AND referenced_name ='Your_Table_Name' 
  

  You can use dba_dependencies to find views in the different schema.

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

• 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

• Read-only materialized view

  When you try to refresh the materialized view, we frequently get the below error. In order to overcome this error to drop and re-create this point of view. I also came to know that there are materialized views unalterable that can be set at the time of the creation of materialized view syntax inorder to avoid the error below.
  Please give me example how to create read-only materialized view.
  
  SQL > BEGIN dbms_mview.refresh ('CPNF_SRCLNK_TBL'); END;
  
  *
  ERROR on line 1:
  ORA-00942: table or view does not exist
  ORA-06512: at "SYS." DBMS_SNAPSHOT", line 2254
  ORA-06512: at "SYS." DBMS_SNAPSHOT", line 2460
  ORA-06512: at "SYS." DBMS_SNAPSHOT", line 2429
  ORA-06512: at line 1
  
  Thank you

  Hello

  See this note.

  * Materialized view refresh fails with ORA-942: table or view is not [236652.1 ID] *.

• Materialized view rebuild to change size of column

  We have changed the size of a varchar2 column in an OLTP table... The matte view in the warehouse pointing to this table/column complains... Is there an argument to 'rebuild' for materialized views in Oracle as I've seen in other databases? Or should I remove mast view create view Matt, create indexes and collect the tablestats to get it to pick up the new size of the column.
  
  The following statement compiles the matte view but does not pick up the new size and the matte view guard Plains.
  

  alter materialized view sms_ar.mv_sufficiency compile;

  I tried to put the argument of the 'reconstruction' on it but could not operate.

  Hi Mark,

  What is

  SQL> create table t(x varchar2(5))
  Table created.
  
  SQL> create materialized view mv
  as
    select x from t
  Materialized View created.
  
  SQL> alter table t modify x varchar2(10)
  Table altered.
  
  SQL> desc t
  TABLE t
   Name                                      Null?    Type
   ----------------------------------------- -------- -----------
   X                                                  VARCHAR2(10)
  
  SQL> desc mv
  TABLE mv
   Name                                      Null?    Type
   ----------------------------------------- -------- -----------
   X                                                  VARCHAR2(5)
  
  SQL> alter materialized view mv modify x varchar2(10)
  Materialized View altered.
  
  SQL> desc mv
  TABLE mv
   Name                                      Null?    Type
   ----------------------------------------- -------- -----------
   X                                                  VARCHAR2(10)
  

  Concerning
  Peter

• Oracle materialized view more Gateway

  Dear Sir.
  
  We have microsoft sql server, oracle gateway (11G) and database server (10.2.0.5)
  
  We already have the complete installation, and it works.
  
  We create a materialized view in the oracle server to read data from sql server, but the updating of the MV can't wait time
  We are planing to create the view materialized in the oracle gateway server.
  
  My question is:
  
  What is the best solution to create the MV in the oracle gateway server?
  I mean I can't download MV only one instance of oracle database.
  
  Thanks in advance.

  Just to clarify: there is normally no need to install a database on the gateway server. You can create the mview directly in your 10.2.0.5 database.
  If you really want to have another data base which contains the mview then install in the box of gateway to the Oracle database using the version standard edition. There is no need to activate Enterprise Manager or other stuff.
  About the size of the memory, it really depends on the amount of data you have to shoot through the gateway and to select by using the synonym. Therefore, there is no generic answer on sizing.

• 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

• Materialized views Oracle | Reporting

  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.
  
  
  Solution (Please confirm):
  
  I intend to use Oracle materialized views in the same host as transactional DB to next part of requirment
  
  "We may have to get a different column data in different tables and store it in a single table / several reports DB tables.
  
  and then use Oracle streams to move at regular intervals of DB reports.
  
  Is this feasible?
  Or please suggest a solution.
  
  Thank you
  APPU

  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.

  Depending on how small and simple is your database, you can create materialized views on the Reporting DB to point to DB Transactionla through the database link.

  I intend to use Oracle materialized views in the same host as transactional DB to next part of requirment

  If are simple MVs, then let them cool off quickly. If too complex, all jobs to refresh at specific intervals.

  "We may have to get a different column data in different tables and store it in a single table / several reports DB tables.

  You will be several tables in DB report in the form of the Metrialised views

  and then use Oracle streams to move at regular intervals of DB reports.

  This combination is not necessary. You're talking about two different things at the same time.

• 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

• Materialized Oracle view | Deleting records, Oracle materialized view

  One question reg Materialized views.
  
  If as part of the interview of the Source database, we remove some (older) recordings, the materialized view will also be updated with the deletion?
  
  I believe that the answer is Yes. In this case make sure that deletion is not the case?
  
  Is there anyway that we'll stop MView update to delete records that is inserted once even if we remove the same records in the source DB?

  This is a common scenario, especially with materialized views that summarizes the detail data where you want to keep the summary but not the detail, and it is discussed in the documentation.

  The technique is to make the MV refresh on request, delete the data in the detail tables and the CONSIDER_FRESH procedure to prevent the changes propagating to the MV. You will probably find it in the docs by searching on DBMS_MView.Consider_Fresh. There are a few caveats to note, in my opinion.

• Oracle 8i Materialized view

  I'm on oracle 8.1.7
  
  A few times is not automatically refresh
  
  -I want to connect view refresh time in other tables when it refreshes
  
  -wanted to know whether the necessary changes in the view script
  
  
  DROP MATERIALIZED VIEW MSIRC. IL_BRANCHES;
  
  CREATE THE MSIRC MATERIALIZED VIEW. IL_BRANCHES
  REFRESH FORCE
  START WITH TO_DATE (October 12, 2009 09:15:42 "," dd-mon-yyyy hh24:mi:ss')
  NEXT sysdate + 1/1440
  WITH THE PRIMARY KEY
  ACTIVATE THE QUERY REWRITING
  AS
  / * In format on 2009-10-12 13:44:16 (PS5 v5.115.810.9015) * /.
  SELECT 'IL_BRANCHES '. "" BRANCH_ID ""BRANCH_ID"
  'IL_BRANCHES '. ' ' ' 'NAME',
  'IL_BRANCHES '. "' HEADLINE '"TITLE. "
  'IL_BRANCHES '. "" INSTANCE_ID ""INSTANCE_ID. "
  'IL_BRANCHES '. "' PARENT_ID '"PARENT_ID"
  'IL_BRANCHES '. "" PUB_STATUS ""PUB_STATUS"
  'IL_BRANCHES '. "" ALERT_STATUS ""ALERT_STATUS"
  'IL_BRANCHES '. "' ORDER_FIELD ' 'ORDER_FIELD ',.
  'IL_BRANCHES '. "" DESCRIPTION ""DESCRIPTION. "
  'IL_BRANCHES '. "" RELATED_LINKS ""RELATED_LINKS"
  'IL_BRANCHES '. "" EXTERNAL_LINK ""EXTERNAL_LINK. "
  'IL_BRANCHES '. "" SEND ""SENT. "
  'IL_BRANCHES '. ' ' CONTENT_1 ' 'CONTENT_1 '.
  OF ' IL_BRANCHES"@STAGING 'IL_BRANCHES ';

  I want to connect view refresh time in other tables when it refreshes

  You can check the last_refresh of the user_snapshot_refresh_times view and the view user_refresh next_date

  You can use it in the below format

  TO_CHAR (last_refresh, "DD-MM-YY HH24:MI:SS) last_refresh

  Anand

• Oracle Materialized view... Auto-refresh

  Hello
  
  I want to refresh my view daily Oracle Materilized @ night mi... I am a new Bee and need your help in detail
  
  Thank you

  DBMS_JOB
  DBMS_SCHEDULER

• How to understand where are the data in a materialized view, coming from

  HI: when I run select NAME, OWNER of dba_mview_refresh_times, I see a number of materialized views. How can I find more information on this view it's source data and fields. The source in a different database table has changed. But the view on my database where the materialized view has not changed. I want to confirm origin of data in this view
  
  TIA
  Ravi

  Take a look at the column of the QUERY to the DBA_MVIEWS view.

• 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