create materialized view log on the table without a primary key

Similar Questions

• Impact on performance at the addition of materialized view logs at the tables?

  I write a very complex query for a client of our database system transaction and this will require the creation of a materialized viewbecause, all attempts at development to make acceptable performance failed.
  
  I want to activate the fast refresh the MVIEW but I am confused about the consequences of the addition of the addition of materialized view logs to the base tables.
  
  Some tables are large and involved in a large number of transactions and I wonder if the INSERT/update performance will be seriously affected by the presence of a newspaper mview.
  
  Maybe it's a simple question, but I was unable to find an answer very clear in the literature.
  
  Thanks for all the answers!
  
  Chris Mills
  Biotechnology data management consultant

  There is an overload for the newspapers of the view materialized, a little less, but roughly on par with a trigger that writes to a table.

  If it is an OLTP system where you do a lot of low-value transactions, the general expenses percentage is probably not particularly great, something in the range of 5-10% maybe (although, of course, by running tests in the development environment would be desirable). If there are loads in bulk, the impact of the percentage could be higher.

  Justin

• 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

• Diagram of all the tables list of primary key column names

  Hi people,
  
  I have a Scott user for example, I want to retrieve all tables primary key column names in the user Scott.
  
  can someone help me please.
  
  Thanks in advance,
  karmaya

  You can log in to SCOTT and try this

  select c.constraint_name
       , cc.table_name
       , cc.column_name
    from user_constraints c
    join user_cons_columns cc
      on c.constraint_name = cc.constraint_name
   where c.constraint_type = 'P';
  

• Generate the ddl to create materialized view log...

  Hi gurus...
  
  Oracle db: 11g
  
  I am trying to generate / excerpt from script MVIEW Logs from prod to be applied on the test.
  I tried
  < code >
  DBMS_METADATA. GET_DDL (decode(object_type,'materialized_view_log'), object_name, owner)
  from dba_objects
  where owner = < ABC >;
  < code >
  
  above fails, any ideas?
  
  Thank you

  >
  Oracle db: 11g

  I am trying to generate / excerpt from script MVIEW Logs from prod to be applied on the test.
  I tried
  
dbms_metadata.get_ddl(decode(object_type,'materialized_view_log'), object_name, owner)
from dba_objects
where owner=;


  above fails, any ideas?
  >
  Please try to use the tags in code, but you need to add.

   on the line before and the line after your code instead of what you are using.
  
  The object type names are case-sensitive so you need to use
  

  DBMS_METADATA. GET_DDL ('MATERIALIZED_VIEW_LOG', object_name, owner)

  Why are you using DECODE?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
  

• MATERIALIZED View Log Index Tablespace

  Is anyone aware of the syntax or a framework to be able to specify the index of a materialized view of the journal storage space?

  We chunk our objects by tablespace - index, tables, CLOB.

  Creating a materialized view log and specifying the storage space in which it should be created created the mv log in the correct location, but the index that is created uses the default tablespace for the user.

  And Yes, I Googled it. LMGTFY

  create materialized view log on MY_TEST tablespace my_tablespace ;
  

  select table_name, tablespace_name
    from user_tables
   where table_name like 'MLOG%';
  

  TABLE-NAME	TABLESPACE_NAME
  MLOG$ _MY_TEST	MY_TABLESPACE

  select table_name, index_name, tablespace_name
    from user_indexes
   where table_name like 'MLOG%';
  

  TABLE-NAME	INDEX_NAME	TABLESPACE_NAME
  MLOG$ _MY_TEST	I_MLOG$ _MY_TEST	USERS

  I found these documents:

  Index on MLOG$ (materialized view Log): difference in behavior between 11.2.0.3 and 11.2.0.4 (Doc ID 1959657.1)

  Materialized View Log (Mlog$) Index not created in its default Tablespace (Doc ID 1959658.1)

  I guess you are running 11.2.0.4, right?

  In previous versions, no index has been created automatically for the journal of MV.

  Kind regards

  Bashar

• ORA-12096: error in materialized view log

  Hi all
  
  
  I had created a display of fast refresh materialized. Log was also created.
  
  Now, I dropped the mv and newspapers.
  
  But now, every time I update or insert into the customer table I receive the error message.
  
  
  ORA-12096: error in materialized view log on the client
  ORA-00942: table or view does not exist
  
  There are entries in the DBA_MVIEW_LOGS for the customer table.
  
  Please suggest.

  Hello

  Which version of the database, you are on?
  And you have access to the Oracle Metalink/My Support?

  Found this, by the way:

  ORA-12096: error in materialized view log

  If problems occur when you try to access a log of a materialized view, the system issues an error ORA-12096 which is followed by the actual error. If the error ORA-12096 is accompanied by a message ORA-00942, the problem may be due to a reorganization in line which was only partially cancelled. In this case, you can remove the log file for manually materialized view (after checking that it is no longer necessary):

  DROP NEWSPAPER MATERIALIZED VIEWS

  ;

  Published by: hoek on July 29, 2009 14:15

