What is 'Table of container' in materialized views

Hello

What is meant by ' Container Table ' in materialized views?

"Materialized view" (MV) is, in fact, a table, rather than a view.

The term MV is used of the 9i database. In the 7 and 8 databases is the term 'snapshot' (to make things more complicated, the MV concept appeared in the 8i database, but in the context of the data warehouse).

When you create a MV, for example. using the:

Create materialized view emp_mv

full refresh on demand

as select empno, ename from EMP

/

you have, in fact, have created two objects in the data dictionary:

Select object_name, object_type

from user_objects

where object_name = 'EMP_MV. '

order by 1, 2;

OBJECT_NAME OBJECT_TYPE

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

MATERIALIZED VIEW EMP_MV

EMP_MV TABLE

You can remove MV and a table of container:

drop materialized view emp_mv;

or you can delete only MV, preserving a table containing:

Let fall the materialized view emp_mv maintain the table;

Kind regards

Zlatko

Tags: Database

Similar Questions

  • What is the desertion of orderly materialized view with MLOG$.

    I have 11.2.4.0 Oracle enterprise edition.

    I want to remove completely the MATERIALIZED view and MATERIALIZED view logs.


    I need to do this on a production of databases.


    It's the right order?

    Thank you.

    You can drop the materialized view log first, then the materialized views.

    Because when you drop a materialized view log is therefore more available to fast refresh, however, it is available to rewrite, so drop materialized view log first, then materialized views. Additional information provided below may help Doc Oracle.

    If you delete a simple materialized view that is the least recently refreshed materialized view of a main table, then the database automatically purges the materialized master table see only connect the required lines to refresh the materialized view has fallen.

    If you delete a materialized view that was created on a predefined table, then the database removes the materialized view, and table preconstruitse returns to his identity in a table.

    When you delete a master table, the database does not automatically drop the materialized views based on the table. However, the database returns an error when it tries to refresh materialized view based on a main table that has been abandoned.

    If you delete a materialized view, then all the compiled queries that have been rewritten to use the materialized view will be invalidated and recompiled automatically. If the materialized view was preconstruitse on a table, then the table is not deleted, but it can no longer be maintained by the materialized view refresh mechanism.

  • Materialized view and Table

    Dear friends,

    A quick question...

    If the name of the materialized view and table name is same truncate table data truncates too materialized view?

    Thanks /.

    kumar73 wrote:
    Dear friends,

    A quick question...

    If the name of the materialized view and table name is same truncate table data truncates too materialized view?

    Thanks /.

    If the materialized view is built on the table and the Table is truncated data will continue to reside in the MView as long as it is not refreshed.

    Once you refresh the MView, data must disappear.

    With MView and Table names even, does not affect.

  • 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

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

  • fast refresh on MATERIALIZED VIEW

    Oracle 10 g R2 (10.2.0.5)

    Scott.mv_test CREATE MATERIALIZED VIEW
    Users TABLESPACE
    NOCACHE
    LOGGING
    NOCOMPRESS
    NOPARALLEL
    IMMEDIATE CONSTRUCTION
    REFRESH THE STRENGTH TO DEMAND
    WITH THE PRIMARY KEY
    AS
    Select...

    I this MV, when I do the QUICK refersh as follows, I get the error message

    SQL > execute DBMS_MVIEW. REFRESH ('MV_TEST', 'f');
    DBMS_MVIEW BEGIN. REFRESH ('MV_TEST', 'f'); END;

    *
    ERROR on line 1:
    ORA-12004: QUICK COOLING can be used to view materialized "SCOTT." "" MV_TEST ".
    ORA-06512: at "SYS." DBMS_SNAPSHOT", line 2251
    ORA-06512: at "SYS." DBMS_SNAPSHOT", line 2457
    ORA-06512: at "SYS." DBMS_SNAPSHOT", line 2426
    ORA-06512: at line 1

    But it works with full refresh.

    Is this planned, any help would be appreciated.

    Thank you 
    ORA-12004: REFRESH FAST cannot be used for materialized view "string"."string"
