Better Materialized View support in 11g?

We are using materialized views as a work-around to improve performance on versioned tables with spatial data and would like to know if there will be improved support in 11g.
Currently we have to do a complete refresh but would like to use options like "fast refresh" or "on commit".
Regards,
Lewis.

Hi Lewis,
Using materialized views with Workspace Manager still requires a complete refresh in 11g. Changes to allow incremental refresh are not currently possible within Workspace Manager.
Regards,
Ben

Similar Messages

Bug: Can not create materialized view log on 11G XE

Hi,
I log in as HR user and try create materialized view log
CREATE MATERIALIZED VIEW LOG ON HR.EMPLOYEES;I get error
>
Error starting at line 1 in command:
CREATE MATERIALIZED VIEW LOG ON HR.EMPLOYEES
Error at Command Line:1 Column:0
Error report:
SQL Error: ORA-00439: feature not enabled: Advanced replication
00439. 00000 - "feature not enabled: %s"
*Cause: The specified feature is not enabled.
*Action: Do not attempt to use this feature.
>
You can create materialized view log on 10G XE without any problem.
Regards,
Jari
http://dbswh.webhop.net/dbswh/f?p=BLOG:HOME:0

Is it a bug in 11g or 10g?
It was reported earlier in now archived beta forum. {thread:id=2214092}
The current doc lists MV sites only (and "No" for Advanced Replication feature):
http://download.oracle.com/docs/cd/E17781_01/license.112/e18068/toc.htm#BABDFDAI

A quicker way to create a materialized view?

Hi,
I'm new to replication and have been reading doco on it. Basically I want to set up read-only materialized views in oracle 11g.
So on the replicated database I created a db link that points to the master db.
Then I created a materialized view that does "select * from table@dblink" and that is forced refresh every 10 minutes.
Problem is that the table on the master db is large and the network link is slow, so the "create materialized view" statement would take a long time to complete.
So I think to speed up the process I would export/import the table from master to replicated db, then make this imported table a materialized view somehow.
Is this possible, and if so, how?
Thanks.
Long

If you are able to use other means (exp-imp, expdp/impdp, unload-sqlldr, externalfile etc) to copy the data faster (as a normal table in the target database), you can then use the "ON PREBUILT TABLE" clause in the CREATE MATERAILIZED VIEW statement.
See
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_6002.htm#i2063793
Alternatively, you must first verify if the CREATE is slow only because of SQL Query performance on the source, rather than because of network bandwidth/latency. If query execution needs to be tuned, that would be a cleaner solution, because the Refresh can then be automatically handled by Oracle.
Remember that you can use Materialized View Log(s) on the source tables to enable FAST Refresh's as well.

Truncate table and materialized view log

I user oracle 10 R2
I have a table and on that table a materialized view log.
I execute in a pl/sql procedure:
1) execute immediate('drop materialized view log on tab1');
then:
2) execute immediate('truncate table tab1');
3) Now I insert a lot of records in tab1
4) execute immediate('create materialized view log on tab1 WITH rowid INCLUDING NEW VALUES');
When I create the materialized view log I recieved this message:
ora32321: refresh fast on tab2 unsupported after detail table truncate
Why?

Refresh fast after truncate operation on container table is not supported, regardless the container table is or is not partitioned.
Perform a refresh complete.
ORA-32321 :
Cause:     A detail table has been truncated and no materialized view
     supports fast refersh after a detail table has been truncated
Action:     Use REFRESH COMPLETE. Note: you can determine why your
     materialized view does not support fast refresh after TRUNCATE
     using the DBMS_MVIEW.EXPLAIN_MV() API.

Materialized Views or DBMS_JOBS?

Hellow
I have a situation where there are 2 database servers "db1" and
"db2". Both the servers have a common schema containing common tables.
Some tables in db1 is getting updated repeatedly in every 3sec. I need
to synchronise this tables with the corresponding replica tables in
db2 after every 4sec.
I cannot opt for trigger because in every 3 sec entire data in the
able is flushed out and new data is populated....so i need to wait for 3
sec and then do the same thing for the replica table in db2 by copying data
from db1 to db2...
what option will be better Materialized View or DBMS_JOB...I mean i
thought of writing a plsql script which will update the table in db2
after every 5sec..by associating this script with DBMS_JOB
performance wise which will be more better?
Regards
sam

