Query on Materialized Views

Hi,
Could any of you please confirm that we always require a Materialized View Log on the table(s) at the Master site for FAST REFRESH to work on the Materialized View.
If we do not have a Materialized View Log on, the Materialized View always do a COMPLETE REFRESH.
Thanks,
Chanjal

http://download.oracle.com/docs/cd/E11882_01/server.112/e10713/schemaob.htm#CNCPT411

Similar Messages

Select query in materialized view with two dblinks

Hi All,
We have oracle 10g On windows.
We are trying to create materialized view. Scenario is we have base table on other database and we are creating mview on different database.
Basa database have two schema's and i am selecting records from that two schema's using two private db links.
But when i am tryin gto create mview its not getting created. After 15 hrs. its still showing creation command and not finished.
Query is :-
Is it good practice to have two db links in select query of materialized view.

Billy Verreynne wrote:
Chanchal Wankhade wrote:
Is it good practice to have two db links in select query of materialized view.Same db link being used twice, or two different db links?
If the former, you ideally want the local Oracle db to send the join to the remote database, and for the remote database to drive the join between those 2 tables. There is a hint (<i>driving_site</i>) that can be used - or the join query can be defined on the remote database as a view, and the local materialised view can then use that remote view.
If you have 2 different db links and joining across these - usually a bad idea to perform distributed database joins. There are lots of limitations as to how the tables can be joined. Worse case, full table scans of both remote tables, pulling all the rows from the 2 remote database tables to the local database, and joining these on the local database.
I have seen some severe performance issues in the past as a result of distributed joins. I'll rather use 2 materialised views for pulling both distributed tables's data locally, and then do the join on local data (using indexes, partition pruning, etc)Hi Billy,
My scenario is i have two database database A and database B. Database A is having two schema's SCOTT AND HR. SCOTT schema have select privileges on HR schema.
DB LINK is between Database B to Database A. name is db.link.B.A.oracle.com.
What if i priovide while creating materialized view, the schema name before the table name in database B for this particuler table so it will pick up the table from that schema using same DB LINK(db.link.B.A.oracle.com.) that i am using to fetch records from SCOTT schema.
Above schnario is like two base schema's and one db link using two schema.

Query on Materialized view and materialized view log

I am creating a materialized view something like this.but getting following error:
ERROR at line 1:
ORA-12032: cannot use rowid column from materialized view log on "SCOTT"."EMP"
SQL> create snapshot log on scott.emp;
Materialized view log created.
SQL> create materialized view scott_emp refresh fast on demand as select deptno,sum(sal) sum_sal from scott.emp group by deptno;
ERROR at line 1:
ORA-12032: cannot use rowid column from materialized view log on "SCOTT"."EMP"
Note when i have my query in materialized view as "select * from emp;" in place of
"select deptno,sum(sal) sum_sal from scott.emp group by deptno;" This code works fine.
How do i have a materialized with with a group by clause.
Thanks in Advance

Got the answer myself.
I wasnt adding all the required columns.
CREATE MATERIALIZED VIEW LOG ON scott.emp
WITH SEQUENCE, ROWID (<all the required columns>)
INCLUDING NEW VALUES;
Anyways,
Thanks guys...

Help needed in query for Materialized View

Hi,
I want to create a materialized view which has some precalcultaed values.
I have four dimension tables out of which one is a Time Dimension table with levels as Year->Quarter->Month.
The precalculations are the moving averages and cummulative values of Sales Amt on the dimension values over a period of 4 Months.
The dimension tables are Clients, Products, Channel, Time.
Fact Table is Sales_Fact which will have the sales amount for different members of the dimension.
Since my fact table is very huge, i want to create a materialized view where i could store the required calculated measures, here Moving Average of Sales Amt for each Client, Product, Channel dimensions over a period of 4 Months.
Can anybody help with writing the query for this..Any help in this regard will be appreciated..
Please give me suggestions for this..

Check this link.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14223/aggreg.htm#sthref1612
Regards
Raj

Help with sql query on materialized view logs

