How to test benefits of Materialized View

We have a system have high concurrency of update,insert and select. We have several reports that have many complex queries involving joins of around 15-20 tables.
We have tried using materialized view for generating reports. But how do we conclude difference in performance after using materialized view.

>
every minutes we want to refresh data.
data refresh is on demand.
>
Please explain. Is the refresh every minute? Or is the refresh 'on demand'?
If you can't post an example of what you are actually doing how do you expect anyone to be able to help. You don't have to post your actual code or DDL but you do need to post code and DDL that will reproduce the problem or we can't really help.

Similar Messages

How can I create a materialized view based on hierarchical cube query?

Hi,
database version 10gR2.
When i try to create MV for sql below, i got error .
I tried creating MV log in several ways, but still, keep getting the same error.
SQL Error: ORA-12015: cannot create a fast refresh materialized view from a complex query
12015. 00000 - "cannot create a fast refresh materialized view from a complex query"
*Cause:    Neither ROWIDs and nor primary key constraints are supported for
           complex queries.
*Action:   Reissue the command with the REFRESH FORCE or REFRESH COMPLETE
           option or create a simple materialized view.So, I wonder if it is possible to create MV based on sql below?
if yes, how should I do it?
if no, what is the alternative?
select
      coalesce(UP_ORG_ID_6, UP_ORG_ID_5, UP_ORG_ID_4, UP_ORG_ID_3, UP_ORG_ID_2, UP_ORG_ID_1) as ORG_ID,
      a.day_id as day_id,
      a.TRADE_TYPE_ID as TRADE_TYPE_ID,
      a.CUST_ID,
      coalesce(UP_CODE_6, UP_CODE_5, UP_CODE_4, UP_CODE_3, UP_CODE_2, UP_CODE_1) as product_id,
      QUANTITY_UNIT,
      COST_UNIT,
      A.SOURCE_ID as SOURCE_ID,
      SUM(CONTRACT_AMOUNT) as CONTRACT_AMOUNT,
      SUM(CONTRACT_COST) as CONTRACT_COST,
      SUM(SALE_AMOUNT) as SALE_AMOUNT,
      SUM(SALE_COST) as SALE_COST,
      SUM(ACTUAL_AMOUNT) as ACTUAL_AMOUNT,
      SUM(ACTUAL_COST) as ACTUAL_COST,
      SUM(TRADE_COUNT) as TRADE_COUNT
from DM_F_LO_SALE_DAY a, DM_D_ALL_ORG_FLAT B, DM_D_ALL_PROD_FLAT D
where a.ORG_ID=B.ORG_ID
      and a.PRODUCT_ID=D.CODE
      and a.day_id=20110201
group by rollup(UP_ORG_ID_1, UP_ORG_ID_2, UP_ORG_ID_3, UP_ORG_ID_4, UP_ORG_ID_5, UP_ORG_ID_6),
      a.TRADE_TYPE_ID,
         a.day_id,
      A.CUST_ID,
      rollup(UP_CODE_1, UP_CODE_2, UP_CODE_3, UP_CODE_4, UP_CODE_5, UP_CODE_6),
      a.QUANTITY_UNIT,
      a.COST_UNIT,
      a.SOURCE_ID;Thanks in advance.

Rob vanWjik has an excellent series of fast refresh materialized views starting here:
http://rwijk.blogspot.com/2009/05/fast-refreshable-materialized-view.html
Part three specifically on aggregate MVs is here:
http://rwijk.blogspot.com/2009/06/fast-refreshable-materialized-view.html

How to add trigger on materialized view?

Hi, I'm trying to add trigger on materialized view. I don't know how to do it. I'm new to oracle and PL/SQL. Can you guys put some working example please? Thank you for every advise.

Please check the below link. This answers you query:
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:672989600346945045

How to create types of materialized views

Hi
Can you please tell me how to create vaious types of materialized view.Also please tell me differences among them.

Oracle docs at tahiti.oracle.com contain exactly the info you need as said previous poster. You can look into SQL reference about MV create statement that contains a brief overview of all types as well as data warehousing guide which contains at least 4 chapters that are about MVs - Basic MV, Advanced MV, Basic query rewrite and Advanced query rewrite.
Gints Plivna
http://www.gplivna.eu

How to make backup to Materialized View

Hello Every one:
I'm Have a Materialized View in my DB, When i make backup using Exp Command, and then make restor to my Backup MV import as table !!!
Thx