Cause:      The materialized view log does not exist or cannot be used. PCT refresh is also not enabled on the materialized view
Action:      Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log or PCT refresh is possible after a given set of changes, REFRESH FAST will be available starting the next time the materialized view is refreshed.

    http://ORA-12004.ora-code.com/

  • What is a materialized view?

    If I read oradocs on flashback instructions table and it mentions

    When you delete a table, all the newspapers view materialized, defined on the table are also deleted, but are not placed in the Recycle Bin. Therefore, the materialized view logs cannot be flashed back as well as the table

    (http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_9012.htm#SQLRF01802)


    then I went to oradocs for the view materialized and read the first half logs.

    http://docs.Oracle.com/CD/B19306_01/server.102/b14200/statements_6003.htm

    Now, I know what makes a materialzed view log.

    is a materialized view as a point of view however... ?

    No, it isn't.

    A materialized view is basically a query with its 'materialized' or stored in a table results. A MV can be used by Oracle in a manner transparent re - write a query to be faster.

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

  • 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

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

  • How to stop refreshing materialized views if the source table is null

    any ideas?

    Probably not what you were hoping for, but here's a few ideas.

    Your account shows - 113 (85 pending)
    1. How about helping to keep the forum clean by examining your 85 not resolved previous issues and give credit relatively USEFUL or RESPONDED to those who helped you in the past.

    2. read the FAQ at the top right of the page and view information about your system and your software so that we know what you're working with.

    3 ask your question in the body of the thread. Don't tell "of ideas.

    What is your question? Is this an academic question or you have a real problem that needs to be addressed?

    If you have a problem producing the DDL for the materialized view, and information about the type of discount that has been set up for this. Is there a newspaper view materialized on the underlying tables?

    The simple answer to your quest is to use UPDATE them on REQUEST and check the base tables before making a manual
    a: the best answer depends on what version of Oracle you are using and what is your actual configuration. Are your
    MVs in REFRESH GROUPS? Who can make a difference in the response.

    How can anyone help with this issue if you do not provide the information needed (FAQ)? Why is - someone MUST help if you show you don't appreciate help in marking questions to which answered once you have helped.

  • Questions on the tables of materialized views and MV newspaper

    Hi all

    Have some questions about Materialized View.

    (1) once the materialized view reads the records from the table MLOG, reviews the MLOG get purged. fix? or is that not the case? In some cases, I see still (old) records in the MLOG table even after updating MV.

    (2) how the table MLOG distinguishes between a reading which comes from a MV and a reading that comes from a user? If I execute manually
    "Select * < table MLOG > ' could get record of the table MLOG redacted all the same way as it does after a refresh of MV?

    (3) one of our MV updates crashes intermittently. Based on the events of waiting I noticed that it was a 'db file sequential read' against the main table. Finally I had to put an end to the update. I don't know why it was sequential reading on the main table when she should be reading the table MLOG. Any ideas?

    (4) I saw 'file db scattered read' (full table scan) usually on tables, but I was surprised to see 'db file sequential read' against the table. I thought sequential read occurs normally against the index. All the world has noticed this behavior?

    Thanks for your time.

    (1) once all the registered materialized views have read a particular line in a trunk of materialized view, it is removed, Yes. If there are multiple materialized views that are based on the same newspaper, they would all need to refresh before it would be safe to delete the log entry for MV. If one of the materialized views is no incremental updating, there may be cases where the log purge automatically.

    (2) No, your query does not cause anything be served (although you wouldn't see something interesting unless you get to implement a lot of code to analyze change vectors stored in the journal). I don't know the exact mechanism used by Oracle has been published, if you could go through and draw a session to get an idea of the moving parts. From a practical point of view, you just need to know that when you create an updatable materialized view fast, it will register as interested especially newspapers MV.

    (3) it depends on what is stored in the log of MV. The update process may need to recover specific table columns if your log stores just the fact that the data for a particular key changed. You can specify when you create a materialized view that you want to store specific columns or include the new clause values (with the NEW VALUES INCLUDING). It is perhaps beneficial (or necessary) for the refreshment quick process, but it would tend to increase the storage space for the materialized view log and increase the cost of the maintianing the materialized view log.

    (4) sequential reads on a table are perfectly normal - it just means that someone looking for a block of data in the table (i.e. looking a line in the table of ROWID based on the ROWID in an index or a materialized view log).

    Justin

  • Drop the materialized view's base table

    HI please let me know what happens if I drop from the base table of a materialized view? the MV remains valid with the data?

    Hello

    Well, it's easy to test yourself.

    SQL> select count(*) from t1;

  COUNT(*)
----------
       100

SQL> desc t1
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ID                                                 NUMBER(10)

SQL> create materialized view t1_mv as select * from t1;

Materialized view created.

SQL> select count(*) from t1_mv;

  COUNT(*)
----------
       100

SQL> drop table t1 purge;

Table dropped.

SQL> select count(*) from t1_mv;

  COUNT(*)
----------
       100

SQL> desc t1_mv
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ID                                                 NUMBER(10)

SQL> select object_type, status from user_objects where object_name = 'T1_MV';

OBJECT_TYPE         STATUS
------------------- -------
TABLE               VALID
MATERIALIZED VIEW   INVALID

SQL> select * from t1_mv where rownum < 5;

        ID
----------
         1
         2
         3
         4

SQL>

    I think the answer is very clear.

    Asif Momen
    http://momendba.blogspot.com

  • How to create table containe blob column view?

    Hi, I would like to aske any type of blob data
    I have data containe blob clolumn type table

    I want to create view this table how do?
    and


    If I created the table view blob column data will be responsible for memory or what because that will cause some performance issues because the table contains enormous data?


    Thank you

    You must create the view as

      CREATE OR REPLACE VIEW 
  AS
     SELECT col1, col2, col3.....
     FROM    
     WHERE   
     ...etc...

    The Act of creating the view will not otherwise the data in the table underlying, all it will do is create a view definition.
    Select only the view will select data.

    If you don't need to select the BLOB column in the view, then you would not include it in the list of the columns in the view definition.
    If your LOB data are stored online, then it may be a significant selection of the view, even if the BLOB column is not indicated in the list of the columns in the view.

    Published by: dombrooks on June 1, 2009 10:12

  • How to speed up sqlldr import of a materialized view's base table

    Hi all

    We have a large base on a warehouse system table.

    We charge this table periodically by using SQL * Loader.

    The charges are generally 30 minutes and its supported. Recently, we have created a materialized view using this table as a table base (and his newspaper correspondents materialized view) mode to REFRESH FAST .

    Now we see that expenses will take much longer muuuch.

    We created the view as the ISC documentation, using COUNT (*) columns and refresh mode seems to work. BUT, why is it so slow? Is it possible to speed it up?

    Thank you in advance.


    Mariano
    Spain

    Hello

    You have all the nonunique indexes or indexes on base tables bitmap? If Yes, you can consider disabling or setting their USUSABLE, and rebuild them after charge, you can also consider using PARALLEL INDICATOR your query mview to speed up, but you need to test this on your system with suitable parallel degrees (No. = 2 CPU, parallel = 2).

    The amount of data you load?
    Is the partitioned table, if so, then what system is used?
    Have you considered materialized view partitioning and using PCT (track changes of partition) to refresh loaded recently loaded partition? the amount of data you have in this table?

    Concerning

Maybe you are looking for