Re : Mviews issue

Hi ,
In our infrastructure implemented Materialized views from both Oracle Server.This two server are belongs in diffrent place.Internel network (Lease line) connectivity is very poor after 5 P.M every days. Mviews refresh interval is one hour interval. When disconnect the network then next time Mviews can't be refresh. i have tried manual refresh..but didn't refreshed.
exee dbms_refresh.refresh('mv_name');
exee dbms_snapsht.refresh('mv_name');
For bussiness purpose create the mview manually every morning..can you give some iden how i overcome this issue.
Thanks

Hello,
What is the error message when you refresh the MView? In your case, you need to have a solid connection to the remote database for your mview refresh so that your mviews can be refreshed.
Salman

Similar Messages

Issue with MView betweem DB's with different character sets

source system is char set IS0-8859-15.
BUT - there is some data in the db that is outside the range of ISO - values are between 128 and 159 decimal. - The data is valid in teh Windows-1252 charset but its not valid ISO.
target is utf-8
Current issue is value in source system is 232 (x84). Thiis is lower double quotation mark, but not valid iso character.
After mview replicates the value, it is xC284. This is not a valid utf8 encoded value.
Correct value in utf-8 would be xE2809E (unicode 201E).
Any suggestions on how to get the mviuew to recognize windows-1252 characters, even though the charset of the database is iso?

<BLOCKQUOTE>quote:<HR>Originally posted by Zozzi ([email protected]):
sorry, wrong email in the prev msg ...
this one is correct<HR></BLOCKQUOTE>
Hello,
Did you solve it ?
If yes, how to do it. I am interested in knowing it.
Many Thanks
null

Use CONTEXT index on mview or use mview's rewrite directly

Please let me explain what I mean in Subject. I have 9 tables. Each of these tables has about 40,000 rows and one table has 2 million rows. Using first approach, I can build a join-only materialized view on top of nine table's mview log. then query on these nine tables directly. Advantage for doing that is use rewrite.

for second approach, I build a CONETXT index on several columns on the mview, and then query through CONTEXT index on mview directly. This is pretty much like Barbara did on CREATE INDEX book_idx ON book_search
[http]Indexing multiple columns of multiple tables using CTXCAT
but she used CTXCAT instead of CONTEXT index.

My question is will second approach better than first one and why. Unlike basic join several tables which gives you predictable performance, I often feel that CONTEXT index performance is unpredictable when tables have more than several thousands rows (maybe I did something wrong, but still looking for document regarding performance) .

I will appreciate someone could show hints on the issue.

Message was edited by:
qwe15933
Message was edited by:
qwe15933
Message was edited by:
qwe15933
Message was edited by:
qwe15933

The best method to find out what is best for any individual situation is to test and compare. In general, Oracle Text is best at searching unstructured data, such as large documents and has a lot of features that enable you to do different kinds of searches. If you only have structured data, with each column only containing one short thing and you only need simple searches, then you probably don't need Text. There are also a few things that can be done to indexes and/or queries to optimize performance. It would help to have an idea what your typical data is like and what sorts of searches you anticipate needing.

Mview Fast Refresh Problem

Hello,
We run a fast refresh for a particular mview. I have the mview log created on the primary db (base table) and the mview created on another reporting database.
The fast refresh seems to be fine throughout the day but at the end of a day it fails to do the fast refresh and i'm forced to do a complete refresh everyday which fixes it but this cycle continues until the end of day when it breaks again.
If you notice in the next date column the refresh date turns to 01-JAN-00, not sure why this happens and this is causing the problem.
JOB REFRESH_JOB LAST_DATE NEXT_DATE NEXT_SEC BROKEN
70 CON_SYS"."MV_BRICKNW" 04-AUG-10 01-JAN-00 00:00:00 Y
75 CON_SYS"."MV_BRICKNWCAN" 04-AUG-10 01-JAN-00 00:00:00 Y
Could someone please tell me what the problem is.

