Materialized views in 8i and 9i

Hi All,
I wanted to know the differences/comparison of MVs in 8i and 9i versions.
Can you please lead me to some documentation if available on this?
Thanks in advance...
BRK

I would suggest you check out DbEncrypt for Oracle from www.appsecinc.com. You get download a free evaluation versions. It provides a fully functional encryption system including key manangement, transparent encryption, etc...

Similar Messages

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

How to create materialized view with parameter and index ?

Hi all,
i am using oracle 11g.
i want to create parameter materialized view with two parameter (STORED_VALUE, LOV_NAME) with an index .
i have below view
CREATE OR REPLACE FORCE VIEW SR_MY_TEST(DISPLAYED_VALUE, STORED_VALUE, LOV_NAME) AS
SELECT DISPLAYED_VALUE , LOVVALUE.STORED_VALUE , lovname.lov_name
           FROM (SELECT T.LOV_VALUE_ID,
      T.LOV_ID,
      T.ORG_ENTITY_ID,
      T.STORED_VALUE,
      T.DISPLAYED_VALUE,
      T.ENTERPRISE_ID
     FROM MS_QS_LIST_OF_VALUES_T T) lovvalue, ms_qs_lov_names lovname
          WHERE lovvalue.lov_id = lovname.lov_id
            AND lovvalue.org_entity_id = 1
            and LOVVALUE.ENTERPRISE_ID = 100000
            AND LOVNAME.ENTERPRISE_ID = 100000;
i want to create index on   STORED_VALUE, LOV_NAME
Thanks
Damby

No.AFAIK, there's nothing called as "parameterized MV".
Materialized View store data like tables (and not like Views). So, does it make sense when you say - "table with parameters" ?
Could you please explain your business requirement?
What is the purpose behind those 2 parameters?

Why materialized view taking hours and yet not created

hi,
i am trying to create the following MV
create materialized view MV1
force on demand
start with date 1 next date2
AS
select query 1--> complex query that return approcimately 2 millions rows
union all
select query2 --> complex query that returns 300K rowsit has been taking hours i.e > 4 hrs and still unable to create the MV
w/o the create materialized view statement i am able to return the results from the union of the 2 queries
what might be the possibility ?
tks & rdgs

Issue could be due to the complexity of your query..Even i faced the same issue when i worked on materialized views.It was taking too long to create materialized view and then we splitted the query and created two materialized views.
Finally created a View for those MV's.You can also try the same
Materialized View Log
When you create a materialized view using the FAST option you will need to create a view log on the base tables.A fast refresh uses materialized view logs to update only the rows that have changed since the last refresh.
When DML changes are made to the master table's data, Oracle stores rows describing those changes in the materialized view log and then uses the materialized view log to refresh materialized views based on the base table. This process is called an incremental or fast refresh.Without a materialized view log, Oracle must reexecute the materialized view query to refresh the materialized view. This process is called a complete refresh.Usually, a fast refresh takes less time than a complete refresh.
You can go through the below link
http://www.lc.leidenuniv.nl/awcourse/oracle/server.920/a96567/repmview.htm
Thanks
Suni

Materialized View - "use log" and its "master table" assigned

Oracle 10 g R2. Here is my script to create a mv, but I noticed two interestes properties by EM
CREATE MATERIALIZED VIEW "BAANDB"."R2_MV"
TABLESPACE "USERS" NOLOGGING STORAGE ( INITIAL 128K) USING INDEX
TABLESPACE "BAANIDX" STORAGE ( INITIAL 256K)
REFRESH FORCE ON COMMIT
ENABLE QUERY REWRITE AS
SELECT CM.ROWID c_rid, PC.ROWID p_rid, CM."T$CWOC", CM."T$EMNO", CM."T$NAMA", CM."T$EDTE", PC."T$PERI", PC."T$QUAN", PC."T$YEAR", PC."T$RGDT"
FROM "TTPPPC235201" PC , "TTCCOM001201" CM
WHERE PC."T$EMNO"(+)=CM."T$EMNO"
In EM, the MV list shows a column - "Can Use Log".
1. What does it mean?
2. Why it only says yes, when I used above codes to create the MV; but says "NO" when I created the MV by "OUT JOIN"? no matter is "LEFT.." or "RIGHT JOIN"
3. I also noticed that there is a column - "master table" and it always shows the name of the last table on the from list. Why? More important, does it matter to process. It shows the same table name when I use the "OUT JOIN" clause in from
I have created mv log on each master table with row_id.