I am in need of a query to find out what tablespace and snap shot site a long list of materialized view logs are associated with.
something like below except tablespace and snap_shot_site are not an option for this table.
select log_owner, master, log_table, tablespace, snap_shot_site from dba_mview_logs;

What is the refresh method set as?
Could you paste the full MV log creation script and the corresponding MV creation script.

Query against materialized view from stored procedure brings back empty row

I have a stored procedure that runs a query against a materialized view. When I run the query outside the SP it works just fine. When I change the MV to a table name, the SP works. When I change it back to the MV i get an empty row. Any ideas? The code is below:
PROCEDURE getAuth     (p_naid        IN NUMBER,
                         p_scope       IN VARCHAR2,
                         o_xml_data    OUT SYS_REFCURSOR
                         ) IS
BEGIN
    IF p_scope = 'Approved' THEN
      OPEN o_xml_data FOR
        SELECT naid,
               p_naid,
               auth_type,
               xml_data
        FROM some_mv
        WHERE naid = p_naid;
      RETURN;
      CLOSE o_xml_data;
... the rest of the procedure ...

does procedure contain EXCEPTION handler?
if so, then remove, delete & eliminate EXCEPTION handler (at least during testing & debugging)

UPDATING the query in materialized view

Hi,
i have a little doubt in Materialized view. i created a materialized view and log with the following query,
create table test_mv (a number ,b number )
alter table test_mv add constraint t_pk primary key ( a );
insert into test_mv values (1,2);
insert into test_mv values(2,2);
insert into test_mv values(3,2);
insert into test_mv values(4,2);
insert into test_mv values(5,2);
commit;
CREATE MATERIALIZED VIEW LOG ON test_mv
WITH SEQUENCE, ROWID
*(a,b)*
INCLUDING NEW VALUES;
CREATE MATERIALIZED VIEW product_sales_mv
ENABLE QUERY REWRITE
AS SELECT b from test_mv;
Now i want to update the query in the MV as 'Select a from test_mv' . for that i tried with
*'ALTER MATERIALIZED VIEW product_sales_mv AS SELECT a from test_mv;'*
But it throwing error,
Error starting at line 5 in command:
alter MATERIALIZED VIEW product_sales_mv AS SELECT b from test_mv
Error report:
SQL Error: ORA-00933: SQL command not properly ended
+00933. 00000 - "SQL command not properly ended"+
*Cause:+
*Action:+
i guess i am doing wrong. kindly help me here. i want to update it without drop and recreate.
thanks,
Jeevanand.Ke

Hi Jeeva,
No. you cannot add or drop columns to the materialized view using the ALTER Statement.
To Change the Structure of the view , drop and re-create the materialized view.
To Alter a materialized view log, You can use the ALTER MATERIALIZED VIEW LOG. By this,
You can add new columns to a materialized view log.
ALTER MATERIALIZED VIEW LOG ON sggi_mrps.emp ADD(deptno);Thanks,
Shankar
Edited by: Shankar Viji on Aug 24, 2012 2:11 AM

Please help with the query creating Materialized View

Hi,
We are using the below query to create a Materialized View but it has been running since 3 hours. It is an Oracle 9i database running in HP-UX.The quey is as follows,
(SELECT
/*+ use_nl(A) parallel (A,4)*/
A.ICD_CODE AS ICD_CODE,
A.ICD_DESC AS ICD_DESC,
A.PROC_GROUP as PROC_GROUP,
B.COMPL_ICD_CODE AS COMPL_ICD_CODE,
B.COMPL_GRP_TXT AS COMPL_GRP_TXT,
C.PROC_TYPE AS PROC_TYPE ,
C.I_O_IND AS I_O_IND,
C.DISC_MON AS QUARTER ,
B.PAT_KEY AS PAT_KEY ,
D.COMPL_TYPE_TXT AS COMPL_TYPE_TXT ,
C.PROV_ID AS PROV_ID ,
A.SPECIALTY AS SPECIALTY
FROM
EES_ICD_9_CODE A ,
EES_CLINICAL_COMPL_DATA B,
EES_CLINICAL_DATA C,
EES_CLINCL_COMPL_ICD D
WHERE A.ICD_CODE= B.ICD_CODE
                AND B.ICD_CODE= C.ICD_CODE
                AND B.COMPL_ICD_CODE=D.ICD_9_CD
                AND B.PAT_KEY=C.PAT_KEY
                AND B.COMPL_ICD_CODEB.ICD_CODE
                AND C.PROC_TYPE 'L'
                AND B.COMPL_GRP_TXT'Reoperations'
                AND D.COMPL_TYPE_TXT'Intra-operative Misadventure'
                AND C.DISC_MON>='2003101'
                AND A.SPECIALTY='Colo-Rectal')
