Materialized view Site DB Migration

Similar Questions

• 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

• help a single master more editable site materialized views

  Hello world
  
  I have a solution in which I have 5 sites.
  I decided to implement a single site of master with 4 updatable materialized view sites.
  The reason why I made this decision, it's I want that if my main site does not work, the materialized view sites don't update with other data.
  My question is in this situation if the main site became unavailable can be update view materialized sites update their own individually and after master site data become available, they send their data to that or not, they can query just to their own database until the main site are available?
  
  Thank you

  Hello

  Yes, what you think is correct. Mviews update can run locally even if the primary site is unavailable. She can push further data on the master site when the main site is available.

  The mviews update can be updated even if the primary site is unavailable. But the changes that happened on the site controller is not updated until it becomes available and an update is performed.

  Thank you
  Florent

• materialized view replication

  Hello
  
  We currently have this configuration in our environment:
  Db1 < Master site >
  DB2 < Mview site - Readonly >
  
  We use the replication at the table level. Basically, a NEWSPAPER MVIEW will be created each table in db1 and fast refresh of the table is programmed in the mview site 21:00 daily.
  
  Now, there is an additional requirement to set up a new site < DB3 > mview. DB1 or DB2 data must be replicated to DB3.
  
  Judge of our current environment, can we configure the mview new site based on the < Exisiting mview site > DB2? Or can only replicate in DB1 < master > DB3?
  
  Please advise.
  
  Thank you

  You can replicate the materialized view site (DB2) to another site (DB3). See the link below (for 9i, should be same on later versions) for more details.

  http://docs.Oracle.com/CD/B10501_01/server.920/a96567/repmview.htm

  Salman

• Prob of materialized view

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

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

  create  MATERIALIZED  view maview as select * from sunitha;

  I'm trying to insert into maview
  

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

  Please notify.
  
  
  Thank you
  Miriam.

  Here is an excerpt of the document.

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

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

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

• question on the materialized view unregistered on the main site

  Hello
  
  you know how one knows, on the main site, on the existence of a materialized view another site referring to other tables to a primary site. It seems registration is not required.
  
  the site main orcl1: I have a table, and a materialized view log defined on A table.
  another site orcl2: have a link db orcl1 and rapid updatable view SCOTT materialized. A_MVW (create a materialized view A_MVW cool off quickly in select * from A@orcl1)
  
  on orcl1 I perform: exec DBMS_MVIEW. UNREGISTER_MVIEW (mviewowner = > 'SCOTT', mviewname = > mviewsite, 'A_MVW' = > 'ORCL2');
  so the materialized view seems to be correctly set aside (because it no longer appears in: select * from DBA_REGISTERED_MVIEWS ;))
  But, to my surprise, I can still perform refreshes fast on A_MVW, which also remove rows from the materialized view log. So how is site orcl1 always aware of the existence of the materialized view?
  
  It seems that, registered or not to the main site, a materialized view has the same... or is not? where is it stored, on the main site, information about materialized views (especially those of quickly updatable) as local tables reffer?
  
  Thank you

  See DocIDs 258634.1, 67371.1, 1031924.6
  on Oracle's Support website.

  Hemant K Collette

• performance of Materialized view

  
  Hello Experts!

  I have obligation that migrate tables to materialized views.

  The current process of execution is truncate the table and updating of data that are placed on different the other schema or DB by monthly.

  (insert data into an insert like the example below)

  insert into emp (field 1, Field2,...) select field 1, field 2,... from table1, table2... joins defined.

  If I convert the tables to materialized views.

  Can I know what will be the impact of performance?

  These limited data, I can only comment on a few things from generial:

  1. with MV you don't have to worry about maintenance of the table.

  2 performance will be much better for aggregated data. The cost of Re-calculation will be reduced to a lot because it goes in the MV as a precomputed data.

  3 If you must bear the cost of the insert/update of MV, however, worry the manual activity as this will be done in real time.

• deletion of rows in materialized view

  Hi all
  
  I have a question!
  
  If the main table rows are deleted on which a materialized view exists at a remote site, then the corresponding rows from the materialized view will also be deleted when updating?
  
  Appreciate your help
  
  IM

  That is right.

• 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

• Query on materialized views

  Hello
  
  Could someone of you please confirm that we always demand a Materialized View Log on the tables at the Master site to REFRESH QUICKLY in work on the materialized view.
  
  If we do not have a log of materialized view, materialized view, always do a COMPLETE REFRESH.
  
  Thank you
  Chanjal

  http://download.Oracle.com/docs/CD/E11882_01/server.112/e10713/schemaob.htm#CNCPT411

• 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

• What is the best way to change a column type in the materialized view?

  Hello my dear friends,.

  I want to change a column type in a materialized view. VARCHAR2 NUMBER, so what do you recommend? What is the best way to do it?

  Thank you

  You can not change the data type of the column while there are data in the MV, so you might as well give up and recreate the MV with a TO_CHAR() around the column in question in the application of MV to get the data exactly as you want (be sure to include an appropriate format mask). That said, I'm fighting to think reasonable grounds to make such a change.

• A drop materialized view error

  I tried to drop two materialized views (I want to drop one and the other as a test to make sure that the behavior was consistent) with SQL Developer today, using the GUI, not the window of SQL command. When I did this, Developer SQL with these MVs among the tables, he tried to run a 'DROP TABLE' rather than a 'DROP MATERIALIZED VIEW' statement and an ugly error message came up with that and of course she didn't. Is this a bug that needs to be addressed? Or maybe that it is already identified and addressed in a future version?

  Earl

  Looks like you're down the underlying table, not the materialized view.   If you have a my_mv of materialized view, there is also a table called my_mv.

  You must drop the materialized since the Materialized View node in Object Explorer view.