The answer to this is yes and no. On the older CSS platform, 50, 150, 800 you do not have this functionality, however on the new CSS 11500, you have the option of copying from one disk to another as both the hard disk and flash disk in an 11500 SCM are PCMCIA which in effect give you a C: and D: drive.
There are commands to copy files between disks that include copying operational software.
Regards
Pete Knoops
Cisco Systems

How can I rename a materialized view

I want to rename a materialized view I don't want to recreate it takes too long.
Help...

Unfortunately you can't rename a materialized view :
http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10736/advmv.htm#sthref589
But you can
1) Create a synonym
http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10759/statements_7001.htm#sthref5356
Or
2 )If your materialized view was created based ON PREBUILT TABLE, you can drop it without losing the underlying table.
http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10759/statements_8019.htm#sthref6247
And then you can recreate a new materialized view based on PREBUILT TABLE.
http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10759/statements_6002.htm#i2106785
Best regards,
Franck.

How to find out which materialized views are running on the DB?

So I have a long list of MVs stored on the DB.
Is there a script to find out which MVs are being refreshed right now?
Help!
Thanks

Hi ,
You can use the following data dictionary view to get information on when Mview was last refreshed--
SQL> desc DBA_MVIEWS
Name                                                  Null?    Type
OWNER                                                 NOT NULL VARCHAR2(30)
MVIEW_NAME                                            NOT NULL VARCHAR2(30)
CONTAINER_NAME                                        NOT NULL VARCHAR2(30)
QUERY                                                          LONG
QUERY_LEN                                                      NUMBER(38)
UPDATABLE                                                      VARCHAR2(1)
UPDATE_LOG                                                     VARCHAR2(30)
MASTER_ROLLBACK_SEG                                            VARCHAR2(30)
MASTER_LINK                                                    VARCHAR2(128)
REWRITE_ENABLED                                                VARCHAR2(1)
REWRITE_CAPABILITY                                             VARCHAR2(9)
REFRESH_MODE                                                   VARCHAR2(6)
REFRESH_METHOD                                                 VARCHAR2(8)
BUILD_MODE                                                     VARCHAR2(9)
FAST_REFRESHABLE                                               VARCHAR2(18)
LAST_REFRESH_TYPE                                              VARCHAR2(8)
LAST_REFRESH_DATE                                              DATE
STALENESS                                                      VARCHAR2(19)
AFTER_FAST_REFRESH                                             VARCHAR2(19)
UNKNOWN_PREBUILT                                               VARCHAR2(1)
UNKNOWN_PLSQL_FUNC                                             VARCHAR2(1)
UNKNOWN_EXTERNAL_TABLE                                         VARCHAR2(1)
UNKNOWN_CONSIDER_FRESH                                         VARCHAR2(1)
UNKNOWN_IMPORT                                                 VARCHAR2(1)
UNKNOWN_TRUSTED_FD                                             VARCHAR2(1)
COMPILE_STATE                                                  VARCHAR2(19)
USE_NO_INDEX                                                   VARCHAR2(1)
STALE_SINCE                                                    DATE
SQL>

Refresh Materialized View in a package

Refresh Materialized View in a process.
I have a USER2.Materialized view and when I want to refresh it I execute:
execute dbms_mview.refresh('MV_FACT_SALES','C');
But I have the ETL process in a USER1.package
The User1 needs any Materialized View Grant or any privilegie?
How can I refresh the Materialized View in a procedure in the USER1.package?

