CREATE THE ORA-00957 MATERIALIZED VIEW

Hello

I tried to use this query to create a MVIEW and I get an ORA-00957 (duplicate column name)

select t.month

,t.year

,t.entity_code

,t.itemref_local

,t.qty

,t.revenue

,t.cogs

,t.ppv

,t.FD

,t.var_labor

,t.var_ovhd

,n.code entity_code

,n.name entity_name

,n.finance_responsible

,c.local_name

,c.emea_name

,c.segment

,c.country

,c.origin_entity

,c.icp_code

,c.type

,c.rmm

,c.sales_rep

,c.sales_leader

,c.emea_director

,c.nat_accounts

,o.code country_code

,o.NAME country_name

,o.REGION country_region

,e.ELIMINATED

,i.PART_NUMBER

,i.DESCRIPTION part_description

,i.PRODUCT_GROUP

,i.LINE

,i.CATEGORY

,i.FAMILY

,i.RANGE

,i.SUPPLIER

,i.PLM



FROM hsce_transactions T

       , hsce_entity N 

       , hsce_customers C

       , hsce_country O

       , hsce_elim E

       , HSCE_ITEMS I

       , HSCE_MAPPING M



WHERE T.entity_code = N.code

     AND T.customer_code = C.customer_code

     AND C.ICP_CODE = E.ICP_CODE

     AND C.country = O.code

     AND T.ITEMREF_LOCAL = M.ITEM_REF

     and M.PART_NUMBER = I.PART_NUMBER

Can someone point me to where I have gone wrong?

Thank you
Adam

you have specified entity_code twice 1) as entity_code t.entity_code and n.code 2) second time you use as an alias for the n.code column

Tags: Database

Similar Questions

How do I know how much the number of materialized view columns

How do I know how much the number of materialized view columns
Thank you
Gopal

Best to include the owner too if you use all_tab_columns

Select count (*)

from all_tab_columns

where owner = "."

and table_name = "."

Union - generator of grid view layout query error could not create the checkerboard to correct view

I get the error while I'm trying to run a simple union query below. The query uses simple areas. I use columns the same type of data in the same order in each of the areas and when I run the sql generated backend query, it returns the correct result. Only in obiee front end, it is not showing any result but giving the below error instead. I use version 11.1.1.6.8 Please help!
The presentation view grid generator could not create the checkerboard to correct view. It lacked the logical column with the following ID: c6d9af7a1de3ca97a.
Error details
Error codes: WUSYDB5K
Geographical area: saw.views.evc.activate, saw.httpserver.processrequest, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.
handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads

This is a bug, you must connect your environment to min 11.1.1.6.10 max 11.1.1.6.12/11.1.1.7.x

Impact on performance at the addition of materialized view logs at the tables?
I write a very complex query for a client of our database system transaction and this will require the creation of a materialized viewbecause, all attempts at development to make acceptable performance failed.

I want to activate the fast refresh the MVIEW but I am confused about the consequences of the addition of the addition of materialized view logs to the base tables.

Some tables are large and involved in a large number of transactions and I wonder if the INSERT/update performance will be seriously affected by the presence of a newspaper mview.

Maybe it's a simple question, but I was unable to find an answer very clear in the literature.

Thanks for all the answers!

Chris Mills
Biotechnology data management consultant
There is an overload for the newspapers of the view materialized, a little less, but roughly on par with a trigger that writes to a table.

If it is an OLTP system where you do a lot of low-value transactions, the general expenses percentage is probably not particularly great, something in the range of 5-10% maybe (although, of course, by running tests in the development environment would be desirable). If there are loads in bulk, the impact of the percentage could be higher.

Justin

Difference between the table and Materialized View

Is there an advantage outside automatic synchronization (founded refresh selected type) using Materialized View?
I came across this question as table and MV both store values, and we can also update table using the code what is the need of MV? Why not create a table instead of MV with the same definition and same charly?
I need some explanation to force someone to convince himself.
Thank you

http://docs.Oracle.com/CD/B19306_01/server.102/b14223/basicmv.htm

Sections that highlight its strengths:

1. materialized views for data warehouses

2. materialized views for distributed computing

Query, re - write, features as Materialized view log files that can be used for replication between databases, etc...

Insert the data in materialized views at the Table