The Refresh Date gets reset when the job is Broken (which you see as BROKEN='Y'). The job is Broken when 16 consecutive attempts have failed (which you would see in FAILURE_COUNT).
You have to find out why it fails -- fails 16 times. There seems to be an issue with the date/time logic OR one of the source objects probably gets dropped or becomes unavailable close to the end of the day.
Hemant K Chitale

Mview Refresh Taking more time

Hi Team,
Am using Materialized Mview refresh for my database,with refresh type as fast.
Previously the mview refresh completed within 10-15minutes,but now the mview refresh taking more than 150min to complete.
Please suggest on the above issue.
With Regards,
Venkatesh J.

Venkateshj wrote:
Hi Team,
Am Using Oracle Database 11g, Version 11.1.0.7.0.
In that am using Materialized Mview refresh for my database,with refresh type as fast.
Previously the mview refresh completed within 10-15minutes,but now the mview refresh taking more than 150min to complete.
Please suggest on the above issue for tuning.
Thanks in advance
With Regards,
Venkatesh J.
HOW To Make TUNING request
https://forums.oracle.com/forums/thread.jspa?threadID=2174552#9360003

Query Rewrite ISSUE (ANSI JOINS do not work, traditional join works ) 11gR2

For some types of queries constructed with ANSI JOINS, materialized views are not being used.
This is currently increasing time on various reports since we cannot control the way the queries are generated(Tableau Application generates and runs queries against the STAR Schema).
Have tried to debug this behavior using DBMS_MVIEW.EXPLAIN_REWRITE and mv_capabilities function without any success.
The database is configured for query rewrite: REWRITE INTEGRITY, QUERY REWRITE ENABLED and other settings are in place.
Have successfully reproduced the issue using SH Sample schema:
Q1 and Q2 are logically identical the only difference between them being the type of join used:
Q1: ANSI JOIN
Q2: Traditional join
Below is an example that can be validated on SH sample schema.
Any help on this will be highly appreciated.
-- Q1: the query is generated by an app and needs to be rewritten with materialized view
SELECT cntr.country_subregion, cust.cust_year_of_birth, COUNT(DISTINCT cust.cust_first_name)
FROM customers cust
INNER JOIN countries cntr
   ON cust.country_id = cntr.country_id
GROUP BY cntr.country_subregion, cust_year_of_birth;
-- Q2: the query with traditional join is rewritten with materialized view
SELECT cntr.country_subregion, cust.cust_year_of_birth, COUNT(DISTINCT cust.cust_first_name)
FROM customers cust
INNER JOIN countries cntr
   ON cust.country_id = cntr.country_id
GROUP BY cntr.country_subregion, cust_year_of_birth;Tested both queries with the following materialized views:
CREATE MATERIALIZED VIEW MVIEW_TEST_1
ENABLE QUERY REWRITE
AS
SELECT cntr.country_subregion, cust.cust_year_of_birth, COUNT(DISTINCT cust.cust_first_name)
FROM customers cust
INNER JOIN countries cntr
   ON cust.country_id = cntr.country_id
GROUP BY cntr.country_subregion, cust_year_of_birth;
CREATE MATERIALIZED VIEW MVIEW_TEST_2
ENABLE QUERY REWRITE
AS
SELECT cntr.country_subregion, cust.cust_year_of_birth, COUNT(DISTINCT cust.cust_first_name)
FROM customers cust, countries cntr
WHERE cust.country_id = cntr.country_id
GROUP BY cntr.country_subregion, cust_year_of_birth;Explain Plans showing that Q1 does not use materialized view and Q2 uses materialized view
SET AUTOTRACE TRACEONLY
--Q1 does not use MVIEW_TEST_1
SQL> SELECT cntr.country_subregion, cust.cust_year_of_birth, COUNT(DISTINCT cust.cust_first_name)
FROM customers cust
INNER JOIN countries cntr
   ON cust.country_id = cntr.country_id
