I'd like to preserve all materialized views.

Similar Questions

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

• Materialized view DDL

  I try to get the DDL for all materialized views in the database.
  I am using under sql, but somehow, it does not understand it and gives me errors as follows:
  
  SELECT DBMS_METADATA. GET_DDL ('MATERIALIZED VIEW', 'MV_NAME'), FROM DBA_OBJECTS;
  or
  SELECT dbms_metadata.get_ddl (OBJECT_TYPE, OBJECT_NAME, OWNER) IN DBA_OBJECTS
  WHERE
  OBJECT_TYPE AS "MATERIALIZED VIEW.
  
  Gives me error like below:
  ERROR:
  ORA-31600: entry invalid value MATERIALIZED VIEW for the OBJECT_TYPE parameter in GET_DDL function
  ORA-06512: at "SYS." Dbms_metadata", line 2682
  ORA-06512: at "SYS." Dbms_metadata", line 2733
  ORA-06512: at "SYS." Dbms_metadata", line 4333
  ORA-06512: at line 1
  
  Is there anyway I can get DDL for all the materialized view... ?
  Anyhelp is appreciated.
  JP

  Hi, the valid object types do not have spaces, according to [this table | http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10577/d_metada.htm#BGBIEDIA].

  Try this:

  SELECT owner, object_name, object_type, dbms_metadata.get_ddl(replace(OBJECT_TYPE, ' ', '_'), OBJECT_NAME,OWNER)
    FROM DBA_OBJECTS
   WHERE OBJECT_TYPE = 'MATERIALIZED VIEW'
  

  I didn't really take a broad look to check on each type of object, but this should work for at least materialized views. If this does work for other specific types you want, you may need to use decode or an expression box.

• Help understand materialized views

  I inherited a few db instances that were extensively using materialized views. To be honest, I've never had to configure or use materialized views, and I wonder if my logic on them is correct.
  
  Host instance
  The Materialized View logs live here
  
  Instance of the target
  Materialized views are living here.
  When you want your updated data you run here but all of the activity is on the Pb of the host.
  
  My real question here is I is more necessary than materialized views and I just want to take them off. I recloné the target instance, so all materialized views have been blown away. Should I just delete the materialized view logs to completely remove it from my environment? Or is their something more needs to be done.
  
  Thank you

  >
  My real question here is I is more necessary than materialized views and I just want to take them off. I recloné the target instance, so all materialized views have been blown away. Should I just delete the materialized view logs to completely remove it from my environment? Or is their something more needs to be done.
  >
  That's all you need to do. If you used the REFRESH GROUPS, you can remove those and if you have any DBMS_JOBs that were used to update the MVs you won't need those most.

  Naturally all code referenced directly newspapers MV or the MVs themselves will have to be amended to remove the references.

• How to refresh materialized views

  I'm following the steps to migrate a 12.0.6 financials database to OATM (model Tablespace Oracle Applications). One of the steps say to "perform a refresh all materialized views complete." This step is not part of the Oracle OATM utility. I wasn't able to find much on Metalink on this one. How to achieve this? Thank you... Colin

  Colin,

  See Note: 391483.1 - how to refresh materialized views after migration to the model OATM
  https://metalink2.Oracle.com/MetaLink/PLSQL/ml2_documents.showDocument?p_database_id=not&P_ID=391483.1

• Constraints foreign key in materialized views can be changed (approx 1-master)

  I have a system which consists of a master database and a bunch of materialized view sites homogeneous. 10.2.0.4 all around. Main server is Windows Server 2003. all remote nodes are Windows XP. All materialized views are editable. There are only 20 or two tables (materialized views). Users enter data in the system at the level of the remote nodes via an application.
  
  There are data integrity constraints in the database on the main site. In the hunt for replication errors, I discovered that the integrity constraints do not exist in the context of the remote node. Then, sometimes, that users can enter data not valid that main site integrity constraints disallow, producing errors of replication on the master site. For a test I then implemented manually some of the constraints on a remote node using the java Enterprise Manager UI. Constraints have behaved as expected, as far as I can tell.
  
  My ultimate goal is to implement, on all sites of the materialized view, the current constraints of the integrity of the main site, so that entering data at remote sites is governed by the integrity constraints.
  
  I looked briefly package DBMS_REPCAT subprograms. Nothing jumped out at me.
  
  I started to collect the DDL (ALTER TABLE... ADD CONSTRAINT...) I could run each site through SQL * more sheet calculation.
  
  Then I thought that maybe I could use sqldeveloper to run the DDL but when I open the relevant schema to the level of the remote nodes, the actual tables are not shown, only the USLOG$ _... things. Materialized views are shown - but they do not have a constraints tab.
  
  After some time in the manuals, I decided that I have a good knowledge of what I see; and that's why I'm not sure I'm running in the right direction.
  
  I will summarize two questions:
  
  (1) what is the best way for me to apply constraints of integrity of the master site existing in materialized views can be changed on all nodes?
  
  (2) why I can see and work on the tables on the remote nodes via the EM java, but don't can't see them via sqldeveloper, logged in with the same account twice?
  
  P.S. It is possible for me to delete and re-create all databases and the views materialized on all remote nodes. It is not a high volume system, and there are windows of time during which I can do these things if necessary. I don't expect a structural change to the database, so I don't need to be able to spread future changes, just make things sync'd up now.
  
  Published by: Clark October 10, 2008 11:38

  Hi Clark,.
  you are right THAT FK on mviews can cause many problems during refresh. I mentioned on delete cascade, but delete the null value or remove restricted can cause problem too. You cannot complete with active reftesh FK referencing MV PK.

  Because you cannot control the mviews refresh a refresh Group, that the problems I described before can occur.
  You have to my view of these possibilities:
  1 / move Ref. integrity check from the DB to the logic of the application
  2 / use triggers to maintain ref.integrity check DB
  3 / mutlimaster user instead of mviews replication

  But none of them have their more and less.
  1 / + FK is checked - take some time, any other manipulation of data through the application can break rules FK
  2 / + FK is cheked on DB level - you write triggers, lower performance, changing disorders tables
  3 / + FK is chedked at the DB level, - all the data is replicated on the table plan (for MV, you can define where cluase for replication mutlimaster not), with more than two masters, it is difficult to define the replication conflict resolition method that convert in the last time.

  Last post:
  I my case I use this "thing":
  Because our request has not been managed in environment 24 x 7 I wrote my own routine to refresh.
  This routine that follows:
  1 / disable necessary FK
  2 / call dbms_refresh.refresh to perform the refresh of the refresh Group
  3 / activate FK disabled in step 1 with the novalidate
  Refresh the jobs was launched at night.

• Hi, I'm developing a simple mobile app in DW CC 2015 using JQuery Mobile. LIKE I need the list view with description of the product, functionality and image, I would like to connect with database instead of "writing" all the tables in the bearings inside

  Hi, I'm developing a simple mobile app in DW CC 2015 using JQuery Mobile. LIKE I need the list view with description of the product, functionality and image, I would like to connect with database instead of "writing" all the tables in the bearings inside the Jquery page. In the future I would also be able to add, to remove the DB records. Any help, tutorial... Thanks TG

  I would like to connect with the database instead of "writing" all the tables in the bearings inside the Jquery page

  This is usually done with a CMS (content management system). There are commercial products CMS like WordPress, Joomla and perch. You create one or several layouts and then create pages of these page layouts using the CMS. In this way, it is possible to have hundreds of pages, each with unique content, but a page layout that can be managed in a place of sharing.

  CMSs on shelf don't require programming skills. Otherwise, some of us write our own CMS with custom functions, but this requires back-end, as with PHP programming.

• By creating the Materialized view all size changes to columns

  I'm creatine a materialized view based on the table in a different database.
  The table on which the created materialized view (database table) is to have the size of CHAR (1 byte) column. But in Materialized view this size columns showing as CHAR (3 bytes).
  
  Could u please help me.., why this is happening?
  
  Thank you
  Sachin

  Sachin thombare wrote:
  I'm creatine a materialized view based on the table in a different database.
  The table on which the created materialized view (database table) is to have the size of CHAR (1 byte) column. But in Materialized view this size columns showing as CHAR (3 bytes).

  Could u please help me.., why this is happening?

  Thank you
  Sachin

  Hello
  Do both the database involved in this have defined different character.
  If Yes, then this is a known behavior.

  Concerning
  Anurag Tibrewal.

• ORA-12028: type of materialized view is not supported by the main site

  Hi guys!

  We face a problem these days about the materialized view.

  We have upgraded database version 9.2.0.7 directly to 10.2.0.5 (RHEL4 x 86) on the same host. Database uses the driver dg4odbc to connect with remote SQL Server 2012 through data binding called MIKSERI. Our developer team would like to have replicated SQL server table data side Oracle using the materialized view.

  They created Materialized view, but it is not at all to refresh the data. I tried to study a little bit, and whenever I try to change the view anyway I hit error:

  ORA-12028: view type is not supported by the master site materialized @ 'MIKSERI '.

  ORA-06512: at line 22

  I looked at the solutions proposed and discovered that it is maybe the compatible database parameter, so I changed from previous 9.2.0.0.0 to 10.2.0.1.0 but still no luck. Just to emphasize this database is of course different clone of production to a different database, with db name retained and other parameters, but on another host computer and listening port. I even try to change global name, but still no luck.

  Main problem is that refresh the work does not at all. To be more precise, we have created MV on the side of the Oracle and FULL Refresh should be done every 3 minutes. MV uses HS db link to the sql server database. During the creation of MV, we can see currently given to sql server, but the problem is that we cannot do MV to refresh every 3 minutes. When I try to change MV and put the refresh interval I get above error.

  Any kind of help would be greatly appreciated,

  Thank you

  I found the reason why my MV update jobs failed, job_queue_processes parameter was equal to 0. I change this setting and now works fine.

  Thank you for your time!

• I get "failed to set the refresh attribute COMMIT for the materialized view" when I try to create a MV using a table and another MV

  Experts,

  I'm trying to create a YOUNG refreshable ON COMMIT MV (xyz) using a table (circuit) and quickly updateable on validation MV (abc), but get an error:

  SQL error: ORA-12054: cannot set the attribute ON COMMIT refresh for the materialized view

  12054 00000 - "cannot set the refresh attribute COMMIT for the materialized view.

  * Cause: The materialized view did not meet the requirements for update to

  moment of validation.

  * Action: Specify only valid options.

  1] MV abc
  = MV abc defined as below =.

  CREATE MATERIALIZED view abc_MV

  Immediate CONSTRUCTION

  REFRESH QUICKLY YOU COMMIT using constraints of trust

  WITH ROWID AS SELECT n.*,.

  n.ROWID noderowid

  node n

  where n.nodetype in (1610000069,1610007267);

  
  

  -Above works OK and MV connect you on table node is created successfully

  =====================================================

  [ 2] Circuit Board

  ======================================================

  CREATE MATERIALIZED VIEW LOG ON Cramer.Circuit WITH SEQUENCE, ROWID ( ) -all columns of table ofcircut parentheses

  INCLUDING THE NEW VALUES;

  -More top works OK and MV connect you on table circuit is created successfully

  ======================================================
  

  
  

  
  

  [3] trying to create MV xyz
  

  ======================================================

  CREATE MATERIALIZED VIEW LOG ON cramer.abc_MV WITH SEQUENCE, ROWID ( ) -all columns of abc_MV brackets

  INCLUDING THE NEW VALUES;

  -Above works OK and log on ABC MV MV gets created successfully

  -Problematic step below

  Xyz_MV CREATE MATERIALIZED VIEW

  IMMEDIATE CONSTRUCTION

  REFRESH QUICKLY YOU COMMIT using constraints of trust

  AS

  SELECT c., c.rowid circuit_rowid, n.rowid tr_rowid

  the circuit c, abc_mv n

  where circuit2startnode = n.nodeid

  and c.rpplanId = n.rpplanId;
  ==========================================================

  Clues on how to solve this problem and make quickly updatable ON Commit MV xyz

  Thanks in advance.

  Chanchal,

  If you can read my original post carefully you may have noticed that all these restrictions will not apply in my case.

  All,

  In any case I found the solution to my problem.

  There are a few additional restrictions for materialized views multilayer

  Additional Restrictions for master materialized views

  The following types of materialized views may not be masters of editable materialized views:

  • ROWIDmaterialized views
  • Complex materialized views
  • Read-only materialized views

  I've updated the underlying MV abc below and everything worked like a charm

  CREATE MATERIALIZED view abc_MV

  Immediate CONSTRUCTION

  REFRESH QUICKLY YOU COMMIT using constraints of trust

  IN SELECT

  n.*, n.rowid noderowid, nt.rowid nodetyperowid

  the node n, nodetype_m nt

  where n.node2nodetype = nt.nodetypeid

  and nt.nodetypeid in (1610000069,1610007267);

  Note: To ADD a join without which I was getting error below (although had primary key on the table of the node)

  SQL error: ORA-23415: materialized view log for "NODE" does not save the primary key

  23415 00000 - "view the log for materialized \"%s\".\"%s\"does not save the primary key.

  * Cause: A primary key materialized view is refreshed quickly, but the

  The materialized view log does not record the primary key information.

  * Action: Use CREATING MATERIALIZED VIEW LOG... Command to add a PRIMARY KEY to

  start recording of the primary key information in the materialized view

  Newspaper.

