Does the user have select access on the mlog?
A Joshi wrote:
Hi,
I have a table tableA owned by userA.
If I create a materialized view in another schema/user fast and complete
refresh set to refresh every 10 minutes then only complete refresh works
and refreshes automatically every 10
Mike : Yes the user has select access and is able to do a select on the MLOG table and the original table. Thanks for your help.Mike Spalinger [EMAIL PROTECTED] wrote:
Does the user have select access on the mlog?A Joshi wrote: Hi, I have a table tableA owned by userA. If I create a materialized
Chuan,
You can crteate indexes on MVs if you want to - there is nothing against it;
in fact it may be specifically desirable to do so. MVs are designed to help
in query optimization by selecting against a materialized collection f
data as opposed to selecting from a set of tables as in case of
Creating Indexes on MV is pretty ok and it is good for performance.
I even create mv on mv to further improve the performance of some really frequently
executed SQL.:)
Regards.
Zhu Chao.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday,
I'm not sure if you want to improve the query, or the replication process.
If it's the replication process, one other option is 'refresh force'. Then,
if I understand the docs correctly, you get a fast refresh if it can; and if
refresh fast is not possible, then refresh complete. That's the
Title: RE: Materialized view
don't you need a 'count(*)' for refresh fast?
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts
For fast refresh, you need to have a snapshot log on the master table and
the snapshot must be registered with the master.
Keep in mind, we are only talking about simple, read-only, snapshots here.
There are fancier ways of moving data here and there. But I would have to
do the RTFM thing
Hi Ray,
Please let me know if you received any answer.
Thanks,
Ashoke
-Original Message-
Sent: Friday, September 06, 2002 10:23 AM
To: Multiple recipients of list ORACLE-L
8.1.7.4
create snapshot TEMP as
select * from [EMAIL PROTECTED] partition (020904)
ERROR at line 1:
On Fri, Sep 06, 2002 at 07:23:28AM -0800, Ray Stell wrote:
8.1.7.4
create snapshot TEMP as
select * from [EMAIL PROTECTED] partition (020904)
ERROR at line 1:
ORA-14100: partition extended table name cannot refer to a remote object
Well, it ain't pretty, but...
on the remote db:
Depends mostly on your users needs. If most of the time your users would want monthly
sum of measures, you give them a
materialized view for that.
You can also use the summary advisor feature of oracle (dbms_olap) to find out which
mviews oracle thinks is needed based on
usage.
=)
Chuan Zhang
Title: RE: Simple question on logging..
Not sure
but I think you need to have Enterprise Edition for that. Otherwise it should work
fine
Aleem
-Original
Message-
From: Mandal, Ashoke
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002
5:18 AM
To: Multiple recipients
I would start with checking what database links are
vissible.
Do a select * from all_db_links. A database link in
the invoking schema should take precedence over a
public one. Whatever link is being used, verify that
you can connect to the remote database using it's
connection symantics. You can
Hi Bill
Thanks for your reply.
In fact when I try following SQL i get result (few records available in
table DEPT)
select * from dept@softek1
I could not understand the meaning of your statement You can pull the clear
text
password out of sys.link$ for this puspose.. Please clarify and help.
Title: Materialized View over 2 tables
Thats not
a problem. That is well-documented feature and you can check it with standard
documents.
Fast Refreshes
are meant only for simple MVs/Snapshots and not for complex ones. You are
supposed
to do a
complete refresh for complex ones.
Helmut,
Rajesh is absolutely correct. If one or more of the
base tables are in a remote db then the fast refresh
restrictions in the Replication manual apply; if all
the base tables are local then the fast refresh
restrictions in the Data Warehousing manual apply.
A workaround would be to
Just solved it...Duh!
as sys
grant alter any materialized view to User_B;
--- mohammed bhatti [EMAIL PROTECTED] wrote:
I have a materialized view created by user A in
schema
A. The view consists of simple table joins and
union
statements. I want user B to be able to execute the
refresh
Can you post the entire CREATE statement?
Rick
-Original Message-
From: Terri Williamson/MIS/HQ/KEMET/US [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 9:26 AM
To: Multiple recipients of list ORACLE-L
Subject: Materialized View Problem
Hi All,
I am trying
17 matches
Mail list logo