GROUP BY cntr.country_subregion, cust_year_of_birth; 2    3    4    5
511 rows selected.
Execution Plan
Plan hash value: 1218164197
| Id | Operation           | Name       | Rows | Bytes |TempSpc| Cost (%CPU)| Time       |
|   0 | SELECT STATEMENT      |        |   425 | 12325 |       |   916   (1)| 00:00:11 |
|   1 | HASH GROUP BY           |        |   425 | 12325 |       |   916   (1)| 00:00:11 |
|   2 |   VIEW                | VM_NWVW_1 | 55500 | 1571K|       |   916   (1)| 00:00:11 |
|   3 |    HASH GROUP BY      |        | 55500 | 1842K| 2408K|   916   (1)| 00:00:11 |
|* 4 |     HASH JOIN           |        | 55500 | 1842K|       |   409   (1)| 00:00:05 |
|   5 |      TABLE ACCESS FULL| COUNTRIES |    23 |   414 |       |     3   (0)| 00:00:01 |
|   6 |      TABLE ACCESS FULL| CUSTOMERS | 55500 |   867K|       |   405   (1)| 00:00:05 |
--Q2 uses MVIEW_TEST_2
SQL> SELECT cntr.country_subregion, cust.cust_year_of_birth, COUNT(DISTINCT cust.cust_first_name)
FROM customers cust, countries cntr
WHERE cust.country_id = cntr.country_id
GROUP BY cntr.country_subregion, cust_year_of_birth; 2    3    4
511 rows selected.
Execution Plan
Plan hash value: 2126022771
| Id | Operation               | Name         | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT          |              |     511 | 21973 |       3   (0)| 00:00:01 |
|   1 | MAT_VIEW REWRITE ACCESS FULL| MVIEW_TEST_2 |     511 | 21973 |       3   (0)| 00:00:01 |
---------------------------------------------------------------------------------------------Database version 11gR1 (Tested also on 11gR2)
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE     11.2.0.1.0     Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production

Thanks for the formatting tips.
Just found an Oracle Bug which explains the above behavior.
Unfortunately the bug will be fixed only in 12.1 Release so as a workaround will try to use traditional joins.
For those who have metalink access see [Bug 10145667 : ERRORS TRYING TO REWRITE QUERY WITH EXACT TEXT MATCH TO MVIEW]

ORA-12054: mview in 10g and master table in 8i

Hi all,
I have an issue when creating a mview on 10g with master table accessed via dblink in a 8i DB.
I've done the following:
1.) Created the mv log in master table schema1 in 8idb database version 8.1.7.
CREATE MATERIALIZED VIEW LOG ON SCHEMA1.TAB1
WITH ROWID , PRIMARY KEY
INCLUDING NEW VALUES;
desc tab1
col1 number(4);
col2 varchar2(30);
col3 varchar2(30);
2.) Granted the following privs to user schema2@10gdb (where the mview will be created).
GRANT GLOBAL QUERY REWRITE TO schema2;
grant create materialized view to schema2;
3.) Created the db link 8idb connecting schema2 user to 8idb
4.) Tried to create the Mview:
CREATE MATERIALIZED VIEW SCHEMA2.MV_TEST1
TABLESPACE TABSP1
BUILD IMMEDIATE
REFRESH FAST ON COMMIT
ENABLE QUERY REWRITE
AS
SELECT COL1, COL2, COL3, COUNT(*)
FROM tab1@8idb
GROUP BY COL1, COL2, COL3;
Received the following error:
FROM tab1@8idb
ERROR at line 9:
ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view
Can someone tell me what I'm doing wrong? the creation works fine on the same database in another schema. Am I missing something in 8i environment? I read Oracle8i SQL Reference
about MViews and it seemed to work.