• Re: view opaque and the materialized view

  Hi Experts,

  I want some clarification of opaque and view view in the physical layer OBIEE materialized

  -> what is the main difference between the opaque view and materialized in the RPD perspective view, we have to do this at the level of the RPD or DB.

  -> I want the list of opaque opinion and materialized in the RPD view how I should do.

  -> How opaque views will degrade the performance and how a materialized view will improve performance at the level of the report.

  -> In scenarios that we use view opaque and the view materialized (if possible with a scenario for the best permanent basis).

  Thanks in advance.

  I want some clarification of opaque and view view in the physical layer OBIEE materialized

  -> What is the main difference between opaque view and create the materialized view in the RPD point of view, we have to do this at the level of the RPD or DB.

  Opaque views is a SQL statement that is defined in the physical layer, OBIEE will use all in the construction of a SQL query. In a way it's not different from a database view, except it is set in OBIEE only. Alternatively, you can deploy an Opaque view, which pushes its definition in the database. Read more about it here: work with physical tables, Cubes and joins - 11 g Release 1 (11.1.1)

  A materialized view (MV) is a database concept where the results of a SQL statement are physicalised like a table, and therefore as OBIEE is a MV is just another physical array

  -> If I want a list of the opaque views and materialized in the RPD view how I should do.

  To find opaque views, use the function «Repository of applications» administration tool Search physical Tables and set up a filter on the Type = Select

  Screenshot: https://www.evernote.com/shard/s16/sh/5c843e47-bff1-4d4b-b847-be98f3a2ec09/cf060a6cd9805f687fa0b5b46f3f0020

  To find materialized views, you will need to query the catalog in your database (for example select object_name, object_type from user_objects where type_objet = "MATERIALIZED VIEW" ;) and compare it to the list of tables in your SPR)

  -> How opaque views will degrade the performance and how a materialized view will improve performance at the level of the report.

  A materialized view is materialized, in other words, the results are already stored in the database. This means usually there will be more efficient because all the joins and aggregations, etc. will be settled in advance.

