Error ORA-01115 creating the materialized view

Similar Questions

• By creating the Materialized view all size changes to columns

  I'm creatine a materialized view based on the table in a different database.
  The table on which the created materialized view (database table) is to have the size of CHAR (1 byte) column. But in Materialized view this size columns showing as CHAR (3 bytes).
  
  Could u please help me.., why this is happening?
  
  Thank you
  Sachin

  Sachin thombare wrote:
  I'm creatine a materialized view based on the table in a different database.
  The table on which the created materialized view (database table) is to have the size of CHAR (1 byte) column. But in Materialized view this size columns showing as CHAR (3 bytes).

  Could u please help me.., why this is happening?

  Thank you
  Sachin

  Hello
  Do both the database involved in this have defined different character.
  If Yes, then this is a known behavior.

  Concerning
  Anurag Tibrewal.

• Error ORA-27418 creating the calendar for DBMS_SCHEDULER

  Hello world
  
  Im trying to set up a schedule for dbms_scheduler on Oracle 11 g 2 test user sys like this server:
  
  run DBMS_SCHEDULER. () CREATE_SCHEDULE
  repeat_interval = > ' FREQ = DAILY; BYHOUR = 10:30 '.
  start_date = > to_timestamp_tz ('2013-03-11 Europe/Berlin ',' YYYY-MM-DD TZR').
  schedule_name = > 'FULLBACKUP_DAILY');
  
  
  But I get an error ORA-27418 and ORA-06512:
  
  DBMS_SCHEDULER BEGIN. CREATE_SCHEDULE (repeat_interval = > ' FREQ = DAILY;) BYHOUR = 10:30 ', start_date = > to_timestamp_tz ('2013-03-11 Europe/Berlin ',' YYYY-MM-DD TZR'), schedule_name = > 'FULLBACKUP_DAILY'); END;
  
  *
  FEHLER in line 1:
  ORA-27418: Syntaxfehler in Wiederholungsintervall oder Kalender
  ORA-06512: in 'SYS. DBMS_ISCHED ', line 997 '.
  ORA-06512: in 'SYS. DBMS_SCHEDULER', line 1486
  ORA-06512: In line 1
  
  I had no right as sys to configure a scheduler or forgot to activate something?
  
  Thanks for the help!
  
  Kind regards
  David

  Hello

  Could you try following interval?

  repeat_interval => 'FREQ=DAILY;BYHOUR=10;BYMINUTE=30'
  

  Kind regards

• Re: view opaque and the materialized view

  Hi Experts,

  I want some clarification of opaque and view view in the physical layer OBIEE materialized

  -> what is the main difference between the opaque view and materialized in the RPD perspective view, we have to do this at the level of the RPD or DB.

  -> I want the list of opaque opinion and materialized in the RPD view how I should do.

  -> How opaque views will degrade the performance and how a materialized view will improve performance at the level of the report.

  -> In scenarios that we use view opaque and the view materialized (if possible with a scenario for the best permanent basis).

  Thanks in advance.

  I want some clarification of opaque and view view in the physical layer OBIEE materialized

  -> What is the main difference between opaque view and create the materialized view in the RPD point of view, we have to do this at the level of the RPD or DB.

  Opaque views is a SQL statement that is defined in the physical layer, OBIEE will use all in the construction of a SQL query. In a way it's not different from a database view, except it is set in OBIEE only. Alternatively, you can deploy an Opaque view, which pushes its definition in the database. Read more about it here: work with physical tables, Cubes and joins - 11 g Release 1 (11.1.1)

  A materialized view (MV) is a database concept where the results of a SQL statement are physicalised like a table, and therefore as OBIEE is a MV is just another physical array

  -> If I want a list of the opaque views and materialized in the RPD view how I should do.

  To find opaque views, use the function «Repository of applications» administration tool Search physical Tables and set up a filter on the Type = Select

  Screenshot: https://www.evernote.com/shard/s16/sh/5c843e47-bff1-4d4b-b847-be98f3a2ec09/cf060a6cd9805f687fa0b5b46f3f0020

  To find materialized views, you will need to query the catalog in your database (for example select object_name, object_type from user_objects where type_objet = "MATERIALIZED VIEW" ;) and compare it to the list of tables in your SPR)

  -> How opaque views will degrade the performance and how a materialized view will improve performance at the level of the report.

  A materialized view is materialized, in other words, the results are already stored in the database. This means usually there will be more efficient because all the joins and aggregations, etc. will be settled in advance.