Hello
We have a problem in which some incorrect data has been loaded for tables.
Users now are pointing to the materialized views and data access using synonyms.
Is it possible to insert data from a view, materialized at the tables?
Kind regards
VN

Hello

As sb92075 has said, we can insert in the table of the materialized view.

Test below data:

SQL > select * from t1;

CITY OF AMOUNT ID COMMENTS

---------- -------------------- ---------- --------------------

1 XXX 28 Chicago

2 AAA LAS 25

3 YYY 25 NY

4 35 Texas XXX

5 XXX 55 Arlington

6 56 Chicago YYY

7 XXX 66 NY

7 selected lines.

SQL > create mv_t1 view materialized in select * from t1;

Materialized view created.

SQL > select * from mv_t1;

CITY OF AMOUNT ID COMMENTS

---------- -------------------- ---------- --------------------

1 XXX 28 Chicago

2 AAA LAS 25

3 YYY 25 NY

4 35 Texas XXX

5 XXX 55 Arlington

6 56 Chicago YYY

7 XXX 66 NY

7 selected lines.

SQL > insert into t1 values(8,'BBB',22,'NY');

1 line of creation.

SQL > select * from mv_t1;

CITY OF AMOUNT ID COMMENTS

---------- -------------------- ---------- --------------------

1 XXX 28 Chicago

2 AAA LAS 25

3 YYY 25 NY

4 35 Texas XXX

5 XXX 55 Arlington

6 56 Chicago YYY

7 XXX 66 NY

7 selected lines.

SQL > select * from t1;

CITY OF AMOUNT ID COMMENTS

---------- -------------------- ---------- --------------------

1 XXX 28 Chicago

2 AAA LAS 25

3 YYY 25 NY

4 35 Texas XXX

5 XXX 55 Arlington

6 56 Chicago YYY

7 XXX 66 NY

NEW YORK 8 22 BBB

8 selected lines.

SQL > commit;

Validation complete.

SQL > select * from mv_t1;

CITY OF AMOUNT ID COMMENTS

---------- -------------------- ---------- --------------------

1 XXX 28 Chicago

2 AAA LAS 25

3 YYY 25 NY

4 35 Texas XXX

5 XXX 55 Arlington

6 56 Chicago YYY

7 XXX 66 NY

7 selected lines.

SQL > delete from t1;

8 deleted rows.

SQL > select * from mv_t1;

CITY OF AMOUNT ID COMMENTS

---------- -------------------- ---------- --------------------

1 XXX 28 Chicago

2 AAA LAS 25

3 YYY 25 NY

4 35 Texas XXX

5 XXX 55 Arlington

6 56 Chicago YYY

7 XXX 66 NY

7 selected lines.

SQL > insert into t1 select * from mv_t1;

7 lines were created.

SQL > select * from t1;

CITY OF AMOUNT ID COMMENTS

---------- -------------------- ---------- --------------------

1 XXX 28 Chicago

2 AAA LAS 25

3 YYY 25 NY

4 35 Texas XXX

5 XXX 55 Arlington

6 56 Chicago YYY

7 XXX 66 NY

7 selected lines.

SQL >

extracting data from the CLOB using materialized views

Hello
We have xml data from clob which I have a requirement to extract (~ 50 attributes) on a daily basis, so we decided to use materialized views with refreshes full (open good suggestions)
A small snippet of code
CREATE THE MWMRPT MATERIALIZED VIEW. TASK_INBOUND
IMMEDIATE CONSTRUCTION
FULL REFRESH ON DEMAND
WITH ROWID
AS
SELECT M.TASK_ID, M.BO_STATUS_CD, b.*
OF CISADM. M1_TASK m,
XMLTABLE (' / a ' XMLPARSE PASSING ())
CONTENT '< a > | M.BO_DATA_AREA | "< /a >."
) COLUMNS
serviceDeliverySiteId varchar2 (15) PATH
"cmPCGeneralInfo/serviceDeliverySiteId"
serviceSequenceId varchar2 (3) PATH "cmPCGeneralInfo/serviceSequenceId"
completedByAssignmentId varchar2 (50) PATH "completedByAssignmentId."
Cust_id varchar2 (10) PATH "cmPCCustomerInformation/customerId,"
ACCT_SEQ varchar2 (5) PATH "customerInformation/accountId"
AGRMT_SEQ varchar2 (5) PATH cmPCCustomerAgreement/agreementId"."
COLL_SEQ varchar2 (5) PATH "cmPCGeneralInfo/accountCollectionSeq"
REVENUE_CLASS varchar2 (10) PATH "cmPCCustomerAgreement/revenueClassCode"
REQUESTED_BY varchar2 (50) PATH ' attributes customerInformation/contactName',...~50
This ddl ran > 20 hours and no materialized view created. There are certain limits that we have
- Cannot create a materialized view log
- cannot change the source as its defined provider table
- cannot do an ETL
DB is 11g R2
Any ideas/suggestions are very much appreciated

