Refresh Fast option in Materialize view

Dear All,
We have oracle 10g On windows.
We have database A having SCOTT schema and tables Emp and Dept.
I have another database B having TEST schema and this schema does not have any objects (Moto is to create mview on this database).
We have created DB LINK between TEST schema to SCOTT schema and planning to create materialize view in TEST schema.
Now I am confuse....
1) I am creating mview in TEST schema and i want to refresh mview increamentally. I search on internet and found only if you want to use FAST REFRESH then you must have to create log table for the base table.
--Query is
1) I am creating mview in TEST schema and my base tables are in SCOTT schema on different database. Where should i create log table(on SCOTT SCHEMA or TEST schema).
2) Does this log tables will occupy more space or log table will truncate after refresh of mview.
3) For using incremental refresh i need to use +REFRESH FORCE+ option or anything else.
4) If log table will not truncate then it will occupy more space so is there anything that we can come up out of this situation.Thanks..

1) You should create log in Scott Schema
2)
Managing Materialized View Log Space
Oracle automatically tracks which rows in a materialized view log have been used during the refreshes of materialized views, and purges these rows from the log so that the log does not grow endlessly. Because multiple simple materialized views can use the same materialized view log, rows already used to refresh one materialized view might still be needed to refresh another materialized view. Oracle does not delete rows from the log until all materialized views have used them.
For example, suppose two materialized views were created against the customers table in a master site. Oracle refreshes the customers materialized view at the spdb1 database. However, the server that manages the master table and associated materialized view log does not purge the materialized view log rows used during the refresh of this materialized view until the customers materialized view at the spdb2 database also refreshes using these rows.
Because Oracle must wait for all dependent materialized views to refresh before purging rows from a materialized view log, unwanted situations can occur that cause a materialized view log to grow indefinitely when multiple materialized views are based on the same master table or master materialized view.
For example, such situations can occur when more than one materialized view is based on a master table or master materialized view and one of the following conditions is true:
One materialized view is not configured for automatic refreshes and has not been manually refreshed for a long time.
One materialized view has an infrequent refresh interval, such as every year (365 days).
A network failure has prevented an automatic refresh of one or more of the materialized views based on the master table or master materialized view.
A network or site failure has prevented a master table or master materialized view from becoming aware that a materialized view has been dropped.
Note:
If you purge or TRUNCATE a materialized view log before a materialized view has refreshed the changes that were deleted, then the materialized view must perform a complete refresh.
Purging Rows from a Materialized View Log
Always try to keep a materialized view log as small as possible to minimize the database space that it uses. To remove rows from a materialized view log and make space for newer log records, you can perform one of the following actions:
Refresh the materialized views associated with the log so that Oracle can purge rows from the materialized view log.
Manually purge records in the log by deleting rows required only by the nth least recently refreshed materialized views.
To manually purge rows from a materialized view log, execute the PURGE_LOG procedure of the DBMS_MVIEW package at the database that contains the log. For example, to purge entries from the materialized view log of the customers table that are necessary only for the least recently refreshed materialized view, execute the following procedure:
3) REFRESH FAST
4) See step 2

Similar Messages

Materialized View creation with REFRESH FAST

Hello ,
Please see below case,
TABLE A1(partitioned range+list)
COLUMN C1 -- Primary key
COLUMN C2 -- NUMBER
TABLE D1
COLUMN C1 -- PRIMARY KEY
created MV log as below
CREATE MATERIALIzED VIEW LOG ON A1 WITH ROWID,PRIMARY KEY INCLUDING NEW VALUES;
CREATE MATERIALIzED VIEW LOG ON D1 WITH ROWID,PRIMARY KEY INCLUDING NEW VALUES;
Trying to create MV like below:
CREATE MATERILIZED VIEW mv1test
                                REFRESH FAST ON COMMIT
AS
Select
FROM A1,
                        D1
                WHERE A1.C1 = D1.CI
