Materialized Views in Discoverer 4.1.33

While trying to create a summary folder I get an error that my user id does not have privilige /quota to create a materialized view and that summary management is not available because the user does not have global query rewrite privilige .
If any one has a resolution to this problem than please respond ASAP. The privilige tab in Disco Admin for the particular Business Area already shows all options for the user checked including the one for creating Summaries and the above error still crops up

Gurman,
The Privilege that are required to create a Summary Folder using Materialized views are,
1. Query Rewrite.
2. Create Any Materialized View.
3. Drop Any Materialized View.
4. Alter Any Materialized View.
So Login into SQL*Plus as SYS User or SYSTEM User or as any DBA User and execute the below SQL,
SQL> Grant Query ReWrite, Create Any Materialize View, Alter Any Materialized View, Drop Any Materialized View to <EUL OWNDER>;
This will solve your issue.
Thanks,
Selva.
null

Similar Messages

Materialized view not being used in the report

I have had a materialized view (MV) for a particular report. Recently, the report definition has changed little bit, so the existing MV is not being used by the report anymore. I copied the code Discoverer's SQL Inspection and recreated the materialized view. But still it is not working. Obviously, I am missing something at the database level. Does anyone have any idea? The database is 9i and Discoverer is 9.0.2. Thank you!

The SQL that you see from the Inspect SQL option will provide you with the SQL that Discoverer sends to the database. The database then may do a query rewrite to point to an available materialized view if available. This rewrite won't be seen from the inspect sql option. You need to check at the database level to verify if a query rewrite did in fact take place.
You may want to check the section titled "Query Rewrite with Materialized Views" from Ch1 - "Introduction to the Optimizer" in the Oracle9i Database Performance Tuning Guide and Reference, Release 2 (9.2), Part Number A96533-02, available at http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96533/optimops.htm#37287
Regards
Abhinav Agarwal
Oracle Business Intelligence Product Management
http://www.oracle.com/bi
http://www.oracle.com/technology/documentation/bi_ee.html
http://www.oracle.com/technology/software/products/ias/htdocs/101320bi.html
http://oraclebi.blogspot.com/

Materialized Views created using ROLLUP

Not sure if this one is best posted to a general Oracle forum, or even to the Discoverer Forum, but it's more to do with Data Warehousing so here goes...
1. If I create a materialized view, either with or without OWB, do I also need to separately create indexes on the materialized view?
2. If I create them using GROUP BY and ROLLUP (to create summaries that calculate all the subtotals along all hierarchies and dimensions), would any subsequent query have to use GROUP BY and ROLLUP to qualify for query rewrite?
3. If I create them using GROUP BY and ROLLUP, would the queries generated by Discoverer ever get rewritten, as I assume they would not use GROUP BY and ROLLUP as these were not features found in earlier versions of Oracle?
Any advice gratefully received.
Mark

Thanks for replying, Igor.
Just to clarify:
1. Do MV's created without fash refresh capabilities still get indexes created automatically? If not, should you manually create them in this instance?
2. Can you confirm that, if a MV gets created using GROUP BY and ROLLUP (to potentially calculate all dimension intersections in one go), users queries to the base fact table do not have to use ROLLUP in their GROUP BY clause - they will still get rewritten ok?
3. You mentioned that Discoverer generates queries using GROUP BY - does it ever use GROUP BY ROLLUP if it knows it's working on an Oracle 9i platform?
I guess where i'm coming from, is that we're considering using the OLAP Summary Manager within OEM to create materialized views, rather than the normal summary adviser, as this creates MV's designed to hold (R)OLAP cubes (as detailed at http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96520/mv.htm#574241). I wouldn't however want to use these if user's queries had to specify ROLLUP in their GROUP by clause to qualify for query rewrite.
Getting back to OWB, are there any plans to improve the support for importing, designing and refreshing materialized views in the Paris release of OWB? Summary management is perhaps a bit of a weak spot in OWB, and it'd be good if Hierarchical Cube Materialized Views - which are an excellent new feature in 9i - were supported in future releases.
best regards
Mark Rittman

LOV on Materialized View--Disco newbie

Hello Forum Members,
I have a materialized view with Region Name as a field.
I have create a parameter in Discoverer desktop[10g]. I am unable to get List of Values for the parameter.When I create the parameter based on a table I am getting list of values.
Please advise me.
Thanks

Please ignore my previous post.
Thanks

Disco 4i Error 'This user requires Create Any Materialized View Sys Priv'