union
(SELECT
/*+ use_nl(A) parallel (A,4)*/
A.ICD_CODE AS ICD_CODE,
A.ICD_DESC AS ICD_DESC,
A.PROC_GROUP as PROC_GROUP,
B.COMPL_ICD_CODE AS COMPL_ICD_CODE,
B.COMPL_GRP_TXT AS COMPL_GRP_TXT,
C.PROC_TYPE AS PROC_TYPE ,
C.I_O_IND AS I_O_IND,
C.DISC_MON AS QUARTER ,
B.PAT_KEY AS PAT_KEY ,
D.COMPL_TYPE_TXT AS COMPL_TYPE_TXT ,
C.PROV_ID AS PROV_ID ,
A.SPECIALTY AS SPECIALTY
FROM
EES_ICD_9_CODE A ,
EES_CLINICAL_COMPL_DATA B,
EES_CLINICAL_DATA C,
EES_CLINCL_COMPL_ICD D
WHERE A.ICD_CODE= B.ICD_CODE
                AND B.ICD_CODE= C.ICD_CODE
                AND B.COMPL_ICD_CODE=D.ICD_9_CD
               AND B.PAT_KEY=C.PAT_KEY
                AND B.COMPL_ICD_CODEB.ICD_CODE
                AND C.PROC_TYPE 'L'
                --AND B.COMPL_GRP_TXT'Reoperations'
                AND D.COMPL_TYPE_TXT='Intra-operative Misadventure'
                AND B.PROC_DAY=C.PROC_DAY
                AND C.DISC_MON>='2003101'
                AND A.SPECIALTY='Colo-Rectal')
union
(SELECT
/*+ use_nl(A) parallel (A,4)*/
A.ICD_CODE AS ICD_CODE,
A.ICD_DESC AS ICD_DESC,
A.PROC_GROUP as PROC_GROUP,
B.COMPL_ICD_CODE AS COMPL_ICD_CODE,
B.COMPL_GRP_TXT AS COMPL_GRP_TXT,
C.PROC_TYPE AS PROC_TYPE ,
C.I_O_IND AS I_O_IND,
C.DISC_MON AS QUARTER ,
B.PAT_KEY AS PAT_KEY ,
D.COMPL_TYPE_TXT AS COMPL_TYPE_TXT ,
C.PROV_ID AS PROV_ID ,
A.SPECIALTY AS SPECIALTY
FROM
EES_ICD_9_CODE A ,
EES_CLINICAL_COMPL_DATA B,
EES_CLINICAL_DATA C,
EES_CLINCL_COMPL_ICD D
WHERE A.ICD_CODE= B.ICD_CODE
                AND B.ICD_CODE= C.ICD_CODE
                AND B.COMPL_ICD_CODE=D.ICD_9_CD
                AND B.PAT_KEY=C.PAT_KEY
                AND B.COMPL_ICD_CODEB.ICD_CODE
                AND C.PROC_TYPE 'L'
                AND B.COMPL_GRP_TXT='Reoperations'
                --AND D.COMPL_TYPE_TXT='Intra-operative Misadventure'
                AND B.PROC_DAY>C.PROC_DAY
                AND C.DISC_MON>='2003101'
                AND A.SPECIALTY='Colo-Rectal')