Hi,
You can't set the on commit refresh attribute for an mview over a db link. It is only valid within a single database.
Cheers,
Harry

Problem Creating MVIEW in Prod Env.

I'm trying to create MVIEW in schema A which is located in APJ region and the source schema B which contains MVIEW logs located in AMF region. When I'm runing create MVIEW, its not retrrning back even after 3 to 4 hours and we are about to miss deployment window. The source table is big table contains CLOB columns. Any Idea how to overcome it.

Well, in the first post you said
When I'm runing create MVIEW, its not retrrning back even after 3 to 4 hours ...
And in this last post you say
...create statement is not getting exectued.
So i am a little confused as to what your exact issue is, from the original post it sounds like you're trying to create a materialized view with a lot of data and it's taking a long time, too long, which implies....tuning.
From your second post it sounds like the statement isn't even executing (which implies an error) and that you need to properly set things up in order to create a materialized view.
So is either of those the case? If so which one, if not... what?

Issue with query involving remote tables

Hi I have a query inside a procedure that has 4 union all statements ,2 of which are based on tables at a remote database.
The query is something like
Select col1, col2, col3…..col n from Table_a, table_b, table c where join condition and certain hard-coded conditions based on run time parameters
Union all
Select col1, col2, col3…..col n from Table_a, table_b , table c where some join condition and certain hard-coded conditions based on run time parameters
Union all
Select col1, col2, col3…..col n from Table_a@remote_db, table_b@remote_db, table c@remote_db where join condition and certain hard-coded conditions based on run time parameters
Union all
Select col1, col2, col3…..col n from Table_a @remote_db, table_b @remote_db, table c@ remote_db where some join condition and certain hard-coded conditions based on run time parameters
The join conditions on the tables are quite good and when executed individually bring data in good time.The queries on the remote database also run fine when I execute them in the remote database.
However when I run this query, it doesn’t get data at all and after hours of running I have to cancel or kill it.I don’t get anything in the long-ops and in the wait class it just shows “SQL*Net message from dblink” or “SQL*Net more data to dblink”.
I thought that there could be some latency issues AND the data retreival over the dblink could be slow, so I tried the /*+driving_site(rmote table alias)*/ hint , after which it comes up in the long ops as its reading from Table a/ table b from my current database but the wait time is something like millions of seconds and it runs forever.
The issue is Table A and Table B both in the remote and the current database are huge tables with at least 40-50 million records in them.
Can anyone suggest an easy way out in this scenario, other than the hard way of re-designing the entire program(which I am afraid I might have to in the end).
Thanks

@metzquar I Put the hint in the unions where I am accessing the remote tables
@blushadow .. i was thinking about that but as these remote tables are in a sort of archived database, I dont think I will be allowed to create a mview.But thats a good suggestion.
@Earth.. I tried that , but the table population itself gets very time consuming
Thanks

About Performance issue

Hi All,
I have a table which is very frequently used for transcational purposes (like Insert,Delete,Update) from Oracle apps database.
I have created a view based on this table only and this view is referenced by another database very frequently using DB Link.
Will there be any performance issue either on view or on table since table is getting used same time in Select queries and also in transcations (like Insert,Delete,Update) from different databases?
is it better to create to Materilized view or normal view for this purpose (Since Mview can be refreshed daily once).
Please suggest..
Thanks

