Create materialized view at the trigger.

Similar Questions

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

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

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

• '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}                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            
  

• Moving all the newspapers and Materialized View at the schema level using the data pump in

  Hi Experts,
  
  Please help me on how I can exp/imp all materialized views andMV logs (as are some MVs) only the full scheme of other databases. I want to exclude everything else.
  
  Concerning
  -Samar-

  Using DBMS_METADATA. Create the following SQL script:

  SET FEEDBACK OFF
  SET SERVEROUTPUT ON FORMAT WORD_WRAPPED
  SET TERMOUT OFF
  SPOOL C:\TEMP\MVIEW.SQL
  DECLARE
      CURSOR V_MLOG_CUR
        IS
          SELECT  DBMS_METADATA.GET_DDL('MATERIALIZED_VIEW_LOG',LOG_TABLE) DDL
            FROM  USER_MVIEW_LOGS;
      CURSOR V_MVIEW_CUR
        IS
          SELECT  DBMS_METADATA.GET_DDL('MATERIALIZED_VIEW',MVIEW_NAME) DDL
            FROM  USER_MVIEWS;
  BEGIN
      DBMS_METADATA.SET_TRANSFORM_PARAM(DBMS_METADATA.SESSION_TRANSFORM,'SQLTERMINATOR',TRUE);
      FOR V_REC IN V_MLOG_CUR LOOP
        DBMS_OUTPUT.PUT_LINE(V_REC.DDL);
      END LOOP;
      FOR V_REC IN V_MVIEW_CUR LOOP
        DBMS_OUTPUT.PUT_LINE(V_REC.DDL);
      END LOOP;
  END;
  /
  SPOOL OFF
  

  In my case the script is saved as C:\TEMP\MVIEW_GEN. SQL. Now I will create a journal mview and mview in schema SCOTT and run the script above:

  SQL> CREATE MATERIALIZED VIEW LOG ON EMP
    2  /
  
  Materialized view log created.
  
  SQL> CREATE MATERIALIZED VIEW EMP_MV
    2  AS SELECT * FROM EMP
    3  /
  
  Materialized view created.
  
  SQL> @C:\TEMP\MVIEW_GEN
  SQL> 
  

  Run the C:\TEMP\MVIEW_GEN script. SQL generated a C:\TEMP\MVIEW queue. SQL:

    CREATE MATERIALIZED VIEW LOG ON "SCOTT"."EMP"
   PCTFREE 10 PCTUSED 30 INITRANS
  1 MAXTRANS 255 LOGGING
    STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1
  MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL
  DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
    TABLESPACE "USERS" 
  
  WITH PRIMARY KEY EXCLUDING NEW VALUES;
  
    CREATE MATERIALIZED VIEW "SCOTT"."EMP_MV" ("EMPNO", "ENAME", "JOB", "MGR",
  "HIREDATE", "SAL", "COMM", "DEPTNO")
    ORGANIZATION HEAP PCTFREE 10 PCTUSED 40
  INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
    STORAGE(INITIAL 65536 NEXT 1048576
  MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
  BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
    TABLESPACE
  "USERS"
    BUILD IMMEDIATE
    USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 
  
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
  
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE
  DEFAULT CELL_FLASH_CACHE DEFAULT)
    TABLESPACE "USERS"
    REFRESH FORCE ON
  DEMAND
    WITH PRIMARY KEY USING DEFAULT LOCAL ROLLBACK SEGMENT
    USING ENFORCED
  CONSTRAINTS DISABLE QUERY REWRITE
    AS SELECT "EMP"."EMPNO"
  "EMPNO","EMP"."ENAME" "ENAME","EMP"."JOB" "JOB","EMP"."MGR"
  "MGR","EMP"."HIREDATE" "HIREDATE","EMP"."SAL" "SAL","EMP"."COMM"
  "COMM","EMP"."DEPTNO" "DEPTNO" FROM "EMP" "EMP";
                                 
  

  Now, you can run this on the database. You may need to adjust the tablespace and storage clauses. Or you can add more DBMS_METADATA. SET_TRANSFORM_PARAM calls to C:\TEMP\MVIEW_GEN. SQL to force DBMS_METADATA not to include the tablespace or / and the terms of storage.

  SY.

• 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 materialized view

  Hello
  I found that when oracle executes the create materialized view statement it must be longer than the duration of execution of the actual query.
  I do an IMMEDIATE CONSTRUCTION.
  Is there a reason for this?
  
  For example. the query in the create statement took 25 minutes and did not create the MV for 2 hours.
  The following query, which took 10 seconds was not created during more than 11 minutes and is still ongoing.
  So I want to know what the reason is behind this? pls share if you know... Thank you.
  
  PS:
  I have advice in the select query. Oracle uses it advice during the creation of MV too or is this the reason why it's taking the time to build the MV?
  
  any suggestion is appreciated. thnks!
  
  Published by: user254668 on January 11, 2011 08:08

  How do measure you queries?

  http://jonathanlewis.WordPress.com/2010/08/29/fair-comparison/

  Re: Question Performace and Order by
  Re: receiving ORA-01722 invalid number mistake while creating a materialized view
  Re: long term with ORDER by clause
  Re: Improve the performance of the query with the order of

