Creating a discount on commit Materialized view

Similar Questions

• How to create a complex organization Index Materialized View example

  Hello
  
  I have a database 11g that I'm trying to create a complex Materialized View I would make organization Index? How can I specify that I want for a primary key?
  CREATE THE RCS_STG MATERIALIZED VIEW. MV_NEXT_HOP_iot
  INDEX OF THE ORGANIZATION
  AS
  SELECT r1.resource_key, resource_key2, r2.resource_full_path_name, device_name, r2.resource_key, device_model,.
  service_telephone_number, service_package_name, telephone_number.telephone_number_key, c1.created_on
  OF network_resource r1 PARTITION (network_resource_subinterface).
  connection c1,
  network_resource r2 PARTITION (network_resource_subinterface),
  device d1,
  tn_network_resource,
  telephone_number
  WHERE r1.resource_key = c1.resource1_key
  AND c1.resource2_key = r2.resource_key
  AND d1.device_key = r2.device_key
  AND tn_network_resource.resource_key (+) = r2.resource_key
  AND telephone_number.telephone_number_key (+) = tn_network_resource.telephone_number_key
  UNION ALL
  SELECT r2.resource_key, resource_key2, r1.resource_full_path_name, device_name, r1.resource_key, device_model,.
  service_telephone_number, service_package_name, telephone_number.telephone_number_key, c1.created_on
  OF network_resource r1 PARTITION (network_resource_subinterface).
  connection c1,
  network_resource r2 PARTITION (network_resource_subinterface),
  device d1,
  tn_network_resource,
  telephone_number
  WHERE r1.resource_key = c1.resource1_key
  AND c1.resource2_key = r2.resource_key
  AND d1.device_key = r1.device_key
  AND tn_network_resource.resource_key (+) = r1.resource_key
  AND telephone_number.telephone_number_key (+) = tn_network_resource.telephone_number_key
  /
  
  I get an error ORA-25175: no PRIMARY KEY constraint found
  
  I want to say resource_key, resource_key2, and service_telephone_number as my primary key?

  user12002352 wrote:
  I'm not sure I understand your example.

  Should I do a create table iot_example in select * from 'my query above.

  Would not you other placed in front of the game that you are now (unless you can ETG and specify the index of the Organization, which I think is not the case).

  You know the query and the types of data required for the materialized view, you try to create it now. You know you want it impose a primary key constraint.

  Take this knowledge and create the table you normally create a table (columns, constraints, etc...) as I showed in my example. And then post your order to create materialized view as you now except use the syntax I have demonstrated to make use of the existing index organized table.