Lakshmi V wrote:
Hi All,
I have a table which is very frequently used for transcational purposes (like Insert,Delete,Update) from Oracle apps database.
I have created a view based on this table only and this view is referenced by another database very frequently using DB Link.
Will there be any performance issue either on view or on table since table is getting used same time in Select queries and also in transcations (like Insert,Delete,Update) from different databases?Yes and No.... or It Depends.
Oracle doesn't have a problem querying tables whilst inserts, deletes or updates are taking place on them. The database engine is designed to be multi-transactional, so things won't hold up a query against the data. The only thing that will slow it down really is the I/O which is primarily related to disc access, so if the physical server is doing a lot of I/O to process the inserts/updates and deletes, then the query may get slowed down as a result of that, but it really depends on the hardware and how the data is spread on the discs.
is it better to create to Materilized view or normal view for this purpose (Since Mview can be refreshed daily once).You could if your business process allows for snapshots of data rather than near-real-time, that's entirely your choice. It won't necessarily help improve the I/O, though it may.
Without your database version, table structures, and details of your hardware, explain plans, test cases etc. there's no correct answer to give you.
Personally, I wouldn't bother with the Materialized view unless I needed to look at a snapshot of the data, or I needed to perform queries using different search clauses from normal such that I needed some different indexes that I didn't want to apply to the base table. I certainly wouldn't consider it just to try and improve performance and take the querying away from the transactional data.

Refreshing mview is hanging after a database level gather stats

hi guys,
can you please help me identify the root cause of this issue.
the scenario is this:
1. we have a scheduled unix job that will refresh an mview everyday, from tuesday to saturdays.
2. database maintenance being done during weekends (sundays), gathering stats at a database level.
3. the refresh mview unix job apparently is hanging every tuesdays.
4. our workaround is to kill the job, request for a schema gather stats, then re-run the job. and voila, refresh mview will be successful then.
5. and the rest of the weekdays until saturdays, refresh mview is having no problems.
we already identified during testing that the scenario where the refresh mview is failing is when after we are gathering stats in a database level.
during gather stats in a schema level, refresh mview is successful.
can you please help me understand why we are failing refreshing mview after we gather stats in the database level??
we are using oracle 9i
the creation of the mview goes something like below:
create materialized view hanging_mview
build deferred
refresh on demand
query rewrite disabled
appreciate all your help.
thanks a lot in advance.

1. we have a scheduled unix job that will refresh an mview everyday, from tuesday to saturdays.
2. database maintenance being done during weekends (sundays), gathering stats at a database level.
3. the refresh mview unix job apparently is hanging every tuesdays.
4. our workaround is to kill the job, request for a schema gather stats, then re-run the job. and voila, refresh mview will be successful then.
5. and the rest of the weekdays until saturdays, refresh mview is having no problems.
You know Tuesday's MV refresh "hangs".
You don't know why it does not complete.
You desire solution so that it does complete.
You don't really know what is is doing on Tuesdays, but hope automagical solution will be offered here.
The ONLY way I know how to possibly get some clues is SQL_TRACE.
Only after knowing where time is being spent will you have a chance to take corrective action.
The ball is in your court.
Enjoy your mystery!

IS ORACLE HELPLESS IN REFRESHING COMPLEX MVIEW FAST??

I have a mview with a complicated query.But I need to refresh it fast on commit.I would be grateful if you people could solve this prob anyway.My mview script is given below..
SELECT TAS.ANSWER_SET_ID ALGORITHM_ID,
          TAS2.ANSWER_SET_ID RULE_ID, TAS2.CODEVAL1 SEQUENCE_NO,
     DE.EFFECTIVE_FROM_DATE EFFECTIVE_DATE,
          DE.ALPHANUMERIC_CODE_VALUE STATUS,
     MN1.MESSAGE_TEXT STAT_CODE,
          MN2.MESSAGE_TEXT CREDIT_PERCENTAGE,
          MN3.MESSAGE_TEXT DEBIT_PERCENTAGE,
     MN4.MESSAGE_TEXT CREDIT_DOLLAR,
          MN5.MESSAGE_TEXT DEBIT_DOLLAR,
          MN6.MESSAGE_TEXT ELEMENT_INCLUDED_IN,
     MN7.MESSAGE_TEXT PREMIUM_BASED_ON,
          MN8.MESSAGE_TEXT PREM_RATING_ELEMENT,
     EXP1.MESSAGE_TEXT EXPIARY_DATE