I 'm sorry, but I want to create a procedure under USER2 and when I execute the script to create it I receive the error:
ORA-06550: line 4, column 12:
PLS-00103: Encountered the symbol "DBMS_MVIEW" when expecting one of the following:
:= . ( @ % ; immediate
The symbol ":=" was substituted for "DBMS_MVIEW" to continue.
Te script procedure is:
PROCEDURE REFRESH_MV IS
BEGIN
execute dbms_mview.refresh('MV_FACT_SALES','C');
END;
How can I refresh a Materialized view in a procedure?
Thanks!

Create a materialized view :-

How do I create a materialized view on a view ,so that it will refresh automatically on every commit in base table where the view having more that 9 function ?

Read Materialized View Refresh for complete information.
For a Jist:
Refresh Mode Description
ON COMMIT
Refresh occurs automatically when a transaction that modified one of the materialized view's detail tables commits. This can be specified as long as the materialized view is fast refreshable (in other words, not complex). The ON COMMIT privilege is necessary to use this mode.
ON DEMAND
Refresh occurs when a user manually executes one of the available refresh procedures contained in the DBMS_MVIEW package (REFRESH, REFRESH_ALL_MVIEWS, REFRESH_DEPENDENT).
When a materialized view is maintained using the ON COMMIT method, the time required to complete the commit may be slightly longer than usual. This is because the refresh operation is performed as part of the commit process. Therefore this method may not be suitable if many users are concurrently changing the tables upon which the materialized view is based.
If you anticipate performing insert, update or delete operations on tables referenced by a materialized view concurrently with the refresh of that materialized view, and that materialized view includes joins and aggregation, Oracle recommends you use ON COMMIT fast refresh rather than ON DEMAND fast refresh.
If you think the materialized view did not refresh, check the alert log or trace file.
If a materialized view fails during refresh at COMMIT time, you must explicitly invoke the refresh procedure using the DBMS_MVIEW package after addressing the errors specified in the trace files. Until this is done, the materialized view will no longer be refreshed automatically at commit time.

Referencing a column of a materialized view

Hi,
I have a master table in a database A
CREATE TABLE formations (
nom_formation VARCHAR2(30) CONSTRAINT formations_nom_pk PRIMARY KEY
I have made a materialized view of that table in a remote database B
CREATE MATERIALIZED VIEW formations_mv
In the database B I also want to have this table
CREATE TABLE etudiants (
matricule NUMBER CONSTRAINT etudiants_matricule_pk PRIMARY KEY,
nom_formation VARCHAR2(30) CONSTRAINT etudiants_nom_formation_fk REFERENCES formations_mv(nom_formation)
But when I try to create the table etudiants I get an error on the foreign key that references a column in the materialized view formations_mv.
Is it impossible to reference a column in a materialized view from another table ?
Thanks.

Hi,
In database B this is how I create formations_mv
CREATE MATERIALIZED VIEW formations_mv
     REFRESH FAST
START WITH SYSDATE
NEXT (SYSDATE + 1 / 24 / 60)
     WITH PRIMARY KEY
AS
     SELECT *
FROM formations@etudiants_casa_db_link;
And in database A I create a materialized view log as
CREATE MATERIALIZED VIEW LOG ON formations
WITH PRIMARY KEY
INCLUDING NEW VALUES;

Materialized view with date range

hey,
i have a Statistics Query with start date and end date and its Table table_a would be refreshed every hour....:
e.g.
select ...
from table_a a, table_b b ....
where table_a.transactiondate between start_date and end_date and ....;
So I am wondering how to create a effective materialized view? This is a big query with mutilple tables and each table has many rows.
I have tried to use:
create materialized view view_a
refresh fast
start with sysdate next sysdate + 1/24
as
select a.start_date, a.end_date, ....
from table_a a, table_b b ....
where ....;
Thanks.

If you want to use FAST REFRESH, you must create a MV Log. It would be something like this:
create materialized view log on TABLE
with primary key including new values
create materialized view mv_TABLE
refresh fast
start with sysdate next sysdate + 1/24
as select * from TABLE
For more info about MV:
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10759/statements_6002.htm
Hope I've helped!
Regards,
Marcos

Materialized View with Joins and Possibilities of Partitioning

Hi,
We have a materialized view which has a data to query around 12 gb. The query goes some thing like
this.
Select a.c1,a.c2,b.c1,b.c2,c.c1,c.c2
from a,b,c
where a.c1=b.c1
--and the where condition goes on...
--i.e Basically joining 3 different tables with complex join conditions but without any group functions and subqueries.
Now i have few questions here.
Firstly as the Mview is created with joins we will have to create separate logs for each tables and we have did the same. The logs are created with rowid and sequence for better performance during refresh.
Question No 1
Is this is a best approach for materializing a query with complex join conditions. Or Is it better to make 3 different materialized views for each 3 tables and join those 3 MViews and write a query for my report. I ask this question just to make sure the refresh time is brought down by this method. But as such as we have created 3 different logs for 3 tables the refresh must be happening separately.
Question No 2
Data is likely to grow faster and faster on this. So we have a idea of making this a partitioned Mview. Can the Pro's advice me on this and suggest me the right practice for the same and help me to correct links from where i can pick a example and continue from there.
Question No 3
How to find whether the materialized view has refreshed on a fast mode or complete mode after the last refresh.
Apart from querying and checking the rowid which i feel is quiet cumbersome for a mview with a data volume like what we have. By default when i see the info in TOAD for this Mview it shows Refresh Mode as "Force". But how to ascertain this.
Thanks in anticipation for a good round of discussion

Hi,
We have a materialized view which has a data to query around 12 gb. The query goes some thing like
this.
Select a.c1,a.c2,b.c1,b.c2,c.c1,c.c2
from a,b,c
where a.c1=b.c1
--and the where condition goes on...
--i.e Basically joining 3 different tables with complex join conditions but without any group functions and subqueries.
Now i have few questions here.
Firstly as the Mview is created with joins we will have to create separate logs for each tables and we have did the same. The logs are created with rowid and sequence for better performance during refresh.
Question No 1
Is this is a best approach for materializing a query with complex join conditions. Or Is it better to make 3 different materialized views for each 3 tables and join those 3 MViews and write a query for my report. I ask this question just to make sure the refresh time is brought down by this method. But as such as we have created 3 different logs for 3 tables the refresh must be happening separately.
Question No 2
Data is likely to grow faster and faster on this. So we have a idea of making this a partitioned Mview. Can the Pro's advice me on this and suggest me the right practice for the same and help me to correct links from where i can pick a example and continue from there.
Question No 3
How to find whether the materialized view has refreshed on a fast mode or complete mode after the last refresh.
Apart from querying and checking the rowid which i feel is quiet cumbersome for a mview with a data volume like what we have. By default when i see the info in TOAD for this Mview it shows Refresh Mode as "Force". But how to ascertain this.
Thanks in anticipation for a good round of discussion

Setting DBMS_METADATA.GET_DDL Output for Materialized Views

Hi all.
My Oracle version is 10g.
I'm extracting the DDL of all the objects from database using the DBMS_METADATA package. I'm using SET_TRANSFORM_PARAM to configure the output because I need a simple sql code, without information about tablespaces, storage and segment attributes. Everything works fine except when I'm working with mviews object types. I can't remove the information about tablespace, storage or segment attributes for materialized views.
I would like to know if there's a related issue about it. Or there's something missing in my code?
I tried to specify the object type as another parameter on DBMS_METADATA.SET_TRANSFORM_PARAM but don't work too.
The only transform parameter that works fine with Materialized Views is the SQLTERMINATOR.
See how I have done:
declare
vDDL clob;
begin
dbms_metadata.set_transform_param (DBMS_METADATA.SESSION_TRANSFORM, 'STORAGE', FALSE);
dbms_metadata.set_transform_param (DBMS_METADATA.SESSION_TRANSFORM, 'TABLESPACE', FALSE);
dbms_metadata.set_transform_param (DBMS_METADATA.SESSION_TRANSFORM, 'SEGMENT_ATTRIBUTES', FALSE);
dbms_metadata.set_transform_param (DBMS_METADATA.SESSION_TRANSFORM, 'SQLTERMINATOR',TRUE);
select dbms_metadata.get_ddl ('MATERIALIZED_VIEW', 'MV_STO020', 'HIS117_CHECK') into vDDL FROM DUAL;
dbms_output.put_line (vDDL);
end;
and how the output is:
CREATE MATERIALIZED VIEW "HIS117_CHECK"."MV_STO020"
ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "TS_HIS117"
BUILD IMMEDIATE
USING INDEX
REFRESH FORCE ON DEMAND
WITH PRIMARY KEY USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE
AS SELECT
STO020_MOVEMENT_LOG_ID STO020_MOVEMENT_LOG_ID
, STO020_QUANTITY STO020_QUANTITY
, STO020_DATE STO020_DATE
, STO020_BEFORE_BALANCE STO020_BEFORE_BALANCE
, STO011_PRODUCT_MOVEMENT_ID STO011_PRODUCT_MOVEMENT_ID
, ADM082_PRODUCT_ID ADM082_PRODUCT_ID
, ADM089_PRODUCT_PRESENTATION_ID ADM089_PRODUCT_PRESENTATION_ID
, STO010_MOVEMENT_TYPE_ID STO010_MOVEMENT_TYPE_ID
, STO001_STOCK_ID STO001_STOCK_ID
, STO001_TARGET_STOCK_ID STO001_TARGET_STOCK_ID
, STO003_PRODUCT_LOT_ID STO003_PRODUCT_LOT_ID
, SYS010_USER_ID SYS010_USER_ID
, EIR001_MPI EIR001_MPI
, ADM056_MEDICAL_ATTENTION_ID ADM056_MEDICAL_ATTENTION_ID
, ADM094_USE_UNIT_ID ADM094_USE_UNIT_ID
FROM
STO020_MOVEMENT_LOG;
Thank you in advanced!
Edited by: lucporto on 28/08/2012 07:26

Right. I found this way but I consider this just a quick fix, because I think there should be a better way to do this.
create table t_clob (c_long);
declare
p clob;
begin
delete from t_clob;
execute immediate 'insert into t_clob (select to_lob(query) from dba_mviews where owner = :1 and mview_name = :2)'
USING 'HIS117', 'MV_STO020';
select 'CREATE MATERIALIZED VIEW MV_STO020' || chr(10) ||
'REFRESH ON DEMAND' || chr(10) || 'AS' || CHR(10) || mv.c_long
into p
from t_clob mv;
dbms_output.put_line(p);
end;
Thanks all.

Materialized Views Not Refreshing

I have created several materialized views and I am having a problem with them never refreshing even though their refresh times are specified in the create statement. Here is the SQL statement for one of them.
create MATERIALIZED view autonomy_mvw
     nocache
     logging
     noparallel
     build immediate
     refresh complete
     start with to_date(sysdate,'dd-mon-yyyy hh24:mi:ss')
     next sysdate + 18/24
as
     select c.contract_seq,
          c.contract_number contract,
cast('' as VARCHAR2(1)) contract_mod,
          cast('' as VARCHAR2(1)) do,
          cast('' as VARCHAR2(1)) do_seq,
          cast('' as VARCHAR2(1)) do_mod_number,
          c.contract_number co_do,
          c.contract_name title,
          c.contract_remarks description,
          c.contract_effective_date award_date,
          to_char(c.contract_performance_end_date) originalpop,
          to_char(cont_perform_end_date(c.contract_seq)) currentpop,
          c.control_group controlgroup,
          c.fiscal_year_execution fy,
c.quarter,
          nvl(CON_PENDING_ROLLUP_AMOUNT(c.contract_seq),0) pendingamt,
          nvl(CON_OBLIGATED_ROLLUP_AMOUNT(c.contract_seq),0) originalamt,
          cont_majcoms_comma(c.contract_seq) majcom,
cont_installations_desc_comma(c.contract_seq) installation,
          case pocPM.last_name || ', ' || pocPM.first_name || nvl2(pocPM.mi,' '||pocPM.mi,'') when ', ' then 'Not Assigned'
          else pocPM.last_name || ', ' || pocPM.first_name || nvl2(pocPM.mi,' '||pocPM.mi,'') end     pm,
          case pocCM.last_name || ', ' || pocCM.first_name || nvl2(pocCM.mi,' '||pocCM.mi,'') when ', ' then 'Not Assigned'
          else pocCM.last_name || ', ' || pocCM.first_name || nvl2(pocCM.mi,' '||pocCM.mi,'')     end cm,
          case pocBCO.last_name || ', ' || pocBCO.first_name || nvl2(pocBCO.mi,' '||pocBCO.mi,'') when ', ' then 'Not Assigned'
          else pocBCO.last_name || ', ' || pocBCO.first_name || nvl2(pocBCO.mi,' '||pocBCO.mi,'') end BCO,
          con.contractor_name contractor,
          c.contract_status status,
          cast('' as VARCHAR2(1)) active_status,
          nvl(c.prg_name,'Non Program') prg_name,
          c.funds_type fund_type,
          c.contract_instr_num
     from contract c,
          contractor con,
          cg_level cgl,
          poc_user_info pocPM,
          poc_user_info pocCM,
          poc_user_info pocBCO
     where c.contractor_number = con.contractor_number
     and c.control_group = cgl.control_group(+)
     and c.pm_seq = pocPM.poc_user_seq(+)
     and c.cm_seq = pocCM.poc_user_seq(+)
     and c.bco_seq = pocBCO.poc_user_seq(+)
     and c.contract_instr_num <> 'D'
     and c.contract_status in ('AC', 'NEW')
     union
     select c.contract_seq,
          c.contract_number contract,
          cmod.contract_mod_num contract_mod,
          cast('' as VARCHAR2(1)) do,
          cast('' as VARCHAR2(1)) do_seq,
          cast('' as VARCHAR2(1)) do_mod_number,
          c.contract_number||'/'||cmod.contract_mod_num co_do,
          c.contract_name title,
          c.contract_remarks description,
          c.contract_effective_date award_date,
          to_char(c.contract_performance_end_date) originalpop,
          to_char(cont_perform_end_date(c.contract_seq)) currentpop,
          c.control_group controlgroup,
          cmod.fiscal_year_execution fy,
cmod.quarter,
          nvl(cmod.contract_mod_committed_amt,0) pendingamt,
          nvl(cmod.afcee_oblig_contract_mod_amt, 0) originalamt,
          cont_majcoms_comma(c.contract_seq) majcom,
          cont_installations_desc_comma(c.contract_seq) installation,
          case pocPM.last_name || ', ' || pocPM.first_name || nvl2(pocPM.mi,' '||pocPM.mi,'') when ', ' then 'Not Assigned'
          else pocPM.last_name || ', ' || pocPM.first_name || nvl2(pocPM.mi,' '||pocPM.mi,'') end pm,
          case pocCM.last_name || ', ' || pocCM.first_name || nvl2(pocCM.mi,' '||pocCM.mi,'') when ', ' then 'Not Assigned'
          else pocCM.last_name || ', ' || pocCM.first_name || nvl2(pocCM.mi,' '||pocCM.mi,'') end cm,
          case pocBCO.last_name || ', ' || pocBCO.first_name || nvl2(pocBCO.mi,' '||pocBCO.mi,'') when ', ' then 'Not Assigned'
          else pocBCO.last_name || ', ' || pocBCO.first_name || nvl2(pocBCO.mi,' '||pocBCO.mi,'') end BCO,
          con.contractor_name contractor,
          c.contract_status status,
          cast('' as VARCHAR2(1)) active_status,
          nvl(c.prg_name,'Non Program') prg_name,
          c.funds_type fund_type,
          c.contract_instr_num
     from contract c,
          contract_modification cmod,
          contractor con,
          cg_level cgl,
          poc_user_info pocPM,
          poc_user_info pocCM,
          poc_user_info pocBCO
     where c.contract_seq = cmod.contract_seq
     and c.contractor_number = con.contractor_number
     and c.control_group = cgl.control_group(+)
     and c.pm_seq = pocPM.poc_user_seq(+)
     and c.cm_seq = pocCM.poc_user_seq(+)
     and c.bco_seq = pocBCO.poc_user_seq(+)
     and c.contract_instr_num <> 'D'
     and c.contract_status in ('AC', 'NEW')
     union
     select c.contract_seq,
          c.contract_number contract,
          cast('' as VARCHAR2(1)) contract_mod,
          do.do_number do,
          to_char(do.do_seq) do_seq,
          cast('' as VARCHAR2(1)) do_mod,
          c.contract_number||'-'||do.do_number co_do,
          do.do_title title,
          do.do_description description,
          do.afcee_obligated_do_date award_date,
          to_char(do.do_end_date) originalpop,
     to_char(do_mod_end_date(do.do_seq)) currentpop,
          do.control_group controlgroup,
          do.fiscal_year_execution fy,
do.quarter,
          nvl(DO_PENDING_ROLLUP_AMOUNT(do.do_seq),0) pendingamt,
          nvl(DO_OBLIGATED_ROLLUP_AMOUNT(do.do_seq),0) originalamt,
do_majcoms_comma(do.do_seq, null) majcom,
do_installations_desc_comma(do.do_seq, null) installation,
          case pocPM.last_name || ', ' || pocPM.first_name || nvl2(pocPM.mi,' '||pocPM.mi,'') when ', ' then 'Not Assigned'
          else pocPM.last_name || ', ' || pocPM.first_name || nvl2(pocPM.mi,' '||pocPM.mi,'') end pm,
          case pocCM.last_name || ', ' || pocCM.first_name || nvl2(pocCM.mi,' '||pocCM.mi,'') when ', ' then 'Not Assigned'
          else pocCM.last_name || ', ' || pocCM.first_name || nvl2(pocCM.mi,' '||pocCM.mi,'') end cm,
          case pocBCO.last_name || ', ' || pocBCO.first_name || nvl2(pocBCO.mi,' '||pocBCO.mi,'') when ', ' then 'Not Assigned'
          else pocBCO.last_name || ', ' || pocBCO.first_name || nvl2(pocBCO.mi,' '||pocBCO.mi,'') end BCO,
          con.contractor_name contractor,
          do.do_status status,
          do.do_actv_status active_status,
          nvl(c.prg_name,'Non Program') prg_name,
          do_fundtypes_comma(do.do_seq,null) fund_type,
          c.contract_instr_num
     from delivery_order do,
          contract c,
          contractor con,
          cg_level cgl,
          poc_user_info pocPM,
          poc_user_info pocCM,
          poc_user_info pocBCO
     where do.contract_seq = c.contract_seq
     and c.contractor_number = con.contractor_number
     and do.control_group = cgl.control_group(+)
     and do.pm_seq = pocPM.poc_user_seq(+)
     and do.cm_seq = pocCM.poc_user_seq(+)
     and do.bco_seq = pocBCO.poc_user_seq(+)
     and do.do_status in ('CURR')
     and do.do_actv_status in ('RESV','ANTC','FORE','COMM','OBLG','FIN_INV')
     union
     select c.contract_seq,
          c.contract_number contract,
          ''contract_mod,
          do.do_number do,
          to_char(do.do_seq) do_seq,
          domod.do_mod_number do_mod,
          c.contract_number||'-'||do.do_number||'-'||domod.do_mod_number co_do,
          do.do_title title,
          domod.do_mod_description description,
          domod.afcee_obligated_do_mod_date award_date,
          to_char(do.do_end_date) originalpop,
to_char(do_mod_end_date(do.do_seq)) currentpop,
          domod.control_group controlgroup,
          domod.fiscal_year_execution fy,
domod.quarter,
          (nvl(domod.do_mod_committed_amount,0) + nvl(domod.reserved_amount,0)+ nvl(domod.anticipated_amount,0)
               + nvl(domod.forecasted_amount,0)) pendingamt,
          (nvl(domod.afcee_obligated_do_mod_amount, 0)) originalamt,
do_majcoms_comma(do.do_seq, domod.do_mod_number) majcom,
do_installations_desc_comma(do.do_seq, domod.do_mod_number) installation,
          case pocPM.last_name || ', ' || pocPM.first_name || nvl2(pocPM.mi,' '||pocPM.mi,'') when ', ' then 'Not Assigned'
          else pocPM.last_name || ', ' || pocPM.first_name || nvl2(pocPM.mi,' '||pocPM.mi,'') end pm,
          case pocCM.last_name || ', ' || pocCM.first_name || nvl2(pocCM.mi,' '||pocCM.mi,'') when ', ' then 'Not Assigned'
          else pocCM.last_name || ', ' || pocCM.first_name || nvl2(pocCM.mi,' '||pocCM.mi,'') end cm,
          case pocBCO.last_name || ', ' || pocBCO.first_name || nvl2(pocBCO.mi,' '||pocBCO.mi,'') when ', ' then 'Not Assigned'
          else pocBCO.last_name || ', ' || pocBCO.first_name || nvl2(pocBCO.mi,' '||pocBCO.mi,'') end BCO,
          con.contractor_name contractor,
          do.do_status status,
          do.do_actv_status active_status,
          nvl(c.prg_name,'Non Program') prg_name,
          do_fundtypes_comma(do.do_seq,domod.do_mod_number) fund_type,
          c.contract_instr_num
     from delivery_order do,
          delivery_order_modification domod,
          contract c,
          contractor con,
          cg_level cgl,
          poc_user_info pocPM,
          poc_user_info pocCM,
          poc_user_info pocBCO
     where do.do_seq = domod.do_seq
     and do.contract_seq = c.contract_seq
     and c.contractor_number = con.contractor_number
     and do.control_group = cgl.control_group(+)
     and do.pm_seq = pocPM.poc_user_seq(+)
     and do.cm_seq = pocCM.poc_user_seq(+)
     and do.bco_seq = pocBCO.poc_user_seq(+)
     and domod.do_mod_status in ('CURR')
     and domod.do_mod_actv_status in ('RESV','ANTC','FORE','COMM','OBLG','DEOBLG','FIN_INV');
As you can see, I cannot use the On Commit refresh method because I violate several of the requirements in order to use the On Commit refresh method. I do not have a materialized view logs.
I did the following select from all_mviews:
1 select
2 MVIEW_NAME,
3 UPDATABLE,
4 UPDATE_LOG,
5 REWRITE_ENABLED,
6 REWRITE_CAPABILITY,
7 REFRESH_MODE,
8 REFRESH_METHOD,
9 BUILD_MODE,
10 LAST_REFRESH_TYPE,
11 LAST_REFRESH_DATE,
12 STALENESS
13 from all_mviews
14* where mview_name = 'AUTONOMY_MVW'
MVIEW_NAME U UPDATE_LOG R REWRITE_C REFRES REFRESH_ BUILD_MOD LAST_REF LAST_REFR STALENESS
AUTONOMY_MVW N N NONE DEMAND COMPLETE IMMEDIATE COMPLETE 17-NOV-05 STALE
I then called the dbms_mview package to force a REFRESH on this view and then re-ran the above sql
MVIEW_NAME U UPDATE_LOG R REWRITE_C REFRES REFRESH_ BUILD_MOD LAST_REF LAST_REFR STALENESS
AUTONOMY_MVW N N NONE DEMAND COMPLETE IMMEDIATE COMPLETE 04-MAY-06 STALE
I noticed that while it was refreshed it shows as stale.
How do I get this materialized view (and my other ones) to refresh in a regular manner?
Thanks
Richard Anderson

Here is what I got when I ran the sql you provided. BTW, I increased the substr size for the "Command" to 70 so I could see the whole thing. I have 6 materialized views in this instance but one of them has a compile_state of "ERROR" and so it doesn't show in the job queue. All the others show up.
Job User Schem Last Date Next Date B Failed Command
9 MXT MXT 04.05.2006 16:55 04.05.2006 17:55 N 0 dbms_refresh.refresh('"MXT"."PMR_CON_DO_REPORT_MVW"');
51 MXT MXT 04.05.2006 16:55 04.05.2006 17:55 N 0 dbms_refresh.refresh('"MXT"."MIEN_FY_MV"');
4 MXT MXT 04.05.2006 16:55 04.05.2006 17:55 N 0 dbms_refresh.refresh('"MXT"."PMR_ALL_STATUS_AMT_REPORT_MVW"');
7 MXT MXT 04.05.2006 16:55 04.05.2006 17:55 N 0 dbms_refresh.refresh('"MXT"."PMR_AMOUNT_REPORT_MVW"');
31 MXT MXT 04.05.2006 16:58 04.05.2006 17:28 N 0 dbms_refresh.refresh('"MXT"."PMR_TEST_MVW"');
Rick Anderson
PS, this list was run on my DEV server so it doesn't have the AUTONOMY_MVW at all but both my DEV and PROD instances are having the same issues.
I downloaded Oracle SQL Developer and used it to look at the materialized views and they have a details tab which contained the following:
"Name"     "Value"
"OWNER"     "MXT"
"MVIEW_NAME"     "PMR_AMOUNT_REPORT_MVW"
"CONTAINER_NAME"     "PMR_AMOUNT_REPORT_MVW"
"QUERY_LEN"     "31020"
"UPDATABLE"     "N"
"UPDATE_LOG"     ""
"MASTER_ROLLBACK_SEG"     ""
"MASTER_LINK"     ""
"REWRITE_ENABLED"     "N"
"REWRITE_CAPABILITY"     "NONE"
"REFRESH_MODE"     "DEMAND"
"REFRESH_METHOD"     "COMPLETE"
"BUILD_MODE"     "IMMEDIATE"
"FAST_REFRESHABLE"     "NO"
"LAST_REFRESH_TYPE"     "COMPLETE"
"LAST_REFRESH_DATE"     "04-MAY-06"
"STALENESS"     "UNKNOWN"
"AFTER_FAST_REFRESH"     "NA"
"UNKNOWN_PREBUILT"     "N"
"UNKNOWN_PLSQL_FUNC"     "Y"
"UNKNOWN_EXTERNAL_TABLE"     "N"
"UNKNOWN_CONSIDER_FRESH"     "N"
"UNKNOWN_IMPORT"     "N"
"COMPILE_STATE"     "VALID"
"USE_NO_INDEX"     "N"
Message was edited by:
RichardAnderson

Materialized Views in OBIEE

Hi,
I have a quick question. How can I include a materialized view (which I created in the OWB) in OBIEE (11.1.1.5)?
Obviously I have to import the view with the administration tool but do I have to join the view with the fact table?
Is there a "how to" or a tutorial to this matter? I searched but didn't find anything which helped me.
thx

Why use an opaque view ? Its not like there is anything complex about including an aggregate table.
Makes debugging a nightmare and lineage is ruined once you go that route.
And why are you joining a Materialised view to your fact table ? I would have thought you would join them to the dimension tables.
Import it as a table, join up the FK's and model it as you would an aggregate table. Unless im missing something?

How to test benefits of Materialized View

Similar Messages

Maybe you are looking for