• Pivot can be used in fast refresh materialized view?

  Hi, I have a question about materialized view nested mode fast refresh on Oracle 11 g (It support function of pivot, but oracle 10 g doesn't support).
  
  When I created, he throws "ORA-12015: cannot create a view fast refresh materialized by a complex query.
  Then I used dbms_mview.explain_mview to see reason, and it tell me the following
  REFRESH_FAST_AFTER_INSERT ' view inline or subquery in LIST not supported for this type of MV.
  
  Can someone help me, any suggestions will be appreciated
  

  create table empX as select * from scott.emp;
  alter table empX add constraint PK_empX_empno primary key (empno);
  
  --drop  MATERIALIZED VIEW LOG ON empX;
  CREATE MATERIALIZED VIEW LOG ON empX with rowid, sequence(empno);
  
  --drop MATERIALIZED VIEW mv_empX;
  CREATE MATERIALIZED VIEW mv_empX
  REFRESH FAST START WITH SYSDATE
  NEXT  SYSDATE + 1/1440
  AS   
    select * from
    (
     select rowid emp_rowid, deptno, job, sal from empX
    )
    PIVOT( max(sal) for job IN ('ANALYST' job1, 'CLERK' job2, 'MANAGER' job3));
   
  --select * from mv_capabilities_table
  declare
    lv_sqltext varchar2(4000);
  begin
    execute immediate 'truncate table mv_capabilities_table';
    lv_sqltext := 'select * from
    (
     select deptno, job, sal from empX
    )
    PIVOT( max(sal) for job IN (''ANALYST'' job1, ''CLERK'' job2, ''MANAGER'' job3))
    ';  
    dbms_mview.explain_mview(lv_sqltext,'nested=>TRUE');
    commit;
  end;
  /

  Let me help you...
  I have done following and it run/view updated because I just replaced quickly with a complete word, because there are limitations for quickly updatable views:

  SQL> show user;
  USER is "SCOTT"
  SQL> create table empX as select * from scott.emp;
  
  Table created.
  
  SQL> alter table empX add constraint PK_empX_empno primary key (empno);
  
  Table altered.
  
  SQL>
  SQL> --drop  MATERIALIZED VIEW LOG ON empX;
  SQL> CREATE MATERIALIZED VIEW LOG ON empX with rowid, sequence(empno);
  
  Materialized view log created.
  
  SQL>
  SQL> --drop MATERIALIZED VIEW mv_empX;
  SQL> CREATE MATERIALIZED VIEW mv_empX
    2  REFRESH COMPLETE WITH rowid
    3  START WITH sysdate
    4  NEXT  SYSDATE + 1/1440
    5  AS
    6    select * from
    7    (
    8     select rowid emp_rowid, deptno, job, sal from empX
    9    )
   10    PIVOT( max(sal) for job IN ('ANALYST' job1, 'CLERK' job2, 'MANAGER' job3));
  
  Materialized view created.
  
  SQL> select * from mv_empx;
  
  EMP_ROWID              DEPTNO       JOB1       JOB2       JOB3
  ------------------ ---------- ---------- ---------- ----------
  AAAShcAAEAAAATTAAN         10                  1300
  AAAShcAAEAAAATTAAE         30
  AAAShcAAEAAAATTAAJ         30
  AAAShcAAEAAAATTAAC         30
  AAAShcAAEAAAATTAAA         20                   800
  AAAShcAAEAAAATTAAK         20                  1100
  AAAShcAAEAAAATTAAM         20       3000
  AAAShcAAEAAAATTAAD         20                             2975
  AAAShcAAEAAAATTAAB         30
  AAAShcAAEAAAATTAAI         10
  AAAShcAAEAAAATTAAL         30                   950
  
  EMP_ROWID              DEPTNO       JOB1       JOB2       JOB3
  ------------------ ---------- ---------- ---------- ----------
  AAAShcAAEAAAATTAAF         30                             2850
  AAAShcAAEAAAATTAAG         10                             2450
  AAAShcAAEAAAATTAAH         20       3000
  
  14 rows selected.
  
  SQL> begin
    2  dbms_mview.refresh('SCOTT.mv_empx');
    3  end;
    4  /
  
  PL/SQL procedure successfully completed.
  
  SQL> select * from mv_empx;
  
  EMP_ROWID              DEPTNO       JOB1       JOB2       JOB3
  ------------------ ---------- ---------- ---------- ----------
  AAAShcAAEAAAATTAAN         10                  1300
  AAAShcAAEAAAATTAAE         30
  AAAShcAAEAAAATTAAJ         30
  AAAShcAAEAAAATTAAC         30
  AAAShcAAEAAAATTAAA         20                   800
  AAAShcAAEAAAATTAAK         20                  1100
  AAAShcAAEAAAATTAAM         20       3000
  AAAShcAAEAAAATTAAD         20                             2975
  AAAShcAAEAAAATTAAB         30
  AAAShcAAEAAAATTAAI         10
  AAAShcAAEAAAATTAAL         30                   950
  
  EMP_ROWID              DEPTNO       JOB1       JOB2       JOB3
  ------------------ ---------- ---------- ---------- ----------
  AAAShcAAEAAAATTAAF         30                             2850
  AAAShcAAEAAAATTAAG         10                             2450
  AAAShcAAEAAAATTAAH         20       3000
  
  14 rows selected.
  
  SQL>
  

  So, the answer is Yes, we can use Pivot with Materialized view but:
  1 MV must be full refresh.
  2 oracle version should be 11 g; of course the pivot is available in Oracle 11 g.

  If this answers your question, please close the message, otherwise continue.

  These links may also be of interest:
  http://docs.Oracle.com/CD/B28359_01/server.111/b28313/basicmv.htm#i1007028
  http://docs.Oracle.com/CD/B28359_01/server.111/b28313/basicmv.htm#i1007007

  http://rwijk.blogspot.in/2009/06/fast-refreshable-MATERIALIZED-view.html

  And:

  Please see if (Note: 179466.1 - view to fast refresh materialized diagnose ORA-12015 / complex queries) help.

  Concerning
  Girish Sharma

• A fall of materialized views

  If you delete a view, materialized, all dependent on the view fell becomes invalidated.
  
  It is: when you recreate this material point of view dependent invalidated it gets recompiled/re-validated or need to recompile views dependent on the material?
  
  Reason I ask that is that most of the DROP statements indicate that happens when you re-create the object fell, but materialized views DROP statement does not work.

  Hello;

  You will have to recompile the dependent views.

  Best regards

  mseberg

• Refresh materialized views

  Hi all
  
  I created a procedure to refresh materialized views:
  
  create or replace procedure refresh_MV1 is
  Start
  dbms_mview. Refresh('Materialized_view_1','C')
  exception
  while others then
  INSERT into tablelog_mv (sysdate, 'Materialized_view_1', substr(sqlerrm,1,200));
  end;
  When I run run this procedurev (exec refresh_MV1), I am getting following error:
  
  due to: ORA-12018: following error occurred during the generation of code for "ISGCOS". «Materialized_view_1 "ORA-00942: table or view is no ORA-00942: table or view does not exist»
  
  But if I run anonymously without creating a procedure as below, it works very well and the matte view gets updated:
  
  Start
  dbms_mview. Refresh('Materialized_view_1','C')
  exception
  while others then
  INSERT into tablelog_mv (sysdate, 'Materialized_view_1', substr(sqlerrm,1,200));
  end;
  
  I couldn't understand what could be the problem?
  
  Thank you
  Chrystelle

  Privileges on tables and views must be granted directly to the user when they are referenced in the procedures. Grants to the roles will not work.

  Most likely your username has been granted privileges via a role

  grant all on Materialized_view_1 to myRole;
  grant myRole to myUser; -- this won't give you the privileges in a procedure
  

  You have the privileges directly

  grant all on Materialized_view_1 to myUser
  

• 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.

• Failed to create the fast refresh on the materialized view

  Hi, I am creating a materialized on the tables with fast refresh view on commit but I get an error message.

  I have created the following logs:

  Bonus CREATE MATERIALIZED VIEW LOG ON
  Users TABLESPACE
  WITH THE PRIMARY KEY
  INCLUDING THE NEW VALUES

  Used to CREATE MATERIALIZED VIEW LOG ON
  Users TABLESPACE
  WITH THE PRIMARY KEY
  INCLUDING THE NEW VALUES

  I then try to create the following:

  Test.BAM CREATE MATERIALIZED VIEW

  IMMEDIATE CONSTRUCTION
  COOL OFF QUICKLY ON COMMIT
  AS
  SELECT a.dept_no, SUM (a.salary)
  EMPLOYEE a, b bonus
  WHERE a.employee_id = b.employee_id
  GROUP BY dept_no

  When I do that, I get the following error:

  . ORA-12032: cannot use column rowid of materialized

  view log on 'test '. "" BONUS ".

  If I change to a full refresh, it works pretty well. If I create a MV with a fast refresh on a query just within the limits of the table bonus it also works very well, for example ' select * bonus where employee_id = 2'

  What I am doing wrong? Also when looking at the notes for MV connects in some places, he said using the primary key and others, he says to the sequence of use and row_id. Which is correct and what difference does it make?

  11.2 aix.

  Thank you very much

  I suggest that investigate you the reason why your MV is not quickly updatable with the following method:

  (1) create MV_CAPABILITIES_TABLE with @?/rdbms/admin/utlxmv.sql

  (2) exec ('BAM') dbms_mview.explain_mview

  3)

  column format a100 msgtxt

  column related_text format a20

  SELECT the possible, capability_name, related_text,

  msgtxt

  OF mv_capabilities_table;

  That should tell you the reason why he isn't yet quickly updatable.

  There was a popular quote on men and fishing, but I don't remember it for now :-)

  Kind regards

  Uwe Hesse