Actually it is getting populated by new coordinates which depict the latest location of a moving object. this data is constantly getting updated (deleted and re-populated)
this is being done in db1 and we are asked to replicate the tables and populate the latest data from the tables in db1 to corresponding tables in db2.
we need to perform the same operation in db2 in every 5sec...thats the main issue
we will be accessing these coordinates and display them on a map, later...
performance wise which option will be good
1. Materialized Views
2. DBMS_JOBS (relating to a pl/sql code)
also is there any much difference in performance from a normal view when compared to materialized views?
please suggest
Regards
Sam

Issue with materialized view and fast refresh between Oracle 10g and 11g

Hi all,
I've hit a problem when trying to create a fast-refreshable materialized view.
I've got two databases, one 10.2.0.10, another 11.2.0.1.0, running on 32-bit Windows. Both are enterprise edition, and I'm trying to pull data from the 10g one into the 11g one. I can happily query across the database link from 11g to 10g, and can use complete refresh with no problem except the time it takes.
On the 10g side, I've got tables with primary keys and m.v. logs created, the logs being of this form ...
CREATE MATERIALIZED VIEW LOG ON table WITH PRIMARY KEY INCLUDING NEW VALUES
On the 11g side, when I try to create an m.v. against that ...
CREATE MATERIALIZED VIEW mv_table REFRESH FAST WITH PRIMARY KEY AS SELECT col1, col2 FROM table@dblink;
... I get an ORA-12028 error (materialized view type is not supported by master site).
After running the EXPLAIN_MVIEW procedure it shows this;
REFRESH_FAST_AFTER_INSERT not supported for this type mv by Oracle version at master site
A colleague has managed to build a fast-refresh m.v. from the same source database, but pulling to a different one than I'm using; his target is also 10g, like the (common) source, so I've no idea why I'm getting the 'not supported' message whilst he isn't.
I've been able, on previous projects, to do exactly what I'm trying to achieve but on those someone with more knowledge than me has configured the database!
I'm now stumped. I'm also no DBA but despite that it's been left to me to install the new 11g database on the 32-bit Windows server from scratch, so there are probably a couple of things I'm missing. It's probably something really obvious but I don't really know where to look now.
If anyone can give me any pointers at all, I'd be really grateful. This question is also duplicated in the Replication forum but hasn't had any replies as yet, so I'm reproducing it here in hope!
Thanks in advance,
Steve

Hi Steve,
You should have a look at metalink, Doc ID 1059547.1
If that does not help, there may be something else in Mater note ID 1353040.1
Best regards
Peter

Problems in creating Materialized View from 10g R2 to 11g

Hi,
We have two databases in 10g Release 2. These databases are on two different servers and we use
Materialized views to replicate data between these servers. We are currently using 64 bit version of
oracle 10g release 2 for LINUX.
Oracle Database 10g Release 10.2.0.1.0 - 64 bit Production
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
We use CENTOS 5 - 64 bit edition
We upgraded one of the databases to 11g (We exported the data from old database and
imported it in new database) . Then we tried to create a Materialized view with incremental refresh
on it where the base table is in the second Oracle 10g database.
The problem is that it is not letting us create the view with FAST Refresh. It kept on giving ORA-12028
error. We tried different remedies suggested on forums like creating a view with ROWID, but still it
continued giving us the same error. We also synchronized the characterset of Oracle 10g and Oracle 11g
installations but still it did not work.
Our base table size is pretty large (over 10 Million records) and if we do a full refresh, it takes hours to
refresh it.
Without incremental refresh, we will not be able to fucntion, and to upgrade both database simultaneously
we will need a large down-time which also we can not afford.
Please advise what should we do.
Best Regards
Madhup
Edited by: Madhup on Mar 2, 2009 10:45 AM

Hello,
Yesterday I met the same problem and very sad about this, however, my story is much more complicated (I think so).
I have 6 databases:
2 - 11g
2 - 10g
2 - 9i
Every database of each release has different characterset(UTF8 and AL16UTF16).
I am trying to create Materialized view with FAST REFRESH on Oracle 11g, when master tables are located on 10g database and 9i database.
Materialized view, which points to 9i database, was successfully created.
Materialized view, which points to 10g database, gets ORA-12028
Like you, I tried many notes from METALINK and thought at the begining that the problem is my characterset. But, when the materialized views were successfully built on Oracle 9i database, I understood that the problem is something else.
Did you find the actual reason why this issue does not work??
Thanks,
Alex

ORACLE 11G XE-Materialized view info/issue