AND A1.C2 IS NOT NULL;
It gives below error message:
ORA-12052: cannot fast refresh materialized view schema.mv1test
12052. 00000 - "cannot fast refresh materialized view %s.%s"
*Cause:    Either ROWIDs of certain tables were missing in the definition or
           the inner table of an outer join did not have UNIQUE constraints on
           join columns.
*Action:   Specify the FORCE or COMPLETE option. If this error is got
           during creation, the materialized view definition may have be
           changed. Refer to the documentation on materialized views.
However ,as discussed in earlier thread i checked all general restrictions of the 'Refresh fast' approach for join.
Restrictions on Fast Refresh on Materialized Views with Joins Only
Defining queries for materialized views with joins only and no aggregates have the following restrictions on fast refresh:
1) They cannot have GROUPBY clauses or aggregates.
2) Rowids of all the tables in the FROM list must appear in the SELECT list of the query.
3)Materialized view logs must exist with rowids for all the base tables in the FROM list of the query.
4)You cannot create a fast refreshable materialized view from multiple tables with simple joins that include an object type column in the SELECTstatement.
As per above restrictions ,
1) Group by clause is not present
2)i do not understand 2nd point , i have added a1.rowid and d1.rowid in select statement of MV, but got same error.
3) observed same as 2nd point.
4)we have CLOB column in select list. Tried removing this column but got same error.
Please do let me know any workaround on this.
Thanks in advanced ..
PM

Basic Materialized Views show how to analyse MVs using dbms_mview. I'm not sure about creating MVs on partitioned tables, that partition maintenance might cause problems

Materialized view - REFRESH FAST ON COMMIT - UNION ALL

In a materialized view which uses REFRESH FAST ON COMMIT to update the data, how many UNION ALL can be used.
I am asking this question because my materialized view works fine when there are only 2 SELECT statement (1 UNION ALL).
Thank you.

In a materialized view which uses REFRESH FAST ON COMMIT to update the data, how many UNION ALL can be used.As far as I remember you can have 64K UNIONized selects.
I am asking this question because my materialized view works fine when there are only 2 SELECT statement (1 UNION ALL).Post SQL that does not work.

Materialized View and Refresh Fast

Hi,
Below is a sample query for generating a MV. Since I am new to Oracle,
Experts please help me.
create materialized view user1.mv_empdept refresh fast
as select * from user1.employee e
where exists(select * from user2.department d where d.deptId=e.deptid);
Is it possible to have a MV with objects from different schema of the same
database for Refresh Fast?
I ran into "insufficient privileges" error eventhough both user1 and user2 have sysdba privileges.
Thanks,
Jagan

Hi Ajiaz,
User user1 has select privileges on Department table.
if we omit "refresh fast" in the query, I am able to create the MV
create materialized view user1.mv_empdept refresh fast
as select * from user1.employee e
where exists(select * from user2.department d where d.deptId=e.deptid);
Regards,
Jagan Kumar K

Create materialized view is failing when refresh fast is used

version 10.2.0.4 on solaris
This statement is working fine
CREATE MATERIALIZED VIEW MVIEW1
TABLESPACE MIS_CURD01
BUILD IMMEDIATE
as
SELECT ACTIVITY_ID "ACTIVITY_ID",
ASSOC_ID "ASSOC_ID",
PIT_ROLE_CODE "PIT_ROLE_CODE",
PIT_BANK_CODE "PIT_BANK_CODE",
PIT_COST_CENTER "PIT_COST_CENTER",
RESP_ASSOC_IND "RESP_ASSOC_IND"
FROM TABLE1@DBLINK;
The statement with fast refresh is failing with this error message
ERROR at line 18:
ORA-12018: following error encountered during code generation for
"TABLE1"
ORA-00942: table or view does not exist
Here is the statement
CREATE MATERIALIZED VIEW MVIEW1
TABLESPACE MIS_CURD01
NOCACHE
LOGGING
NOCOMPRESS
NOPARALLEL
BUILD IMMEDIATE
USING INDEX TABLESPACE MIS_CURI01
REFRESH FAST ON DEMAND
WITH PRIMARY KEY
AS
SELECT ACTIVITY_ID "ACTIVITY_ID",
ASSOC_ID "ASSOC_ID",
PIT_ROLE_CODE "PIT_ROLE_CODE",
PIT_BANK_CODE "PIT_BANK_CODE",
PIT_COST_CENTER "PIT_COST_CENTER",
RESP_ASSOC_IND "RESP_ASSOC_IND"
FROM TABLE1@DBLINK;
Any idea what's going wrong here. Thanks for your help in advance.
Edited by: user11319873 on Jun 30, 2010 4:17 PM