Hi,
Firstly I will say we are late with moving to Disco 10g, fully understood and constantly remind people of need to upgrade.
Oracle Apps 11i instance, we have upgraded the database 10g.
In Disco 4i Admin, Import folder from Database, we receive Error Message:
*'This user requires Create Any Materialized View System Priviledge'*
Have spoken to number of our DBA's but been unable to resolve this. I have read loads of stuff about similar issues, but no direct hits really help me.
I am guessing we need to logon as SYSTEM db user and execute
h5. SQL> grant create materialized view to <username>;
h5. SQL> grant alter any materialized view to <username>;
Please can anyone advise, I am sure it's going to be a DB/Schema owner, as the username; i.e. APPS or EUL_US?
I cannot see it being the fnd_user for the Disco EUL owner, e.g. SYSADMIN or PatStock.
Thanks
Mike

Hi,
If you are doing the import as SYSADMIN then you are connected as APPS so this is the database user that needs additional privilege.
However, the APPS user only needs create materialized view privileges if there are manually created summary folders in the EUL, i.e. summary folders based on materialized views. If you are not using these then the privilege is not required.
The EUL_US user just needs to give Discoverer Administrator privileges to the SYS_ADMIN user. Nothing else should be needed.
Rod West

Support for 8i materialized views

Hi
Can anyone pls explain in breif what does the new feature "discoverer 4.1 admn supports oracle 8i materialized views" mean???
I just have an idea what a materilazed view mean..but iam unable to comprehend how discoverer uses or supports this feature.
Pls help me
Harati

While it is certainly true that a query with a UNION may be complex, it is relatively rare that it must be complex. The two things that make a UNION query complex in 10.1 (the criteria do tend to change in different releases) are
- One of the queries that is being UNIONed is complex
- The columns in the SELECT list do not match
In the first case, the root cause of the complexity is not the UNION, so I assume that's not what you have. The second case is generally pretty trivial to resolve, so it would be pretty rare that this would be a roadblock.
Of course, if you mean that you have a UNION ALL, not a UNION, you have a rather different problem.
Justin

Summary Folders vs Materialized Views

Hi everybody,
Which is best to use summary folders/tables or materialized views? In other words , can materialized views replace the summary folders or vice versa?
In which situations are we using materialized views and in which other situations are we using summary tables created by Discoverer..????
Thanks , a lot
Simon

Hi ,
I found at least one hindrance in creating a summary table from Discoverer Admin.
Whereas , in SQL , i can write freely , for example....
CREATE MATERIALIZED VIEW MV_DINAMIKOTITA_KLINON_TMHMA
BUILD IMMEDIATE
REFRESH START WITH TO_DATE(ADD_MONTHS(TRUNC(SYSDATE, 'RRRR'), 12) ,'DD/MM/RRRR')
NEXT TRUNC(ADD_MONTHS(SYSDATE,12),'RRRR')
AS
SELECT TO_CHAR(SYSDATE,'RRRR') YEAR, CODE_TMHMATA , COUNT(BED) DINAMIKOTITA
FROM BEDS
GROUP BY TO_CHAR(SYSDATE,'RRRR') , CODE_TMHMATA
where column 'BED' is of varchar2 datatype
in Discoverer , the clause count(bed) is not produced when i select the table beds , as expected....because is of varchar2 datatype.
When I add a custom item COUNT_BEDS which is a function count(beds) and trying to add it in the summary table an error message apperas:
'That item have default aggregate of Detail and cannot be added to the summary....'.
Having read the documetation and examples about summary tables , i found that at least one of the columns of the imported tables or views or mv's must be in number datatype , in order to be created as a summary table.....
In my case this means that the column 'BED' should be of number datatype not varchar2...
Are the above notes correct and how can i create the above displayed SQL statement as summary table...
Thanks , a lot , anyway
Simon

What is the difference between view and materialized views

Hi
What is the difference between view and materialized view ? can we update the base table using views

can we update the base table using viewsYes:
VIEWS
1. an updatable view is one that lets you perform DML on the underlying table
(see Oracle Database Concepts 10g - 5 Schema Objects)
2. non-updatable view requires INSTEAD OF Triggers
(see Oracle Database Concepts 10g - 22 Triggers)
SNAPSHOTS
You can have updateable (and writeable) snapshots - in updateable (writeable) MV replication.
Oracle uses snapshots (Materialized Views - MV) for two different purposes:
1. replication
2. automated Query Rewrite facility (first introduced in Oracle Discoverer, later included in Oracle database 8i).
Replication types in Oracle are:
a) Basic replication (MV replication)
- transaction based
- row-level
- asynchronous from master table to MV (Materialized View)
- DML replication only
- database 7 / 8.0 / 8i / 9i / 10g
- Standard and Enterprise Edition
1. Read-only MV replication
2. Updateable MV replication:
2.1 asynchronous from MV to master
2.2 synchronous from MV to master
3. Writeable MV replication
b) Multimaster replication
- transaction based
- row-level or procedural
- asynchronous or synchronous
- DML and DDL replication
- database 7 / 8.0 / 8i / 9i / 10g
- Enterprise Edition only
1. row-level asynchronous replication
2. row-level synchronous replication
3. procedural asynchronous replication
4. procedural synchronous replication
c) Streams replication
- (redo) log based
- row-level
- asynchronous
- DML and DDL replication
- database 9i / 10g (10g has Down Streams Capture)
- Enterprise Edition only (Standard Edition 10g can execute Apply process)
Regards,
Zlatko Sirotic