The explain plan is as follows,
PLAN_TABLE_OUTPUT
| Id | Operation                          | Name                    | Rows | Bytes |TempSpc| Cost | TQ    |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT                   |                          | 46935 | 6716K|       | 10648 |        |      |            |
|   1 | SORT UNIQUE                       |                          | 46935 | 6716K|    14M| 10648 | 45,14 | P->S | QC (RAND) |
|   2 |   UNION-ALL                        |                          |       |       |       |       | 45,13 | P->P | HASH       |
|* 3 |    HASH JOIN                       |                          | 42801 | 6102K|       | 4640 | 45,13 | PCWP |            |
|* 4 |     TABLE ACCESS FULL              | EES_CLINCL_COMPL_ICD     |   875 | 18375 |       |     2 | 45,02
|* 5 |     HASH JOIN                      |                          | 41552 | 5072K|    14M| 4638 | 45,13 | PCWP |            |
|* 6 |      TABLE ACCESS FULL             | EES_CLINICAL_DATA        | 1430K|    40M|       | 2855 | 45,03
|* 7 |      HASH JOIN                     |                          |   628K|    56M|       |   494 | 45,10 | P->P | HASH       |
|* 8 |       TABLE ACCESS FULL            | EES_ICD_9_CODE           |    37 | 2183 |       |     1 | 45,08
|* 9 |       TABLE ACCESS BY INDEX ROWID | EES_CLINICAL_COMPL_DATA | 2090K|    71M|       |   49
| 10 |        BITMAP CONVERSION TO ROWIDS |                          |       |       |       |       |        |
|* 11 |         BITMAP INDEX FULL SCAN     | INX_COMPL_GRP            |       |       |       |       |        |
|* 12 |    TABLE ACCESS BY INDEX ROWID     | EES_CLINICAL_DATA        |     1 |    33 |       |     1
| 13 |     NESTED LOOPS                   |                          | 1327 |   196K|       |   947 | 45,13 | PCWP |            |
|* 14 |      HASH JOIN                     |                          | 60205 | 6996K|       |   495 | 45,13 | PCWP |            |
| 15 |       TABLE ACCESS BY INDEX ROWID | EES_CLINCL_COMPL_ICD     |    36 |   756 |       |
|* 16 |        INDEX RANGE SCAN            | COMPL_TYPE_TXT_3         |     1 |       |       |     1 |
|* 17 |       HASH JOIN                    |                          | 1420K|   132M|       |   494 | 45,13 | PCWP |            |
|* 18 |        TABLE ACCESS FULL           | EES_ICD_9_CODE           |    37 | 2183 |       |     1 | 45,11
|* 19 |        TABLE ACCESS BY INDEX ROWID | EES_CLINICAL_COMPL_DATA | 4722K|   175M|       |   49
| 20 |         BITMAP CONVERSION TO ROWIDS|                          |       |       |       |       |        |      |
| 21 |          BITMAP INDEX FULL SCAN    | INX_COMPL_GRP            |       |       |       |       |        |
|* 22 |      INDEX RANGE SCAN              | EES_CLINICAL_DATA_IND1   |     1 |       |       |     2 | 45,13
|* 23 |    HASH JOIN                       |                          | 2807 |   416K|       | 4695 | 45,13 | PCWP |            |
| 24 |     TABLE ACCESS FULL              | EES_CLINCL_COMPL_ICD     |   911 | 19131 |       |     2 | 45,06
|* 25 |     HASH JOIN                      |                          | 2617 |   334K|    15M| 4693 | 45,13 | PCWP |            |
|* 26 |      TABLE ACCESS FULL             | EES_CLINICAL_DATA        | 1430K|    45M|       | 2855 | 45,07
|* 27 |      HASH JOIN                     |                          |   791K|    74M|       |   305 | 45,12 | P->P | HASH       |
|* 28 |       TABLE ACCESS FULL            | EES_ICD_9_CODE           |    37 | 2183 |       |     1 | 45,09
|* 29 |       TABLE ACCESS BY INDEX ROWID | EES_CLINICAL_COMPL_DATA | 2632K|    97M|       |   30
| 30 |        BITMAP CONVERSION TO ROWIDS |                          |       |       |       |       |        |
|* 31 |         BITMAP INDEX SINGLE VALUE | INX_COMPL_GRP            |       |       |       |       |        |
Predicate Information (identified by operation id):
   3 - access("B"."COMPL_ICD_CODE"="D"."ICD_9_CD")
   4 - filter("D"."COMPL_TYPE_TXT"'Intra-operative Misadventure')
   5 - access("B"."ICD_CODE"="C"."ICD_CODE" AND "B"."PAT_KEY"="C"."PAT_KEY")
   6 - filter("C"."PROC_TYPE"'L' AND "C"."DISC_MON">=2003101)
   7 - access("A"."ICD_CODE"="B"."ICD_CODE")
   8 - filter("A"."SPECIALTY"='Colo-Rectal')
   9 - filter("B"."COMPL_ICD_CODE""B"."ICD_CODE")