FROM T_RULE_CONTEXT RC,
          T_ANSWER_SET TAS,
          T_ANSWER_SET TAS1,
     T_ANSWER_SET TAS2,
     T_DECISION_PARAMETER DP,
          T_DECISION_EXPRESSION DE,
     T_DECISION_MESSAGE DM1,
          T_DECISION_MESSAGE DM2,
          T_DECISION_MESSAGE DM3,
     T_DECISION_MESSAGE DM4,
          T_DECISION_MESSAGE DM5,
          T_DECISION_MESSAGE DM6,
     T_DECISION_MESSAGE DM7,
          T_DECISION_MESSAGE DM8,
     (SELECT MESSAGE_NOTE_ID, DM4.ANSWER_SET_ID FROM T_DECISION_MESSAGE DM4, T_ANSWER_SET TAS2 WHERE DM4.ANSWER_SET_ID = TAS2.ANSWER_SET_ID AND MESSAGE_NAME='EXPIARY_DATE') EXP,
     T_MESSAGE_NOTE MN1,
          T_MESSAGE_NOTE MN2,
          T_MESSAGE_NOTE MN3,
     T_MESSAGE_NOTE MN4,
          T_MESSAGE_NOTE MN5,
          T_MESSAGE_NOTE MN6,
          T_MESSAGE_NOTE MN7,
          T_MESSAGE_NOTE MN8,
     (SELECT DM5.MESSAGE_NOTE_ID A, DM5.ANSWER_SET_ID, MN4.MESSAGE_NOTE_ID B, MESSAGE_TEXT FROM T_DECISION_MESSAGE DM5, T_ANSWER_SET TAS3, T_MESSAGE_NOTE MN4 WHERE DM5.ANSWER_SET_ID = TAS3.ANSWER_SET_ID AND DM5.MESSAGE_NAME='EXPIARY_DATE' AND DM5.MESSAGE_NOTE_ID = MN4.MESSAGE_NOTE_ID(+)) EXP1
WHERE      RC.CONTEXT_NAME = 'ALGORITHMS'
AND      RC.QUESTION_SET_ID = TAS.QUESTION_SET_ID_PARENT
AND      TAS1.CODEVAL1 = 'NO'
AND      TAS1.QUESTION_SET_ID_PARENT(+) = TAS.QUESTION_SET_ID_CHILD
AND      TAS1.QUESTION_SET_ID_PARENT IN
                         (SELECT QUESTION_SET_ID_CHILD
                         FROM T_RULE_CONTEXT , T_ANSWER_SET
                         WHERE RC.CONTEXT_NAME = 'ALGORITHMS'
                         AND QUESTION_SET_ID = QUESTION_SET_ID_PARENT)
AND      TAS2.QUESTION_SET_ID_PARENT = TAS1.QUESTION_SET_ID_CHILD
AND      DP.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DE.DECISION_PARAMETER_ID = DP.DECISION_PARAMETER_ID
AND      DM1.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM2.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM3.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM4.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM5.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM6.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM7.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      DM8.ANSWER_SET_ID = TAS2.ANSWER_SET_ID
AND      TAS2.ANSWER_SET_ID = EXP.ANSWER_SET_ID(+)
AND      DM1.MESSAGE_NAME = 'STAT_CODE'
AND      DM2.MESSAGE_NAME = 'CREDIT_PERCENTAGE'
AND      DM3.MESSAGE_NAME = 'DEBIT_PERCENTAGE'
AND      DM4.MESSAGE_NAME = 'CREDIT_DOLLAR'
AND      DM5.MESSAGE_NAME = 'DEBIT_DOLLAR'
AND      DM6.MESSAGE_NAME = 'ELEMENT_INCLUDED_IN'
AND      DM7.MESSAGE_NAME = 'PREMIUM_BASED_ON'
AND      DM8.MESSAGE_NAME = 'PREM_RATING_ELEMENT'
AND      MN1.MESSAGE_NOTE_ID = DM1.MESSAGE_NOTE_ID
AND      MN2.MESSAGE_NOTE_ID = DM2.MESSAGE_NOTE_ID
AND      MN3.MESSAGE_NOTE_ID = DM3.MESSAGE_NOTE_ID
AND      MN4.MESSAGE_NOTE_ID = DM4.MESSAGE_NOTE_ID
AND      MN5.MESSAGE_NOTE_ID = DM5.MESSAGE_NOTE_ID
AND      MN6.MESSAGE_NOTE_ID = DM6.MESSAGE_NOTE_ID
AND      MN7.MESSAGE_NOTE_ID = DM7.MESSAGE_NOTE_ID
AND      MN8.MESSAGE_NOTE_ID = DM8.MESSAGE_NOTE_ID
AND      EXP.MESSAGE_NOTE_ID = EXP1.A(+)
IS THERE ANY WAY TO DO THIS OR ITS A LIMITATION OF ORACLE??