Hi,
I have two Oracle XE databases with the version 11g, now i want to sync both of this dbs using materialized view feature.
I have created base table in primary db and created materialized view in secondary db using db link.
It got created and am able to view the records first time. but when i am selecting view next time its not reflecting changed records.
Please suggest what needs to do to get it reflected in secondary db.
mv query is as below
CREATE MATERIALIZED VIEW mv_emp_pk
     REFRESH FAST START WITH SYSDATE
     NEXT SYSDATE + 1/86400
     WITH PRIMARY KEY
     AS SELECT * FROM emp@remote_db;
Regards
Kiran

The name of this forum is "Streams" not "Materialized Views." Please post your question in the correct forum. Thank you.

Materialized View - Refresh in 10g FAST .. refresh in 11g SLOW

Sorry I'm not able to paste anything.
The customer moved their database from 10g to a 11gR2 database.
They created the MV in the new system and now it takes 26 hours to refresh
as opposed to 15 min in the old 10g database.
Just looking for a game plan for troubleshooting.
I know I'm not providing much of anything so please forgive me.
Where would you look first ? Explain plan .. system settings .. ? Let me know.
If you have a good reference then that would work. The docs are not working.
Thanks in advance.
BB

Do you mean they upgraded their existing database from 10g to 11gr2?
Or do you mean they loaded the data into a new 11gr2 database?Yeah I confirmed this morning that they data-pumped the entire database to the 11g host.
Unless you provide more information there is no way to provide any specific suggestions.
What kind of MV? Are the source and MV on the same server?They do a manual refresh :
create materialized view (mview_name as select ...)
dbms_snapshot.refresh(mview_name, 'C')
The source is the same for both however it is from a place that uses a connection.
If it is a new DB then there may be missing indexes or constraints.
The MV may initially be empty and the first refresh will be a COMPLETE
one that will take a lot longer than an incremental.
Some of the objects or constraints could be invalid. The indexes appear to be the same and the constraints enabled/disabled in the same manner.
They confirmed that the refresh after the initial is taking way too long compared to before (10g).
Oddly some of the mviews see no performance degradation in the new environment.
They have many.
Thanks for taking the time to think about it. It was much appreciated.
If I get to the bottom of it I'll let everybody know.
BB

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

CacheConnect Support for Oracle Materialized View

Does TimesTen cacheconnect support caching Oracle Materialized views? It is my understanding that materialized views are really just Oracle tables under the covers.

hi Scheung,
I noted following description in Page40 of standard document 6.0.8 cacheconnect.pdf
Note: You can define a USERMANAGED cache group to include an Oracle
materialized view, but the cache group will be restricted, as described in “About
restricted cache groups” on page 49. Alternatively, you can create any type of
cache group to include an Oracle detail table for a materialized view.
and actually in 7.0.2, we can still create usermanaged cache group based on Oracle MV, but the above description disappears in 7.0.2 document. is it deprecated ?

How to view SQL for a materialized view in SQL Developer (Oracle 11g R2)

Good Morning,
I am new to SQL Developer 3.1.07 and just installed it on a Windows 7 PC yesterday.
There's a materialized view for which I need to view (and eventually update) the SQL. The mat'lized view is in another schema, but my Oracle user does have access to the schema and to this particular mat'lized view. My user also has SELECT, INSERT, UPDATE, DELETE, DEBUG, and ALTER permissions. When I select (click on) the matl'ized view in the object tree on the left, a multi-tab window opens with information in the Columns, Indexes, Grants, Dependencies and Details tabs, but the SQL pane is blank. I don't know if there's some other GRANT that I need in Oracle, or if there's something else I need to do in SQL Developer to see the matl'ized view SQL.
Thanks
Bob Gardner
[email protected]

1007420 wrote:
There's a materialized view for which I need to view (and eventually update) the SQL. The mat'lized view is in another schema, but my Oracle user does have access to the schema and to this particular mat'lized view. My user also has SELECT, INSERT, UPDATE, DELETE, DEBUG, and ALTER permissions. When I select (click on) the matl'ized view in the object tree on the left, a multi-tab window opens with information in the Columns, Indexes, Grants, Dependencies and Details tabs, but the SQL pane is blank. I don't know if there's some other GRANT that I need in Oracle, or if there's something else I need to do in SQL Developer to see the matl'ized view SQL.SQL*Developer can be tricky regarding what it shows for other schemas. I'm not sure what privileges you might need besides the one you listed except RESOURCE on the MV, or maybe CREATE ANY MATERIALIZED VIEW.
Can you use DBMS_METADATA.GET_DDL to get the data you want (may/may not work due to privileges)?