Review the rules for your version of Oracle, you didn't think it important to name it, with respect to when you can do FAST REFRESH and when it can use REFRESH LOGs.

Materialized View creation advice and SQL advice

I want to create a materialized view for the table below. The materialized view should query data from only this table and i want to join 2 rows to one.
The key for the joins are the column internal_correlation_id which is unique for request/response pair.
The table is updated every day with 2 million rows.
What type of materialized view should i use and how can i query to get one row?
CREATE TABLE EVENT (
       caller_id                              VARCHAR2(255)          NOT NULL
     , service_id                         VARCHAR2(255)          NOT NULL
     , country_code                         VARCHAR2(2)
     , internal_correlation_id                  VARCHAR2(255)          NOT NULL -- Unique for request response pair
     , received_date                         DATE                    NOT NULL
     , status                              VARCHAR2(20)
     , queue_name                         VARCHAR2(255)          NOT NULL
     , USER_ID                              VARCHAR2(50)
     , engine_id                         VARCHAR2(50)
     , tracking_correlation_id                  VARCHAR2(2000)
     , mnc                              VARCHAR2(20)
     , mcc                              VARCHAR2(20)
     , request_type                         VARCHAR2(50) -- REQUEST or RESPONSE
     , app_id                              VARCHAR2(50)
     , failure_code                         VARCHAR2(50)
     , failure_string                            VARCHAR2(255)
     , created_date                          DATE DEFAULT SYSDATE
    , updated_date                             DATE DEFAULT SYSDATE
    DB release 11G release 1
Edited by: Alekons01 on Mar 24, 2012 2:43 PM

Anyway, I don't believe you will be able to create MV with fast refresh. MV with complete refresh:
CREATE MATERIALIZED VIEW event_mv
BUILD IMMEDIATE
REFRESH COMPLETE ON DEMAND
AS
    SELECT e1.caller_id req_caller_id,
            e1.service_id req_service_id,
            e1.country_code req_country_code,
            e1.internal_correlation_id req_internal_correlation_id,
            e1.received_date req_received_date,
            e1.status req_status,
            e1.queue_name req_queue_name,
            e1.user_id req_user_id,
            e1.engine_id req_engine_id,
            e1.tracking_correlation_id req_tracking_correlation_id,
            e1.mnc req_mnc,
            e1.mcc req_mcc,
            e1.request_type req_request_type,
            e1.app_id req_app_id,
            e1.failure_code req_failure_code,
            e1.failure_string req_failure_string,
            e1.created_date req_created_date,
            e1.updated_date req_updated_date,
            e2.caller_id rsp_caller_id,
            e2.service_id rsp_service_id,
            e2.country_code rsp_country_code,
            e2.internal_correlation_id rsp_internal_correlation_id,
            e2.received_date rsp_received_date,
            e2.status rsp_status,
            e2.queue_name rsp_queue_name,
            e2.user_id rsp_user_id,
            e2.engine_id rsp_engine_id,
            e2.tracking_correlation_id rsp_tracking_correlation_id,
            e2.mnc rsp_mnc,
            e2.mcc rsp_mcc,
            e2.request_type rsp_request_type,
            e2.app_id rsp_app_id,
            e2.failure_code rsp_failure_code,
            e2.failure_string rsp_failure_string,
            e2.created_date rsp_created_date,
            e2.updated_date rsp_updated_date
      FROM event e1,
            event e2
      WHERE e2.internal_correlation_id = e1.internal_correlation_id
        AND e1.request_type = 'REQUEST'
        AND e2.request_type = 'RESPONSE'
/SY.

MATERIALIZED VIEW ORA-12006 and ORA-08103

We have an old 9.2.0.6 database which uses materialized views to access information from other systems via database links. One of these views though will no longer refresh, the others are OK including ones using the same database link and source system.
When we try to refresh get:
CREATE MATERIALIZED VIEW <user>.<materialized view>
REFRESH FORCE
AS SELECT *
FROM <source user>.<source table>@<database link>
AS SELECT *
ERROR at line 3:
ORA-12006: a materialized view with the same user.name already exists
drop MATERIALIZED VIEW <user>.<materialized view>
ERROR at line 1:
ORA-08103: object no longer exists
Obviously we can't rename the view and because of various restrictions I can't upgrade the database, we are in the process of migrating it to 11g.
Does anyone have a magic bullet to resolve this as I have been looking around and haven't found an answer as yet.

Sorry you think the results are confusing but they are the results, obviously I have to protect exact names etc...
Materialized View system:
Shows other views for other source systems but not the ones for this source system.
It shows these ones as an object_type of TABLE in dba_objects even though they were created as materilized views.
Source system select:
OBJECT_NAME OBJECT_TYPE OWNER
<table name> TABLE <table owner>
<table name> SYNONYM PUBLIC
If I use a new name yes it does resolve the issue but I don't want to use a different name if possible as either the application guys have to change some code or I will have to build in another level of synonyms to translate the new name. At the end of the day if this is the only solution!

Need to refresh materialized view from procedure and pl/sql block

Hi,
I need to refresh materialized view (complete refresh)from procedure and pl/sql block .can some one help.
MV name:MV_DGN_TEST_SESSION
Thanks,
Rajasekhar

dbms_mview.REFRESH ('MV_DGN_TEST_SESSION', 'C');Regards,
Mahesh Kaila
Edited by: user4211491 on Dec 1, 2009 10:41 PM

Materialized View and Redo Information

Hi!!
I have created a materialized view with fast refresh. I have created a materialized view log on master table with NOLOGING. My view is refresh every 3 seconds but My problem is that my archivelogs is now growing so much!!!
Please, How I avoid that redo information increasing so much?
Thank you,
Roxana.

I want to show on line some tables of my database,
because I have created materialized view every 3
seconds on test enviroment. I'm not sure I follow exactly what you're saying here.
- Are you sure that you need materialized views here? And not just a regular view? If you need to display the data online and you need a lag of no more than three seconds, is there some reason that you're not using a regular old view? Are you doing some significant aggregation of the data?
- Are you sure that you need the materialized views to refresh every 3 seconds? And not on some longer interval?
- If you're looking for near real-time data replication, you may be better served by using Streams rather than materialized views.
When I use stand by database, I have to replica my
full database???.- I'm assuming this is a completely separate question with no relation to the previous section.
- Yes, DataGuard (physical or logical) would create and maintain a copy of your existing database on a separate server in order to fail over in the event of a disaster or to be a reporting server.
Justin

Use of db sequence in a materialized view

Hi,
Will it be possible to use a database sequence in a materialized view?
The materialized view is to return the result set of query that joins multiple tables. One of the columns in the result set - the to-be-created materialized view - is null and requires a sequence.
Will it be possible to include a db sequence in the query?
Example:
create materialized view example_mview
as
select example_sequence.nextval, table1.'*', table2.'*'
from example_table1 table1, example_table2 table2
where table1.id=table2.id

What is the purpose of such numbering? To number each row?
If so - then use ROWNUM as 1st column.
SQL>with ddd
       as
       (select 333 COL from dual union all select 5444 COL from dual)
       select rownum,COL from ddd;ROWNUM COL
1 333
2 5444

Way to add an additional column that acts as a PK in a Materialized View?

I want to create a materialized view that also has an index column. A unique number sequence assigned to each record. Is this even possible? Can a materialized view do this, and would the indexes stay the same on a refresh?
Any help would be greatly appreciated.

Materialized views are copies of data or aggregations. They can be used to replicate all or part of a table, or to replicate the result of a query against multiple tables. The big advantage they have is that unlike a standard view, which can return the same data, you can index the materialized view to improve performance. These indexes will be maintained and updated during the refresh process.
Refer to Metalink document: 76673.1 or the Oracle Concepts manual for more information.

Creating Materialized View in Toad

As with every new endeavor - come new questions.
I am trying to create a materialized view via toad (first time doing this). Now - toad is great, since it provides a kind-of wizard interface. Hence, one doesn't have to completely code in the create statement, with all of the options, etc.
Instead, in toad, one can (via the schema browser), go into the Materialized Views tab and click on create new. This opens a window with 6 tabs: Basic Info, Refresh Info, Physical Attributes, Query, Partitions & Subpartition Template.
In the Basic Info, one can put a check mark next to some of the following options:
-Build Deffered
-Parallel
-Cache
-Logging
-Using index
-Allow updates
etc.
I have read that build deferred refers to whether or not you would like the view to be created automatically or to be deferred.
Anyways, I tried to find Toad documentation to explain each of the options in-detail. No success. Hence, am researching each part piece by piece.
But - here is my question:
In the Query tab, we are asked to specify a query. I am assuming that the query does not have to be a full query, beginning with CREATE MATERIALIZED VIEW mv_table1 REFRESH FAST etc...
Since in this 'wizard', we are providing the MV name at the top of the dialog box, we are checking the 'options' in the other tabs, etc.
And so, I assumed that the query should merely be a select query in the window mentioned above.
So I entered the following:
select * from table1@remote_db;
When I go to verify the syntax, I get the error message: ORA_00911: invalid character. It seems to be pointing to my db_link (remote_db). I have been using this link throughout many places, w/o any problems.
Has anyone created a MV in toad before? Any links to good toad documentation would be helpful as well.
Thanks.

(This is fun... ;))
For anyone endeavoring this in the future, below I have attached the prerequisites required in order to create a materialized view (can also be found @ http://download-uk.oracle.com/docs/cd/B14117_01/server.101/b10759/statements_6002.htm):
Prerequisites
The privileges required to create a materialized view should be granted directly rather than through a role.
To create a materialized view in your own schema:
You must have been granted the CREATE MATERIALIZED VIEW system privilege and either the CREATE TABLE or CREATE ANY TABLE system privilege.
You must also have access to any master tables of the materialized view that you do not own, either through a SELECT object privilege on each of the tables or through the SELECT ANY TABLE system privilege.
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.
To create a refresh-on-commit materialized view (ON COMMIT REFRESH clause), in addition to the preceding privileges, you must have the ON COMMIT REFRESH object privilege on any master tables that you do not own or you must have the ON COMMIT REFRESH system privilege.
To create the materialized view with query rewrite enabled, in addition to the preceding privileges:
If the schema owner does not own the master tables, then the schema owner must have the GLOBAL QUERY REWRITE privilege or the QUERY REWRITE object privilege on each table outside the schema.
If you are defining the materialized view on a prebuilt container (ON PREBUILT TABLE clause), then you must have the SELECT privilege WITH GRANT OPTION on the container table.
The user whose schema contains the materialized view must have sufficient quota in the target tablespace to store the master table and index of the materialized view or must have the UNLIMITED TABLESPACE system privilege.
When you create a materialized view, Oracle Database creates one internal table and at least one index, and may create one view, all in the schema of the materialized view. Oracle Database uses these objects to maintain the materialized view data. You must have the privileges necessary to create these objects.

Fast refresh on MATERIALIZED VIEW

Oracle 10 g R2 (10.2.0.5)
CREATE MATERIALIZED VIEW scott.mv_test
TABLESPACE users
NOCACHE
LOGGING
NOCOMPRESS
NOPARALLEL
BUILD IMMEDIATE
REFRESH FORCE ON DEMAND
WITH PRIMARY KEY
AS
Select ....
I have this MV, when I do the FAST refersh as follows , I am getting error
SQL> execute DBMS_MVIEW.REFRESH( 'MV_TEST','f');
BEGIN DBMS_MVIEW.REFRESH( 'MV_TEST','f'); END;
ERROR at line 1:
ORA-12004: REFRESH FAST cannot be used for materialized view "SCOTT"."MV_TEST"
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2251
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2457
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2426
ORA-06512: at line 1
But it's working with Complete refresh.
Is that expecte, any help would be appreciated.
Thanks,

ORA-12004: REFRESH FAST cannot be used for materialized view "string"."string"
Cause: The materialized view log does not exist or cannot be used. PCT refresh is also not enabled on the materialized view
Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log or PCT refresh is possible after a given set of changes, REFRESH FAST will be available starting the next time the materialized view is refreshed.http://ora-12004.ora-code.com/

Materialized View to be run every 1 minute through dbms_scheduler

Hi,
I have a materialized view on 1 database which has its select statement going across a database link to numerous tables on another database.
The materialized view creates fine and when refreshed using dbms_snapshot refreshes without error.
My requirement is to automate this refresh for every minute. I have created a job through dbms_scheduler for the refresh to happen every minute but it fails with the error message
ORA-12008: error in materialized view refresh path
I have ctreated another materialized view on the database which does not go across a dblink and scheduled this though dbms_scheduler for every minute, this works fine.........
So it appears my issue is the selecting from tables across a dblink.
Does any one have any experience of this area, how to resolve this issue or maybe an alternative solution than dbms_scheduler?
Thanks in advance.
Mark.

How is your database link defined?
Is it using a fixed user? i.e create database link .... identified by xxxxx
I think it needs to be to be used in a scheduled job.
Carl

How to CREATE MATERIALIZED VIEW LOG (MV fast refresh) with some JOINS

Hi @ all,
i'm trying to create a MATERIALIZED VIEW LOG for a fast refresh of a MATERIALIZED VIEW.
It works fine with a simple Request in the MATERIALIZED VIEW:
CREATE MATERIALIZED VIEW MV_ZOTD43_P
TABLESPACE GDII
BUILD IMMEDIATE
REFRESH FORCE AS
SELECT * FROM ZOTD43_P;
COMMIT;
CREATE MATERIALIZED VIEW LOG ON ZOTD43_P
TABLESPACE "GDII"
WITH PRIMARY KEY, ROWID, SEQUENCE INCLUDING NEW VALUES;
call DBMS_MVIEW.REFRESH('MV_ZOTD43_P', 'f');
But when I use a complex SQL-Request with some JOINS (one of the Table with spatial Data) in the MATERIALIZED VIEW, I get an error:
CREATE MATERIALIZED VIEW MV_TEST
TABLESPACE GDII
BUILD IMMEDIATE
REFRESH FORCE AS
SELECT lptd04_p.sst_nr AS sst_nr,
lptd03_p.aaaa AS aaaa,
lptd04_geom.geom as geom
FROM lptd04_p lptd04_p
JOIN lptd01_p lptd01_p ON lptd01_p.cre_nr = lptd04_p.sst_nr
JOIN lptd04_geom ON lptd04_geom.sst_nr = lptd04_p.sst_nr
JOIN lptd03_p lptd03_p ON lptd03_p.lief_nr = lptd04_p.lief_nr;
COMMIT;
CREATE MATERIALIZED VIEW LOG ON LPTD04_P
TABLESPACE "GDII"
WITH PRIMARY KEY, ROWID, SEQUENCE INCLUDING NEW VALUES;
call DBMS_MVIEW.REFRESH('MV_TEST', 'f');
Error report:
SQL Error: ORA-12004: REFRESH FAST kann für Materialized View "GDI"."MV_GDI_SST_STAMM" nicht benutzt werden
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 2255
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 2461
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 2430
ORA-06512: in Zeile 1
12004. 00000 - "REFRESH FAST cannot be used for materialized view \"%s\".\"%s\""
*Cause: The materialized view log does not exist or cannot be used. PCT
refresh is also not enabled on the materialized view
*Action: Use just REFRESH, which will reinstantiate the entire table.
If a materialized view log exists and the form of the materialized
view allows the use of a materialized view log or PCT refresh is
possible after a given set of changes, REFRESH FAST will
be available starting the next time the materialized view is
refreshed.
Am I doing something wrong or is it not possible CREATE MATERIALIZED VIEW LOG when the MATERIALIZED VIEW got some JOINS?
Regards,
Greq

Thanks for the link Alessandro ,
the error seems something to do with the Column-Type SDO_GEOMETRY, so
i create a new thread in the Spatial Discussion forum:
FAST REFRESHing of Oracle Materialized Views containing SDO_GEOMETRY column
Regards,
Greq

Materialized views in 8i and 9i

Similar Messages

Maybe you are looking for