is missing a closing parenthesis in create materialized view statement

Hi, I am using oracle 10g R2 and try to create a view of materalized with the following statement:

CREATE MATERIALIZED VIEW MVT_DEC_TAB USING INDEX REFRESH FAST ON COMMIT AS 
select i.rowid as ind_rowid,c.rowid as indc_rowid,r.rowid as r_rowid,b.rowid as b_rowid,brk.rowid as brk_rowid,
i.name,i.sname,i.address,i.tel,i.fax,i.email,
DECODE(c.BRKNO,null,0,1) AS DEC_BRK,
TO_TIMESTAMP(NVL(VEKDOV,'2001/01/01')||' 12:00:00','YYYY/MM/DD HH:MI:SS'),
DECODE(c.brkno,null,DECODE(c.ncmpcode,null,c.vekdov,b.bcarddov),brk.validitydov)
from indiv i,indivcoding c
LEFT OUTER JOIN BROKER brk ON brk.brkno = c.brkno
LEFT OUTER JOIN CORPORAT r
ON c.ncmpcode=r.cmpcode INNER JOIN BCARD b ON b.bcardno=r.bcardno
where c.typeact=2  
and c.natcode=i.natcode
and c.brkno is not null or c.ncmpcode is not null or c.nnatcode is not null

but I get an error message:
where c.typeact = 2
ERROR on line 11:
ORA-00907: lack of right parenthesis

which makes no sense because if I run the sql code of the materialized view, it runs normally.
I need to know what the causing this can someone help?

Do not use the "LEFT OUTER JOIN" ANSI syntax in your CREATE MATERIALIZED VIEW definition.
Specify

FROM indiv i,indivcoding c, broker brk, corporat r
WHERE brk.brkno(+) = c.brkno
AND c.ncmpcode(+) = r.cmpcode

FROM indiv i,indivcoding c, broker brk, corporat r
WHERE c.brkno = brk.brkno(+)
AND r.ncmpcode = c.cmpcode(+)

(I find it more readable).

Hemant K Collette

Tags: Database

Similar Questions

Create materialized view
Hello
I found that when oracle executes the create materialized view statement it must be longer than the duration of execution of the actual query.
I do an IMMEDIATE CONSTRUCTION.
Is there a reason for this?

For example. the query in the create statement took 25 minutes and did not create the MV for 2 hours.
The following query, which took 10 seconds was not created during more than 11 minutes and is still ongoing.
So I want to know what the reason is behind this? pls share if you know... Thank you.

PS:
I have advice in the select query. Oracle uses it advice during the creation of MV too or is this the reason why it's taking the time to build the MV?

any suggestion is appreciated. thnks!

Published by: user254668 on January 11, 2011 08:08
How do measure you queries?

http://jonathanlewis.WordPress.com/2010/08/29/fair-comparison/

Re: Question Performace and Order by
Re: receiving ORA-01722 invalid number mistake while creating a materialized view
Re: long term with ORDER by clause
Re: Improve the performance of the query with the order of

'Invalid metadata objects' when creating materialized views

Hi experts,

I ran into some trouble. I had an analytic workspace that has grown too quickly (see 11.2.0.2 size AW grows regularly with each generation of cube so I deleted and created a new.)

He seemed to do very well with the tip David Greenfield, gave us in the mentioned forum post, but when I try to activate materialized views (that I had activated in the previous workspace) I am gettig the following error:

-----
Your metadata changes have been saved, with the following errors
Invalid metadata objects:
Invalid object "TABLESPACE. LECTURAS': 'CREATE A MATERIALIZED VIEW 'TABLESPACE' '. "CB$ LECTURAS.
ORGANIZATION OF CUBE ON THE TABLESPACE. () TABLESPACE_AW
MADE "LECTURAS_STORED"("LECTURAS_MEASURE_DIM" "LECTURA") IS "LECTURA"
DIMENSION "TIEMPO" IS "TIEMPO", WITH THE HELP OF "TIEMPO_TIEMPO_HOUR_ID_UNIQUE_KEY."
DIMENSION 'GEOGRAPHY' IS 'GEOGRAPHY' WITH THE HELP OF 'GEOGRAFIA_GEOGRAFIA_CONTADOR_ID_UNIQUE_KEY')
POSTPONED BUILD
UPDATE ON REQUEST
FORCE
WITH THE HELP OF CONSTRAINTS OF TRUST
AS
(
SELECT
TO_CHAR (T1." FEC_LECTURA', "dd/mm/yyyy hh24:mi:ss") "TIEMPO"
T1. "" COD_METERID ""GEOGRAPHY. "
SUM (T1." VAL_AI_HOR') "LECTURA".
Of
TABLESPACE. "' LECTURA_HORARIA_FINAL ' T1
GROUP BY
(TO_CHAR (T1." (FEC_LECTURA"," hh24:mi:ss dd/mm/yyyy '), T1. ("' COD_METERID")
)
ORA-00942: table or view does not exist
"
-----

This same script running in SQLDeveloper gives the same error in line 17, which is the FROM clause. BUT I can run the select by itself and returns the expected result. If the table exists in the correct storage space.

I must be missing something big...

Thanks in advance.

Joan

P.S.: In the above code I use 'SPACE' to replace the real name from username and a tablespace (which is the same) for reasons of confidentiality.

When you run the select statement, you connect to the same user you are trying to activate the VM?

You can create a standard (No cube) MV with the same select statement? (Connected to the same user that you used in AWM).

"CREATE MATERIALIZED VIEW "TABLESPACE"."MV_TEST"
  BUILD DEFERRED
  REFRESH ON DEMAND
  FORCE
  USING TRUSTED CONSTRAINTS
AS
(
  SELECT
   TO_CHAR(T1."FEC_LECTURA", 'dd/mm/yyyy hh24:mi:ss') "TIEMPO",
   T1."COD_METERID" "GEOGRAFIA",
   SUM(T1."VAL_AI_HOR") "LECTURA"
  FROM
   TABLESPACE."LECTURA_HORARIA_FINAL" T1
  GROUP BY
   (TO_CHAR(T1."FEC_LECTURA", 'dd/mm/yyyy hh24:mi:ss') , T1."COD_METERID")
)
{code}

Create Materialized view and Materialized view log.

I wanted to create a materialized view with option "REFRESH QUICKLY YOU COMMIT".
(1) table 1 - it is partitioned range + list - added primary key
(2) View1 - having primary keys on the base table of view
Steps to follow:
(1) create the materialized on Table1; view journal -primary key by default
(2) create the materialized on view1 view log. -It gives below error.
ORA-00942: table or view does not exist
I wanted to create Materialized view as below
create a materialized view
Quickly REFRESH ON validation
as
Select...
........
... from table1
where c1 (select c1 from View1 which...);

Question:
(1) because I am getting above error when creating journal of MV on the view. Can one create log view MV or we create a MV newspaper on the base table of view?
(2) to create the MV with "REFRESH QUICKLY YOU COMMIT' option, we need to have the primary key on the main tables?

Pointers on this will be really useful.

Thank you
Prasad

"When a materialized view is maintained by the ON COMMIT method, the time required to perform the validation can be slightly longer than usual." This is because the refresh operation is performed as part of the validation process. This is why this method may not be suitable if many users at the same time change the tables on which is based the materialized view. »

See: basis of materialized views (refreshment options) for all the other options and how they work.

create materialized view log on the table without a primary key

Hi all

CREATE TABLE client_months 
(
  SUBJ_CODE         NUMBER(4),
  SERV_CODE         NUMBER(4),
  DEBIT_CODE        NUMBER(4),
  PERIOD_NUM        NUMBER(2),
  PERIOD_NAME       VARCHAR2(40 CHAR),
  FIRST_MON_DAY     DATE,
  LAST_MON_DAY      DATE,
  VALUE_MON_DAY     DATE,
  MONTHES           NUMBER(4,2),
  GARDENING_WEIGHT  NUMBER(5,4),
  REASON_CODE       NUMBER(5),
  STAMP_ACTION      VARCHAR2(1 CHAR),
  STAMP_CDATE       DATE                        DEFAULT SYSDATE,
  STAMP_DATE        DATE,
  STAMP_USER        VARCHAR2(15 CHAR),
  REGION_CODE       NUMBER(9)
)
table created.

CREATE UNIQUE INDEX client_months_UK  ON client_months 
(SUBJ_CODE, SERV_CODE, DEBIT_CODE, PERIOD_NUM, REGION_CODE)
index created.

CREATE MATERIALIZED VIEW LOG ON client_months with rowid;

CREATE MATERIALIZED VIEW client_months_mv 
BUILD immediate 
REFRESH FAST ON COMMIT 
AS 
SELECT * FROM client_months;

ORA-12014: table 'CLIENT_MONTHS' does not contain a primary key constraint

I don't want to refresh the mview when validation is performed on the base table.
And I don't want to change the base table by adding a primary key.

is it possible to create the mview journal using the unique index? or another solution?
Please help
Thanks in advance
Naama

Naamas wrote:
No,
I already read this post!

Then you read wrong:

SQL> CREATE TABLE client_months
  2  (
  3    SUBJ_CODE         NUMBER(4),
  4    SERV_CODE         NUMBER(4),
  5    DEBIT_CODE        NUMBER(4),
  6    PERIOD_NUM        NUMBER(2),
  7    PERIOD_NAME       VARCHAR2(40 CHAR),
  8    FIRST_MON_DAY     DATE,
  9    LAST_MON_DAY      DATE,
 10    VALUE_MON_DAY     DATE,
 11    MONTHES           NUMBER(4,2),
 12    GARDENING_WEIGHT  NUMBER(5,4),
 13    REASON_CODE       NUMBER(5),
 14    STAMP_ACTION      VARCHAR2(1 CHAR),
 15    STAMP_CDATE       DATE                        DEFAULT SYSDATE,
 16    STAMP_DATE        DATE,
 17    STAMP_USER        VARCHAR2(15 CHAR),
 18    REGION_CODE       NUMBER(9)
 19  )
 20  /

Table created.

SQL> CREATE UNIQUE INDEX client_months_UK  ON client_months
  2  (SUBJ_CODE, SERV_CODE, DEBIT_CODE, PERIOD_NUM, REGION_CODE)
  3  /

Index created.

SQL> CREATE MATERIALIZED VIEW LOG ON client_months with rowid
  2  /

Materialized view log created.

SQL> CREATE MATERIALIZED VIEW client_months_mv
  2  BUILD immediate
  3  REFRESH FAST WITH ROWID ON COMMIT -- pay attention to WITH ROWID
  4  AS
  5  SELECT * FROM client_months
  6  /

Materialized view created.

SQL>

SY.

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}

Bug: Cannot create materialized view log on XE 11 G
Hello

I connect as try and HR user create materialized view log
```
CREATE MATERIALIZED VIEW LOG ON HR.EMPLOYEES;
```
I get the error
>
Error from the 1 in the command line:
CREATE LOG VIEW MATERIALIZED ON HUMAN RESOURCES. EMPLOYEES
Error in the command line: 1 column: 0
Error report:
SQL error: ORA-00439: feature not enabled not: Advanced replication
00439 00000 - "function not enabled: %s."
* Cause: The specified feature is not enabled.
* Action: Try not to use this feature.
>

You can create a materialized view log on 10G XE with no problems.

Kind regards
Jari

http://dbswh.webhop.NET/dbswh/f?p=blog:Home:0
Is this a bug in 11g or 10g?

It was reported earlier in the beta forum now archived. {: identifier of the thread = 2214092}

The current doc lists the MV sites only (and 'No' to the function of replication advanced):
http://download.Oracle.com/docs/CD/E17781_01/license.112/e18068/TOC.htm#BABDFDAI

Create Materialized View ORA-01723: columns of length zero are not allowed
I am trying to create a materialized view that derives from a column of a function and I get: ORA-01723: columns null are not allowed.

I use 10 gr 2 with the following definition (simple version):

CREATE MATERIALIZED VIEW ACES
SELECT
function_name (column_name) alias_de_colonne
FROM table_name;

I even tried to cast it as below:

CREATE MATERIALIZED VIEW ACES
SELECT
Cast (function_name (column_name) AS VARCHAR2 (200)) alias_de_colonne
FROM table_name;

My function has an exception to return a value, even if no value are.

I looked everywhere for the solution. Someone at - there a way around this problem? I really need my function to calculate the column because it has business rules that I can't join in my definition of the materialized view. My only hope around this is to insert values into a table and then create a materialized table view, I don't want to do that if someone has a solution around this.

Any help would be greatly appreciated.

Thank you

Kyle

Published by: Kyle Miller on April 19, 2011 08:28
Have you tried to create a table with the correct structure and then by creating the view materialized, based on the predefined table as described here...

http://www.oaktable.NET/content/ultra-fast-MV-alteration-using-prebuilt-table-option

?

See you soon

Ben

With as subquery block in create MATERIALIZED view or bulk pl/sql

Hi all

Can I use the with as subquery block in create MATERIALIZED view?

or in pl/sql

-Thank you

Published by: xwo0owx on March 31, 2011 11:23

Published by: xwo0owx on March 31, 2011 11:23

Have you tried to test it? :)

SQL > SELECT * FROM V$VERSION;

BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
PL/SQL Release 11.2.0.2.0 - Production
CORE    11.2.0.2.0      Production
TNS for 32-bit Windows: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production

SQL > CREATE VIEW TEST_VIEW
  2  AS
  3  WITH d AS
  4  (
  5          SELECT * FROM DUAL
  6  )
  7  SELECT *
  8  FROM   d
  9  ;

View created.

SQL > SELECT * FROM test_view;

D
-
X

SQL > DECLARE
  2          x DUAL.DUMMY%TYPE;
  3  BEGIN
  4          WITH d AS
  5          (
  6                  SELECT * FROM DUAL
  7          )
  8          SELECT dummy
  9          INTO   x
 10          FROM   d
 11          ;
 12
 13          DBMS_OUTPUT.PUT_LINE(x);
 14  END;
 15  /
X

PL/SQL procedure successfully completed.

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

ORA-00907 is missing a closing parenthesis in the value
Hi all

I am writing code for a table, the value type, but is ORA-00907 missing right parenthesis at the opening of the LOV in the window to submit competing demand.
The internal code of the defined value is as follows:

Table:_ gl_ledgers_public_all_v gl, gl_ledgers lg, gl_ledger_configurations lc

Columns in the table:_
Value: gl.name
ID: gl.ledger_id

Où :_
```
WHERE gl.ledger_id = lg.ledger_id 
      AND lg.configuration_id = lc.configuration_id 
      AND :$FLEX$.FND_MO_REPORTING_LEVEL='1000'
UNION ALL
SELECT name, organization_id
   FROM hr_operating_units
   WHERE :$FLEX$.FND_MO_REPORTING_LEVEL='3000'
```
Where FND_MO_REPORTING_LEVEL is a value which returns Char and is used by a previous setting.

I looked around for the triggers of this error (misuse apostrophes, questions of subquery...) but nothing in my case. Can someone check to see what could be the cause of this error? Thanks in advance.
Oops!
It looks like we can't use UNION / GROUP BY / SEEN in value sets' where clause article, as it implecitly by adding parentheses.
Of http://docs.oracle.com/cd/A60725_05/pdf/flex.pdf

Special treatment for WHERE the Clauses
Behind the scenes, the flexfield adds one and... clause in the WHERE clause that you set for your table validated set of values.
If your WHERE clause contains a RC, then the seal in the annex AND clause may not apply to your WHERE clause integer (without the brackets).
and could not get the desired result.
Then, flexfields put implicitly parentheses around your WHERE clause.

http://docs.Oracle.com/CD/A60725_05/HTML/comnls/us/FND/fndffm03.htm

Of http://docs.oracle.com/cd/E18727_01/doc.121/e12892/T354897T361276.htm
You can create a view with the UNION and use it in the set of values.
(Or) you will need to have an internal selection in the field of the table itself.

By
VAMSi

Create materialized view at the trigger.

Hello
I use version below:
Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
PL/SQL Release 11.2.0.1.0 - Production
I created a materialized view query below:
CREATE THE FSG1_FUND000 MATERIALIZED VIEW
PCTUSED, PCTFREE 5 70
Users TABLESPACE
STORAGE (INITIAL 500K NEXT 500K)
Refresh a start fast with (sysdate) next (sysdate + (1 / 1440))
WITH rowid
AS
SELECT * FROM ABNDEV_T24. FSG1_FUND000@abndev;
This Mview if any insert or update only (WITHOUT DELETING) are coming which should be copy to another table. But in mView trigger does not work.
So pls advice me no alternative.
Querys trigger:
create or replace trigger trg_dummy
after insert or update on FSG1_FUND000
for each line
Start
If the insertion
insert into FSG1_FUND001 (RECID, XMLRECORD) values (: new.) RECID,: new. XMLRECORD);
elsif update then
insert into FSG1_FUND001 (RECID, XMLRECORD) values (: new.) RECID,: new. XMLRECORD);
end if;
end;
/
Kind regards
Villa