Refresh FAST requires that
a. An MV Log (Snapshot Log) be created on the source table
b. The user doing the refresh (i.e. the account that the DBLink uses) has SELECT privilege on the MV Log.
Hemant K Chitale

Refresh FAST for Materialized View failed after Partition Operation

Dear all,
I have created a Materialized View having a simple join between a Dimension and Fact Table of a Datawarehouse. The MV is REFRESH FAST ON DEMAND.
However, when a Partition Maintenance Operation (PMOP) was performed on the Master Tables, the MV failed to Refresh giving a ORA-32313 error.
As suggested on one of the troubleshooting websites, we did a complete refresh of the MV and fixed it temporarily. However, I would like to know the exact cause for this and would like to have a permanent fix for the same.
Can the DBA for this Database provide me the answers or are there some standard troubleshooting steps for the same?
Please let me know.
Best,
Ketan

Hello Maurice,
Here are the answers to your questions.
1) Database is Oracle 9i.
2) We have a stored procedure to refresh the MV. The command is dbms_mview.refresh('SALES_FACT_MV','f'). It was working fine daily. Only after a PMOP was done on the Master Tables, it failed to refresh. We have also created indexes on some columns of the MV for performance improvement. We are getting a very good improvement.
3) We have MV logs for both Master Tables to store the incremental values.
4) We are not able to get the output from DBMS_MVIEW.EXPLAIN_MVIEW since this can be done only by the DBA. WIll update you once I have the info.
5) Same as Point 2.
Let me know if you need any further info.
Thanks, Ketan

How to find total refresh time of Materialize view?

Hello All,
I want to know the total refresh time of Materialize view. i m refreshing MV by below statement
i hv not logging the start and end time of this in process.
exec dbms_mview.refresh('EMP_MV','C','',FALSE,FALSE,0,0,0,TRUE);
So, anybody can you please know the using which database table it cab be possible?
Thanks in advance

The only way you can log the refresh time for each execution is to wrap the call inside a procedure that also logs the start and end times to a logging table.
(if you manually run the exec dbms_mview.refresh from an SQLPlus command line, you could also SET TIMING ON in SQLPlus)
Hemant K Chitale

ORA-02243:invalid ALTER INDEX or ALTER MATERIALIZES VIEW option

Hi, Friend,
I am changing all the index to another tablespace of one of my schema.When I run the DDL script,got the error:
ORA-02243:invalid ALTER INDEX or ALTER MATERIALIZES VIEW option
I checked the metalink, got nothing.Anyone can help? Thanks!

I also googled some info,like:
Oracle Error :: ORA-02243
invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
Cause
An option other than INITRANS, MAXTRANS,or STORAGE is specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER MATERIALIZED VIEW statement.
Action
Specify only legal options.
But I still can't find the clue.

ORACLE ERROR ORA-32314: REFRESH FAST unsupported after deletes/updates