I explored a similar approach, using the following test case.

It creates a table "MASTER_TABLE" containing 20,000 lines and a CLOB containing an XML fragment like this:

09HOLVUF3T6VX5QUN8UBV9BRW3FHRB9JFO4TSV79R6J87QWVGN

UUL47WDW6C63YIIBOP1X4FEEJ2Z7NCR9BDFHGSLA5YZ5SAH8Y8

O1BU1EXLBU945HQLLFB3LUO03XPWMHBN8Y7SO8YRCQXRSWKKL4

...

1HT88050QIGOPGUHGS9RKK54YP7W6OOI6NXVM107GM47R5LUNC

9FJ1JZ615EOUIX6EKBIVOWFDYCPQZM2HBQQ8HDP3ABVJ5N1OJA

then an intermediate table "MASTER_TABLE_XML" with the same columns with the exception of the CLOB which turns into XMLType and finally a MVIEW:

SQL > create table master_table like

2. Select level as id

3, cast ('ROW' | to_char (Level) as varchar2 (30)) as the name

4       , (

5. Select xmlserialize (content

XMLAGG 6)

7 xmlelement (evalname ('ThisIsElement' | to_char (Level)), dbms_random.string ('X', 50))

8                    )

9 as clob dash

10                  )

11 double

12 connect by level<=>

(13) as xmlcontent

14 double

15 connect by level<= 20000="">

Table created.

SQL > call dbms_stats.gather_table_stats (user, 'MASTER_TABLE');

Calls made.

SQL > create table (master_table_xml)

Identification number 2

3, name varchar2 (30)

4, xmlcontent xmltype

5)

binary xmltype 6 securefile XML column xmlcontent store

7;

Table created.

SQL > create materialized view master_table_mv

2 build postponed

full 3 Refresh on demand

4, as

5. Select t.id

6, t.nom

7       , x.*

master_table_xml 8 t

9, xmltable ('/ r' in passing t.xmlcontent)

10 columns

11 path of varchar2 (50) ThisIsElement1 'ThisIsElement1 '.

12, path of varchar2 (50) ThisIsElement2 'ThisIsElement2 '.

13, path of varchar2 (50) ThisIsElement3 'ThisIsElement3 '.

14, path of varchar2 (50) ThisIsElement4 'ThisIsElement4 '.

15 road of varchar2 (50) ThisIsElement5 'ThisIsElement5 '.

16, road of varchar2 (50) ThisIsElement6 'ThisIsElement6 '.

17 road of varchar2 (50) ThisIsElement7 'ThisIsElement7 '.

18 road of varchar2 (50) ThisIsElement8 'ThisIsElement8 '.

19 road to varchar2 (50) ThisIsElement9 'ThisIsElement9 '.

20, path of varchar2 (50) ThisIsElement10 'ThisIsElement10 '.

21, road to varchar2 (50) ThisIsElement11 'ThisIsElement11 '.

22 road of varchar2 (50) ThisIsElement12 'ThisIsElement12 '.

23 road of varchar2 (50) ThisIsElement13 'ThisIsElement13 '.

24, path of varchar2 (50) ThisIsElement14 'ThisIsElement14 '.

25 road of varchar2 (50) ThisIsElement15 'ThisIsElement15 '.

26, path of varchar2 (50) ThisIsElement16 'ThisIsElement16 '.

27, way to varchar2 (50) ThisIsElement17 'ThisIsElement17 '.

28 road of varchar2 (50) ThisIsElement18 'ThisIsElement18 '.

29 road of varchar2 (50) ThisIsElement19 'ThisIsElement19 '.

30, path of varchar2 (50) ThisIsElement20 'ThisIsElement20 '.

31, path of varchar2 (50) ThisIsElement21 'ThisIsElement21 '.

32 road of varchar2 (50) ThisIsElement22 'ThisIsElement22 '.

