EXPort (without Mat view logs)

Hi
Oracle10g, Win2003
Is there a way to take EXPort without "materialized view logs", as these logs cause error in IMPort and some time even terminate IMPort.
It will be equally well for me if i got a way to completely exclude "materialized view & materialized view logs" from EXPort.
Some one please guide me the way to exclude them from IMP or EXP?
Wishes

Additionally when ever I IMPort a user some objects appear in non-compiled state, I compile them with my client tool, but I have to drop and recreate materialized view every time.
Can come one have an improved way to get IMPort with materialized view?
Wisehs

Similar Messages

Identifying updated column in materialized view logs

Hi all,
I created a materialized view log for a table with three columns(say colA,colB,colC). Is there any way to identify which column got updated among these three columns? through the entries in mat view logs?
any inputs on this ll be of great help.
Thanks in advance.
gopi

Can someone tell me about M_ROWS$$ column in Materialized view.
I am in confucion.

MATERIALIZED VIEW and MATERIALIZED VIEW LOG

Hello,
I have the following table
create table My_price
(price_id number(10),
product_id number(10),
price_date date,
price_value number(10,2));
I want to create the following materialized view
create materialized view Last_Price_Date
refresh
on commit complete
as
select max(price_date) as max_date, product_id from my_price group by product_id;
Do I have to create materialized view log ? Will my materialized view be refresh on commit without materialized view log ?

As a student the requisite first task is always to study. Thus your assignment is to go to http://tahiti.oracle.com and read the concept and architecture docs on Materialized Views so that you can learn about the different types of MVs and how and when they are refreshed. There you will learn about what ON COMMIT means.
Then please turn your "I want to create" into an "I created it." Then, having read the docs, you will be able to observe how your MV behaves.
PS: Your SELECT statement is not syntactically correct. Start by fixing it so that it works in SQL*Plus.

CREATE MATERIALIZED VIEW LOG ON / SNAPSHOT LOG ON

HI,
Is there any difference between create materialized view log on and creat snapshot on.
Did some googling, found out that: A snapshot log is a table associated with
the master table of a snapshot and Is used for refresh the master table\'s snapshots.
Materialized view log is a table associated with the master table of a materialized view. Seem like the same.
By the way, are these tables important? Will my database function as normal without these view log.
regards,
becks