Hi,
Take a look on restrictions applied on fast refresh of materialized views:
General Restrictions:
1.) The materialized view must not contain references to non-repeating expressions like SYSDATE and ROWNUM.
2.) The materialized view must not contain references to RAW or LONG RAW data types.
Restrictions on Fast Refresh on Materialized Views with Joins Only:
1.) All restrictions from "General Restrictions on Fast Refresh".
2.) They cannot have GROUP BY clauses or aggregates.
3.) If the WHERE clause of the query contains outer joins, then unique constraints must exist on the join columns of the inner join table.
4.) If there are no outer joins, you can have arbitrary selections and joins in the WHERE clause. However, if there are outer joins, the WHERE clause cannot have any selections. Furthermore, if there are outer joins, all the joins must be connected by ANDs and must use the equality (=) operator.
5.) Materialized view logs must exist with rowids for all the base tables in the FROM list of the query.
In your case look on point 3 and 4. This might cause problems. Sort out issues relating to point 3 & 4. Then i hope that fast refreshing should work with your view.

MVIEW and RAC

Hi All,
This is a hypothetical question. We are planning to have MVIEWS inside our 2 node RAC 10g R2 databse. Now in case MVIEW refresh is happening and one of the node fails , what will happen to the refresh job?
-Amit

It depend , on which node job is running. If job is not running on failed node then no issue.

Problem with MVIEWS in import

I had got an export dump from an Oracle 8.1.7.4 database and imported it into a 10gR2 database (2 node RAC on AIX 5.3, 64 bit, 10.2.0.3). All the MVIEWS got created.
Now again i took [traditional] export of the new database and created it on another machine (10.2.0.3 non-RAC on AIX 5.3,64 bit). Now here came the issue. Some of the MVIEWS got created as VIEWS.
That SNAP$ table got created and then what was supposed to be a MVIEW, got created as VIEW on SNAP$ table. It happened with 12 MVIEWS out of total 32.
Any ideas what could be the reason or anybody faced something similar ?
Any more information required please let me know.
Thanks
Amardeep Sidhu
Corrected some information....
Message was edited by:
Amardeep Sidhu

Could you list the steps you are going through in detail?
I just tried stacking some images in the import window (from the HD not a card) and they came into the album as closed stacks containing all the images. Doesn't stop it being a bug on your installation, of course, just that it doesn't reproduce on my machine.
Ian

New DVR Issues (First Run, Channel Switching, etc.)