Refresh/Update data in a materialized view

Hi,
I have question about the data in a materialized view and how it is refreshed. My mat view has all my dimension-ids and my (for my specialize needs) aggregated measures from my fact table. I used the mat view wizard to create my view - which works perfectly. But now I wonder if I have to create some sort of mapping(?) or some sort of trigger to refresh the data in the mat view. Or is the data automatically refreshed when I start my fact table mappings. I use OWB 11gR2
thx

MVs have properties for refresh - you an refresh based on schedules or when dependent data is committed or manually.
Cheers
David

How can I fast refresh the materialized view !!

I created a MV base on some tables in order to improve the querey speed.
but the mv I have created falied to refresh fast.
because there are two same table in the from clause:
jcdm jc1,jcdm jc2
create materialized view temp_mv
nologging
pctfree 0
storage (initial 2048k next 2048k pctincrease 0)
parallel
build immediate
refresh force
on demand
as
select
TAB_GSHX.rowid hx_rid,
TAB_GSHD.rowid hd_rid ,
JC1.rowid jc1_rid ,
JC2.rowid jc2_rid ,
YSHD_ID     HXID,
JC1.JCDM     QFD,
JC2.JCDM     JLD
FROM
TAB_GSHX,
TAB_GSHD,
jCDM JC1,
JCDM JC2
WHERE
YSHD_ID=YSHX_ID
AND YSHD_QFD=JC1.JBJC_ID
AND YSHD_JLD=JC2.JBJC_ID
AND TO_CHAR(YSHX_time,'YYYYMMDD')='20030101'
the column msgtxt of the table MV_CAPABILITIES_TABLE is :
"the multiple instances of the same table or view" and " one or more joins present in mv".
How can I succeed in fast refresh the above temp_mv!!!
thanks.

lianjun,
When you are using Oracle9i there is a procedure which can help you setup the materialized view. If some option isn't working it gives you hint why it doesn't work.
The procedure is dbms_mview.explain_mview.
Take a look at the documentation how to use it. (In the Oracle9i DWH guide the package is explained.)
Hope this helps
With kind regards,
Bas Roelands

How to get Materialized View to ignore unused columns in source table

When updating a column in a source table, records are generated in the corresponding materialized view log table. This happens even if the column being updated is not used in any MV that references the source table. That could be OK, so long as those updates are ignored. However they are not ignored, so when the MV is fast refreshed, I find it can take over a minute, even though no changes are required or made. Is there some way of configuring the materialized view log such that the materialized view refresh ignores these updates ?
So for examle if I have table TEST:
CREATE table test (
d_id NUMBER(10) PRIMARY KEY,
d_name VARCHAR2(100),
d_desc VARCHAR2(256)
This has an MV log MLOG$_TEST:
CREATE MATERIALIZED VIEW LOG ON TEST with rowid, sequence, primary key;
CREATE MATERIALIZED VIEW test_mv
refresh fast on demand
as
select d_id, d_name
from test;
INSERT 200,000 records
exec dbms_mview.refresh('TEST_MV','f');
update test set d_desc = upper(d_desc) ;
exec dbms_mview.refresh('TEST_MV','f'); -- This takes 37 seconds, yet no changes are required.
Oracle 10g/11g

I would love to hear a positive answer to this question - I have the exact same issue :-)
In the "old" days (version 8 I think it was) populating the materialized view logs was done by Oracle auto-creating triggers on the base table. A "trick" could then make that trigger become "FOR UPDATE OF <used_column_list>". Now-a-days it has been internalized so such "triggers" are not visible and modifiable by us mere mortals.
I have not found a way to explicitly tell Oracle "only populate MV log for updates of these columns." I think the underlying reason is that the MV log potentially could be used for several different materialized views at possibly several different target databases. So to be safe that the MV log can be used for any MV created in the future - Oracle always populates MV log at any update (I think.)
One way around the problem is to migrate to STREAMS replication rather than materialized views - but it seems to me like swatting a fly with a bowling ball...
One thing to be aware of: Once the MV log has been "bloated" with a lot of unneccessary logging, you may perhaps see that all your FAST REFRESHes afterwards becomes slow - even after the one that checked all the 200000 unneccessary updates. We have seen that it can happen that Oracle decides on full table scanning the MV log when it does a fast refresh - which usually makes sense. But after a "bloat" has happened, the high water mark of the MV log is now unnaturally high, which can make the full table scan slow by scanning a lot of empty blocks.
We have a nightly job that checks each MV log if it is empty. If it is empty, it locks the MV log and locks the base table, checks for emptiness again, and truncates the MV log if it is still empty, before finally unlocking the tables. That way if an update during the day has happened to bloat the MV log, all the empty space in the MV log will be reclaimed at night.
But I hope someone can answer both you and me with a better solution ;-)