33, path of varchar2 (50) ThisIsElement23 'ThisIsElement23 '.

34 road of varchar2 (50) ThisIsElement24 'ThisIsElement24 '.

35 road of varchar2 (50) ThisIsElement25 'ThisIsElement25 '.

36, road to varchar2 (50) ThisIsElement26 'ThisIsElement26 '.

37, path of varchar2 (50) ThisIsElement27 'ThisIsElement27 '.

38, path of varchar2 (50) ThisIsElement28 'ThisIsElement28 '.

39, path of varchar2 (50) ThisIsElement29 'ThisIsElement29 '.

40, road of varchar2 (50) ThisIsElement30 'ThisIsElement30 '.

41 road of varchar2 (50) ThisIsElement31 'ThisIsElement31 '.

42, path of varchar2 (50) ThisIsElement32 'ThisIsElement32 '.

43, road to varchar2 (50) ThisIsElement33 'ThisIsElement33 '.

44, path of varchar2 (50) ThisIsElement34 'ThisIsElement34 '.

45, path of varchar2 (50) ThisIsElement35 'ThisIsElement35 '.

46, path of varchar2 (50) ThisIsElement36 'ThisIsElement36 '.

47, path of varchar2 (50) ThisIsElement37 'ThisIsElement37 '.

48, path of varchar2 (50) ThisIsElement38 'ThisIsElement38 '.

49, path of varchar2 (50) ThisIsElement39 'ThisIsElement39 '.

50 road of varchar2 (50) ThisIsElement40 'ThisIsElement40 '.

51, path of varchar2 (50) ThisIsElement41 'ThisIsElement41 '.

52, path of varchar2 (50) ThisIsElement42 'ThisIsElement42 '.

53, path of varchar2 (50) ThisIsElement43 'ThisIsElement43 '.

54, path of varchar2 (50) ThisIsElement44 'ThisIsElement44 '.

55 road of varchar2 (50) ThisIsElement45 'ThisIsElement45 '.

56, path of varchar2 (50) ThisIsElement46 'ThisIsElement46 '.

57, path of varchar2 (50) ThisIsElement47 'ThisIsElement47 '.

58 road of varchar2 (50) ThisIsElement48 'ThisIsElement48 '.

59 road of varchar2 (50) ThisIsElement49 'ThisIsElement49 '.

60 road of varchar2 (50) ThisIsElement50 'ThisIsElement50 '.

(61) x;

Materialized view created.

The discount is then performed in two steps:
1. INSERT INTO master_table_xml
2. Refresh the MVIEW
(Note: as we insert in an XMLType column, we need an XML (only root) document this time)

SQL > set timing on

SQL >

SQL > truncate table master_table_xml;

Table truncated.

Elapsed time: 00:00:00.27

SQL >

SQL > insert into master_table_xml

2. select id

3, name

4, xmlparse (document '' |) XmlContent |'')

5 master_table;

20000 rows created.

Elapsed time: 00:04:38.72

SQL >

SQL > call dbms_mview.refresh ('MASTER_TABLE_MV');

Calls made.

Elapsed time: 00:00:22.42

SQL >

SQL > select count (*) in the master_table_mv;

COUNT (*)

----------

20000

Elapsed time: 00:00:01.38

SQL > truncate table master_table_xml;

Table truncated.

Elapsed time: 00:00:00.41

Moving all the newspapers and Materialized View at the schema level using the data pump in

Hi Experts,

Please help me on how I can exp/imp all materialized views andMV logs (as are some MVs) only the full scheme of other databases. I want to exclude everything else.

Concerning
-Samar-

Using DBMS_METADATA. Create the following SQL script:

SET FEEDBACK OFF
SET SERVEROUTPUT ON FORMAT WORD_WRAPPED
SET TERMOUT OFF
SPOOL C:\TEMP\MVIEW.SQL
DECLARE
    CURSOR V_MLOG_CUR
      IS
        SELECT  DBMS_METADATA.GET_DDL('MATERIALIZED_VIEW_LOG',LOG_TABLE) DDL
          FROM  USER_MVIEW_LOGS;
    CURSOR V_MVIEW_CUR
      IS
        SELECT  DBMS_METADATA.GET_DDL('MATERIALIZED_VIEW',MVIEW_NAME) DDL
          FROM  USER_MVIEWS;