I've spent the last 30 minutes trying to find answers through the search with no luck, so sorry if I missed something.
I recently switched to FIOS from RCN cable in New York. I've gone through trying to setup my DVR and am running into issues and was hoping for some answers.
1. I setup two programs to record at 8PM, I was watching another channel at the time and only half paying attention. Around 8:02 I noticed a message had popped up asking if I would like to switch channels to start recording. I was expecting it to force it to switch like my old DVR, but in this case it didn't switch and I missed the first two minutes of one of the shows. I typically leave my DVR on all day and just turn off the TV, this dual show handling will cause issues with that if I forget to turn off the DVR. Is there a setting I can change that will force the DVR to choose one of the recording channels?
2. I setup all my recordings for "First Run" because I only want to see the new episodes. One show I setup was The Daily Show on comedy central, which is shown weeknights at 11pm and repeated 3-4 times throughout the day. My scheduled recordings is showing all these as planned recordings even though only the 11pm show is really "new". Most of the shows I've setup are once a week so they aren't a problem, but this seems like it will quickly fill my DVR. Any fixes?
Thanks for the help.
Solved!
Go to Solution.

I came from RCN about a year ago. Fios is different in several ways, not all of them desirable. Here are several ways to get--and fix--unwanted recordings from a series recording setup.
Some general principles.
Saving changes. When you originally create a series with options, or if you go back to edit the options for an existing series, You MUST save the Series Options changes. Pretty much everywhere else in the user interface, when you change an option, the change takes effect immediately--but not in Series Options. Look at the Series Options window. Look at the far right side. There is a vertical "Save" bar, which you must navigate to and click OK on to actually save your changes. Exiting the Series Options window without having first saved your changes loses all your attempted changes--immediately.
Default Series Options. This is accessed from [Menu]--DVR--Settings--Default Series Options. This will bring up the series options that will automatically be applied to the creation of a NEW series. The options for every previously created series will not be affected by a subsequent modification of the Default Series Options. You should set these options to the way you would like them to be for the majority of series recordings that you are likely to create. Be sure to SAVE your changes. This is what you will get when you select "Create Series Recording" from the Guide. When creating a new series recording where you think that you may want options different from the default, select "Create Series with Options" instead. Series Options can always be changed for any individual series set up later--but not for all series at once.
Non-series recordings. With Fios you have no directly available options for these. With RCN and most other DVRs, you can change the start and end times for individual episodes, including individual episodes that are also in a series. With Fios, your workarounds are to create a series with options for a single program, then delete the series later; change the series options if the program is already in a series, then undo the changes you made to the series options later; or schedule recordings of the preceding and/or following shows as needed.
And now, to the unwanted repeats.
First, make sure your series options for the specific series in question--and not just the series default options--include "First Run Only". If not, fix that and SAVE. Then check you results by viewing the current options using the Series Manager app under the DVR menu.
Second, and most annoying, the Guide can have repeat programs on your channel tagged as "New". It happens. Set the series option "Air Time" to "Selected Time". To make this work correctly, you must have set up the original series recording after selecting the program in the Guide at the exact time of a first run showing (11pm, in your case), and not on a repeat entry in the Guide. Then, even it The Daily Show is tagged as New for repeat showings, these will be ignored.
Third, another channel may air reruns of the program in your series recording, and the first showing of a rerun episode on the other channel may be tagged as "New". These can be ignored in your series if you set the series option "Channel" to "Selected Channel". Related to this, if there is both an SD and HD channel broadcasting you series program, you will record them both if the series option "Duplicates" is set to "Yes". However, when the Channel option is set to "Selected Channel", the Duplicates Option is always effectively "No", regardless of what shows up on the options screen.
As for you missing two minutes, I have sereral instances in which two programs start recording at the same time. To the best of my recollection, whenever the warning message has appeared, ignoring it has not caused a loss of recording time. You might have an older software version. Newest is v.1.8. Look at Menu--Settings--System Info. Or, I might not have noticed the loss of minutes. I regularly see up to a minute of previous programming at the start of a recording, or a few missing seconds at the beginning or end of a recording. There are a lot of possibilities for that, but the DVR clock being incorrect is not one of them. With RCN, the DVR clocks occasionally drifted off by as much as a minute and a half.

Re : Mviews issue

Similar Messages

Maybe you are looking for