• 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 a view with the double data type

  I have Windows XP with 10g 10.2.0.1.0
  
  I need to create a view of the double and with the type of data, such as NUMBER (5.2), NUMBER or VARCHAR2 (20).
  such as:
  create see test (view_test varchar2 (20)) as (select view_test from double)
  
  
  Help, please. Thanks in advance.

  It seems a little strange, but you can do something like this with the CAST function:

  SQL> create view dual_view as
    2  select cast(null as number(5,2)) col1
    3        ,cast(null as date)    col2
    4        ,cast(null as varchar2(30)) col3
    5  from   dual;
  
  View created.
  
  SQL> desc dual_view
   Name                                      Null?    Type
   ----------------------------------------- -------- -------------------------
   COL1                                               NUMBER(5,2)
   COL2                                               DATE
   COL3                                               VARCHAR2(30)
  

  I used the NULL values, but you can use the actual values if you wish.

• materialized view of the site / site of master

  Hello
  
  Currently I have an updatable materialized view and a main site.
  
  Whatever the changes bring to emp table of the main site that will be included in the emp materialized view in the view of the site.
  
  Whatever the changes bring to materialized view emp is also included in table emp from the main site.
  
  
  Right now, in my materialized view site, I have two jobs:
  defer_sys.push and dbms_refresh
  
  I would like to know the differences between the 2 posts...
  
  
  Can someone advise? Do I really need both jobs or only one of them will do?
  
  Range of jobs is important?
  
  Thank you

  Yes, you're right.

  You use DBMS_REFRESH, which is normally used to refresh the groups. However, a Updatabe Materialized View must be in a group of refreshing (otherwise, it's only a writable MV).

  I find this paragraph in the documentation on the update process when using a group of refreshing:

  A refresh of an updatable materialized view first pushes the deferred transactions at the materialized view site to its master site or master materialized view site. Then, the data at the master site or master materialized view site is pulled down and applied to the materialized view.
  

  See http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/repmview.htm#i30557

  and http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/repmview.htm#i31171

• Insert the data in materialized views at the Table

  Hello

  We have a problem in which some incorrect data has been loaded for tables.

  Users now are pointing to the materialized views and data access using synonyms.

  Is it possible to insert data from a view, materialized at the tables?

  Kind regards

  VN

  Hello

  As sb92075 has said, we can insert in the table of the materialized view.

  Test below data:

  SQL > select * from t1;

  CITY OF AMOUNT ID COMMENTS

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

  1 XXX 28 Chicago

  2 AAA LAS 25

  3 YYY 25 NY

  4 35 Texas XXX

  5 XXX 55 Arlington

  6 56 Chicago YYY

  7 XXX 66 NY

  7 selected lines.

  SQL > create mv_t1 view materialized in select * from t1;

  Materialized view created.

  SQL > select * from mv_t1;

  CITY OF AMOUNT ID COMMENTS

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

  1 XXX 28 Chicago

  2 AAA LAS 25

  3 YYY 25 NY

  4 35 Texas XXX

  5 XXX 55 Arlington

  6 56 Chicago YYY

  7 XXX 66 NY

  7 selected lines.

  SQL > insert into t1 values(8,'BBB',22,'NY');

  1 line of creation.

  SQL > select * from mv_t1;

  CITY OF AMOUNT ID COMMENTS

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

  1 XXX 28 Chicago

  2 AAA LAS 25

  3 YYY 25 NY

  4 35 Texas XXX

  5 XXX 55 Arlington

  6 56 Chicago YYY

  7 XXX 66 NY

  7 selected lines.

  SQL > select * from t1;

  CITY OF AMOUNT ID COMMENTS

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

  1 XXX 28 Chicago

  2 AAA LAS 25

  3 YYY 25 NY

  4 35 Texas XXX

  5 XXX 55 Arlington

  6 56 Chicago YYY

  7 XXX 66 NY

  NEW YORK 8 22 BBB

  8 selected lines.

  SQL > commit;

  Validation complete.

  SQL > select * from mv_t1;

  CITY OF AMOUNT ID COMMENTS

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

  1 XXX 28 Chicago

  2 AAA LAS 25

  3 YYY 25 NY

  4 35 Texas XXX

  5 XXX 55 Arlington

  6 56 Chicago YYY

  7 XXX 66 NY

  7 selected lines.

  SQL > delete from t1;

  8 deleted rows.

  SQL > select * from mv_t1;

  CITY OF AMOUNT ID COMMENTS

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

  1 XXX 28 Chicago

  2 AAA LAS 25

  3 YYY 25 NY

  4 35 Texas XXX

  5 XXX 55 Arlington

  6 56 Chicago YYY

  7 XXX 66 NY

  7 selected lines.

  SQL > insert into t1 select * from mv_t1;

  7 lines were created.

  SQL > select * from t1;

  CITY OF AMOUNT ID COMMENTS

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

  1 XXX 28 Chicago

  2 AAA LAS 25

  3 YYY 25 NY

  4 35 Texas XXX

  5 XXX 55 Arlington

  6 56 Chicago YYY

  7 XXX 66 NY

  7 selected lines.

  SQL >