hi,
I have a materialized view created with fast refresh on demand option. Now when i try to refresh it manually the next day, it gives me an error . I have both count(*) and count(1) inside the materialized view. There is update and delete transactions done on most of the tables. The refresh is set to be at 4 am though a refresh group . But it fails with the error shown below . Please help. thanks
here is the script from toad
DROP MATERIALIZED VIEW MYPORTAL.ACCOUNT_COST_CATEGORY_MV;
CREATE MATERIALIZED VIEW MYPORTAL.ACCOUNT_COST_CATEGORY_MV
TABLESPACE USERS
PCTUSED    0
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
            INITIAL          64K
            MINEXTENTS       1
            MAXEXTENTS       UNLIMITED
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
NOCACHE
LOGGING
NOCOMPRESS
NOPARALLEL
BUILD IMMEDIATE
USING INDEX
            TABLESPACE USERS
            PCTFREE    10
            INITRANS   2
            MAXTRANS   255
            STORAGE    (
                        INITIAL          64K
                        MINEXTENTS       1
                        MAXEXTENTS       UNLIMITED
                        PCTINCREASE      0
                        BUFFER_POOL      DEFAULT
REFRESH FAST ON DEMAND
WITH PRIMARY KEY
AS
/* Formatted on 2011/01/07 10:04 (Formatter Plus v4.8.8) */
SELECT   ac.account_id,
         ac.account_manager mgr_id,
         ac.account_number,
         ac.account_name,
         bc.burden_center_name burden_center,
         p.surname_isi || ', ' || p.first_name account_manager,
         p.division_id,
         item.code_id,
         item.code_name cost_category_item,
         TO_NUMBER (TO_CHAR (ap.first_day, 'YYYY')) period_year,
         ap.first_day period,
         ap.fiscal_system_period_cal_yr_eq || ', ' || ap.fiscal_year period_asr,
         COUNT (*) total_row_count,
         COUNT (1) total_one_count,
         SUM (NVL (ad.current_expense, 0)) expense,
         SUM (NVL (ad.total_budget, 0)) budget,
         SUM (NVL (ad.cumltv_expense, 0)) cumltv_expense,
         SUM (NVL (ad.commitments, 0)) commitments,
         SUM (NVL (ad.budget_balance, 0)) budget_balance
    FROM accounts ac,
         burden_centers bc,
         personnel p,
         asr_headers ah,
         asr_details ad,
         codes item,
         codes costcat,
         all_periods ap,
         codes cost_element,
         accounting_base_group abg
   WHERE ac.account_manager = p.personnel_id
     AND ac.burden_center_id = bc.burden_center_id
     AND ac.account_id = ah.account_id
     AND ah.asr_header_id = ad.asr_header_id
     AND ah.period_asr =
                   ap.fiscal_system_period_cal_yr_eq || ', ' || ap.fiscal_year
     AND abg.cost_element_cat_item_id = item.code_id
     AND cost_element.code_id = abg.cost_element_id
     AND ad.object_code = cost_element.code_value
     AND item.code_parent_id = costcat.code_id
     AND (   costcat.code_name = 'Report 1'
          OR (costcat.code_name = 'Base' AND item.code_name = 'MTDC')
GROUP BY ac.account_id,
         ac.account_manager,
         ac.account_number,
         ac.account_name,
         bc.burden_center_name,
         p.surname_isi || ', ' || p.first_name,
         p.division_id,
         item.code_id,
         item.code_name,
         TO_NUMBER (TO_CHAR (ap.first_day, 'YYYY')),
         ap.first_day,
         ap.fiscal_system_period_cal_yr_eq || ', ' || ap.fiscal_year;
COMMENT ON MATERIALIZED VIEW MYPORTAL.ACCOUNT_COST_CATEGORY_MV IS 'snapshot table for snapshot MYPORTAL.ACCOUNT_COST_CATEGORY_MV';
CREATE INDEX MYPORTAL.ACCOUNT_COST_CAT_MV_IDX ON MYPORTAL.ACCOUNT_COST_CATEGORY_MV
(ACCOUNT_ID, CODE_ID, PERIOD)
LOGGING
TABLESPACE USERS
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
            INITIAL          64K
            MINEXTENTS       1
            MAXEXTENTS       UNLIMITED
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
NOPARALLEL;
-- Note: Index I_SNAP$_ACCOUNT_COST_CATEG will be created automatically
--       by Oracle with the associated materialized view.
here is the error :
10:10:04 SQL> exec dbms_mview.refresh('account_cost_category_mv');
BEGIN dbms_mview.refresh('account_cost_category_mv'); END;
ERROR at line 1:
ORA-32314: REFRESH FAST of "MYPORTAL"."ACCOUNT_COST_CATEGORY_MV" unsupported after deletes/updates
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2254
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2460
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2429
ORA-06512: at line 1
10:10:14 SQL>

Check out the error cause and action:
ORA-32314: REFRESH FAST of "string"."string" unsupported after deletes/updates
Cause:      One or more deletes or updates has been performed on one or more of the detail tables referenced by the specified materialized view. This materialized view does not support fast refresh after deletes or updates.
Action:      Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after deletes or updates using the DBMS_MVIEW.EXPLAIN_MVIEW() API.

Materialize views logs

hey gurus
in my database we have some materialize views . and some of them are using clouse REFRESH COMPLETE and some are USING REFRESH FAST.my point of concern is " for a fast refresh we have to create mat. view logs".how can i check what are log exist for my database because i checked in all_object i havn't find any object with type = log . is it really a object else what it do when we run a DDL
" create materialise view log on tablename ....."
thanks in advance

Seems to be working for me, but I don't have a machine that would even run 8.1.7 to test with. I have no experience with the old Server Manager tool, you might try using SQL*Plus instead.
Describing a materialized view log, though, isn't particularly interesting. I created one on the EMP table
SCOTT @ jcave102 Local> select * from dba_mview_logs;
LOG_OWNER                      MASTER                         LOG_TABLE
LOG_TRIGGER                    ROW PRI OBJ FIL SEQ INC
SCOTT                          EMP                            MLOG$_EMP
                               NO YES NO NO NO NO
Elapsed: 00:00:00.01
SCOTT @ jcave102 Local> desc mlog$_emp
Name                                                  Null?    Type
EMPNO                                                          NUMBER(4)
SNAPTIME$$                                                     DATE
DMLTYPE$$                                                      VARCHAR2(1)
OLD_NEW$$                                                      VARCHAR2(1)
CHANGE_VECTOR$$                                                RAW(255)and you'll see that most of the interesting bits are in the RAW(255) CHANGE_VECTOR$$ column.
Justin

Why sys does not refresh fast ?

Hi everyone.
The following test was made on a Windows XP Professional 2002 SP 2 box.
I don't understand why sys user does not perform a fast refresh on a materialized view. With others users it works fine. May be I am missing something.
This is my simple test case:
C:\>sqlplus "sys/sys as sysdba"
SQL*Plus: Release 9.2.0.1.0 - Production on Sun Nov 6 14:44:51 2005
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> create table my_objects as select * from user_objects;
Table created.
SQL> alter table my_objects add primary key(object_id);
Table altered.
SQL> create materialized view log on my_objects with primary key including new values;
Materialized view log created.
SQL> create materialized view mv_my_objects
2 refresh fast on demand
3 as select * from my_objects;
Materialized view created.
SQL> select count(*) from my_objects;
COUNT(*)
13535
SQL> select count(*) from mv_my_objects;
COUNT(*)
13535
SQL> delete from my_objects where rownum <=100;
100 rows deleted.
SQL> commit;
Commit complete.
SQL> select count(*) from mv_my_objects;
COUNT(*)
13535
SQL> select count(*) from my_objects;
COUNT(*)
13435
SQL> exec dbms_mview.refresh('mv_my_objects', 'F');
PL/SQL procedure successfully completed.
SQL> select count(*) from mv_my_objects;
COUNT(*)
13535
C:\>sqlplus scott/tiger
SQL*Plus: Release 9.2.0.1.0 - Production on Sun Nov 6 14:50:31 2005
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> create table my_objects as select * from user_objects;
Table created.
SQL> alter table my_objects add primary key(object_id);
Table altered.
SQL> create materialized view log on my_objects with primary key including new values;
Materialized view log created.
SQL> create materialized view mv_my_objects
2 refresh fast on demand
3 as select * from my_objects;
Materialized view created.
SQL> select count(*) from my_objects;
COUNT(*)
8
SQL> select count(*) from mv_my_objects;
COUNT(*)
8
SQL> delete from my_objects where rownum <=4;
4 rows deleted.
SQL> commit;
Commit complete.
SQL> select count(*) from mv_my_objects;
COUNT(*)
8
SQL> select count(*) from my_objects;
COUNT(*)
4
SQL> exec dbms_mview.refresh('mv_my_objects', 'F');
PL/SQL procedure successfully completed.
SQL> select count(*) from mv_my_objects;
COUNT(*)
4
SQL>

I agree, never create objects under sys schema. I noticed that behaviour just by accident, making some tests while reading the data warehousing manual.
It is more surprising the fact Oracle lets you create the log, and also throws a "PL/SQL procedure successfully completed" message when you use it.
Regards.

Modal popup window refresh the parent (calling) window/view

I have a modal popup window that is adding detail records. When this window is closed via the Hide method in my controller I would like to refresh the parent (calling) window/view.
What is the best way to do this?
Regards,
Diane

Here's my process.....
2-windows & 3 views
Window 1 - Selection View and Detail View
Window 2 - Add View (used as a modal popup window called by a button click on the detail view)
Selection View has all the options for obtaining a list of data for the detail view. The detail view has an Add button. Component controller has the hide method and access to the other components that do the update/query methods. On the detail view the user can click Add and a popup modal window shows. User enters data and clicks either the add or cancel button. The Detail view needs to refresh to show the additional data that has been added by the modal window. There are calcuated values in the detail view from a supply function. This function is not running and the values are not changed.
What should be put in the hide method that will cause the detail view to obtain new data and supply the calculated values? If I was using the Add view as part of the same window as the detail/selection views I'd just put in a navigation link between the detail and add views and fire the plug. I like the idea of the popup window so I'd like to get this to work.
I put the wdContext.initialize() in the hide method - which yes - caused the detail view to run - however the context lost all the key values so I received a data not found. I then tried to initialize those nodes that did not contain the key values but the detail view did not display new values.
Thanks for any ideas.....Diane
Edited by: Diane Fuller on Jan 8, 2009 6:48 AM

Can we do Dml statements on materialize views

I want to know can we do Dml statements on materialize views .If yes, how

Can you? Maybe. Depends on how you created the materialized view. Should you? Maybe. Are you running a multi-master environment? Or are you using materialized views for one-way replication? If you are doing one-way replication, do you want your DML changes to be retained beyond the next refresh of the materialized view?
Justin

Unable to hide Refresh link in "No Result" view in BISE1 10.1.3.2.1 version

Hi experts,
I am using Business Intelligence Standard Edition One 10.1.3.2.1 version.
I am unable to hide the Refresh link in No Result view, I have checked all the blogs and forums related to this problem. They have asked to use the following script but it is not working for me in my BI version, still the refresh link exists.
<script type="text/javascript">

</script>
Please provide me a solution with exact script which suite to my version.
Thanks & Regards,
Raj

Hi,
Thanks for your help.
The code worked well.
Then I am showing my report as "Link - Within the dashboard" as a option in display result of report property.
So there is Return link and refresh link shown in my No Result view. If I use your code it removes both the link. But I need only the Refresh link to be removed. So I just added a code with your code to have the return link without the refresh link.

Regards,
Raj

Refresh All option returns all zeros

Hi,
I am using MS office 2003 and Smart view 9.3.1.4. When I use refresh all options, it rerurns zeros in all sheets.
Has anybody ever faced similar kind of issue? Can you please let me know the possible ressolution?
Thanks in advance.

One possibility is that connection is timing out between server and client. Update the values on on the client machine(test machine) and see whether this resolves the scenario:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
ReceiveTimeout 900000
KeepAliveTimeout 900000
ServerInfoTimeout 900000
http://support.microsoft.com/kb/181050
http://support.microsoft.com/kb/813827

Refresh Fast option in Materialize view

Similar Messages

Maybe you are looking for