Materialized view and Table

Similar Questions

• question on MATERIALIZED VIEW and table

  Hello
  
  There is table (name is test123) and MATERIALIZED VIEW (the name is also test123) stored in the same pattern (the name is schema123).
  
  If I run sql: Select in schema123.test123; *
  
  I want to know the result I get data data table test123 or MATERIALIZED VIEW test123, which one of them?
  
  Thanks in advance!

  Hi Tao2,

  You will get the data in the table.

  Kind regards
  oraclekt

• Questions on the tables of materialized views and MV newspaper

  Hi all
  
  Have some questions about Materialized View.
  
  (1) once the materialized view reads the records from the table MLOG, reviews the MLOG get purged. fix? or is that not the case? In some cases, I see still (old) records in the MLOG table even after updating MV.
  
  (2) how the table MLOG distinguishes between a reading which comes from a MV and a reading that comes from a user? If I execute manually
  "Select * < table MLOG > ' could get record of the table MLOG redacted all the same way as it does after a refresh of MV?
  
  (3) one of our MV updates crashes intermittently. Based on the events of waiting I noticed that it was a 'db file sequential read' against the main table. Finally I had to put an end to the update. I don't know why it was sequential reading on the main table when she should be reading the table MLOG. Any ideas?
  
  (4) I saw 'file db scattered read' (full table scan) usually on tables, but I was surprised to see 'db file sequential read' against the table. I thought sequential read occurs normally against the index. All the world has noticed this behavior?
  
  Thanks for your time.

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

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

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

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

  Justin

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