11 - filter("B"."COMPL_GRP_TXT"'Reoperations')
12 - filter("B"."ICD_CODE"="C"."ICD_CODE" AND "C"."PROC_TYPE"'L' AND "B"."PROC_DAY"="C"."PROC_DA
14 - access("B"."COMPL_ICD_CODE"="D"."ICD_9_CD")
16 - access("D"."COMPL_TYPE_TXT"='Intra-operative Misadventure')
17 - access("A"."ICD_CODE"="B"."ICD_CODE")
18 - filter("A"."SPECIALTY"='Colo-Rectal')
19 - filter("B"."COMPL_ICD_CODE""B"."ICD_CODE")
22 - access("B"."PAT_KEY"="C"."PAT_KEY")
23 - access("B"."COMPL_ICD_CODE"="D"."ICD_9_CD")
25 - access("B"."ICD_CODE"="C"."ICD_CODE" AND "B"."PAT_KEY"="C"."PAT_KEY")
       filter("B"."PROC_DAY">"C"."PROC_DAY")
26 - filter("C"."PROC_TYPE"'L' AND "C"."DISC_MON">=2003101)
27 - access("A"."ICD_CODE"="B"."ICD_CODE")
28 - filter("A"."SPECIALTY"='Colo-Rectal')
29 - filter("B"."COMPL_ICD_CODE""B"."ICD_CODE")
31 - access("B"."COMPL_GRP_TXT"='Reoperations')
Note: cpu costing is offPlease help.

Try removing the hints.
Is 47,000 a reasonable estimate of how many rows you expect in the results?
See these posts for other information that you should supply.
HOW TO: Post a SQL statement tuning request
HOW TO: Post a SQL statement tuning request - template posting
When your query takes too long
When your query takes too long ...

Query on materialized view

Hi,
Materialized view can't be renamed, so how can I reduce the downtime for any new column addition in the materialized view.
Regards,
Koushik

Agree with your reply.
I like to do the following steps assuming there is already a materialized view created on a base table :
1. Add any new column to the base table.
2. Drop and recreate the mlog table.
3. execute the statement "alter materialized view <mv_name> consider fresh" to simulate the error "ORA-12034: snapshot log on "<schema>"."<mv_name>" younger than last refresh"
4. Create a new MV with the additional columns and with a different name.
5. Drop the existing(old) MV.
6. Rename the new MV with the name of the old one.
Now this renaming is not possible. Is there any alternative way do the thing whatever I am trying to do by the above steps.
Can you please also tell me what is use of "ENABLE QUERY REWRITE" option during creation of a materialized view.
Thanks & Regards,
Koushik

Query on Materialized View Logs

We need a denormalised data step-up, we decided on implementing Materialized Views and started working on them. I have created Materialized View log on a table using below mentioned syntax
CREATE MATERIALIZED VIEW LOG ON <table_name> WITH ROWID
I have tested it and its working fine.A Strange error I am facing is, after an hour or so the materialised view gets corrupted and applicatin users gets an error saying error with the materialised view log.
The log entry in the data dictionary gets deleted. Later I have to execute DROP on the log to completely remove it.
I am confused how this can happen.

What is the refresh method set as?
Could you paste the full MV log creation script and the corresponding MV creation script.

Query Regarding Materialized View

Hi,
I have materialized view mv_test which is derived from a base table test. My question is if I modify any of the column width of table test,do it effect on materialized view refresh?If so what are the procedures I need to follow if I want to modify the base table column size?
Thanks
Hena

user11253970 wrote:
Hi,
I have materialized view mv_test which is derived from a base table test. My question is if I modify any of the column width of table test,do it effect on materialized view refresh?Yes. (Materialized) View is nothing but a select statement that will get executed on the base table when the view is accessed. So, you don't have to do anything special on the view when you change the datatype of the base table.
If so what are the procedures I need to follow if I want to modify the base table column size?You don't have to follow any procedure as such. Just make sure your data in the base table does not get affected by the change ;-)
-Arun
>
>
Thanks
Hena

Query Regarding Materialized view invalid

Hi,
What is the reason for the Materialized view invalid.

Question is vague. Can you be more specific?

Query against materialized view awful after refresh of Mview

We have a materialized view defined to refresh complete daily at 5am. YOu can run queries against the MV alone or joining it to other tables. Results come back in 2 or 3 seconds. Once the MView refreshes at 5am - those same queries now take 15 minutes or even more sometimes to complete. WHY IS THIS HAPPENING?? Help anyone?

okay this is better... sorry...
this is the GOOD EXPLAIN PLAN:
PLAN_TABLE_OUTPUT
| Id | Operation                         | Name             | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT                  |                   |     1 |   127 | 1665 |
|   1 | SORT AGGREGATE                   |                   |     1 |   127 |       |
|   2 |   NESTED LOOPS                    |                   |     1 |   127 | 1665 |
|   3 |    NESTED LOOPS                   |                   |     1 |   113 | 1664 |
|   4 |     NESTED LOOPS                  |                   |     1 |    99 | 1663 |
|   5 |      NESTED LOOPS                 |                   |     1 |    88 | 1662 |
|* 6 |       HASH JOIN ANTI              |                   |     1 |    70 | 1661 |
|* 7 |        TABLE ACCESS BY INDEX ROWID| CONTACT           | 3815 |   201K| 1534 |
|   8 |         AND-EQUAL                 |                   |       |       |       |
|* 9 |          INDEX RANGE SCAN         | IDX_CNT__C_STATE |       |       |       |
|* 10 |          INDEX RANGE SCAN         | IDX_CNT__STATUS   |       |       |       |
| 11 |        INDEX FAST FULL SCAN       | PK_RPP            | 69277 | 1082K|   120 |
|* 12 |       TABLE ACCESS BY INDEX ROWID | REP_PROFILE       |     1 |    18 |     1 |
|* 13 |        INDEX UNIQUE SCAN          | PK_C19            |     1 |       |       |
|* 14 |      INDEX UNIQUE SCAN            | PK_B01            |     1 |    11 |       |
|* 15 |     INDEX UNIQUE SCAN             | PK_B02            |     1 |    14 |       |
|* 16 |    INDEX UNIQUE SCAN              | PK_RCN            |     1 |    14 |       |
Predicate Information (identified by operation id):
   6 - access("B"."CONTACT_ID"="RPP"."PARTNERSHIP_ID")
   7 - filter("B"."C_STATE"='GA' AND "B"."C_LAST"<>'Name Unknown' AND
              "B"."STATUS"='Confirmed')
   9 - access("B"."C_STATE"='GA')
10 - access("B"."STATUS"='Confirmed')
12 - filter("C19"."TERR1"='46')
13 - access("B"."CONTACT_ID"="C19"."CONTACT_ID")
14 - access("B"."FIRM_ID"="B01"."FIRM_ID")
15 - access("B"."OFFICE_ID"="B02"."OFFICE_ID")
16 - access("B"."CONTACT_ID"="RCN"."CONTACT_ID")
Note: cpu costing is off
38 rows selected.

Query on Materialized View created on Prebuilt Table

Hi,
I am trying to explain the scenario below on Materialized View which I want to setup for our database.
I have created a materialized view on prebuilt table on target side on primary key. Now for purging history data from target side which are more than 5 years old I have executed the following steps:
1. Dropped the materialized view which was created previously on prebuilt table in target side.
2. Deleted the data from that target table which are more than 5 years old.
3. Now created the materialized view again on the prebuilt table.
Now, the problem which I am facing is that - if any changes happens in the source side during the above 3 steps on the target side those changed records were not captured even after successfully building materialized view again in the target side (i.e. after completing step-3 of above the intermediate changed records were not captured).
Can you please let me know exactly what I am doing wrong here and how can I achieve my intended result.
Regards,
Koushik

See matelink for doc id *252246.1*. The document id says: A materialized view was defined on a Table A. This table had a referential constraint defined against another table, Table B. This constraint was defined as 'ON DELETE CASCADE'. An 'ON DELETE CASCADE' constraint is not allowed on views but as the constraint was created on the table underlying the materialized view, Table A, it could be created although it would behave as a constraint on the view. The constraint existed for performance reasons, which is permitted, and was disabled when created but a general script had been run to enable all constraints. When a delete was performed on Table B the error above was reported although there was no view created on Table B.

Fast refresh of a materialized view works incorrect

Hi All,
I have created a MV using the sql below:
create materialized view WLS
refresh fast
enable query rewrite
as
SELECT Employees.USER_NAME,
       Permissions.ROLE_NAME,
       Vouchers.VOUCHER_ID,
       EmployeeRoles.FROM_DATE,
       EmployeeRoles.TO_DATE,
       VoucherPatterns.rowid   ACC_VOUCHER_PATTERNS_ROW_ID,
       Vouchers.rowid          ACC_VOUCHERS_ROW_ID,
       Ledgers.rowid           ACC_LEDGERS_ROW_ID,
       Employees.rowid         BANK_EMPLOYEES_ROW_ID,
       IncExcUnits.rowid       INC_EXC_UNITS_ROW_ID,
       EmployeeRoles.rowid     BANK_EMPLOYEE_ROLES_ROW_ID,
       ParentRoles.rowid       PARENT_ROLES_ROW_ID,
       Roles.rowid             ROLES_ROW_ID,
       Permissions.rowid       PERMISSIONS_ROLES_ROW_ID,
       RolesMemberships.rowid ROLES_MEMBERSHIPS_ROW_ID
FROM ACC_VOUCHER_PATTERNS        VoucherPatterns,
       ACC_VOUCHERS                Vouchers,
       ACC_LEDGERS                 Ledgers,
       BANK_EMPLOYEES              Employees,
       BANK_EMPLOYEE_INC_EXC_UNITS IncExcUnits,
       BANK_EMPLOYEE_ROLES         EmployeeRoles,
       ROLES                       ParentRoles,
       ROLES                       Roles,
       ROLES                       Permissions,
       ROLES_MEMBERSHIPS           RolesMemberships
WHERE Vouchers.TYPE_VOUCHER_PATTERN_FK =
       VoucherPatterns.VOUCHER_PATTERN_ID
   AND VoucherPatterns.CONFIRM_COUNT = 2
   AND Vouchers.STATE = 'ISU'
   AND Vouchers.LEDGER_FK = Ledgers.LEDGER_ID
   AND Employees.ID = IncExcUnits.BKEM_ID(+)
   AND (((IncExcUnits.INC_EXCLUD_TYPE IS NULL OR
       IncExcUnits.INC_EXCLUD_TYPE != 'EXC') AND
       Ledgers.ORGANIZATION_UNIT_FK = Employees.ORGU_ID) OR
       (Ledgers.ORGANIZATION_UNIT_FK = IncExcUnits.ORGU_ID AND
       IncExcUnits.INC_EXCLUD_TYPE = 'INC'))
   AND EmployeeRoles.BKEM_ID = Employees.ID
   AND ParentRoles.ID = EmployeeRoles.ROLS_ID
   AND ParentRoles.IS_PERMISSION = 'N'
   AND ParentRoles.ROLE_TYPE = 'ORG'
   AND ParentRoles.ID = Roles.ROLS_ID
   AND Roles.IS_PERMISSION = 'N'
   AND Roles.ROLE_TYPE = 'SYS'
   AND Permissions.IS_PERMISSION = 'Y'
   AND Permissions.ROLE_NAME = 'ACC_AccVoucherConfirm'
   AND Roles.ID = RolesMemberships.ROLS_ID
   AND Permissions.ID = RolesMemberships.ROLS_ID_MEMBER_OF;
Then I have issued a SELECT * though it and that works fine.
And then I've manipulated the data in some tables such that according to MV's WHERE clause it must return no rows.
Intuitively before refreshing the MV it will return the data last placed on it,
But it return the same data after issuing the following command in PL/SQL Developer:
call dbms_mview.refresh(list => 'WLS', method => 'F');
And unfortunately the following will correct it:
call dbms_mview.refresh(list => 'WLS', method => 'C');
Why the fast refresh of a fast refreshable MV does not work fine while its complete refresh works good?
How ever after undoing made changes to those tables and issuing the fast refresh using the following command the MV will contain correct updated data:
call dbms_mview.refresh(list => 'WLS', method => 'F');
It seems that it has bug in deleting rows from Fast Refreshable MV but upserts work fine.
I've tried to simulate the problem for a simpler query with simple tables containing some sample data but those don't have any problem.
Please help me,
Thanks

Thanks Martin,
Finally I've discovered one of possible several situations in which a MV fast refreshed incorrectly.
This is happened when an OR condition exists among several AND conditions and at least one outer join symbol there exists!
this is the scenario:
-- create two sample tables
create table t as select 1 a, 2 b from dual;
create table j as select 1 a, 2 b from dual;
-- defining primary keys
alter table t add constraint tp primary key (a);
alter table j add constraint jp primary key (a);
-- creating MV Logs
create materialized view log on t with primary key, rowid;
create materialized view log on j with primary key, rowid;
-- creating Fast Refresh MV with a sample query
create materialized view mvt refresh fast enable query rewrite as
select t.a, j.b, t.rowid tr, j.rowid jr from t,j where t.a = j.a(+)
and (t.b = j.b or t.a = t.b);
-- select through MV, the MV returns correct data
select * from mvt;
     A    B    TR                    JR
    1    2    AAAYwQAAEAAFhwzAAA    AAAYwRAAEAAFhw7AAA
-- intentionally manipulate the data to the query returns no rows
update j set a = 2;
commit;
-- query the select of MV
select t.a, j.b, t.rowid tr, j.rowid jr from t,j where t.a = j.a(+)
and (t.b = j.b or t.a = t.b);
-- returns now rows, The query rewrite does not work here!
-- select through MV, the MV returns correct data because it has not refreshed yet!
select * from mvt;
     A    B    TR                    JR
    1    2    AAAYwQAAEAAFhwzAAA    AAAYwRAAEAAFhw7AAA
-- fast refreshing the mv and issuing select again
call dbms_mview.refresh(list => 'MVT', method => 'F');
select * from mvt;
     A    B        TR                    JR
    1    null    AAAYwuAAEAAFh2jAAA    null
-- A change is occured but it is not correct, it must returns no rows!
-- query the select of MV
select t.a, j.b, t.rowid tr, j.rowid jr from t,j where t.a = j.a(+)
and (t.b = j.b or t.a = t.b);
     A    B        TR                    JR
    1    null    AAAYwuAAEAAFh2jAAA    null
-- Query rewrite does work here! because appending a neutral "and 1=1" conditions will show the correct empty result:
select t.a, j.b, t.rowid tr, j.rowid jr from t,j where t.a = j.a(+)
and (t.b = j.b or t.a = t.b) and 1=1;
-- returns no rows
-- now complete refreshing the MV and achieving the correct result:
call dbms_mview.refresh(list => 'MVT', method => 'C');
select * from mvt;
-- returns no rows
Is this a BUG?
Any suggestions?

Query on Materialized Views

Similar Messages

Maybe you are looking for