• performance of the queries on the main tables of the materialized view vs

  Hello
  
  I'm afraid of strange behavior in db, on my paintings of master UDBMOVEMENT_ORIG (26mil.rows) and UDBIDENTDATA_ORIG (18mil.rows) is created the materialized view TMP_MS_UDB_MV (UDBMOVEMENT stands for this object) that meets certain default conditions and the join on these paintings of master condition. MV got on the lines of 12milions. I created MV for poll not so huge objects, MV got 3GB, paintings of master toghether 12 GB. But I don't understand that physical reads and becomes compatible is less on MV that on the main tables, the final execution time is shorter on the master tables. See my journal below.
  
  Why?
  
  Thanks for the replies.
  
  
  SQL > set echo on
  SQL > @flush
  SQL > alter system flush buffer_cache;
  
  Modified system.
  
  Elapsed time: 00:00:00.20
  SQL > alter system flush shared_pool;
  
  Modified system.
  
  Elapsed time: 00:00:00.65
  SQL > SELECT
  UDBMovement.zIdDevice 2, UDBMovement.sDevice, UDBMovement.zIdLocal, UDBMovement.sComputer, UDBMovement.tActionTime, UDBIdentData.sCardSubType, UDBIdentData.sCardType, UDBMovement.cEpan, UDBMovement.cText, UDBMovement.lArtRef, UDBMovement.sArtClassRef, UDBMovement.lSequenz, UDBMovement.sTransMark, UDBMovement.lBlock, UDBMovement.sTransType, UDBMovement.lGlobalID, UDBMovement.sFacility, UDBIdentData.sCardClass, UDBMovement.lSingleAmount, UDBMovement.sVAT, UDBMovement.lVATTot, UDBIdentData.tTarifTimeStart, UDBIdentData.tTarifTimeEnd, UDBIdentData.cLicensePlate, UDBIdentData.lMoneyValue, UDBIdentData.lPointValue, UDBIdentData.lTimeValue, UDBIdentData.tProdTime, UDBIdentData.tExpireDate
  UDBMOVEMENT_orig UDBMovement 3, Udbidentdata_orig UDBIdentData
  4. WHERE
  5 UDBMovement.lGlobalId = UDBIdentData.lGlobalRef (+) AND UDBMovement.sComputer = UDBIdentData.sComputer (+)
  6 AND UDBMovement.sTransType > 0 AND UDBMovement.sDevice < 1000 AND UDBMovement.sDevice > = 0 AND UDBIdentData.sCardType IN (2) AND (bitand(UDBMovement.sSaleFlag,1) = 0 AND bitand(UDBMovement.sSaleFlag,4) = 0) AND UDBMovement.sArtClassRef < 100
  7 AND UDBMovement.tActionTime > = TO_DATE (May 5, 2011 00:00:00 ',' dd/mm/yyyy hh24:mi:ss') + 0.25 AND UDBMovement.tActionTime < TO_DATE (May 5, 2011 00:00:00 ',' dd/mm/yyyy hh24:mi:ss') + 0.5
  8 ORDER BY tActionTime, lBlock, lSequenz;
  
  4947 selected lines.
  
  Elapsed time: 00:00:15.84
  
  Execution plan
  ----------------------------------------------------------
  Hash value of plan: 1768406139
  
  ------------------------------------------------------------------------------------------------------------
  | ID | Operation | Name | Lines | Bytes | TempSpc | Cost (% CPU). Time |
  ------------------------------------------------------------------------------------------------------------
  | 0 | SELECT STATEMENT | 7166 | 1238K | 20670 (1) | 00:04:09 |
  | 1. SORT ORDER BY | 7166 | 1238K | 1480K | 20670 (1) | 00:04:09 |
  | 2. NESTED LOOPS |
  | 3. NESTED LOOPS | 7166 | 1238K | 20388 (1) | 00:04:05 |
  |* 4 | TABLE ACCESS BY INDEX ROWID | UDBMOVEMENT_ORIG | 7142 | 809K | 7056 (1) | 00:01:25 |
  |* 5 | INDEX RANGE SCAN | IDX_UDBMOVARTICLE | 10709. 61 (0) | 00:00:01 |
  |* 6 | INDEX UNIQUE SCAN | UDBIDENTDATA_PRIM | 1 | | | 1 (0) | 00:00:01 |
  |* 7 | TABLE ACCESS BY INDEX ROWID | UDBIDENTDATA_ORIG | 1. 61. 2 (0) | 00:00:01 |
  ------------------------------------------------------------------------------------------------------------
  
  Information of predicates (identified by the operation identity card):
  ---------------------------------------------------
  
  4 - filter("UDBMOVEMENT".") STRANSTYPE"> 0 AND 'UDBMOVEMENT '. "" SDEVICE ' < 1000 AND
  BITAND ("SSALEFLAG", 1) = 0 AND "UDBMOVEMENT". "" SDEVICE ' > = 0 AND BITAND ("UDBMOVEMENT". "SSALEFLAG «(, 4) = 0)" "
  5 - access("UDBMOVEMENT".") TACTIONTIME' > = TO_DATE (' 2011-05-05 06:00 ',' syyyy-mm-jj)
  ('HH24:mi:SS) AND "UDBMOVEMENT". "' TACTIONTIME ', TO_DATE (' 2011-05-05 12:00 ',' syyyy-mm-jj)
  ('HH24:mi:SS) AND "UDBMOVEMENT". ("' SARTCLASSREF" < 100)
  filter ("UDBMOVEMENT". "SARTCLASSREF" < 100)
  6 - access("UDBMOVEMENT".") LGLOBALID "=" UDBIDENTDATA. " "" LGLOBALREF "AND
  'UDBMOVEMENT '. "' SCOMPUTER"="UDBIDENTDATA." ("' SCOMPUTER")
  7 - filter("UDBIDENTDATA".") SCARDTYPE "= 2)
  
  
  Statistics
  ----------------------------------------------------------
  543 recursive calls
  0 db block Gets
  84383 compatible Gets
  4485 physical reads
  0 redo size
  533990 bytes sent via SQL * Net to client
  3953 bytes received via SQL * Net from client
  331 SQL * Net back and forth to and from the client
  kinds of 86 (memory)
  0 sorts (disk)
  4947 lines processed
  
  SQL > @flush
  SQL > alter system flush buffer_cache;
  
  Modified system.
  
  Elapsed time: 00:00:00.12
  SQL > alter system flush shared_pool;
  
  Modified system.
  
  Elapsed time: 00:00:00.74
  SQL > SELECT UDBMovement.zIdDevice, UDBMovement.sDevice, UDBMovement.zIdLocal, UDBMovement.sComputer, UDBMovement.tActionTime, UDBMovement.sCardSubType, UDBMovement.sCardType, UDBMovement.cEpan, UDBMovement.cText, UDBMovement.lArtRef, UDBMovement.sArtClassRef, UDBMovement.lSequenz, UDBMovement.sTransMark, UDBMovement.lBlock, UDBMovement.sTransType, UDBMovement.lGlobalID, UDBMovement.sFacility, UDBMovement.sCardClass, UDBMovement.lSingleAmount, UDBMovement.sVAT, UDBMovement.lVATTot, UDBMovement.tTarifTimeStart, UDBMovement.tTarifTimeEnd, UDBMovement.cLicensePlate, UDBMovement.lMoneyValue, UDBMovement.lPointValue, UDBMovement.lTimeValue, UDBMovement.tProdTime
  2. OF UDBMOVEMENT WHERE
  3 UDBMovement.sTransType > 0 AND UDBMovement.sDevice < 1000 AND UDBMovement.sDevice > = 0 AND UDBMovement.sCardType IN (2) AND (bitand(UDBMovement.sSaleFlag,1) = 0 AND bitand(UDBMovement.sSaleFlag,4) = 0) AND UDBMovement.sArtClassRef < 100
  4. AND UDBMovement.tActionTime > = TO_DATE (May 5, 2011 00:00:00 ',' the hh24: mi: ss' dd/mm/yyyy) + 0.25
  5 AND UDBMovement.tActionTime < TO_DATE (May 5, 2011 00:00:00 ',' the hh24: mi: ss' dd/mm/yyyy) + 0.5 ORDER BY tActionTime, lBlock, lSequenz;
  
  4947 selected lines.
  
  Elapsed time: 00:00:26.46
  
  Execution plan
  ----------------------------------------------------------
  Hash value of plan: 3648898312
  
  -----------------------------------------------------------------------------------------------------------
  | ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time |
  -----------------------------------------------------------------------------------------------------------
  | 0 | SELECT STATEMENT | 2720 | 443K | 2812 (1) | 00:00:34 |
  | 1. SORT ORDER BY | 2720 | 443K | 2812 (1) | 00:00:34 |
  |* 2 | MAT_VIEW ACCESS BY INDEX ROWID | TMP_MS_UDB_MV | 2720 | 443K | 2811 (1) | 00:00:34 |
  |* 3 | INDEX RANGE SCAN | EEETMP_MS_ACTTIMEDEVICE | 2732 | 89 (0) | 00:00:02 |
  -----------------------------------------------------------------------------------------------------------
  
  Information of predicates (identified by the operation identity card):
  ---------------------------------------------------
  
  2 - filter("UDBMOVEMENT".") STRANSTYPE"> 0 AND BITAND ("UDBMOVEMENT". "SSALEFLAG «(, 4) = 0 AND" "
  BITAND ("SSALEFLAG", 1) = 0 AND "UDBMOVEMENT". ("' SARTCLASSREF" < 100)
  3 - access("UDBMOVEMENT".") TACTIONTIME' > = TO_DATE (' 2011-05-05 06:00 ',' syyyy-mm-jj)
  ('HH24:mi:SS) AND "UDBMOVEMENT". "" SDEVICE ' > = 0 AND "UDBMOVEMENT". ' SCARDTYPE ' = 2 AND ".
  'UDBMOVEMENT '. "" TACTIONTIME "< TO_DATE(' 2011-05-05 12:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
  'UDBMOVEMENT '. ("' SDEVICE ' < 1000)
  filter ("UDBMOVEMENT". "SCARDTYPE"= 2 AND "UDBMOVEMENT"." SDEVICE' < 1000 AND
  'UDBMOVEMENT '. ("' SDEVICE ' > = 0)
  
  
  Statistics
  ----------------------------------------------------------
  449 recursive calls
  0 db block Gets
  6090 gets coherent
  2837 physical reads
  0 redo size
  531987 bytes sent via SQL * Net to client
  3953 bytes received via SQL * Net from client
  331 SQL * Net back and forth to and from the client
  168 sorts (memory)
  0 sorts (disk)
  4947 lines processed
  
  SQL > spool off
  
  Published by: MattSk on February 4, 2013 14:20

  >
  The second query makes a full table of materialized view scan.
  >
  What you base that statement on?

  I do not see any table full scan in terms of the second query. All I see is
  >
  * 2 MAT_VIEW ACCESS BY INDEX ROWID TMP_MS_UDB_MV 2720 443K 2811 (1) 00:00:34

• 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

• Creating dynamic materialized views: insufficient Privileges?

  Hi all
  
  I am currently doing a procedure that will recreate materialized views as columns are deleted or added to a table by the selection of the user to the application level. I wrote the procedure, and it displays the correct syntax to create a materialized view. However once I pass this dynamic sql statement to be executed immediately, it fails, saying: I don't have sufficient privileges. I have sysdba grants on this user in my dev environment. What Miss me? Has it something to do with immediate execution and the privileges associated with the use that? Any help would be greatly appreciated!
  
  
  Kind regards
  TimS

  Within a stored (by default) procedure DEFINER rights, only the privileges that are granted directly to the user, not those granted through a role as SYSDBA, are available.

  -If you change the stored procedure to use the rights of the applicant, the privileges granted through a role are visible. However, this requires that the appellant, not the owner of the procedure has the permissions to create the materialized view.
  -If you grant the CREATE MATERIALIZED VIEW privilege (and all other privileges your code requires) directly to the user, which would also solve the problem.

  Justin

• ORA-12028: type of materialized view is not supported by the main site

  Hi guys!

  We face a problem these days about the materialized view.

  We have upgraded database version 9.2.0.7 directly to 10.2.0.5 (RHEL4 x 86) on the same host. Database uses the driver dg4odbc to connect with remote SQL Server 2012 through data binding called MIKSERI. Our developer team would like to have replicated SQL server table data side Oracle using the materialized view.

  They created Materialized view, but it is not at all to refresh the data. I tried to study a little bit, and whenever I try to change the view anyway I hit error:

  ORA-12028: view type is not supported by the master site materialized @ 'MIKSERI '.

  ORA-06512: at line 22

  I looked at the solutions proposed and discovered that it is maybe the compatible database parameter, so I changed from previous 9.2.0.0.0 to 10.2.0.1.0 but still no luck. Just to emphasize this database is of course different clone of production to a different database, with db name retained and other parameters, but on another host computer and listening port. I even try to change global name, but still no luck.

  Main problem is that refresh the work does not at all. To be more precise, we have created MV on the side of the Oracle and FULL Refresh should be done every 3 minutes. MV uses HS db link to the sql server database. During the creation of MV, we can see currently given to sql server, but the problem is that we cannot do MV to refresh every 3 minutes. When I try to change MV and put the refresh interval I get above error.

  Any kind of help would be greatly appreciated,

  Thank you

  I found the reason why my MV update jobs failed, job_queue_processes parameter was equal to 0. I change this setting and now works fine.

  Thank you for your time!

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

• The Materialized View - ORA-12052: is unable to fast refresh materialized view

  Hello

  I was hitting my head all day trying to create materialized views. I have made some progress, but have hit a brick wall, unfortunately!

  Basically, I have been invited to take a view and see if I can get the benefits of performance by transforming all or part of it in materialized views. Because the underlying tables of the config is updated quite frequently, I want to fast refresh materialized views on commit. However, when I try to create a materialized view containing an outer join in an aggregated materialized view table, I get ORA-12052: is unable to fast refresh materialized view.

  I went through the documentation and also Rob van Wijkvery useful series of blogs on the topic (especially http://rwijk.blogspot.co.uk/2009/09/fast-refreshable-materialized-view.html) but have not found anything that matches. Maybe I missed something somewhere along the line, or maybe I'm asking just something completely impossible?

  My db is 11.2.0.2.

  Here's the test scripts, I've worked with that:

  drop materialized view test1_test2_mv;
  Drop materialized view test2 journal;
  drop table test2;
  Drop materialized view test1_mv newspaper;
  drop materialized view test1_mv;
  Drop materialized view test1 journal;
  drop table test1;

  create table test1 (identification number,
  type varchar2 (10),
  number of Val,
  update_time date,
  constraint t1_pk primary key (id, type, val));
  
  Insert into test1
  Select 1, 'a', 1001, sysdate - 10/24 Union double all the
  Select 1, 'b', 1003, sysdate - 9/24 Union double all the
  Select 1, 'c', 1002, sysdate - 8/24 Union double all the
  Select 1, had ', 1004, sysdate - 7/24 Union double all the
  Select 1, 'e', 1005, sysdate - 6/24 Union double all the
  Select 1, 'c', 1006, sysdate - 5/24 Union double all the
  Select 2, 'a', 1002, sysdate - 4/24 Union double all the
  Select 2, 'b', 1005, sysdate - 3/24 Union double all the
  Select 3, 'a', 1001, sysdate - 2/24 Union double all the
  Select 3, 'c', 1006, sysdate - 1/24 Union double all the
  Select 3, 'e', 1008, sysdate - 2/24 Union double all the
  Select option 4, has ', 1004, sysdate - 3/24 Union double all the
  Select 5, 'b', 1002, sysdate - 4/24 Union double all the
  Select 5, 'g', 1001, sysdate - 5/24 Union double all the
  Select 6, 'h', 1004, sysdate - 6/24 Union double all the
  Select 7, 'b', 1007, sysdate - 7/24 Union double all the
  Select 7, had ', 1001, sysdate - 8/24 double;

  commit;

  Select * from test1;

  
  CREATE MATERIALIZED VIEW LOG ON test1
  WITH rowid, primary key (update_time)
  including the new values;

  
  Test1_mv CREATE MATERIALIZED VIEW
  IMMEDIATE CONSTRUCTION
  COOL OFF QUICKLY ON COMMIT
  Did YOU SELECT id,
  MAX (case when type = "there" end of val) THAT col_a,.
  MAX (case when type = 'b', then val end) AS col_b,.
  MAX (case when type = 'c' then end val) AS col_c,.
  MAX (case when type = ' then end of val) AS col_d,
  MAX (update_time) AS update_time
  OF test1
  WHERE TYPE in ('a',
  « b »,
  « c »,
  a ')
  GROUP BY id;

  CREATE MATERIALIZED VIEW LOG ON test1_mv
  WITH rowid
  including the new values;

  
  create table test2 (identification number,
  col2 number,
  COL3 varchar2 (10),
  number of COL4,
  constraint t2_pk primary key (id));
  
  Insert into test2
  Select 1, 1, 'bob', 1 double Union all
  Select 2, 1, "sue", 1 double Union all
  Select 3, 1, 'tom', 1 double Union all
  Select 4, 1, 'jay', 1 double Union all
  Select 5, 1, 'art', 1 double Union all
  Select 6, 1, 'kay', 1 double Union all
  Select 7, 1, 'max', 1 double Union all
  Select 8, 1, 'tim', 1 double Union all
  Select 9, 1, "liz", 1 from dual;

  commit;

  
  CREATE MATERIALIZED VIEW LOG ON test2
  WITH rowid, primary key
  including the new values;

  
  Test1_test2_mv CREATE MATERIALIZED VIEW
  IMMEDIATE CONSTRUCTION
  COOL OFF QUICKLY ON COMMIT
  LIKE SOME t2.rowid,.
  T1.ID,
  T1.col_a,
  T1.col_b,
  T1.col_c,
  T1.col_d,
  T1.update_time,
  T2.col2,
  T2. COL3
  OF test1_mv t1,.
  Test2 t2
  WHERE (+) t1.id = t2.id; -symbol of outer join is not correctly displayed on the forums without space, grr!

  ORA-12052: is unable to fast refresh materialized view TEST1_TEST2_MV

  Y at - it any way I can get the materialized view fast refresh on commit or I asking the impossible?

  Add t1.rowid:

  SQL > CREATE MATERIALIZED VIEW test1_test2_mv

  2 BUILD IMMEDIATE

  3 QUICK REFRESH YOU COMMIT

  4 AS t2.rowid SELECT rid2,

  5 t1.rowid rid1,

  6 t1.id

  T1.col_a 7,.

  T1.col_b 8,.

  T1.col_c 9,.

  T1.col_d 10,

  T1.update_time 11,

  T2.col2 12,

  13 t2.col3

  14 OF test1_mv t1,

  15 test2 T2

  16 WHERE t1.id = t2.id

  17.

  Materialized view created.

  SQL > select * from test1_test2_mv

  2.

  RID2 RID1 ID COL_A, COL_B, COL_C COL_D UPDATE_TIME COL2 COL3

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

  AAAYB6AANAAAANDAAA AAAYB/AANAAAAN/AAA 1 1001 1003 1006 1004 25 / 06 / 2014 12:54:16 1 bob

  AAAYB6AANAAAANDAAB AAAYB/AANAAAAN/AAB 2 1002 1005 25 / 06 / 2014 1 sue 14:54:16

  AAAYB6AANAAAANDAAC AAAYB/AANAAAAN/AAC 3 1001 1006 25 / 06 / 2014 16:54:16 1 tom

  AAAYB/AANAAAAN/AAD AAAYB6AANAAAANDAAD 4 1004 25/06/2014 14:54:16 1 jay

  AAAYB6AANAAAANDAAE AAAYB / AANAAAAN / AAE 5 1002 2014/06/25 13:54:16 1 art

  AAAYB6AANAAAANDAAF AAAYB/AANAAAAN/AAG 7 1007 1009 25 / 06 / 2014 10:54:16 max 1

  AAAYB/AANAAAAN/AAH                                                                                                        1 tim

  AAAYB/AANAAAAN/AAF                                                                                                        1 kay

  AAAYB/AANAAAAN/AAI                                                                                                        1 liz

  9 selected lines.

  SQL > update of test2

  2 set col3 = "fly."

  3 where id = 7

  6 m

  1 line update.

  SQL > validation

  2.

  Validation complete.

  SQL > select * from test1_test2_mv

  2.

  RID2 RID1 ID COL_A, COL_B, COL_C COL_D UPDATE_TIME COL2 COL3

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

  AAAYB6AANAAAANDAAA AAAYB/AANAAAAN/AAA 1 1001 1003 1006 1004 25 / 06 / 2014 12:54:16 1 bob

  AAAYB6AANAAAANDAAB AAAYB/AANAAAAN/AAB 2 1002 1005 25 / 06 / 2014 1 sue 14:54:16

  AAAYB6AANAAAANDAAC AAAYB/AANAAAAN/AAC 3 1001 1006 25 / 06 / 2014 16:54:16 1 tom

  AAAYB/AANAAAAN/AAD AAAYB6AANAAAANDAAD 4 1004 25/06/2014 14:54:16 1 jay

  AAAYB6AANAAAANDAAE AAAYB / AANAAAAN / AAE 5 1002 2014/06/25 13:54:16 1 art

  AAAYB/AANAAAAN/AAH                                                                                                        1 tim

  AAAYB/AANAAAAN/AAF                                                                                                        1 kay

  AAAYB/AANAAAAN/AAI                                                                                                        1 liz

  AAAYB6AANAAAANDAAF AAAYB/AANAAAAN/AAG 7 1007 1009 25 / 06 / 2014 10:54:16 1 rob

  9 selected lines.

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

• the materialized view query

  Hello
  
  I had created a materialized view, it refreshes every 3 minutes. At the end of 3 minutes next time we are accessing the old records of materialized view should be deleted. Can someone help me with this query...
  

  create or replace materialized view deptd_mvu
       refresh fast on commit
       start with sysdate
       next sysdate + 3/(60*24)
       as select *
          from deptd;

  969052 wrote:
  No, my query shows all data are there is no error in my query? can u help me

  # It is not a mistake on your part of the implementation or Oracle. Error lies in understanding.

  Materialized view appeared in SELECT * FROM DEPT; So, it must take all the data that are available in the Dept table each time it is regenerated.

  What you intend to do is force the MView to choose the data "Modified" of table DEPT. Is not possible, unless you have some distinctive sign that the MView should be checked.

  For Eg :-(just an idea that I did not test this)

  Adding another column to identify records updated the: -.

  alter table dept add is_modified varchar2(1) default 'N';
  

  MView create instruction me altered as

  select *
    from dept
  where is_modified = 'Y';
  

  Write a trigger that sets the column IS_MODIFIED 'Y', each time that a record is inserted or updated. Don't worry about the deleted records (if this isn't a Soft Delete) as MView does not see records that are not present in the master table.

  You simply need to ensure that, whenever the MView is refreshed, the IS_MODIFIED the Department table must be set to 'n', so that it does not display a false positives.

• Complete export dashboard in excel gives error generate document in the table view of subtotals

  Hi all

  We have dashboard with several tabs and you try to export the whole dashboard in excel.

  Excel file is generated with all tabs on the dashboard as the leaves, but few of these leaves are empty with error message of document generation in the first cell.

  After further analysis, we concluded that the cause is seen with subtotals on table. PivotTables with subtotals are generated correctly.

  Workaround obvious to re-create the table views in the articulation points is not possible due to a large number of reports.

  We run Oracle Business Intelligence Product Version 11.1.1.7.150120 (Build 150113.1200 64-bit)

  Any ideas or solutions to this problem would be appreciated.

  Thank you;

  Klaudio

  We just found guilty

  Lines per page to display in the table must be 999999999 max which is more than enough for our needs.

• Trigger on the materialized view

  Hello

  I have the scenario based (Database 11 g):

  There is a view materialized (PERSON), which contains the ID and NAME fields. This MV is update daily with a fast refresh.

  I have a second array (NAMES), with ID and NORM_NAME. This table contains the name of the person, without special characters.

  For example, for recording / * 1 BJORN * / in the PERSON table

  I would check * 1 BJORN * / in table NAMES.

  
  

  Problem is how to fill the NAME table after the filling of the materialized view.

  I used a trigger AFTER INSERT or update, as described below, but even if I update the master table (for this purpose, update the MV), I have only to trigger inserts.

  
  

  Is there a way to implement a trigger "after update" on a materialized view, or do I need another approach?
  

  
  

  /*

  
  

  create or replace TRIGGER TRG_TESTE_MV

  AFTER INSERT OR UPDATE ON THE PERSON

  REFERENCING OLD AS OLD AGAIN AS NEW

  FOR EACH LINE

  BEGIN

  IF THE INSERTION

  INSERT THE NAMES

  VALUES

  (: NEW.id,:NEW.NAME);

  END IF;

  IF THE UPDATE CAN

  UPDATE OF NAMES

  SET NAME =: NEW.NAME WHERE ID =: NEW.id;

  END IF;

  END;

  */

  Thanks for any help

  Your trigger fires, but I doubted that you will be satisfied with the results. You really need to understand how to refresh process works before you begin creating triggers of MV:

  SQL > create table emp1 in select * from EMP
  2.

  Table created.

  SQL > create materialized view emp1 with rowid journal
  2.

  Materialized view log that is created.

  SQL > create materialized view emp1_mv
  2 fast refresh
  3 on request
  4 with rowid
  5 as
  6 select * from emp1
  7.

  Materialized view created.

  SQL > create or replace
  trigger 2 emp1_mv_biudr
  3 before inserting
  4 or update
  5 or delete
  6 on emp1_mv
  7 for each line
  Start 8
  9 insert then dbms_output.put_line ('INSERT' |: new.ename); end if;
  10 if the deletion then dbms_output.put_line ('REMOVE' |: old.ename); end if;
  11 end;
  12.

  Trigger created.

  SQL > insert
  2 in emp1 (empno, ename, sal)
  3 values(1,'X',1000)
  4.

  1 line of creation.

  SQL > validation
  2.

  Validation complete.

  SQL > set serveroutput on
  SQL > exec dbms_mview.refresh ('emp1_mv', 'f');
  INSERTION OF X

  PL/SQL procedure successfully completed.

  SQL > update emp1
  2 set sal = sal + 1
  3 where ename ('King', 'JONES')
  4.

  2 lines to date.

  SQL > validation
  2.

  Validation complete.

  SQL > set serveroutput on
  SQL > exec dbms_mview.refresh ('emp1_mv', 'f');
  INSERTION OF JONES
  INSERTION OF KING

  PL/SQL procedure successfully completed.

  SQL > delete emp1
  2 where in ename ('ALLEN', 'SMITH')
  3.

  2 deleted rows.

  SQL > validation
  2.

  Validation complete.

  SQL > set serveroutput on
  SQL > exec dbms_mview.refresh ('emp1_mv', 'f');

  PL/SQL procedure successfully completed.

  SQL >

  As you can see, refresh MV updates ever. Results update underlying table to remove/insert in MV. That's why your trigger will not give the results that you expected.

  SY.

• Do not to use the materialized view

  I wonder if we've already created a materialized view, can we prefer not to use this point of view, materialized for a query? I want to say can we determine if a query uses MV and other queries don't use MV?  Thank you.

  Hello Indra,

  I'm not completely sure about that, but you can read (with examples) concerning the indications- NO_REWRITE and REWRITE

  Text over the doc links:

  Council of REWRITING:

  The REWRITE Council instructs the optimizer to rewrite a query regarding the materialized views when possible, regardless of cost. Use the REWRITE trick with or without a display list. If you use REWRITE with a view list and the list contains an eligible materialized view, then Oracle uses this view regardless of its cost.

  Tip NO_REWRITE:

  The NO_REWRITE Council tells the optimizer to disable the rewrite of the query to the query block, of the substitution of the definition of the parameter QUERY_REWRITE_ENABLED .

  Be aware! -The NOREWRITE suspicion has been deprecated. Use the NO_REWRITE hint instead.

  Read here: setting QUERY_REWRITE_ENABLED

  -Nordine