Materialized View to run only once in a year...

Hi everybody...
I want to create a materialized view which will run only once in a year and specifically some minutes after 00:00 a.m. on new year's day,
so i created the following:
CREATE MATERIALIZED VIEW <mv_name>
BUILD IMMEDIATE
REFRESH START WITH TO_DATE('01/01/2007 00:15:00','DD/MM/RRRR HH24:MI:SS')
NEXT SYSDATE+366
I have two notes:
1) how to declare the refresh to be done the first new year's day after the day it'll be created , i mean not static date (01/01/2007)
2)some years are leap and some are not , so in order to run every new year's day how should i transform the above..????
3)is there any view which displays the next run of a materialized view..???
the view DBA_MV_REFRESH_TIMES displays the last refresh of mv's...
I use Oracle 10.2.0.1 on XP ...
Thanks , a lot
Simon

1).
use the expression that evaluates to next january first.
SQL> select sysdate, add_months(trunc(sysdate, 'yyyy'), 12) from dual ;
SYSDATE ADD_MONTHS(
19-JUN-2006 01-JAN-2007
1 row selected.
SQL>2). for this also use the same expression that will evaluate to the january first of the year after that.

Is it possible to refresh the table from a Materialized view

Hi,
Is it possible to update the underlying table on which a Materialized view is created when some changes in a Materialized view is done.Is this reverse compatibility possible in Materialized View?
Thanks in Advance,
V.Dennis

If you created the materialized view as UPDATEABLE then changes to it should automatically be relected in the underlying table. If this is not occurring I suggest you check the replication jobs. You probably have a stack of errors in DEFERROR.
Cheers, APC

The data of my materialized view....in the while

Hello
We have problems with materialized views
We have one wich re-build each a short period of time
¿Can i avoid the data to dissapear in the time process of refresh?
Is so annoing to our clients to see that "from time to time" the data just dissapear for one period of time -the time while the materialized view is refreshing-
Thank you in advance
Bruno. Madrid. Spain

> Is so annoing to our clients to see that "from time to time" the data just dissapear for
one period of time -the time while the materialized view is refreshing-
Have a similar problem. And dealing with large data volumes that makes the DELETE of the MV a very undesirable feature. Not as much a the resource footprint required, but the time it takes to do this - and the very tight processing windows that exist.
The solution is a self-rolled and very likely not ideal for most - but it works well enough for us in production.
No MV. Create a partition table. Create a staging table. Do a manual "full refresh" of the staging table (TRUNCATE and direct path INSERT). Follow this by a partition exchange with the partition table (no validation and including indexes). The result is that the data is replaced in the partitioned table within a second - no long running and expensive DELETE. End-users not effected by having a truncate pulling the data from beneath their reports.

Exporting data from a materialized view in Oracle 10g

Can anybody tell me how to export data to a remote server and import data in that remote server without using ftp utility. Actually I want to export the data from a materialized view to the remote server and import the same in the remote server.
If everything works well, I'll put the exporting and importing in a cronjob.
Please let me know how can I do that if that's possible .
Any reply would be appreciated.
Thanks.

Here is what I'm trying to do.
I created materialized views using multiple base tables in my local server and the base tables got populated using a long process.
Now I want to copy those data alone to some remote server since it doesn't have any base tables in it. For now, the remote server should depends on the localserver's data. I'm going to use the remote server's data for some testing purposes.
I know it is easy to create mat.views in the remote server but it doesn't have I don't want to do that now. I just want to copy the snapshots from my local server to the remote server.
Please let me know how to do that.
Thanks.

Materialized Views in Discoverer 4.1.33

Similar Messages

Maybe you are looking for