Creating collection vs. materialized view - better performance?

Hi, I am trying to improve the performance of our application and am looking at everything possible. I am wondering if the use of multiple, complex collections is slowing down our application. Would the use of materialized views, as opposed to collections improve things? thanks Karen

to provide more info....
here is the process which creates the list of species based on favorite species identified (and followed by the query to select from this collection)
declare
yes_are NUMBER;
pCount NUMBER;
l_seq_id NUMBER;
yes_hms NUMBER;
found_area NUMBER;
found_unit NUMBER;
unitmeasure VARCHAR2(2);
pbCount NUMBER;
pbPrice NUMBER;
begin
--create license collection so that if error on a submit the information retains
if apex_collection.collection_exists('LICENSE_COLLECTION') then
apex_collection.delete_collection('LICENSE_COLLECTION');
end if;
--create vessel collection so that if error on a submit the information retains
if apex_collection.collection_exists('SUPVES_COLLECTION') then
apex_collection.delete_collection('SUPVES_COLLECTION');
end if;
apex_collection.create_or_truncate_collection('FP_COLLECTION');
--create collection to save landings
apex_collection.create_or_truncate_collection('SPECIES_COLLECTION');
--loop through the favorite species and populate with pre-existing data
for rec IN (select *
from frequent_species
where permit_id = :G_PERMIT_ID
order by fav_order)
LOOP
-- check to see if there is a priceboard entry for the favorite species
select count(*) into pbCount
from price_board
where permit_id = :G_PERMIT_ID and
species_itis = rec.species_itis and
grade_code = rec.grade_code and
market_code = rec.market_code and
unit_of_measure = rec.unit_measure and
price is not null;
-- if there is a price board entry
if pbCount = 1 then
--get the default price for that species combination
select price into pbPrice
from price_board
where permit_id = :G_PERMIT_ID and
species_itis = rec.species_itis and
grade_code = rec.grade_code and
market_code = rec.market_code and
unit_of_measure = rec.unit_measure and
price is not null;
--add landings row with price board data
l_seq_id := apex_collection.add_member('SPECIES_COLLECTION',
null,
null,
null,
rec.species_itis,
rec.grade_code,
rec.market_code,
rec.unit_measure,
nvl(rec.disposition_code,:G_FIRST_DISPOSITION),
0, null,pbPrice,null);
-- no price board entry
else
-- add landings row without any priceboard data
l_seq_id := apex_collection.add_member('SPECIES_COLLECTION',
null,
null,
null,
rec.species_itis,
rec.grade_code,
rec.market_code,
rec.unit_measure,
nvl(rec.disposition_code,:G_FIRST_DISPOSITION),
0, null,null,null);
end if;
apex_collection.update_member_attribute(p_collection_name=>'SPECIES_COLLECTION',
p_seq => l_seq_id,
p_attr_number =>14,
p_attr_value => 'ERROR');
--set first disposition
:G_FIRST_DISPOSITION := nvl(rec.disposition_code,:G_FIRST_DISPOSITION);
found_area:=0;
-- All rows need to be checked to determine if additional info is needed based on partner_options table
-- check if AREA will be needed
select count(*) into found_area
from partner_options
where partner_id = :G_ISSUING_AGENCY and
substr(species_itis,1,6) = rec.species_itis and
option_type = 'ARE' and
nvl(inactivate_option_date, sysdate) >= sysdate;
-- landing row requires AREA data
if found_area > 0 then
apex_collection.update_member_attribute(p_collection_name=>'SPECIES_COLLECTION',
p_seq => l_seq_id,
p_attr_number =>13,
p_attr_value => 'Y');
-- landing row does NOT require AREA data
else
apex_collection.update_member_attribute(p_collection_name=>'SPECIES_COLLECTION',
p_seq => l_seq_id,
p_attr_number =>13,
p_attr_value => 'N');
end if;
found_unit := 0;
-- check if COUNT will be needed
select count(*) into found_unit
from partner_options
where partner_id = :G_ISSUING_AGENCY and
substr(species_itis,1,6) = rec.species_itis and
option_type = 'LBC' and
nvl(inactivate_option_date, sysdate) >= sysdate;
-- landing row requires UNIT data
if found_unit > 0 then
select unit_measure into unitmeasure
from partner_options
where partner_id = :G_ISSUING_AGENCY and
substr(species_itis,1,6) = rec.species_itis and
option_type = 'LBC' and nvl(inactivate_option_date, sysdate) >= sysdate;
apex_collection.update_member_attribute(p_collection_name=>'SPECIES_COLLECTION',
p_seq => l_seq_id,
p_attr_number =>17,
p_attr_value => 'Y');
apex_collection.update_member_attribute(p_collection_name=>'SPECIES_COLLECTION',
p_seq => l_seq_id,
p_attr_number =>19,
p_attr_value => unitmeasure);
--landing row does NOT require UNIT data
else
apex_collection.update_member_attribute(p_collection_name=>'SPECIES_COLLECTION',
p_seq => l_seq_id,
p_attr_number =>17,
p_attr_value => 'N');
end if;
-- check if HMS
SELECT count(*) into yes_hms
FROM HMSSpecies a
where hmsspeciesitis = rec.species_itis;
-- landing row requires HMS data
if yes_hms > 0 and rec.grade_code = '10' then
apex_collection.update_member_attribute(p_collection_name=>'SPECIES_COLLECTION',
p_seq=> l_seq_id,
p_attr_number=>20,
p_attr_value=>'Y');
else
-- landing row does NOT require HMS data
apex_collection.update_member_attribute(p_collection_name=>'SPECIES_COLLECTION',
p_seq=> l_seq_id,
p_attr_number=>20,
p_attr_value=>'N');
end if;
end loop;
end;
and the query for the region:
SELECT
apex_item.text(1,seq_id,'','','id="f01_#ROWNUM#"','','') "DeleteRow",
apex_item.text_from_LOV(c004,'SPECIES')||'-'||apex_item.text_from_LOV(c005,'GRADE')||'-'||apex_item.text_from_LOV(c006,'MARKETCODE')||'-'||apex_item.text_from_LOV_query(c007,'select unit_of_measure d, unit_of_measure r from species_qc') unit,
apex_item.select_list_from_LOV(6,c008,'DISPOSITIONS','onchange="getAllDisposition(#ROWNUM#)"','YES','0',' -- Select Favorite -- ','f06_#ROWNUM#','') Disposition,
apex_item.select_list_from_LOV(7,c009,'GEARS','style="background-color:#FBEC5D; "onFocus="checkGearPreviousFocus(#ROWNUM#);"onchange="getAllGears(#ROWNUM#)"','YES','0','-- Select Favorite --','f07_#ROWNUM#','') Gear,
apex_item.text(8,TO_NUMBER(c010),5,null,'onchange="setTotal(#ROWNUM#)"','f08_#ROWNUM#','') Quantity,
apex_item.text(9,TO_NUMBER(c011),5,null,'onchange="getPriceBoundaries(#ROWNUM#)"','f09_#ROWNUM#','') Price,
apex_item.text(10, TO_NUMBER(c012),5,null, 'onchange="changePrice(#ROWNUM#)" onKeyPress="selectDollarsFocus(#ROWNUM#);"','f10_#ROWNUM#','') Dollars,
apex_item.select_list_from_LOV_XL(11, c014,'AREAFISHED','style="background-color:#FBEC5D; "onchange="getAllAreaFished(#ROWNUM#)"','YES','ERROR','-- Select Area Fished --','f11_#ROWNUM#','') Area_Fished,
apex_item.text(12, c018,4,null,'style="background-color:#FBEC5D; "onBlur="setUnitQuantity(#ROWNUM#)"','f12_#ROWNUM#','') UNIT_QUANTITY,
apex_item.text(13, 'CN',3,null,'readOnly=readOnly','f13_#ROWNUM#','') UNIT_COUNT,
apex_item.checkbox(14,'Y','id="f14_#ROWNUM#" style="background-color:#FBEC5D; " onClick="alterYes(#ROWNUM#);" onKeyPress="alterYes(#ROWNUM#);"',c021) FinsAttached,
apex_item.checkbox(15,'N','id="f15_#ROWNUM#" style="background-color:#FBEC5D; " onClick="alterNo(#ROWNUM#);" onKeyPress="alterNo(#ROWNUM#);"',c022) FinsNotAttached,
apex_item.checkbox(16,'U','id="f16_#ROWNUM#" style="background-color:#FBEC5D; " onClick="alterUnk(#ROWNUM#);" onKeyPress="alterUnk(#ROWNUM#);"',c023) FinsUnknown
from apex_collections
where collection_name = 'SPECIES_COLLECTION' order by seq_id
/