BEGIN
    DBMS_METADATA.SET_TRANSFORM_PARAM(DBMS_METADATA.SESSION_TRANSFORM,'SQLTERMINATOR',TRUE);
    FOR V_REC IN V_MLOG_CUR LOOP
      DBMS_OUTPUT.PUT_LINE(V_REC.DDL);
    END LOOP;
    FOR V_REC IN V_MVIEW_CUR LOOP
      DBMS_OUTPUT.PUT_LINE(V_REC.DDL);
    END LOOP;
END;
/
SPOOL OFF

In my case the script is saved as C:\TEMP\MVIEW_GEN. SQL. Now I will create a journal mview and mview in schema SCOTT and run the script above:

SQL> CREATE MATERIALIZED VIEW LOG ON EMP
  2  /

Materialized view log created.

SQL> CREATE MATERIALIZED VIEW EMP_MV
  2  AS SELECT * FROM EMP
  3  /

Materialized view created.

SQL> @C:\TEMP\MVIEW_GEN
SQL>

Run the C:\TEMP\MVIEW_GEN script. SQL generated a C:\TEMP\MVIEW queue. SQL:

  CREATE MATERIALIZED VIEW LOG ON "SCOTT"."EMP"
 PCTFREE 10 PCTUSED 30 INITRANS
1 MAXTRANS 255 LOGGING
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1
MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL
DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
  TABLESPACE "USERS" 

WITH PRIMARY KEY EXCLUDING NEW VALUES;

  CREATE MATERIALIZED VIEW "SCOTT"."EMP_MV" ("EMPNO", "ENAME", "JOB", "MGR",
"HIREDATE", "SAL", "COMM", "DEPTNO")
  ORGANIZATION HEAP PCTFREE 10 PCTUSED 40
INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
  STORAGE(INITIAL 65536 NEXT 1048576
MINEXTENTS 1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
  TABLESPACE
"USERS"
  BUILD IMMEDIATE
  USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 

STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645

PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE
DEFAULT CELL_FLASH_CACHE DEFAULT)
  TABLESPACE "USERS"
  REFRESH FORCE ON
DEMAND
  WITH PRIMARY KEY USING DEFAULT LOCAL ROLLBACK SEGMENT
  USING ENFORCED
CONSTRAINTS DISABLE QUERY REWRITE
  AS SELECT "EMP"."EMPNO"
"EMPNO","EMP"."ENAME" "ENAME","EMP"."JOB" "JOB","EMP"."MGR"
"MGR","EMP"."HIREDATE" "HIREDATE","EMP"."SAL" "SAL","EMP"."COMM"
"COMM","EMP"."DEPTNO" "DEPTNO" FROM "EMP" "EMP";

Now, you can run this on the database. You may need to adjust the tablespace and storage clauses. Or you can add more DBMS_METADATA. SET_TRANSFORM_PARAM calls to C:\TEMP\MVIEW_GEN. SQL to force DBMS_METADATA not to include the tablespace or / and the terms of storage.

SY.

Questions on the tables of materialized views and MV newspaper
Hi all

Have some questions about Materialized View.

(1) once the materialized view reads the records from the table MLOG, reviews the MLOG get purged. fix? or is that not the case? In some cases, I see still (old) records in the MLOG table even after updating MV.

(2) how the table MLOG distinguishes between a reading which comes from a MV and a reading that comes from a user? If I execute manually
"Select * < table MLOG > ' could get record of the table MLOG redacted all the same way as it does after a refresh of MV?

(3) one of our MV updates crashes intermittently. Based on the events of waiting I noticed that it was a 'db file sequential read' against the main table. Finally I had to put an end to the update. I don't know why it was sequential reading on the main table when she should be reading the table MLOG. Any ideas?

(4) I saw 'file db scattered read' (full table scan) usually on tables, but I was surprised to see 'db file sequential read' against the table. I thought sequential read occurs normally against the index. All the world has noticed this behavior?

Thanks for your time.
(1) once all the registered materialized views have read a particular line in a trunk of materialized view, it is removed, Yes. If there are multiple materialized views that are based on the same newspaper, they would all need to refresh before it would be safe to delete the log entry for MV. If one of the materialized views is no incremental updating, there may be cases where the log purge automatically.

