Concept of materialized views in creating datawarehouse?????

Hi All,
I want to understand the concept of Materialized views.
We have a requirment that we have OLTP system EBS R12, now we have to fetch the data from EBS and load it into the target and then have to use the pre-built reports of financial, HR.
We are not using Informatica and DAC, I heard that there is some other concept (using materialized views) to load the data into the target, so can any both through some light on the same or any links or doc.
Regards,
Tarang Jain

Hi Tarang,
Main purpose of using Materialized view is to eliminate the overhead associated with expensive joins and aggregations for a large or important class of queries.
In data warehouses, you can use materialized views to precompute and store aggregated data such as the sum of sales.
Below are the some URLs helps you in understaing MV Concept:
[http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14223/basicmv.htm#g1028195]
[http://www.psoug.org/reference/materialized_views.html]
-Vency

Similar Messages

ASCP Roll up materialized View not created

Hi ,
I applied ASCP RUP#38 8639586. A worker failed while creating materialized View.
FAILED: file MSC_PHUB_CUSTOMERS_MV.xdf on worker 4 for product msc username APPS
When i checked to the worker log it had following errors
Exception occured ORA-04063: package body "APPS.MSC_PHUB_UTIL" has errors
ORA-06512: at "APPS.AD_MV", line 124
ORA-06512: at "APPS.AD_MV", line 258
ORA-06512: at line 1
java.sql.SQLException: ORA-04063: package body "APPS.MSC_PHUB_UTIL" has errors
ORA-06512: at "APPS.AD_MV", line 124
ORA-06512: at "APPS.AD_MV", line 258
ORA-06512: at line 1
can anyone help me solve this issue.
Thanks
H2B

did you complied invalid objects..?
need some help understanding the way materialized views are applied through
Edited by: 3Amigos on Dec 16, 2010 2:53 AM

Does create materialized view command creates an index?

Does a Create materialized view command inturn creates indexes?

Sometimes it does. Consider:
scott@ora102> create materialized view emp_desc_mv
2 as select e.empno, e.ename, e.sal, e.comm, d.dname, d.loc
3 from emp e, dept d
4 where e.deptno = d.deptno;
Materialized view created.
scott@ora102> select count(*) from all_indexes where table_name = 'EMP_DESC_MV';
COUNT(*)
0
scott@ora102> alter materialized view emp_desc_mv add primary key (empno);
Materialized view altered.
scott@ora102> select count(*) from all_indexes where table_name = 'EMP_DESC_MV';
COUNT(*)
1
Daniel

Importing materialized views from database into physical layer

Hi,
I have created materialized view in the database. When I try to import the materialized view into the physical layer in OBIEE 10G (using the import from database option), it is not showing in the list of available object. I have selected all the object types (tables,views etc.). Can you please let me know how to import the existing MVs in the database into the physical layer.
Regards
Vinodh.
Edited by: user493441 on Jul 7, 2012 4:11 PM

Hi Vinod,
Refer the below links.
Materialized Views in OBIEE
http://gerardnico.com/wiki/database/oracle/materialized_view
Concept of materialized views in creating datawarehouse?????
Hope this help's
Thanks
Satya

Error while creating materialized view which using database link

Helo!
I'm getting error "ORA-00942: table or view does not exist" when I want to create materialized view.
Details:
1. On destination database I create a database link:
CREATE DATABASE LINK SDATABASE
CONNECT TO MYUSER
IDENTIFIED BY MYUSERPASS
USING 'ORCL';
=> Command "SELECT * FROM TABLE1@SDATABASE" returns data normally!
2. On source database I create MATERIALIZED VIEW LOG:
CREATE MATERIALIZED VIEW LOG
ON TABLE1
WITH PRIMARY KEY
INCLUDING NEW VALUES;
3. Now, when I want to create MATERIALIZED VIEW on destination database:
CREATE MATERIALIZED VIEW TABLE1
REFRESH FAST
START WITH SYSDATE
NEXT SYSDATE + 1/1440
WITH PRIMARY KEY
AS SELECT * FROM TABLE1@SDATABASE;
...I get error "ORA-00942: table or view does not exist"!
How is that possible if command "SELECT * FROM TABLE1@SDATABASE" returns data normally?
Thanks,
Voranc

And, I'm using Oracle 10g.
Voranc

Creating a materialized view for another user

I don't seem to find the correct setup for this....
With the user "dummy"
CREATE MATERIALIZED VIEW dummy.thetable BUILD IMMEDIATE REFRESH FORCE ON DEMAND AS select * from real.thetable;
And the materialized view is created ok.
With a DBA user:
CREATE MATERIALIZED VIEW dummy.thetable BUILD IMMEDIATE REFRESH FORCE ON DEMAND AS select * from real.thetable;
ORA-01031: insufficient privileges
I don't want to be switching back and forth from the user to create materialized views, am I missing a permission here? DBA of course has create any materialized view

From the SQL Reference Guide:
To create a materialized view in another user’s schema:
- You must have the CREATE ANY MATERIALIZED VIEW system privilege.
- The owner of the materialized view must have the CREATE TABLE system privilege. The owner must also have access to any master tables of the materialized view that the schema owner does not own (for example, if the master tables are on a remote database), and to any materialized view logs defined on those master tables, either through a SELECT object privilege on each of the tables or through the SELECT ANY TABLE system privilege.
I suspect that, if you first GRANT CREATE TABLE TO DUMMY, you will be able to create the MV.

Error While Creating Fast Refresh Materialized view.

Table Scripts:
CREATE TABLE CONTRACT_MASTER
CONTRACT_SEQ                    NUMBER(10)    NOT NULL,
PDN                             CHAR(5)       NOT NULL,
APPID                           NUMBER(10)    NOT NULL,
CONTRACT_LOB_DESC               VARCHAR2(20) NOT NULL,
CUSTOMER_NAME                   VARCHAR2(57) NOT NULL,
CONTRACT_DT                     DATE          NOT NULL,
CONTRACT_RECD_DT                DATE          NOT NULL,
HELD_OFFERING_DT                DATE          NOT NULL,
DRAFT_AMT                       NUMBER(15,2) NOT NULL,
STATUS_DESC                                   VARCHAR2(20) NOT NULL,
GIF_UPLOAD_TM                                            TIMESTAMP     NOT NULL
CREATE table CONTRACT_COMMENTS
CONTRACT_COMMENTS_SEQ           NUMBER(10)     NOT NULL,
APPID                           NUMBER(10)     NOT NULL,
COMMENTS                        VARCHAR2(1000) NOT NULL,
GIF_UPLOAD_TM                                            TIMESTAMP      NOT NULL
Constraints on tables
ALTER TABLE CONTRACT_MASTER ADD
CONSTRAINT XPKCONTRACT_MASTER PRIMARY KEY (CONTRACT_SEQ) USING INDEX ;
ALTER TABLE CONTRACT_COMMENTS ADD
CONSTRAINT XPKCONTRACT_COMMENTS PRIMARY KEY (CONTRACT_COMMENTS_SEQ) USING INDEX ;
alter table CONTRACT_MASTER add CONSTRAINT XUIAPPCONTRACT_MASTER UNIQUE (APPID) USING INDEX;
CREATE INDEX XUIAPPCONTRACT_COMMENTS ON
CONTRACT_COMMENTS(APPID) ;
Materialized View Creation:
CREATE MATERIALIZED VIEW LOG ON CONTRACT_MASTER WITH PRIMARY KEY,ROWID;
CREATE MATERIALIZED VIEW LOG ON CONTRACT_COMMENTS WITH PRIMARY KEY, ROWID;
CREATE MATERIALIZED VIEW MV_CONTRACT_COMMENTS_HELDOFFERING
REFRESH FAST
ENABLE QUERY REWRITE AS
SELECT APPID,COMMENTS FROM CONTRACT_COMMENTS WHERE APPID IN (
SELECT APPID FROM CONTRACT_MASTER WHERE STATUS_DESC = 'Held Offering' )
Errors generated:
ERROR at line 4:
ORA-12015: cannot create a fast refresh materialized view from a complex query
_*Afer That I have changed the query but still it was not created like:*_
CREATE MATERIALIZED VIEW MV_CONT_COMMNTS_HELDOFFERNG
REFRESH FAST
ENABLE QUERY REWRITE AS
SELECT CONTRACT_COMMENTS_SEQ,c.APPID,COMMENTS
FROM CONTRACT_COMMENTS c,CONTRACT_MASTER m
WHERE m.APPID = c.APPID and m.STATUS_DESC = 'Held Offering'
*even though error displayed:
SQL> CREATE MATERIALIZED VIEW MV_CONT_COMMNTS_HELDOFFERNG*
   2 REFRESH FAST
   3 ENABLE QUERY REWRITE AS
   4 SELECT CONTRACT_COMMENTS_SEQ,c.APPID,COMMENTS
   5 FROM CONTRACT_COMMENTS c,CONTRACT_MASTER m
   6 WHERE m.APPID = c.APPID and m.STATUS_DESC = 'Held Offering';
FROM CONTRACT_COMMENTS c,CONTRACT_MASTER m
ERROR at line 5:
ORA-12052: cannot fast refresh materialized view GSSIO.MV_CONT_COMMNTS_HELDOFFERNG
*Again I have done "Analyzing Materialized Views for Fast Refresh" as follows:*
1: exec dbms_mview.explain_mview('MV_CONT_COMMNTS_HELDOFFERNG');
2: SELECT capability_name, possible, SUBSTR(msgtxt,1,60) AS msgtxt
           FROM mv_capabilities_table
           WHERE capability_name like '%FAST%';
Output is :
CAPABILITY_NAME                               P              MSGTXT
REFRESH_FAST                                   N
REFRESH_FAST_AFTER_INSERT            N the SELECT list does not have the rowids of all the detail t
REFRESH_FAST_AFTER_ONETAB_DML   N see the reason why REFRESH_FAST_AFTER_INSERT is disabled
REFRESH_FAST_AFTER_ANY_DML         N see the reason why REFRESH_FAST_AFTER_ONETAB_DML is disabled
REFRESH_FAST_PCT                            N PCT is not possible on any of the detail tables in the mater
Please suggest what to do to implement fast refresh materialized view for same.Edited by: dba on Sep 20, 2010 12:00 AM

If the two MVs have to be consistent with each other as of a specific time, put them into a Refresh Group and refresh them with DBMS_MVIEW.REFRESH
If an MV is dependent on another, use DBMS_MVIEW.REFRESH_DEPENDENT
See the "Oracle® Database PL/SQL Packages and Types Reference" documentation pages for DBMS_MVIEW.
Hemant K Chitale
http://hemantoracledba.blogspot.com --- this is NOT a documentation site.
Edited by: Hemant K Chitale on Sep 20, 2010 5:19 PM

Recieving ORA-01722 invalid number error while creating a materialized view

Hi,
I am receiving a ORA-01722 invalid number error while creating a materialized view. when run the select statement of the view i don't get any error, but when i use the same select statement to create a materialized view i receive this error. Could any please help in resolving this error. Here is the code i am using to create a materialized view.
CREATE MATERIALIZED VIEW MV_EBS_CH_CLOSED
REFRESH FORCE ON DEMAND
AS
SELECT DISTINCT kr.request_id, org.org_unit_name,
ebs_ch_ticket_type (kr.request_id) ticket_type,
DECODE
(kr.status_code,
'CLOSED_SUCCESS', kr.last_update_date,
'IN_PROGRESS', (SELECT MAX (start_time)
FROM ebs_ch_datastore ecd1
WHERE kr.request_id = ecd1.request_id
AND workflow_step_name =
'Final BA Review and Deployment Exit Criteria')
) closed_date,
substr(krhd.visible_parameter12,1,10) siebel_start_date,
kr.creation_date itg_start_date
FROM kcrt_requests kr,
kcrt_request_types krt,
kcrt_req_header_details krhd, kcrt_request_details krd1,
(SELECT koum.user_id user_id,
DECODE (koup.org_unit_name,
'IT Implementations', 'CHS - Service Management BA',
koup.org_unit_name
) org_unit_name
FROM krsc_org_unit_members koum, krsc_org_units koup
WHERE 1 = 1
AND 'Y' = koup.enabled_flag
AND koum.org_unit_id = koup.org_unit_id
AND EXISTS (
SELECT 'X'
FROM krsc_org_units kouc
WHERE koup.org_unit_id = kouc.org_unit_id
START WITH kouc.parent_org_unit_id =
ANY (SELECT org_unit_id
FROM krsc_org_units krsc_org_units1
WHERE 'Clearinghouse' =
org_unit_name)
CONNECT BY kouc.parent_org_unit_id =
PRIOR kouc.org_unit_id)
UNION
SELECT kou.manager_id user_id,
DECODE
(kou.org_unit_name,
'IT Implementations', 'CHS - Service Management BA',
kou.org_unit_name
) org_unit_name
FROM krsc_org_units kou
WHERE 'Y' = kou.enabled_flag
START WITH kou.parent_org_unit_id =
(SELECT org_unit_id
FROM krsc_org_units krsc_org_units2
WHERE 'Clearinghouse' = org_unit_name)
CONNECT BY kou.parent_org_unit_id = PRIOR kou.org_unit_id) org
WHERE krt.request_type_id = kr.request_type_id
AND krt.request_type_name IN ('Bug Fix', 'IT Enhancement')
and kr.REQUEST_ID = krd1.request_id
and krd1.batch_number = 1
AND kr.request_id = krhd.request_id
AND org.user_id in (krd1.parameter4, krd1.parameter5, krd1.parameter7)
AND ( 'CLOSED_SUCCESS' = kr.status_code
OR 'IN_PROGRESS' = kr.status_code
AND kr.request_id IN (
SELECT request_id
FROM (SELECT DISTINCT request_id,
MAX
(start_time)
closed_date
FROM ebs_ch_datastore
WHERE 'Final BA Review and Deployment Exit Criteria' =
workflow_step_name
GROUP BY request_id))
Thanks,
Shaik Mohiuddin

This error occurs when you try to create a materialized view , but if you run the sql the results are perfectly fine. Well it happend to me also and to fix this I made sure all the coulmns have the same data type which are used in joins or in where clause.
use
where
to_number(col1)=to_number(col2) and to_number(col3)=to_number(col4)
hope this helps..

Is it possible to create materialized view log file for force refresh

Is it possible to create materialized view log file for force refresh with join condition.
Say for example:
CREATE MATERIALIZED VIEW VU1
REFRESH FORCE
ON DEMAND
AS
SELECT e.employee_id, d.department_id from emp e and departments d
where e.department_id = d.department_id;
how can we create log file using 2 tables?
Also am copying M.View result to new table. Is it possible to have the same values into the new table once the m.view get refreshed?

You cannot create a record as a materialized view within the Application Designer.
But there is workaround.
Create the record as a table within the Application Designer. Don't build it.
Inside your database, create the materialized with same name and columns as the record created previously.
After that, you'll be able to work on that record as for all other within the Peoplesoft tools.
But keep in mind do never build that object, that'll drop your materialized view and create a table instead.
Same problem exists for partitioned tables, for function based-indexes and some other objects database vendor dependant. Same workaround is used.
Nicolas.

Can I create index on Materialized view log

Hello
The ADDM suggest me to create index on some fields of my materialized view log , I don't know does it cause any problem ? Is it safe ? have you done it before ?
thanks

Actually you can do it since materialized view log is in fact a table.
SQL> create table t(x int primary key);
Table created.
SQL> create materialized view log on t;
Materialized view log created.
SQL> select segment_name, segment_type from user_segments;
SEGMENT_NAME
SEGMENT_TYPE
MLOG$_T
TABLE
T
TABLE
SYS_C004857
INDEX
SQL> desc mlog$_t;
Name                                      Null?    Type
X                                                  NUMBER
SNAPTIME$$                                         DATE
DMLTYPE$$                                          VARCHAR2(1)
OLD_NEW$$                                          VARCHAR2(1)
CHANGE_VECTOR$$                                    RAW(255)
SQL> create index i on mlog$_t(x);
Index created.However I don't know if this is really supported and makes sense.

Error creating materialized view log using DBlink

Hi guys,
I have 2 databases in diferent machines . (machine A and B)
Machine A is my production database and I have a database link in machine B accessing Machine A
CREATE MATERIALIZED VIEW vm_test
BUILD IMMEDIATE
REFRESH FAST ON commit as
select * from test@A
-- no problem in this first operation the materialized view was created sucessfully
Now I need to create the LOG
SQL> CREATE MATERIALIZED VIEW LOG ON test
2 PCTFREE 5
3 TABLESPACE prodemge_2006
4 STORAGE (INITIAL 10K NEXT 10K);
CREATE MATERIALIZED VIEW LOG ON test
ERROR at line 1:
ORA-02050: transaction 5.21.8771 rolled back, some remote DBs may be in-doubt
ORA-02068: following severe error from A
ORA-03113: end-of-file on communication channel
What could be causing this error ?
Thank you,
Felipe

ORA-02050 transaction string rolled back, some remote DBs may be in-doubt
Cause: Network or remote failure during a two-phase commit.
Action: Notify operations; remote databases will automatically re-sync when the failure is repaired.
ORA-02068 following severe error from stringstring
Cause: A severe error (disconnect, fatal Oracle error) was received from the indicated database link. See following error text.
Action: Contact the remote system administrator.
M.S.Taj

Create materialized view, ORA-00942

I would like to create a materialized view on user scott@orcl for user colinsuper. User scott@orcl have
"CREATE ANY MATERIALIZED VIEW" permissions. Why does I get an ORA-00942 error?
Remote-Database: remote_orcl.world
Remote-Database-User: lindasuper
Remote-Database-Table: cars
scott@orcl>create synonym cars for lindasuper.cars@remote_orcl.world
2 /
Synonym created.
scott@orcl>select car_no cno, car_bez cbez from cars
2 where rownum <= 1;
cno   cbez
3     32-mxl
scott@orcl
scott@orcl
scott@orcl>CREATE MATERIALIZED VIEW colinsuper.CARS_MV
2    TABLESPACE my_tablespace
3    BUILD IMMEDIATE
4    USING INDEX TABLESPACE my_idx
5    REFRESH
6       START WITH sysdate
7       NEXT ROUND(SYSDATE)+5/24
8       WITH PRIMARY KEY
9    ENABLE QUERY REWRITE
10    AS
11    SELECT car_no cno
12           car_bez cbez
13    FROM cars
14 /
CREATE MATERIALIZED VIEW colinsuper.CARS_MV
FEHLER in Zeile 1:
ORA-00942: Tabelle or View does not exist
scott@orcl>
scott@orcl>
scott@orcl>When I am creating the materialized view without the user colinsuper, materialized view
is creating without problems.
scott@orcl>CREATE MATERIALIZED VIEW CARS_MV
2    TABLESPACE my_tablespace
3    BUILD IMMEDIATE
4    USING INDEX TABLESPACE my_idx
5    REFRESH
6       START WITH sysdate
7       NEXT ROUND(SYSDATE)+5/24
8       WITH PRIMARY KEY
9    ENABLE QUERY REWRITE
10    AS
11    SELECT car_no cno
12           car_bez cbez
13    FROM cars
14 /
Materialized View wurde erstellt.
scott@orcl>
scott@orcl>I think there is somthing wrong with the permissions of colinsuper!?

Is this colinsuper a user in the remote database.
ORA-00942:     table or view does not exist
Cause:
The table or view entered does not exist, a synonym that is not allowed here was used, or a view was referenced where a table is required. Existing user tables and views can be listed by querying the data dictionary. Certain privileges may be required to access the table. If an application returned this message, the table the application tried to access does not exist in the database, or the application does not have access to it.
Action:
Check each of the following:
the spelling of the table or view name.
that a view is not specified where a table is required.
that an existing table or view name exists.
Contact the database administrator if the table needs to be created or if user or application privileges are required to access the table.
Also, if attempting to access a table or view in another schema, make certain the correct schema is referenced and that access to the object is granted.

Create materialized view failed!

I want to create a mv from a table which does not contain primary key constraint,but failed. why?
SQL> Create Table tb_test01
2 (
3 Id Number,
4 Name Varchar2(1024)
5 );
Table created.
SQL>
SQL> Create Materialized View Log On tb_test01
2 With Sequence,Rowid(Id,Name)
3 Including New Values;
Materialized view log created.
SQL> Create Materialized View mv_tb_test01
2 Refresh Fast On Commit
3 As
4 Select * From tb_test01;
Select * From tb_test01
ERROR at line 4:
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 7
ORA-12014: table 'TB_TEST01' does not contain a primary key constraint

12014, 00000, "table '%s' does not contain a primary key constraint"
// *Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the
//          WITH PRIMARY KEY option and the master table did not contain
//          a primary key constraint or the constraint was disabled.
// *Action: Reissue the command using only the WITH ROWID option, create a
//          primary key constraint on the master table, or enable an existing
//          primary key constraint.

Cannot create Materialized View using PL/SQL procedure

Hello,
I have a question related to Materialized View creation.
I have a stored procedure that creates materialized view. When trying to run this procedure I get insufficient privileges error: ORA-01031.
When I run content of this procedure as anonymous PL/SQL block them materialized view is created without any complications.
Can you please advice me on that topic?
Is it even possible to create materialized view in stored procedure as I haven't found an info on it.
Thanks
Petr

Hi chudapet,
Whenever you do operation in procedure you need to have direct grants and not via a role.
Most probably the grant to create materialized view is available via a role to your user.
Assign direct grant to the user:
grant create materialized view to scott;
{code}

How to create one procedure which can drop and create materialized view

Hi,
I want to create one pl/sql procedure which can first drop materialized view CATEGORY_PK and after that create same materialized view CATEGORY_PK.
programme is as follows:
DROP MATERIALIZED VIEW CATEGORY_PK;
CREATE MATERIALIZED VIEW CATEGORY_PK REFRESH FORCE WITH PRIMARY KEY AS
SELECT cav1.ownerid AS categoryid, p.uuid AS productid ,p.domainID AS productdomainid,pav.stringvalue AS NAME
     ,pav2.stringvalue AS ID, pav3.stringvalue AS SHORT
FROM product p, product_av pav, catalogcategory_av cav1, catalogcategory_av cav2,product_av pav2,product_av pav3
WHERE
cav1.NAME = 'PRODUCT_BINDING_ATTRIBUTE' AND
cav2.NAME = 'PRODUCT_BINDING_VALUE' AND
cav1.ownerid = cav2.ownerid AND
p.uuid = pav.ownerid AND
          p.uuid = pav2.ownerid AND
          p.uuid = pav3.ownerid AND
pav.NAME = cav1.stringvalue AND
          pav2.NAME = cav1.stringvalue AND
          pav2.NAME = cav1.stringvalue AND
pav.stringvalue = cav2.stringvalue AND
          pav2.stringvalue = cav2.stringvalue AND
          pav3.stringvalue = cav2.stringvalue
UNION
SELECT catalogcategoryid AS categoryid, productid, repdomainid AS productdomainid,pav1.stringvalue AS NAME
     ,pav2.stringvalue AS ID, pav3.stringvalue AS SHORT
FROM productcategoryassignment ,product_av pav1,product_av pav2,product_av pav3
     WHERE pav1.ownerid=productid
     AND pav2.ownerid=productid
     AND pav3.ownerid=productid
     AND pav1.NAME='name'
     AND pav2.NAME='productID'
     AND pav3.NAME='shortDescription';

user498566 wrote:
I want to create one pl/sql procedure which can first drop materialized view CATEGORY_PK and after that create same materialized view CATEGORY_PK.That sounds like a waste of time and resources. What do you hope to achieve by this? A refresh? If so, a simple refresh of the old materialized view will do.
If you truly want to continue this road, you'll have to use the EXECUTE IMMEDIATE command to execute DDL commands from within PL/SQL.
Regards,
Rob.

Concept of materialized views in creating datawarehouse?????

Similar Messages

Maybe you are looking for