• The Materialized View - ORA-12052: is unable to fast refresh materialized view

  Hello

  I was hitting my head all day trying to create materialized views. I have made some progress, but have hit a brick wall, unfortunately!

  Basically, I have been invited to take a view and see if I can get the benefits of performance by transforming all or part of it in materialized views. Because the underlying tables of the config is updated quite frequently, I want to fast refresh materialized views on commit. However, when I try to create a materialized view containing an outer join in an aggregated materialized view table, I get ORA-12052: is unable to fast refresh materialized view.

  I went through the documentation and also Rob van Wijkvery useful series of blogs on the topic (especially http://rwijk.blogspot.co.uk/2009/09/fast-refreshable-materialized-view.html) but have not found anything that matches. Maybe I missed something somewhere along the line, or maybe I'm asking just something completely impossible?

  My db is 11.2.0.2.

  Here's the test scripts, I've worked with that:

  drop materialized view test1_test2_mv;
  Drop materialized view test2 journal;
  drop table test2;
  Drop materialized view test1_mv newspaper;
  drop materialized view test1_mv;
  Drop materialized view test1 journal;
  drop table test1;

  create table test1 (identification number,
  type varchar2 (10),
  number of Val,
  update_time date,
  constraint t1_pk primary key (id, type, val));
  
  Insert into test1
  Select 1, 'a', 1001, sysdate - 10/24 Union double all the
  Select 1, 'b', 1003, sysdate - 9/24 Union double all the
  Select 1, 'c', 1002, sysdate - 8/24 Union double all the
  Select 1, had ', 1004, sysdate - 7/24 Union double all the
  Select 1, 'e', 1005, sysdate - 6/24 Union double all the
  Select 1, 'c', 1006, sysdate - 5/24 Union double all the
  Select 2, 'a', 1002, sysdate - 4/24 Union double all the
  Select 2, 'b', 1005, sysdate - 3/24 Union double all the
  Select 3, 'a', 1001, sysdate - 2/24 Union double all the
  Select 3, 'c', 1006, sysdate - 1/24 Union double all the
  Select 3, 'e', 1008, sysdate - 2/24 Union double all the
  Select option 4, has ', 1004, sysdate - 3/24 Union double all the
  Select 5, 'b', 1002, sysdate - 4/24 Union double all the
  Select 5, 'g', 1001, sysdate - 5/24 Union double all the
  Select 6, 'h', 1004, sysdate - 6/24 Union double all the
  Select 7, 'b', 1007, sysdate - 7/24 Union double all the
  Select 7, had ', 1001, sysdate - 8/24 double;

  commit;

  Select * from test1;

  
  CREATE MATERIALIZED VIEW LOG ON test1
  WITH rowid, primary key (update_time)
  including the new values;

  
  Test1_mv CREATE MATERIALIZED VIEW
  IMMEDIATE CONSTRUCTION
  COOL OFF QUICKLY ON COMMIT
  Did YOU SELECT id,
  MAX (case when type = "there" end of val) THAT col_a,.
  MAX (case when type = 'b', then val end) AS col_b,.
  MAX (case when type = 'c' then end val) AS col_c,.
  MAX (case when type = ' then end of val) AS col_d,
  MAX (update_time) AS update_time
  OF test1
  WHERE TYPE in ('a',
  « b »,
  « c »,
  a ')
  GROUP BY id;

  CREATE MATERIALIZED VIEW LOG ON test1_mv
  WITH rowid
  including the new values;

  
  create table test2 (identification number,
  col2 number,
  COL3 varchar2 (10),
  number of COL4,
  constraint t2_pk primary key (id));
  
  Insert into test2
  Select 1, 1, 'bob', 1 double Union all
  Select 2, 1, "sue", 1 double Union all
  Select 3, 1, 'tom', 1 double Union all
  Select 4, 1, 'jay', 1 double Union all
  Select 5, 1, 'art', 1 double Union all
  Select 6, 1, 'kay', 1 double Union all
  Select 7, 1, 'max', 1 double Union all
  Select 8, 1, 'tim', 1 double Union all
  Select 9, 1, "liz", 1 from dual;

  commit;

  
  CREATE MATERIALIZED VIEW LOG ON test2
  WITH rowid, primary key
  including the new values;

  
  Test1_test2_mv CREATE MATERIALIZED VIEW
  IMMEDIATE CONSTRUCTION
  COOL OFF QUICKLY ON COMMIT
  LIKE SOME t2.rowid,.
  T1.ID,
  T1.col_a,
  T1.col_b,
  T1.col_c,
  T1.col_d,
  T1.update_time,
  T2.col2,
  T2. COL3
  OF test1_mv t1,.
  Test2 t2
  WHERE (+) t1.id = t2.id; -symbol of outer join is not correctly displayed on the forums without space, grr!

  ORA-12052: is unable to fast refresh materialized view TEST1_TEST2_MV

  Y at - it any way I can get the materialized view fast refresh on commit or I asking the impossible?

  Add t1.rowid:

  SQL > CREATE MATERIALIZED VIEW test1_test2_mv

  2 BUILD IMMEDIATE

  3 QUICK REFRESH YOU COMMIT

  4 AS t2.rowid SELECT rid2,

  5 t1.rowid rid1,

  6 t1.id

  T1.col_a 7,.

  T1.col_b 8,.

  T1.col_c 9,.

  T1.col_d 10,

  T1.update_time 11,

  T2.col2 12,

  13 t2.col3

  14 OF test1_mv t1,

  15 test2 T2

  16 WHERE t1.id = t2.id

  17.

  Materialized view created.

  SQL > select * from test1_test2_mv

  2.

  RID2 RID1 ID COL_A, COL_B, COL_C COL_D UPDATE_TIME COL2 COL3

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

  AAAYB6AANAAAANDAAA AAAYB/AANAAAAN/AAA 1 1001 1003 1006 1004 25 / 06 / 2014 12:54:16 1 bob

  AAAYB6AANAAAANDAAB AAAYB/AANAAAAN/AAB 2 1002 1005 25 / 06 / 2014 1 sue 14:54:16

  AAAYB6AANAAAANDAAC AAAYB/AANAAAAN/AAC 3 1001 1006 25 / 06 / 2014 16:54:16 1 tom

  AAAYB/AANAAAAN/AAD AAAYB6AANAAAANDAAD 4 1004 25/06/2014 14:54:16 1 jay

  AAAYB6AANAAAANDAAE AAAYB / AANAAAAN / AAE 5 1002 2014/06/25 13:54:16 1 art

  AAAYB6AANAAAANDAAF AAAYB/AANAAAAN/AAG 7 1007 1009 25 / 06 / 2014 10:54:16 max 1

  AAAYB/AANAAAAN/AAH                                                                                                        1 tim

  AAAYB/AANAAAAN/AAF                                                                                                        1 kay

  AAAYB/AANAAAAN/AAI                                                                                                        1 liz

  9 selected lines.

  SQL > update of test2

  2 set col3 = "fly."

  3 where id = 7

  6 m

  1 line update.

  SQL > validation

  2.

  Validation complete.

  SQL > select * from test1_test2_mv

  2.

  RID2 RID1 ID COL_A, COL_B, COL_C COL_D UPDATE_TIME COL2 COL3

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

  AAAYB6AANAAAANDAAA AAAYB/AANAAAAN/AAA 1 1001 1003 1006 1004 25 / 06 / 2014 12:54:16 1 bob

  AAAYB6AANAAAANDAAB AAAYB/AANAAAAN/AAB 2 1002 1005 25 / 06 / 2014 1 sue 14:54:16

  AAAYB6AANAAAANDAAC AAAYB/AANAAAAN/AAC 3 1001 1006 25 / 06 / 2014 16:54:16 1 tom

  AAAYB/AANAAAAN/AAD AAAYB6AANAAAANDAAD 4 1004 25/06/2014 14:54:16 1 jay

  AAAYB6AANAAAANDAAE AAAYB / AANAAAAN / AAE 5 1002 2014/06/25 13:54:16 1 art

  AAAYB/AANAAAAN/AAH                                                                                                        1 tim

  AAAYB/AANAAAAN/AAF                                                                                                        1 kay

  AAAYB/AANAAAAN/AAI                                                                                                        1 liz

  AAAYB6AANAAAANDAAF AAAYB/AANAAAAN/AAG 7 1007 1009 25 / 06 / 2014 10:54:16 1 rob

  9 selected lines.

• Materialized view, based on the stored procedure

  Hi all

  is it possible to create a materialized view on the results returned by a stored procedure?

  If this is not the case, do you think that any other way except for filling a table with data from the stored procedure and then founded the MV on it?

  Thanks in advance.

  MichaelTsilikidis wrote:

  Sorry I don't speak properly. In fact the procedure does not return a value, it fills one of its parameters (of the ref cursor type) of data. That's what I wanted.

  No it's not.

  REF CURSOR don't store data, so it's not possible.

  A Ref cursor is just a pointer to a query... and you can't "select from" a ref cursor, you can retrieve only one open.

  PL/SQL 101: Understand the Ref Cursor

  As correctly stated above, you can't question from a procedure to a function, and a materialized view is based on a query, you cannot use a procedure in a materialized view.

  You could use a function pipeline instead of a procedure, or have the pipeline function obtain the results of the procedure and pipelines, and then the materialized view could be based on the results of this function in the pipeline.

  example of function pipeline:

  SQL > CREATE or REPLACE TYPE AS OBJECT num_descript (num number, descript varchar2 (30))
  2.

  Type of creation.

  SQL >
  SQL > CREATE or REPLACE TYPE tbl_num_descript AS TABLE OF THE num_descript
  2.

  Type of creation.

  SQL >
  SQL >
  SQL > CREATE or REPLACE PACKAGE AS-reftest
  2 FUNCTION pipedata (number p_choice) tbl_num_descript RETURN PIPELINED;
  3 END;
  4.

  Package created.

  SQL >
  SQL > CREATE or REPLACE PACKAGE BODY AS-reftest
  2 FUNCTION pipedata (number p_choice) tbl_num_descript RETURN PIPELINED IS
  3 v_obj num_descript: = num_descript (NULL, NULL);
  4 v_rc sys_refcursor;
  5 BEGIN
  6. IF p_choice = 1 THEN
  7 v_rc OPEN to SELECT empno as num, ename like descript FROM emp;
  8 ELSIF p_choice = 2 THEN
  9 OPEN v_rc to SELECT deptno as num, dname as descript OF THE Department;
  10 END IF;
  11 LOOP
  12 FETCH v_rc INTO v_obj.num, v_obj.descript;
  EXIT 13 WHEN v_rc % NOTFOUND;
  14 PIPE ROW (v_obj);
  15 END LOOP;
  16 v_rc NARROW;
  RETURN 17;
  18 END;
  END 19;
  20.

  Package body created.

  SQL > select * from table (reftest.pipedata (1));

  DESCRIPT NUM
  ---------- ------------------------------
  7369 SMITH
  7499 ALLEN
  7521 WARD
  7566 JONES
  7654 MARTIN
  7698 BLAKE
  7782 CLARK
  7788 SCOTT
  KING 7839
  7844 TURNER
  7876 ADAMS
  JAMES 7900
  7902 FORD
  7934 MILLER

  14 selected lines.

  SQL > select * from table (reftest.pipedata (2));

  DESCRIPT NUM
  ---------- ------------------------------
  10 ACCOUNTING
  SEARCH 20
  30 SALES
  40 OPERATIONS

• How to get a materialized view can freshen up after the job is 'broken '.

  We have created a materialized view some time ago with the following statement:

  create a materialized view SXV_PUB_EMPLOYEE_CERT_ALL_M

  full refresh on demand

  Start with to_date (August 30, 2009 04:00 ',' dd-mm-yyyy hh24:mi:ss') next trunc (sysdate) + (28/24)

  as

  Select sxv_emp_cert_all.*

  of sxv_employee_certification_all sxv_emp_cert_all;

  This week, we found that it had not been updated for about a month

  In dba_jobs the broken column was 'Y', next_date time something like 01-01-4000 and failures 16

  When I ran it manually by running

  DBMS_MVIEW BEGIN. REFRESH ("SXV_PUB_EMPLOYEE_CERT_ALL_M", "C"); END;

  I found that one of the columns was too small (probably one of the underlying tables columns had been extended since the creation of the materialized view)

  After the correction of what I ussied yesterday (29/08/2013) education:

  change the SXV_PUB_EMPLOYEE_CERT_ALL_M materialized view

  full refresh on demand

  Start with to_date (August 30, 2009 04:00 ',' dd-mm-yyyy hh24:mi:ss') next trunc (sysdate) + (28/24)

  After that the table dba_jobs showed me the 04:00 08/30/2013 as the date of the next

  I expected to run that night at 04:00, but there is no

  last_date column value was still of a month ago, the broken column still shows 'Y '.

  and the next date 08/30/2013 04:00 (whereas it would have been set to the 01:00 08/31/2013

  Freezes

  DBMS_MVIEW BEGIN. REFRESH ("SXV_PUB_EMPLOYEE_CERT_ALL_M", "C"); END;

  has given no mistake this time

  and in User_Mview_Analysis, the last_refresh_date column showed the time that I had run

  No idea how to do the job "unbroken" again for the view refreshes every night?

  the database is Oracle Database 10g Release 10.2.0.4.0

  Kind regards

  Remco

  Thanks for all your useful and accurate answers. but finally I found it myself

  exec dbms_job.broken (, false);

• Change the definition of the materialized view while maintaining access for users uninteruupted

  Hello

  We have a system report and the need to change the report definition mv access - like to do it without interruption.

  Is this possible?

  the sql behind mv was change picks up so column of another table.

  Have you heard but not used for dbms_redefinition tables

  Thank you

  It is built in the Oracle solution for this one, where you can edit the definition WITHOUT interruption. You can drop the materialized view existing with the clause "save table" and rebuilt the view materialized on 'predefined table'. I googled this example for you

  create materialized view mv1 as select dept , count(*) as cnt from scott.emp;

  We want to change the statement so that only dept more 5 will be calculated

  drop materialized view mv1 preserve table;
  

  Notice that PRESERVE TABLE clause - mv1 table is not droped - single layer mview.

  desc mv1
  

  now, we create the mview with a different query on top of the existing table

  create materialized view mv1 on prebuilt table as  select dept , count(*) as cnt from scott.emp where dept > 5;
  

  Notice that on prebuilt table the mview uses the existing object clause.

  exec dbms_mview.refresh_mview('mv1');
  

  http://StackOverflow.com/questions/18085894/redefine-MATERIALIZED-view-with-no-downtime

  http://Arup.blogspot.com/2009/01/ultra-fast-MV-alteration-using-prebuilt.html