Hello

I learned and referred website as much as we can not able to create a trigger in MView (sorry we create trigger but none use of creation because in view no insert and update happened). So I drop completely the materialized view concepts and relaxation.

Instead of, I have using the procedure to insert records in a table and then I created one by dbms_scheduler job.

This discussion will be useful for any future reference.

-procedure-

create or replace procedure p2

as

Start

INSERT / * + APPEND * / INTO FSG1_FUND000 SELECT * FROM FSG1_FUND000@remote;

End; BluShadow

/

-----------------job--------------------

Begin

DBMS_SCHEDULER. () CREATE_JOB

job_name-online "JOB4."

job_type-online "PLSQL_BLOCK."

JOB_ACTION => ' BEGIN p2; END;',

start_date => SYSDATE,

repeat_interval => ' FREQ = MINUTELY; INTERVAL = 5;',

End_date => NULL,

-Online TRUE, enabled

comments => "Inserting a record in a table");

end;

/

missing closing parenthesis when creating foreign key

Schema1.Table1 ALTER TABLE ADD (CONSTRAINT test_FK
FOREIGN KEY (test)
REFERENCES schema1.table2 (test)
USING INDEX TABLESPACE indextb);
With the HELP of INDEX TABLESPACE indextb)
*
ERROR on line 4:
ORA-00907: lack of right parenthesis
Please help, I tried several times. But I still get the same error