Where did you pick up this syntax from ?
The MV Log that will be created on DOCUMENT will be called MLOG$_DOCUMENT.
So, the correct syntax is :
create materialized view log on DOCUMENT with primary key;this will create a "table" called MLOG$_DOCUMENT which serves as the Materialized View Log on the real table called DOCUMENT. This will allow you to create one or more Materialized Views based on DOCUMENT, which can be fast refreshed because of the presence of the MV Log. For example :
create materialized view MV_DOCUMENT refresh fast on demand as select DOC_ID, DOC_DATE from DOCUMENT;(i.e. assuming you want an MV that has only two columns from the table DOCUMENT.
Hemant K Chitale
http://hemantoracledba.blogspot.com

ORA-12034: materialized view log on table younger than last refresh

I am getting this error while creating the materialized view.
This error seems to be refresh error.
but when i have a mat view log already and running script to create the materialized view how can that happen?

34MCA2K2, Google lover?
I confess perhaps I gave a little info.
View log was created before MV.
It was the first initial load.
No refresh failed.
No DDL.
No purge log.
Not warehouse.
There is no such behavior for MVs on another sites.
P.S. I ask help someone who knows what's wrong or who faced with it or can me follow by usefull link.
P.P.S. It's a pity that there is no button "Useless answer"

Materialize views logs

hey gurus
in my database we have some materialize views . and some of them are using clouse REFRESH COMPLETE and some are USING REFRESH FAST.my point of concern is " for a fast refresh we have to create mat. view logs".how can i check what are log exist for my database because i checked in all_object i havn't find any object with type = log . is it really a object else what it do when we run a DDL
" create materialise view log on tablename ....."
thanks in advance

Seems to be working for me, but I don't have a machine that would even run 8.1.7 to test with. I have no experience with the old Server Manager tool, you might try using SQL*Plus instead.
Describing a materialized view log, though, isn't particularly interesting. I created one on the EMP table
SCOTT @ jcave102 Local> select * from dba_mview_logs;
LOG_OWNER                      MASTER                         LOG_TABLE
LOG_TRIGGER                    ROW PRI OBJ FIL SEQ INC
SCOTT                          EMP                            MLOG$_EMP
                               NO YES NO NO NO NO
Elapsed: 00:00:00.01
SCOTT @ jcave102 Local> desc mlog$_emp
Name                                                  Null?    Type
EMPNO                                                          NUMBER(4)
SNAPTIME$$                                                     DATE
DMLTYPE$$                                                      VARCHAR2(1)
OLD_NEW$$                                                      VARCHAR2(1)
CHANGE_VECTOR$$                                                RAW(255)and you'll see that most of the interesting bits are in the RAW(255) CHANGE_VECTOR$$ column.
Justin

How to view logs from browser/front-end without using Visual Admin

Hi,
Is there a way to view logs from the front-end computer without looging into the Visual Admin tool either in the browser or using some stand-alone application.
Thanks,
CD

Hi,
You can use http://ipaddress (or) fqdn :5xx00/NWA
use monitoring and logs option you will view logs.
Regards,
Vamshi.

Refresh Materilaized Views without generating Archive Logs

Hello Gurus,
I'm facing an emebarassing situation,
I've a job every night to execute a dbms_refresh on several materialiled Views, but there are 2 Mviews that take almost 30 minutes each but another issue thay generates almost 10G of data and my File system becomes full in a minute.
I've done an alter Mview Nologging but it doesn't change anything.
Does soemon ahve an idea how to do a refresh without generating Archive logs - or
without logging?
thxs in advance
C.

Since this is a TRUNCATE and INSERT, any user / application querying the MV while the Refresh is running will see ZERO rows. Furthermore if the INSERT fails (e.g. insufficent space to add an extent), the MV remains with ZERO rows.
A DELETE and INSERT avoids such situations (even if the refresh fails, both INSERT and DELETE are rolled-back and the MV is reverted to the state as it was before the Refresh began -- thus showing data from the previous refresh)
Hemant K Chitale
http://hemantoracledba.blogspot.com
Just to clarify : My paragraphs above are not about data "missing" but about precautions to be taken. A COMPLETE Refresh is done during defined outages -- users/applications are made aware that data is not available while the Refresh is running.
Edited by: Hemant K Chitale on Sep 1, 2009 10:53 AM

Creating a Materialized View Log After the Data has been instered

Hi,
I am trying to create a method of replication from Oracle to MySQL using the Materialized View Log table.
This has been done before and works quite well, the only problem is that I am trying to impliment the log after the table has been created and populated and wish to push all the existing data through the log file...
Does anyone know if it is possible to refresh the Materialized View Log and not a Materialized View.
The way the replication is intended to work is:
Oracle> Data inserted into table
Oracle> writes the vector data to the MVL
Script> Monitors the MVL and can see the changes being made to the Oracle Table
Script> Updates MySQL with the data and removes the rows from the MVL
MySQL is then used with other unix systems
Currently we export the data from the table using Triggers and a cronjob running every x minute to check for changes in the TriggerTables
Many thanks for your time on this, I have been checking for almost a whole working day and not found the answer to this problem.

Thats what I thought, the MVL will only read data that has changed since it was created and wont have the option to load in all the data as though it was made before the table was created.
From what I have read, the MVL is quicker than a Trigger and I have some free code that prooved to work from a MVL using it as a reference to know what records to update. There is not that much to a MVL, a record ID and type of update, New, Update or Delete.
I think what I will have to do is work on a the same principle for the MVL but use a Trigger as this way we can do a full reload if required at any point.
Many thanks for your help.

Creating a Mat View having the same name with that of the table name

Hi everyone,
After dropping the mat view name "QQ.TRDLN_DIM_MV", I'm trying to re-create it by having the same name as that of the table but I got an error stating that "name is already used by an existing object". How can create a mat view to look like the object owned by schema "GQ", having a name that is the same as that of the table name, without dropping the table?
OWNER_O OBJECT_TYPE CREATED LAST_DDL_ TIMESTAMP STATUS OBJECT_NAME
===
GQ MATERIALIZED VIEW 05-NOV-08 13-DEC-08 2008-11-05:06:31:46 VALID TRDLN_DIM_MV
GQ TABLE 05-NOV-08 15-DEC-08 2008-11-05:06:31:00 VALID TRDLN_DIM_MV
QQ TABLE 17-AUG-07 16-MAR-09 2007-08-17:17:05:21 VALID TRDLN_DIM_MV
SQL>CREATE MATERIALIZED VIEW QQ.TRDLN_DIM_MV
2 TABLESPACE FPLC01S
3 NOCACHE
4 NOLOGGING
5 COMPRESS
6 PARALLEL ( DEGREE 2 INSTANCES 1 )
7 BUILD IMMEDIATE
8 REFRESH FORCE ON DEMAND
9 WITH PRIMARY KEY
10 AS
11 select /*+ NO_REWRITE */ trdln_id,
12 trdln_skid,
13 trdln_end_date,
14 first_value(trdln_end_date) over (partition by trdln_id order by trdln_end_date DESC) as MaxDate
15 from QQ.trdln_dim;
from QQ.trdln_dim
ERROR at line 15:
ORA-00955: name is already used by an existing object
I appreciate your help. Many thanks in advance!
Regards,
Radic

You'd have to rename the table (using ALTER TABLE tablename RENAME TO othername; ) before you create the MV.
You can't have both existing with the same name in the same schema.
What you see in the GQ schema is that the "table" is the underlying table for the Materialized View.
When you do a CREATE MATERIALIZED VIEW MY_MV AS ...
Oracle creates two objects with the same name, one being the Materialized View MY_MV and the other being the table MY_MV which is the physical storage. {Remember that a Materialized View is a means of getting a physical representation of a View}.
In the QQ schema what you have is either
a. a real Table
or
b. an improperly dropped MV, resulting in the underlying Table still present.

Need Help in Mat View Creation

I have the following query to create a mat view
CREATE MATERIALIZED VIEW IB_CONT1
REFRESH FAST ON DEMAND WITH ROWID
AS
SELECT
        CUST,
        CONSEQ,
        STD,
        ENDD,
        ADD
FROM
     ADMIN.CONTACT@IB_DBLINK;But it displays an error as
        ADMIN.CONTACT@IB_DBLINK
ERROR at line 11:
ORA-12018: following error encountered during code generation for
"OWNER"."IB_CONT1"
ORA-00942: table or view does not existBut when i query the table i displays data.
SQL> select count(*) from admin.contact@ib_dblink;
COUNT(*)
      100what could be the reason?
Any help will be highly appreciated.
Thanks in advance.

Try without ROWID option.
Regards
RK

How to export all the views in one schema?

Hi,
I have more than 1000 views in one shcema.
How to export all the views in one schema?
Amy

Hi,
It's not a very easy question, I have develop a script wich create a script to create view from old database to new database :
/* &1: Oracle SID Source
/* &2: Oracle Schema Source
SET HEAD OFF
SET VERIFY OFF
SET PAGESIZE 0
SET LONG 40000000
SET LONGCHUNKSIZE 2000
SET LINESIZE 2000
SET FEEDBACK OFF
CREATE TABLE RECREATE_VIEW(VIEW_NAME VARCHAR2(30), TEXT LONG);
/* Selection du texte de la vue */
DECLARE
w_text long;
w_text_debut long;
w_text_column long;
w_view varchar2 (30);
w_schema varchar2 (8):='&2';
CURSOR w_cursor IS
SELECT a.view_name, a.text
FROM dba_views a
WHERE a.owner = w_schema;
CURSOR w_column IS
SELECT DECODE (ROWNUM,
1, 'CREATE OR REPLACE FORCE VIEW ' || '&' || '1..'
|| a.table_name || chr(10)
|| '('
|| a.column_name
|| DECODE (ROWNUM, nbcolumns, ')' || chr(10) || 'AS' || chr(10), ',' || chr(10))
FROM (select column_name,table_name
FROM dba_tab_columns
WHERE owner = '&1'
AND table_name = w_view
order by column_id ) a,
(SELECT COUNT (1) nbcolumns
FROM dba_tab_columns
WHERE owner = '&1'
AND table_name = w_view
GROUP BY owner, table_name) b
order by rownum;
BEGIN
OPEN w_cursor;
LOOP
FETCH w_cursor INTO w_view, w_text;
EXIT WHEN w_cursor%NOTFOUND;
w_text_debut := NULL;
w_text_column := NULL;
OPEN w_column;
LOOP
FETCH w_column INTO w_text_column;
EXIT WHEN w_column%NOTFOUND;
w_text_debut := w_text_debut || w_text_column || ' ';
w_text_column := NULL;
END LOOP;
CLOSE w_column;
w_text := w_text_debut||w_text||';';
insert into RECREATE_VIEW(VIEW_NAME, TEXT) VALUES (w_view, w_text);
COMMIT;
w_text := NULL;
w_view := NULL;
END LOOP;
CLOSE w_cursor;
END;
SPOOL scripts_views_&1..sql
PROMPT SPOOL scripts_views_&1..log
PROMPT
SELECT TEXT
FROM RECREATE_VIEW;
PROMPT
PROMPT SPOOL OFF
PROMPT
SPOOL off
PROMPT /* Formattage du fichier SQL */
!sed 's/[ ]*$//' scripts_views_&1..sql > aprilia.tmp
!rm scripts_views_&1..sql
!mv aprilia.tmp scripts_views_&1..sql
DROP TABLE RECREATE_VIEW;
EXIT
I hope that help you.
Nicolas.

Materialized View Log Error

I keep getting a materialized view log error on a table that is not a master table, in fact there are no materialized views created on any tables in this database. The schema was imported from another but the export schema did not have any materialized views either from what I can see.
Is there a data dictionary or something I can check?
This is the error: ORA-12096: error in materialized view log on "Schema"."Table".
ORA-00942: table or view does not exist
I get this error anytime I try to update or insert.
Apparently it thinks it should be associated to a materialized view log, how can I disassociate it?
Thanks

Hey Justin, thanks for your reply. I did not use the real table names but the original error message did.
There was a log when I queried the view. I dont know why there was one. We never created any materialized views in or from this database.
I dropped the log. It took it out of the data dictionary so everything works again.
Thanks for your reply.

Materialized View Log options

I have read the documentation. I know you can specify options such as 'with primary key' and/or 'with rowid' when creating a materialized view log. Also, that you can specify to include additional columns in the log -and that these can then be seen in the MLOG$ table that gets created. But I don't know why or in what circumstances you'd specify the one or the other, or include columns or not. Can anyone give some example scenarios where you'd do one or the other?

Hello again,
The fundamental reason (why you would specify primary key and/or ROWID) is to facilitate fast refreshes (as opposed to a complete refresh) of the materialized view -- a lot will depend on the MV query itself, and whether one or both of primary key & ROWID are needed, i.e., if there's a COUNT(*) involved, where the primary key would play a role, or without such an aggregate, the ROWID will be necessary (in any case) for fast refresh.
Edited by: SeánMacGC on Jul 9, 2009 5:54 PM
If you run the utlxmv.sql script in $ORACLE_HOME/rdbms/admin, that will create the MV_CAPABILITIES_TABLE, which when you create an MV and execute DBMS_MVIEW.EXPLAIN_MVIEW('your_mview') will populate that with what that MV is capable of, i.e.,
SQL> desc mv_capabilities_table;
Name                                      Null?    Type
STATEMENT_ID                                       VARCHAR2(30)
MVOWNER                                            VARCHAR2(30)
MVNAME                                             VARCHAR2(30)
CAPABILITY_NAME                                    VARCHAR2(30)
POSSIBLE                                           CHAR(1)
RELATED_TEXT                                       VARCHAR2(2000)
RELATED_NUM                                        NUMBER
MSGNO                                              NUMBER(38)
MSGTXT                                             VARCHAR2(2000)
SEQ                                                NUMBER
SQL> select capability_name, possible from mv_capabilities_table;
CAPABILITY_NAME                P
PCT                            N
REFRESH_COMPLETE               Y
REFRESH_FAST                   N
REWRITE                        N
PCT_TABLE                      N
REFRESH_FAST_AFTER_INSERT      N
REFRESH_FAST_AFTER_ONETAB_DML N
REFRESH_FAST_AFTER_ANY_DML     N
REFRESH_FAST_PCT               N
REWRITE_FULL_TEXT_MATCH        N
REWRITE_FULL_TEXT_MATCH        N
REWRITE_PARTIAL_TEXT_MATCH     N
REWRITE_PARTIAL_TEXT_MATCH     N
REWRITE_GENERAL                N
REWRITE_GENERAL                N
REWRITE_PCT                    N
PCT_TABLE_REWRITE              N

Materialized View Log table with sequence

I have a materialized view log in Database A..a very simple one...similar to "create materialized view log on t WITH PRIMARY KEY"...The primary key is a composite key of 2 columns...Description of the mlog table looks like this...
desc mlog$_t
emp_ctr NUMBER
emp_date DATE
SNAPTIME$$ DATE
DMLTYPE$$ VARCHAR2(1)
OLD_NEW$$ VARCHAR2(1)
CHANGE_VECTOR$$ RAW(255)
The Materialized view is in database B...again a simple one...no aggregation...This gets refreshed on demand manually evey week. The records that get accumulated in the MLOG every week is ~ 300K..The manual refresh used to finish in about 20mins but since last week it is running for ever. Upon reviewing the contents of MLOG I noticed that it contained a mixture of inserts and updates. I'm not sure if the MLOG contanied only inserts in the past when the MV used to refresh very quickly...Based on the documentation, Oracle recommends creating MLOGS with "sequence" whenever inserts/updates/deleted are expected. I'm planning to drop and recreate the MLOG with sequence with the hope that this would fix the slow refresh issue...Appreciate if you could let me know your thoughs...
I'm also planning to trace the session to get some wait event statistics to find out the reason for the slow refresh...

There are a few reasons why refreshes slow down over time.
1. Is the log table being cleared out after a refresh? If not, you may have another mview (maybe even one that doesn't exist any more) registered against this log. When this happens, the log table never stops growing.
2. How big is the segment occupied by the table? If it has grown very large at some time in the past (e.g., because refresh was delayed), then when the refresh does a FTS on the log it will scan the whole segment - even if only a few rows are present.
3. It may help to add an index to the PK columns, and another to SNAPTIME$$. Without them, the refresh will FTS the log. For a big segment, that can take a long time.
-- Phil

EXPort (without Mat view logs)

Similar Messages

Maybe you are looking for