Transform 3D to 2D Data via a Materialized View

Hi,
I'm playing with Geoserver against an Oracle Locator database. Things are starting well, but I did notice a bug where 3D points and lines are not supported. I guess this is an issue with GeoTools. Anybody have a way to transform my 3D data to 2D. Since I do use the 3rd dimension for storing elevation, I don't want to lose the data. So I was thinking that I could create materialized views to "virtually strip" the 3rd dimension. Any thoughts? I'm not very strong in PL/SQL, so any code hints would be greatly appreciated as well.
Thanks!
Jeff

I would say the compiled pl/sql would be faster (it would also depend on whether you compiled to the pl/sql virtual machine code - MP-code or the machine-dependent code of the host's C compiler if you chose native copilation): I am coding a Java version of my GEOM.SDO_CENTROID function so will be in a better position to say, categorically, one way or the other.
In my free pl/sql packages there are these functions in case anyone is interested:
   -- @function To_2D
   -- @precis   Converts a 3D geometry to a 2D geometry
   -- @version 2.0
   -- @usage    v_2D_geom := geom.To_2D(MDSYS.SDO_Geometry(3001,....)
   -- @history Albert Godfrind, July 2006, Original Coding
   -- @history Bryan Hall,      July 2006, Modified to handle points
   -- @history Simon Greener,   July 2006, Integrated into geom with GF.
   Function To_2D( p_3D_geom IN MDSYS.SDO_Geometry )
     Return MDSYS.SDO_Geometry deterministic;
   -- @function To_3D
   -- @precis   Converts a 2D geometry to a 3D geometry
   -- @version 1.0
   -- @usage    v_3D_geom := geom.To_3D(MDSYS.SDO_Geometry(2001,....),50)
   -- @history Simon Greener,   May 2007 Original coding
   Function To_3D( p_2D_geom   IN MDSYS.SDO_Geometry,
                   p_default_z IN NUMBER := NULL)
     Return MDSYS.SDO_Geometry deterministic;
   /** @Function : FIX_3D_Z
   ** @Precis   : Checks the Z ordinate in the SDO_GEOMETRY and if NULL changes to p_default_z value
   ** @Note     : Needed as MapServer appears to not handle 3003/3007 polygons with NULL Z values in the sdo_ordinate_array
   ** @History : Simon Greener - JUNE 4th 2007 - Original Coding
   Function Fix_3D_Z( p_3D_geom   IN MDSYS.SDO_Geometry,
                      p_default_z IN NUMBER := -9999 )
            Return MDSYS.SDO_Geometry Deterministic;
/** Function just to change a single point coded in sdo_ordinates to sdo_point representation
* @param p_geometry A sdo_geometry object.
Function ToSdoPoint ( p_geometry in MDSYS.SDO_Geometry )
    return MDSYS.SDO_Geometry Deterministic;Simon

Fast refresh of "materialized view with joins only"

Hi,
My Requirement:
I need to create a materialized view joining two tables.
Table1 -> Does not have primary key
Table2 -> Has a primary key
I need to refesh the mat view only when DML commands are done on Table1 alone.
And it will be better if i have a Refresh on commit rather on demand.
The following code is what i used and it dint work for me:
CREATE MATERIALIZED VIEW LOG ON Table1 WITH ROWID;
CREATE MATERIALIZED VIEW LOG ON Table2;
CREATE MATERIALIZED VIEW AAYT_ETF
REFRESH FORCE ON COMMIT
ENABLE QUERY REWRITE
AS
SELECT A.rowid "table1_rowid", A.ACCTNUM, A.CORR_NUM, A.OFC_NUM, A.RR_NUM, A.BUY_SELL_CDE, A.ACT_AMT, A.CSP_SYM, A.SECR_DESC, A.ACT_QTY
FROM Table1 A, Table2 G WHERE
A.CSP_NUM = G.CSP_NUM AND
G.ASST_SUB_STYP = 'ETF';
Issue Faced: In this case the refresh happends even while i do DML on Table2.
But i need the refresh only when i do DML on Table1. I also unable to create Refresh Fast Mat view.
Can anyone please tell me how to create the Materialized view Log and the Materialized view. Thanks in advance.

This forum only is for questions relating to the use of OLAP Option. I would post your question on the database forum.
Keith Laker
Oracle Data Warehouse Product Management
OLAP Blog: http://oracleOLAP.blogspot.com/
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
DM Blog: http://oracledmt.blogspot.com/
OWB Blog : http://blogs.oracle.com/warehousebuilder/
OWB Wiki : http://wiki.oracle.com/page/Oracle+Warehouse+Builder
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

Better Materialized View support in 11g?

Similar Messages

Maybe you are looking for