• Materialized view and or

  I'm really in need of help as I'm unable to refresh the materialized view. Basically the code below if it is triggered by executing the SQL manually will draw the correct records which is located somewhere in the unique record range 970.
  
  Having worked SQL we created a materialized view which updates every day at 03:00 so that we can send this file to an external service provider. However the materialized view that refers to this SQL when it refreshes draws some 100,000 unique records incorrectly.
  
  After testing several times, I've identified the update seems to be bypassing the declaration "AND/OR" I installed to watch:
  
  (AND ((CURRENT_DATE-msp_loan_d.next_payment_due_date) > = 58 AND msp_property_d.property_alpha_state_code <>'NC'))
  GOLD ((CURRENT_DATE-msp_loan_d.next_payment_due_date) > = 45 AND msp_property_d.property_alpha_state_code = "NC")).
  
  Any ideas on this one and maybe I need to rewrite the SQL code? Not sure why the materialized view would interpret the SQL any differently.
  
  
  
  SELECT DISTINCT msp_loan_d.loan_number, TRUNC (CURRENT_DATE - msp_loan_d.next_payment_due_date, 0) AS DPD,.
  To_date (msp_user_defined_d.user_07_position_field_1a, "MMDDYY") AS Demand_Date,
  MSP_BORROWER_D.MORTGAGOR_EXPANDED_FIRST_NAME,
  MSP_BORROWER_D.MORTGAGOR_EXPANDED_MIDDLE_NAME, MSP_BORROWER_D.MORTGAGOR_EXPANDED_LAST_NAME,
  MSP_BORROWER_D.CO_MRTGR_EXPANDED_FIRST_NAME, MSP_BORROWER_D.CO_MRTGR_EXPANDED_MIDDLE_NAME,
  MSP_BORROWER_D.CO_MRTGR_EXPANDED_LAST_NAME,
  MSP_BORROWER_D.BILLING_ADDRESS_LINE_4, MSP_BORROWER_D.BILLING_CITY_NAME,
  MSP_BORROWER_D.BILLING_STATE, MSP_BORROWER_D.BILLING_ZIP_CODE, MSP_PROPERTY_D.PROPERTY_STREET_ADDRESS, MSP_PROPERTY_D.CITY_NAME.
  MSP_PROPERTY_D.PROPERTY_ALPHA_STATE_CODE, MSP_PROPERTY_D.PROPERTY_ZIP_CODE, msp_loan_d.next_payment_due_date,
  CO. LTD.. ADL_CO_BORR_UNFORMATTED_NAME_1 AS 'ADDITIONAL COBORROWER. "
  CO. LTD.. ADL_CO_BORR_STREET, CO. ADL_CO_BORR_CITY, CO. ADL_CO_BORR_STATE, CO. ADL_CO_BORR_ZIP_CODE,
  MSP_LOAN_D.Investor_ID, msp_loan_d.first_principal_balance, msp_loan_d.last_full_payment_date, MSP_ORIGINAL_LOAN_D.ORIGINAL_MORTGAGE_AMOUNT,
  MSP_LOAN_D.TOTAL_MONTHLY_PAYMENT, MSP_DELINQUENCY_D.DELINQUENT_PAYMENT_COUNT, MSP_DELINQUENCY_D.DELINQUENT_PAYMENT_BALANCE,
  MSP_LOAN_D.ACCRUED_LATE_CHARGE_AMOUNT, MSP_LOAN_D.NSF_FEE_BALANCE, MSP_CORPORATE_ACCOUNTING_D.RECOVER_CORP_ADVANCE_BALANCE,
  MSP_LOAN_D.SUSPENSE_BALANCE, MSP_ORIGINAL_LOAN_D.NOTE_DATE as "DATE of DEPARTURE", MSP_LOAN_D.LOAN_TERM AS "LOAN PERIOD",
  ADD_MONTHS (msp_loan_d.next_payment_due_date-1) "DATE OF LAST PAYMENT DUE", MSP_USER_DEFINED_D.USER_20_POSITION_FIELD_2A AS "SENDER."
  NJCLERK.payee_address_line_1, NJCLERK.payee_address_line_2, NJCLERK.payee_address_line_3,
  NJCLERK.payee_address_line_4, NJCLERK.payee_address_zip_code
  
  
  
  
  
  
  
  OF me589mgr.msp_loan_d@infodb.
  me589mgr.msp_property_d@InfoDB,
  me589mgr.msp_user_defined_d@InfoDB,
  me589mgr.msp_borrower_d@InfoDB,
  ME589MGR. MSP_ORIGINAL_LOAN_D@InfoDB,
  ME589MGR. MSP_DELINQUENCY_D@InfoDB,
  ME589MGR. MSP_CORPORATE_ACCOUNTING_D@InfoDB,
  
  
  
  (SELECT DISTINCT LOAN_NUMBER, Hi_TYPE, LO_TYPE
  OF ME589MGR. MSP_LOAN_D@InfoDB
  WHERE HI_TYPE = 3
  AND LO_TYPE = 8) UNSECURED,.
  
  (SELECT DISTINCT msp_bankruptcy_d.loan_number
  Of ME589MGR. MSP_BANKRUPTCY_D@InfoDB
  Where BKR_STATUS_CODE = ' A') BKLOAN,.
  
  
  (SELECT DISTINCT MSP_ADDITIONAL_CO_BORROWER_D.LOAN_NUMBER,
  ADL_CO_BORR_UNFORMATTED_NAME_1, ADL_CO_BORR_STREET, ADL_CO_BORR_CITY,
  ADL_CO_BORR_STATE, ADL_CO_BORR_ZIP_CODE
  OF ME589MGR. MSP_ADDITIONAL_CO_BORROWER_D@InfoDB
  WHERE ADL_CO_BORR_THIRD_PARTY_FLAG = ' don't
  AND ADL_CO_BORR_SEQUENCE = '1') CO,.
  
  
  
  
  
  (SELECT
  msp_tax_d.loan_number,
  msp_payee_d.payee_address_line_1, msp_payee_d.payee_address_line_2,
  msp_payee_d.payee_address_line_3, msp_payee_d.payee_address_line_4,
  msp_payee_d.payee_address_zip_code,
  ROW_NUMBER() over (PARTITION BY msp_tax_d.loan_number ORDER BY msp_tax_d.tax_key_sequence_number DESC) AS ROW_ORDER
  OF me589mgr.msp_tax_d@infodb.
  me589mgr.msp_payee_d@InfoDB,
  me589mgr.msp_property_d@InfoDB
  WHERE msp_tax_d.tax_key_sequence_number = 1
  AND msp_tax_d.tax_payee_code = msp_payee_d.payee_id
  AND msp_property_d.property_alpha_state_code = "NJ".
  AND msp_tax_d.loan_number = msp_property_d.loan_number) NJCLERK
  
  
  
  
  WHERE (msp_loan_d.loan_number = no GUARANTEE. LOAN_NUMBER (+)
  AND UNSECURED. LOAN_NUMBER IS NULL
  AND msp_loan_d.loan_number = BKLOAN. LOAN_NUMBER (+)
  AND BKLOAN. LOAN_NUMBER IS NULL
  AND msp_loan_d.loan_number = MSP_ORIGINAL_LOAN_D.LOAN_NUMBER (+)
  AND msp_loan_d.loan_number = MSP_DELINQUENCY_D.LOAN_NUMBER (+)
  AND msp_loan_d.loan_number = MSP_CORPORATE_ACCOUNTING_D.LOAN_NUMBER (+)
  AND msp_loan_d.loan_number = msp_user_defined_d.loan_number (+)
  AND msp_loan_d.loan_number = msp_property_d.loan_number (+)
  AND msp_loan_d.loan_number = msp_borrower_d.loan_number (+)
  AND msp_loan_d.loan_number = CO. LOAN_NUMBER (+))
  AND ((CURRENT_DATE-msp_loan_d.next_payment_due_date) > = 58 AND msp_property_d.property_alpha_state_code <>'NC')
  GOLD ((CURRENT_DATE-msp_loan_d.next_payment_due_date) > = 45 AND msp_property_d.property_alpha_state_code = "NC"))
  AND (msp_loan_d.first_principal_balance > 0
  AND msp_loan_d.man_code NOT IN ('U' 'd', 'Y', 'B', 'F', 'L', 'G', 'I' am ', 'o', 'R', 'X', 'Y', 'W', ', 'Q', 'Z' ")
  AND msp_property_d.property_alpha_state_code NOT IN ('WA', 'NM', 'MA', 'MD', 'NY', 'PA')
  AND msp_loan_d.loan_number = NJCLERK. LOAN_NUMBER (+)
  Msp_loan_d.PROCESS_STOP_CODE AND NOT IN ('1', '2', '8', 'A', ' B ', 'C' ' d ', 'E', 'F', 'H', 'J', 'R', '9', 'K', 'o', 'U', 'V', 'X' "))
  AND (msp_loan_d.last_full_payment_date > = TO_DATE (msp_user_defined_d.user_07_position_field_1a, "MMDDYY"))
  HOWEVER (msp_user_defined_d.user_07_position_field_1a IS NULL))

  Hello

  I do not think that or has something to do with your problem. The issue seems to be the writing of outer joins.

  You have an outer join to msp_user_defined_d:

  AND msp_loan_d.loan_number = msp_user_defined_d.loan_number(+)
  

  But here you have an inner join to the same table:

  AND (     msp_loan_d.last_full_payment_date >= TO_DATE (msp_user_defined_d.user_07_position_field_1a, 'MMDDYY')
         OR (msp_user_defined_d.user_07_position_field_1a IS NULL)
      )
  

  Looks like you need to change this to:
  (If you hit ORA-01719: operator of outer join (+) {noformat} {noformat} not allowed in operand of GOLD, or you may have to rewrite accordingly)

  AND (     msp_loan_d.last_full_payment_date >= TO_DATE (msp_user_defined_d.user_07_position_field_1a(+), 'MMDDYY')
         OR (msp_user_defined_d.user_07_position_field_1a IS NULL)
      )
  

  If true, it makes me wonder. Have you tested your only request, he produced the correct result set?

  Concerning
  Peter

• Materialized view and view logs on EBS 11.5.10

  Hello
  Trying to create a log of view materialized on table MTL_SYSTEM_ITEMS_B connected like APPS... the system of claims on: ORA-00942: table or view does not exist
  
  So, I need to create the mv to the schema INV log or I give a priv to user APPS?
  I read in the edoc EBS - Concepts that the materialized view should be created in the schema of the APPS...
  
  What materialized view logs... ???
  
  Thank you
  SIM

  SIM,

  Please consult the following and see if it helps.

  Note: 273924.1 - ORA-12096: LOG of ERRORS IN the MATERIALISEE VIEW ON "INV". " MTL_MATERIAL_TRANSACTIONS
  https://metalink2.Oracle.com/MetaLink/PLSQL/ml2_documents.showDocument?p_database_id=not&P_ID=273924.1

  Note: 215463,1 - ORA-01031 insufficient privileges when create materialized in different schema view journal
  https://metalink2.Oracle.com/MetaLink/PLSQL/ml2_documents.showDocument?p_database_id=not&P_ID=215463.1

  Kind regards
  Hussein

• Materialized view log table to clear

  Hello
  RDBMS: oracle 10.2.0.2
  
  I created the materialized with fast refresh view.
  Now as time passed, Mview journal tables grow much and more.
  
  I want to know, is it possible to shrink the Mview journal tables?
  
  Thank you
  Terranova

  read this link

  http://download.oracle.com/docs/cd/B19306_01/server.102/b14227/rarmanmv.htm#sthref708
  

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

  I have 11.2.4.0 Oracle enterprise edition.

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

  
  

  I need to do this on a production of databases.

  
  

  It's the right order?

  Thank you.

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

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

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

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

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

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

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

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

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

  any ideas?

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

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

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

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

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

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

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

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

• Can I introduce a few relationships in data with the views and the Table maker?

  Hello. I have db with lots of views and tables. Can I introduce a few relationships in maker data with Tables and views? I have to configure PK and FK for my tables and views if I want to see relationships? I just started with the Data Modeler. Thank you for your help.

  Hello

  If you import your database Tables (Import / Data Dictionary), foreign keys defined in your database will be also imported.

  He is also a foreign key discovery tool in maker of data that can help you identify possible FK relationships and add them to your model.

  To use it, right click on the entry for your relational model in the tree view of the browser and select the foreign keys to discover on the menu drop down.

  Note that data Modeler does not support PKs and FKs on views.

  David

• type a materialized view foreign key constraint?

  Hello.
  
  I have a materialized view that flows into a single column 'A' two different columns of different tables of a remote database.
  
  I also have a table that has a column 'B', whose values must exist in the column 'A' of the materialized view.
  
  So it's like defining a constraint foreign key of a table to a view, but this is not possible.
  
  Is it possible to do?
  
  I saw some triggers that verify the existence of the 'A' value before insertion in 'B', but this fails when a value is changed or deleted in 'A'
  
  Any suggestions?
  
  Thank you very much.
  
  Published by: user7029403 on 18-ene-2013 03:57

  There is no problem of definition of a primary key on a materialized view and then reference it with a foreign key. It works for me:

  create database link l1 connect to scott identified by tiger using 'orcl';
  create materialized view mv1 as select deptno||dname as a from dept@l1;
  alter table mv1 add constraint mv1pk primary key (a);
  alter table dept add (fkcol as (deptno||dname));
  alter table dept add constraint deptfk foreign key (fkcol) references mv1;
  

  I don't know there is a more elegant solution than to use a virtual column, which seemed the best way to get around the concatenation of two columns in a single

• Refresh/update of the data in a materialized view

  Hello
  I have question about data in a materialized view, and how it is updated. I think Matt has all my dimension-ID and my (for my specialize needs) aggregated measures of my fact table. I used mat View Wizard to create my opinion - which works perfectly. But now I wonder if I should create some sort of mapping (?) or some kind of trigger to refresh the data in the view of mast. Or are updated automatically when I start my fact table mappings. I use OWB 11 GR 2
  
  THX

  MVs have properties for update - you a discount based on schedules or when dependent data are committed or manually.

  See you soon
  David

• ORA-00600: internal error when delete masters lines in a materialized view

  I have a view, materialized in 11g 2 on Redhat 5, defined as

  CREATE MATERIALIZED VIEW mv_idty
  PARALLEL BUILD IMMEDIATE REFRESH FAST ON COMMIT ENABLE QUERY REWRITE AS
  select IDTY_NAME_FIRST,IDTY_NAME_MIDDLE,IDTY_NAME_LAST,IDTY_NAME_SUFFIX,IDTY_SSN,
    IDTY_DR_LIC_NUM,IDTY_DR_LIC_STA,x.person_id,i.rowid i_rowid,x.rowid x_rowid
    from idty i,person_x_idty x where x.idty_id=i.idty_id;

  I deleted a few lines of the masters and error tables

  13:58:48 SQL> delete idty where  idty_id like 'test_row%' ;
  
  7 rows deleted.
  
  13:58:52 SQL> commit;
  commit
  *
  ERROR at line 1:
  ORA-12008: error in materialized view refresh path 
  ORA-00600: internal error code, arguments: [kkzfrfajv_markdml-1], [], [], [], [], [], [], [], [], [], [], [] 

  I have other materialized views and they all delete OK master. It's the simplest but is a problem. Help!
  
  Published by: user13148231 on August 11, 2010 17:45

  Hello
  Please check this metalink note

  * ORA-600 [Kkzfrfajv_markdml-1] [ID 743766.1] *.

  Thank you