• create view materized without constraint primary key on the base table?

  Hello
  
  I tried to create a materized view, but I got this error:
  
  SQL > CREATE MATERIALIZED VIEW FAST REFRESH TABLE1_MV
  START BY
  TO_DATE (April 25, 2009 03:00:13 ',' DD-MM-YYYY hh24:mi:ss')
  NEXT
  SYSDATE + 1
  AS
  Select * from TABLE1@remote_db
  SQL > /.
  CREATE MATERIALIZED VIEW FAST REFRESH TABLE1_MV
  *
  ERROR on line 1:
  ORA-12014: table 'TABLE1' does not contain a primary key constraint.
  
  Table1 in remote_db is not a primary key constraint. Is there anyway that I can create a view materized on a base table that is not a primary key constraint?
  
  Thank you
  Liz

  Make sure user name used in remote_db database link has select privileges on Journal of MV. On the issue of db source:

  SELECT LOG_TABLE FROM DBA_MVIEW_LOGS WHERE LOG_OWNER = 'TABLE1-owner' AND MASTER = "TABLE1";

  This will give you MV table the journal name. On the issue of target side:

  SELECT * from MV-LOG-NAME@remote_db;

  And after your version.

  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.

• The materialized view log and user...

  Hello
  Suppose a user, we will call him A has a table and another user B must create a log of materialized view on the table that a user has.
  While user B have all the privileges of object (direct priv insert, update, delete... not through a role) on the table to the user may not create a log of mv on this table on its schema...
  Thus, the insert/update/delete stmts on < table_name > are run successfully (after having logged on as user B).
  
  The error message ' ORA-00942: table or view does not exist ' appears when I run the command:
  Connect B/B;
  create log view materialized on table_name with sequence including new values;
  
  Note: I use ORADB 10.2.0.4 and it stands for table-name to user B (which tries to create the log of mv on)...
  
  The req. above is possible somehow?
  
  Thank you
  SIM

  The documentation says the following:

  The materialized view log is created in the same schema as the master of the target.

  HTH!

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

• creating view error table contains no primary key materialized

  I am trying to create a materialized view, but I get an error indicating that the table on which the materialized view is being created doesn't have a primary key.
  

  Create materialized view LEA_N(lea) 
  as        select SUBSTR(sn,1,3) 
  from        comqdhb.school; 
  
  ERROR at line 1:
  ORA-12014: table 'SCHOOL' does not contain a primary key constraint

  I read that it can be rectified using rowid
  
  but where them specify rowid.
  
  Thank you.
  
  Published by: Trooper on January 1st, 2009 05:02

  Rider wrote:
  But the use of rownum is a bad idea is not because the rowid continues to change for each request.

  Not bad, although I agree that it is not optimal, since rownum and rowid are two different things. A rowid does not change for each request.

  Rownum: http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/pseudocolumns009.htm#SQLRF00255
  ROWID: http://download.oracle.com/docs/cd/B28359_01/server.111/b28318/glossary.htm#CNCPT2103

  Kind regards
  Rob.

• effect of pump or etl data on the materialized view logs

  Hi, we are mobile/upgrading an instance of 10g to 12 c, where one materialized view logs and expect to do one of the following:

  (1) extract/import the meta, only using data pump data and move data using an etl tool

  (2) comprehensive database extract/import using the data pump in

  are there questions that we must be aware of when the displacement of these with either scenario materialized view logs?

  Thanks for any information you can provide.

  > are there questions that we should be aware of when the displacement of these materialized view logs with either scenario?

  No problem

• Overhead of triggers VS materialized view log files

  If I need to log UPDTEs, insertions and deletions on a table - is there a difference in charge through newspapers vs MV triggers?
  
  Thank you

  You said that MV newspaper is slightly more effective than a trigger. I'm curious to know why. How they work differently under the hood?

  If the essence of the debate is only why MV newspaper is more effective than the trigger that I think that Justin has stressed that is below good technical points

  1. you don't have to order at the PL/SQL engine.
  2. you also write the binary data that you will put in the newspapers of recovery instead of column-level data.
  And below the text in the documentation:

  Trigger internal for the materialized view log

  When changes are made to the master table or master materialized with DML view, an internal trigger records information about the affected rows in the materialized view log. This information includes the values of the primary key, rowid, or id of the object or both, as well as the values for the other columns in the materialized view log. It is an intern AFTER trigger LINE that runs automatically when you create a journal of materialized to view table main target or master materialized view. It inserts a line in the materialized view log, whenever an INSERT, UPDATE, or DELETE statement modifies data in the table. This trigger is always the last to fire.

  http://docs.Oracle.com/CD/B28359_01/server.111/b28326/repmview.htm#i30732

  3 trigger, i.e. we are coding for the track changes, newspaper MV i.e. tool/technology, which is provided by Oracle itself; So certainly "we are not that much able to write code that is equal to or better than the Oracle itself right?

  Feature of MV's trigger INSTEAD of, but under the hood, with close to internal components of Oracle.

  Concerning
  Girish Sharma