• 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.

• Refresh the Materialized View constructed from an external table commit?

  Is it possible to create a materialized with Refresh view on commit built from an external table?
  
  I think the answer is "no, because there is no way for the outer table report to the view materialized it has been changed," but I would like to be sure before I tell my client who has requested the opportunity to do this (or, Alternatively, to learn how Oracle hoops I have to cross in order to operate).
  
  I can create a Refresh on demand, it is not a question of not having the necessary permissions to create the materialized view itself.

  No, you can't. The outer table is not modified in a transactional way and there no materialized view logs, so there is no event to hang in and no delta to apply.

  However, you can use dbms_scheduler observer file that will ask for the presence of a file and load the data in a table or refresh a materialized view based on the external table.

  Justin

• 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
  

  OR

  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

• 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;

  /

• Error ORA-01115 creating the materialized view

  Hi friends,

  When I create a materialized view it by throwing some error

  CREATE THE PNR_RES_MV MATERIALIZED VIEW
  TABLESPACE FAS
  NOCACHE
  LOGGING
  NOCOMPRESS
  NOPARALLEL
  IMMEDIATE CONSTRUCTION
  REFRESH THE STRENGTH TO DEMAND
  WITH THE PRIMARY KEY
  AS
  SELECT C_CREATION_DATE, C_PNR, B.CARRIER_CD1, B.CARRIER_CD2, B.CURRENT_STATUS_CD, A.CANCELLED_IND, A.BOOKING_OFFC_NMBR,-, B.LEG_NMBR, C_PAX_NMBR
  COUNT (CASE WHEN TRIM (B.CURRENT_STATUS_CD) = "HK" AND (TRIM (C_CHANGE_OR_CANCELL_IND) = "OR C_CHANGE_OR_CANCELL_IND IS NULL) THEN 1 OTHER TRAILING NULL) CONFIRMED_COUNT,.
  COUNT (CASE WHEN (B.CURRENT_STATUS_CD) TRIM = "HK" AND (TRIM (C_CHANGE_OR_CANCELL_IND) = "or C_CHANGE_OR_CANCELL_IND IS NULL) null THEN 1 OTHER END) cancELLED_COUNT
  OF PNR_RES_LEG_PAX_MV B, PNR_RES HAS
  WHERE A.PNR = B.PNR
  AND a.CREATION_DATE = b.CREATION_DATE
  - and A.BOOKING_OFFC_NMBR = '1F'
  - AND C_PNR = 'XE76V. '
  AND A.FILE_UPDATE_DATE. A.UPDATE_DATE IN (SELECT MAX (D.FILE_UPDATE_DATE |)) (UPDATE_DATE) OF PNR_RES D WHERE D.PNR = B.PNR AND D.CREATION_DATE = B.CREATION_DATE)
  GROUP OF C_CREATION_DATE, C_PNR, B.CARRIER_CD1, B.CARRIER_CD2, B.CURRENT_STATUS_CD, A.CANCELLED_IND, A.BOOKING_OFFC_NMBR;

  
  

  
  

  When executing it it gives this error

  
  

  ORA-01115: reading block IO file error 4 (block # 63757)
  ORA-01110: data file 4: ' D:\APP\IGT\ORADATA\ORCL\USERS01. DBF'
  ORA-27070: async read/write failed
  OSD-04006: ReadFile() failure, unable to read the file
  S/O-error: (27 OS) the drive cannot find the sector requested.

  
  

  
  

  And I checked through RMAN

  RMAN > validate the audit logic datafile 4;

  From post 11 March 14
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 127 type device = DISK
  channel ORA_DISK_1: starting from the data file validation
  channel ORA_DISK_1: datafile (s) for specification validation
  Enter a number of file datafile = 00004 name = D:\APP\IGT\ORADATA\ORCL\USERS01. DBF
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure to validate the command channel ORA_DISK_1 11/03/2014 13:0
  04:12
  ORA-19501: read error on the file 'D:\APP\IGT\ORADATA\ORCL\USERS01. DBF', block numbe
  r 63745 (block size = 8192)
  ORA-27070: async read/write failed
  OSD-04016: error queuing an asynchronous i/o request.
  S/O-error: (27 OS) the drive cannot find the sector requested.

  
  

  
  

  Please suggest me what to do it is a mistake to associate related database or OS. DB version is - 11 GR 2

  
  

  Kind regards

  
  

  Arya
  

  
  

  This is the error message that you should focus:

  > O/S-error: (27 OS) the drive cannot find the sector requested.

  Run disk checker utilities, eventually the file system is damaged.

  Hemant K Collette

• Implementation of materialized view (10.2.0.5) - more than an hour to create

  A distributed query (remote several tables, several spaces), all refresh on demand. Note that I have no control over remote tables (impossible to create logs of MV, etc.) and I ask really just the difference in performance between the direct request and the MV.
  
  My MV script:
  
  CREATE MYSCHEMA MATERIALIZED VIEW. PRE-MEDICATION
  STORAGE)
  DEFAULT USER_TABLES
  DEFAULT FLASH_CACHE
  DEFAULT CELL_FLASH_CACHE
  )
  NOCACHE
  NOLOGGING
  NOCOMPRESS
  NOPARALLEL
  IMMEDIATE CONSTRUCTION
  FULL REFRESH ON DEMAND
  AS
  < my query >
  
  The query takes less than 2 seconds to turn, return of 600 lines. When you try to create the MV, I gave up after an hour. There is no index on the MV (of course, as I have not yet even created). The only hint in the query is to specify the table driven as the remote source.
  
  I did not request (I'll do it if necessary) because I'm not as interested tuning the query as I am to determine why the MV would be so ridiculously slow compared to the query itself.

  >
  The disappointing aspect of all this is that the query is essentially made of 3 tables remote (all from the same source, probably less than 1 k lines when joined to the top) and 1 local table (table of correspondence of line 37) while straight equi-joins.
  >
  Your solution is obvious.

  Create a local MV based ONLY on these 3 remote tables.

  Then create your required local MV based on this new local MV first and your local table.

  If these 3 remote lookup tables are even of the very useful by themselves and then create THREE local MVs, one for each of the remote tables.

  And build your local MV required on the three new local VM and your local table.

  You can add the MVs local to a group of refresh to refresh all at once with two approaches

  An approach fracture rule often works well especially with as small as your tables.

• '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}