Delete the TABLESPACE of INDEX clause to HELP. It is not valid here.

Create a foreign key does not implicitly create an index. Since there is no index, there is no tablespace to worry. As a general rule, you don't want to create an index to support the how foreign key constraint there a sense perhaps specify a tablespace.

Justin

Missing a closing parenthesis in the creation of these paintings

Hi, I'm trying to create two tables below 10, those are the two that I can't understand what's wrong with.
Thanks for any help in advance
CREATE TABLE (BIKES
KEY ELEMENTARY SCHOOL/BIKE_ID NUMBER (4)
BIKE_MODEL VARCHAR2 (20).
BIKE_CLASS VARCHAR2 (20).
BIKE_SIZE varchar2 (4).
BIKE_TYPE VARCHAR2 (10),
DATE OF BIKE_PURCHASE_DATE,
BIKE_PURCHASE_PRICE VARCHAR2 (6).
DATE OF BIKE_SALE_DATE,
NUMBER OF DEALER_ID (4),
BIKE_SALE_PRICE VARCHAR2 (6).
MANU_ID NUMBER 4,
CONSTRAINT FK_DEALER_ID FOREIGN KEY (DEALER_ID) REFERS TO DEALER (DEALER_ID)
CONSTRAINT FK_MANU_ID_2 FOREIGN KEY (MANU_ID) REFERS TO MANUFACTURER (MANU_ID)
);
also
create table RENTALS)
KEY ELEMENTARY/RENTAL_ID NUMBER (4)
CUSTOMER_ID NUMBER 4,
NUMBER OF BIKE_ID (4),
RENTAL_TIMEOUT VARCHAR2 (5).
RENTAL_TIMEIN VARCHAR2 (5).
RENTAL_TIMEACTUAL VARCHAR2 (5).
RENTAL_COST VARCHAR2 (7).
EMPLOYEE_ID NUMBER 4,
CONSTRAINT FK_CUSTOMER_ID FOREIGN KEY (CUSTOMER_ID) REFERS TO CUSTOMER (CUSTOMER_ID),
CONSTRAINT FK_BIKE_ID FOREIGN KEY (BIKE_ID) REFERS TO BIKES (BIKE_ID),
CONSTRAINT FK_EMPLOYEE_ID_3 FOREIGN KEY (EMPLOYE_ID) REFERS TO EMPLOYEE (EMPLOYEE_ID)
);

On the first missing a comma after '... REFERENCES DEALER (DEALER_ID).

The second is because one has failed.

Node Firmula is missing a closing parenthesis

The code following the formula node

If (Res == 'Full')
{
MS1 = 0;
MS2 = 0;
McStep = 1;
}

Generates this error.

Error on line 1 is marked by a character ' # ': "if (Res == # 'Full') {MS1 = 0;". M '.

RES is a digital Cntrol with the properties of the Enum.

It is not obvious to me why this code produces a right parenthesis miiising error. What does take to eliminate this error?

Howard

Is not to complain about this parenthesis, it is complaing to "Full". You need to compare the number. Of course, you could code in LabVIEW instead of a node thus forumla.

is missing a closing parenthesis in create materialized view statement

Similar Questions

Maybe you are looking for