(2) No, your query does not cause anything be served (although you wouldn't see something interesting unless you get to implement a lot of code to analyze change vectors stored in the journal). I don't know the exact mechanism used by Oracle has been published, if you could go through and draw a session to get an idea of the moving parts. From a practical point of view, you just need to know that when you create an updatable materialized view fast, it will register as interested especially newspapers MV.

(3) it depends on what is stored in the log of MV. The update process may need to recover specific table columns if your log stores just the fact that the data for a particular key changed. You can specify when you create a materialized view that you want to store specific columns or include the new clause values (with the NEW VALUES INCLUDING). It is perhaps beneficial (or necessary) for the refreshment quick process, but it would tend to increase the storage space for the materialized view log and increase the cost of the maintianing the materialized view log.

(4) sequential reads on a table are perfectly normal - it just means that someone looking for a block of data in the table (i.e. looking a line in the table of ROWID based on the ROWID in an index or a materialized view log).

Justin

Creation of privilege to write to the database master materialized view?
I would like to create materialized views for a few tables of a production Oracle database replication. I have only read access to the source database. I think I need additional privileges to create the journal for the quick update. Is this correct? Have no option if I can't get additional privileges and cannot get a DBA to help me?
If you need to fast refresh to materialized view log, you will need help of DBA.

Otherwise, you need to create complete refresh Mviews.

change the position of the region in the middle of the page / create the new Point of view from the region
I have used apex 4.1, 10.3 oracle database, theme 21 (scarlet) window7

I want to change any position the region to appear in the middle of the page and I have tray every thing to do and no results

I change REGION_ATTRIBUTES to be: style = vertical-align: middle
and I add in the header of the region {< div style = "vertical-align: middle" > < / div > ""} and no results and the region do not move in the middle of the page

My question is
1 a way to make the region in middle of page other

2. How can create the new Point of display area as (region Position2, Page (1) template body) with the middle position

Thank you

Published by: Ahmed Farouk on April 15, 2012 11:01

Published by: Ahmed Farouk on April 15, 2012 11:01
Hello

No need to give ' style = vertical-align: middle ", replace it with this: nowrap ="nowrap"align ="center ".

see if it works.

and for the second, you can copy the existing model definition: model, in the table tag you can see #REGION_ATTRIBUTES #, simply add align = 'center' after this

and apply this model in your area.

Thank you
Tauceef

I get "failed to set the refresh attribute COMMIT for the materialized view" when I try to create a MV using a table and another MV

Experts,
I'm trying to create a YOUNG refreshable ON COMMIT MV (xyz) using a table (circuit) and quickly updateable on validation MV (abc), but get an error:
SQL error: ORA-12054: cannot set the attribute ON COMMIT refresh for the materialized view
12054 00000 - "cannot set the refresh attribute COMMIT for the materialized view.
* Cause: The materialized view did not meet the requirements for update to
moment of validation.
* Action: Specify only valid options.
1] MV abc
= MV abc defined as below =.
CREATE MATERIALIZED view abc_MV
Immediate CONSTRUCTION
REFRESH QUICKLY YOU COMMIT using constraints of trust
WITH ROWID AS SELECT n.*,.
n.ROWID noderowid
node n
where n.nodetype in (1610000069,1610007267);

-Above works OK and MV connect you on table node is created successfully
=====================================================
[ 2] Circuit Board
======================================================
CREATE MATERIALIZED VIEW LOG ON Cramer.Circuit WITH SEQUENCE, ROWID ( ) -all columns of table ofcircut parentheses
INCLUDING THE NEW VALUES;
-More top works OK and MV connect you on table circuit is created successfully
======================================================

[3] trying to create MV xyz
======================================================
CREATE MATERIALIZED VIEW LOG ON cramer.abc_MV WITH SEQUENCE, ROWID ( ) -all columns of abc_MV brackets
INCLUDING THE NEW VALUES;
-Above works OK and log on ABC MV MV gets created successfully
-Problematic step below
Xyz_MV CREATE MATERIALIZED VIEW
IMMEDIATE CONSTRUCTION
REFRESH QUICKLY YOU COMMIT using constraints of trust
AS
SELECT c., c.rowid circuit_rowid, n.rowid tr_rowid
the circuit c, abc_mv n
where circuit2startnode = n.nodeid
and c.rpplanId = n.rpplanId;
==========================================================
Clues on how to solve this problem and make quickly updatable ON Commit MV xyz
Thanks in advance.

Chanchal,

If you can read my original post carefully you may have noticed that all these restrictions will not apply in my case.

All,

In any case I found the solution to my problem.

There are a few additional restrictions for materialized views multilayer

Additional Restrictions for master materialized views

The following types of materialized views may not be masters of editable materialized views:
- ROWIDmaterialized views
- Complex materialized views
- Read-only materialized views
I've updated the underlying MV abc below and everything worked like a charm

CREATE MATERIALIZED view abc_MV

Immediate CONSTRUCTION

REFRESH QUICKLY YOU COMMIT using constraints of trust

IN SELECT

n.*, n.rowid noderowid, nt.rowid nodetyperowid

the node n, nodetype_m nt

where n.node2nodetype = nt.nodetypeid

and nt.nodetypeid in (1610000069,1610007267);

Note: To ADD a join without which I was getting error below (although had primary key on the table of the node)

SQL error: ORA-23415: materialized view log for "NODE" does not save the primary key

23415 00000 - "view the log for materialized \"%s\".\"%s\"does not save the primary key.

* Cause: A primary key materialized view is refreshed quickly, but the

The materialized view log does not record the primary key information.

* Action: Use CREATING MATERIALIZED VIEW LOG... Command to add a PRIMARY KEY to

start recording of the primary key information in the materialized view

Newspaper.

Cannot create Materialized View using the PL/SQL procedure

Hello

I have a question related to the creation of materialized view.
I have a stored procedure that creates the materialized view. When you try to perform this procedure, I get not enough privileges error: ORA-01031.

When I run the content of this procedure as a PL/SQL block anonymous their materialized view is created without any complications.
Can you please advice me on this subject?
It is even possible to create a materialized view in the stored procedure as I found no info on this subject.

Thank you
Petr

Hi chudapet,

Whenever you make in procedure, you must have direct subsidies and not through a role.

Most likely the grant to create a materialized view is available via a role to your username.
Assign a direct grant to the user:

grant create materialized view to scott;
{code}

Create table works, create materialized view only - long column names?
Hello.

I have no probs creating a table as well: -.
CREATE TABLE blah
(
DEVICE_ID
)
in select
"Device_ID" AS DEVICE_ID
"of"sum" Device"@ed_link_3
where "Device_ID" < 5;

But when I try to create a materialized view:
Blah1 CREATE MATERIALIZED VIEW
(
DEVICE_ID
)
< various materialized view parms >
in select
"Device_ID" AS DEVICE_ID
"of"sum" Device"@ed_link_3
where "Device_ID" < 5;

It fails with errors: -.
ORA-04052: error occurred when searching to the top of the remote object Aggregate.Device@ED_LINK_3
ORA-01948: length of the name of the identifier (31) exceeds maximum (30)

Is there a way to get around this?
Is the problem with the columns of the remote table of device, which I do NOT need to import to have column names that are longer than 30 characters?

For now, I want only the Device_ID column which is a simple 9 characters long.

Oh, and the remote database is MySQL.
I'm uncomfortable with the < parms of materialized view > as they work fine when I choose a different remote table with only short column names.

Thank you.
To my knowledge, you have the option
(a) create view (with shortened column names or only with desired columns if they are already less than 30 char limit) side of mysql
(b) use dbms_passthrough to force the analysis to be done on mysql (as in the example provided by SY here use dbms_passthrough to create a view )
However, I prefer to stick to one), because with dbms_passtrhough, you retrieve row by row.

Best regards

Maxim

The materialized view log and user...
Hello
Suppose a user, we will call him A has a table and another user B must create a log of materialized view on the table that a user has.
While user B have all the privileges of object (direct priv insert, update, delete... not through a role) on the table to the user may not create a log of mv on this table on its schema...
Thus, the insert/update/delete stmts on < table_name > are run successfully (after having logged on as user B).

The error message ' ORA-00942: table or view does not exist ' appears when I run the command:
Connect B/B;
create log view materialized on table_name with sequence including new values;

Note: I use ORADB 10.2.0.4 and it stands for table-name to user B (which tries to create the log of mv on)...

The req. above is possible somehow?

Thank you
SIM
The documentation says the following:

The materialized view log is created in the same schema as the master of the target.

HTH!

CREATE THE ORA-00957 MATERIALIZED VIEW

Similar Questions

Additional Restrictions for master materialized views

Maybe you are looking for