Materialized views Oracle | Reporting

Similar Questions

• Oracle Warehouse builder or materialized views

  I have a requirement as follows:
  
  Requirement:
  We must create a Reporting DB to be used for information and a transactional database will be in separate host. Fundamentally, he need to extract data from a set of transactional DB tables and move to the Reporting DB schema at adequate intervals.
  
  We may have to get a different column data in different tables and store it in a single table / several reports DB tables.
  
  
  Can someone whether to go with Oracle Warehouse builder or the materialized views for this offer please?
  Or use OWB to create and maintain the MVs.
  
  Also please me a link point to what features are available with OWB
  
  Our Oracle is installed in Solaris 10 and one who is perfect either generator warehouse Oracle or materialized views
  
  Thank you
  APPU
  
  Published by: user12094414 on October 25, 2009 21:52
  
  Published by: user12094414 on October 25, 2009 22:17

  user12094414 wrote:
  Can someone whether to go with Oracle Warehouse builder or the materialized views for this offer please?
  Or use OWB to create and maintain the MVs.

  The two are not exclusive. OWB is a tool for designing the data movement and implement updates to the warehouse.

  MVs are a tool integrated into the database in support of materialization of the current request to speed up some types of applications related to data that is availoable, perhaps after transport OWB.

  >

  Also please me a link point to what features are available with OWB

  Normal (to allow the future of mutual aid) access is

  http://OTN.Oracle.com
  -> Products (perma menu on the left): database (link)
  -> Warehouseing Bi & data (link in the middle section)
  -> Related products (product menu on the right): Warehouse Builder
  where you can get a Viewlet, whitepapers, docs, demos, tutorials, etc.

  Direct access to the page above is http://www.oracle.com/technology/products/warehouse/index.html

• Oracle materialized view more Gateway

  Dear Sir.
  
  We have microsoft sql server, oracle gateway (11G) and database server (10.2.0.5)
  
  We already have the complete installation, and it works.
  
  We create a materialized view in the oracle server to read data from sql server, but the updating of the MV can't wait time
  We are planing to create the view materialized in the oracle gateway server.
  
  My question is:
  
  What is the best solution to create the MV in the oracle gateway server?
  I mean I can't download MV only one instance of oracle database.
  
  Thanks in advance.

  Just to clarify: there is normally no need to install a database on the gateway server. You can create the mview directly in your 10.2.0.5 database.
  If you really want to have another data base which contains the mview then install in the box of gateway to the Oracle database using the version standard edition. There is no need to activate Enterprise Manager or other stuff.
  About the size of the memory, it really depends on the amount of data you have to shoot through the gateway and to select by using the synonym. Therefore, there is no generic answer on sizing.

• Are materialized views in Oracle OLAP licenses. ?

  Hi all
  We use the EE Oracle 10 g 2. We try to find the list of products of Oracle 10gEE. License part materialized views in Oracle OLAP or that come with the Standard edition.
  
  Thank you

  Commerce 10.2 has a table of availability of the editing features (a SE, SE, EE) which establishes good enough differences:
  http://download.Oracle.com/docs/CD/B19306_01/license.102/b14199/editions.htm#BABJICBB

  However I don't see, documentation, its use of MV (license) is clearly defined. Basically, it seems it depends of the use of MVs.

  See, for example, Data Warehouse (syntheses) and integration - based replication. Sometimes, the documentation uses the phrase "materialized views to...» ». SQL aggregation / analytical seems to be a missing piece as well (in the current doc sets).
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14200/statements_6002.htm
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14223/basicmv.htm#i1006193
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14226/repmview.htm

  The new 11g Cube materialized views feature is of course an OLAP option.

  And, as usual, you can find in the documentation, forums etc is almost irrelevant when it comes to licensing issues. You should see your specific contract. Talk to your sales person.

  "License issues really, really, really should be addressed to your representative commercial Oracle." Nothing we say here links to Oracle. We don't know other agreements, your organization may have with Oracle. ... explaining that "a guy on the internet with a card to play said logo is OK," probably won't do more good. »
  (borrowed from Oracle licenses VMware + Quadcore

  Published by: orafad on January 27, 2011 20:39

• Oracle 8i Materialized view

  I'm on oracle 8.1.7
  
  A few times is not automatically refresh
  
  -I want to connect view refresh time in other tables when it refreshes
  
  -wanted to know whether the necessary changes in the view script
  
  
  DROP MATERIALIZED VIEW MSIRC. IL_BRANCHES;
  
  CREATE THE MSIRC MATERIALIZED VIEW. IL_BRANCHES
  REFRESH FORCE
  START WITH TO_DATE (October 12, 2009 09:15:42 "," dd-mon-yyyy hh24:mi:ss')
  NEXT sysdate + 1/1440
  WITH THE PRIMARY KEY
  ACTIVATE THE QUERY REWRITING
  AS
  / * In format on 2009-10-12 13:44:16 (PS5 v5.115.810.9015) * /.
  SELECT 'IL_BRANCHES '. "" BRANCH_ID ""BRANCH_ID"
  'IL_BRANCHES '. ' ' ' 'NAME',
  'IL_BRANCHES '. "' HEADLINE '"TITLE. "
  'IL_BRANCHES '. "" INSTANCE_ID ""INSTANCE_ID. "
  'IL_BRANCHES '. "' PARENT_ID '"PARENT_ID"
  'IL_BRANCHES '. "" PUB_STATUS ""PUB_STATUS"
  'IL_BRANCHES '. "" ALERT_STATUS ""ALERT_STATUS"
  'IL_BRANCHES '. "' ORDER_FIELD ' 'ORDER_FIELD ',.
  'IL_BRANCHES '. "" DESCRIPTION ""DESCRIPTION. "
  'IL_BRANCHES '. "" RELATED_LINKS ""RELATED_LINKS"
  'IL_BRANCHES '. "" EXTERNAL_LINK ""EXTERNAL_LINK. "
  'IL_BRANCHES '. "" SEND ""SENT. "
  'IL_BRANCHES '. ' ' CONTENT_1 ' 'CONTENT_1 '.
  OF ' IL_BRANCHES"@STAGING 'IL_BRANCHES ';

  I want to connect view refresh time in other tables when it refreshes

  You can check the last_refresh of the user_snapshot_refresh_times view and the view user_refresh next_date

  You can use it in the below format

  TO_CHAR (last_refresh, "DD-MM-YY HH24:MI:SS) last_refresh

  Anand

• Materialized Oracle view | Deleting records, Oracle materialized view

  One question reg Materialized views.
  
  If as part of the interview of the Source database, we remove some (older) recordings, the materialized view will also be updated with the deletion?
  
  I believe that the answer is Yes. In this case make sure that deletion is not the case?
  
  Is there anyway that we'll stop MView update to delete records that is inserted once even if we remove the same records in the source DB?

  This is a common scenario, especially with materialized views that summarizes the detail data where you want to keep the summary but not the detail, and it is discussed in the documentation.

  The technique is to make the MV refresh on request, delete the data in the detail tables and the CONSIDER_FRESH procedure to prevent the changes propagating to the MV. You will probably find it in the docs by searching on DBMS_MView.Consider_Fresh. There are a few caveats to note, in my opinion.

• Change the definition of the materialized view while maintaining access for users uninteruupted

  Hello

  We have a system report and the need to change the report definition mv access - like to do it without interruption.

  Is this possible?

  the sql behind mv was change picks up so column of another table.

  Have you heard but not used for dbms_redefinition tables

  Thank you

  It is built in the Oracle solution for this one, where you can edit the definition WITHOUT interruption. You can drop the materialized view existing with the clause "save table" and rebuilt the view materialized on 'predefined table'. I googled this example for you

  create materialized view mv1 as select dept , count(*) as cnt from scott.emp;

  We want to change the statement so that only dept more 5 will be calculated

  drop materialized view mv1 preserve table;
  

  Notice that PRESERVE TABLE clause - mv1 table is not droped - single layer mview.

  desc mv1
  

  now, we create the mview with a different query on top of the existing table

  create materialized view mv1 on prebuilt table as  select dept , count(*) as cnt from scott.emp where dept > 5;
  

  Notice that on prebuilt table the mview uses the existing object clause.

  exec dbms_mview.refresh_mview('mv1');
  

  http://StackOverflow.com/questions/18085894/redefine-MATERIALIZED-view-with-no-downtime

  http://Arup.blogspot.com/2009/01/ultra-fast-MV-alteration-using-prebuilt.html

• PX Deq Credit: send blkd hang while the materialized view Refresh

  Hi all
  
  When we are materialized view refreshing. It takes more than 2.30 minutes. Initially, it took 1.40 minutes.
  
  We use parallel and base are partitioned. When I checked the tkprof report I see a lot of insert query expects especially PX Deq Credit: send blkd event. When I check the ASH report that I find not just any question about MV was running but always refresh MV was going on
  
  
  

  TKPROF: Release 11.2.0.1.0 - Development on Wed Jun 5 16:27:29 2013
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
  
  Trace file: CHDFCI_p001_43384918_PARALLEL.trc
  Sort options: exeela  prsela  fchela  
  ********************************************************************************
  count    = number of times OCI procedure was executed
  cpu      = cpu time in seconds executing 
  elapsed  = elapsed time in seconds executing
  disk     = number of physical reads of buffers from disk
  query    = number of buffers gotten for consistent read
  current  = number of buffers gotten in current mode (usually for update)
  rows     = number of rows processed by the fetch or execute call
  ********************************************************************************
  
  
  EXPLAIN PLAN option disabled.
  ********************************************************************************
  
  SQL ID: 2x210q5g30m4t
  Plan Hash: 2058446196
  INSERT /*+ BYPASS_RECURSIVE_CHECK APPEND  */ INTO 
    "APPS"."GL_BAL_MV" SELECT * FROM 
    GL_BAL_V
  
  
  call     count       cpu    elapsed       disk      query    current        rows
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  Parse        1      0.00       0.00          0          0          0           0
  Execute      1    362.20    9372.04    1158765          0          0           0
  Fetch        0      0.00       0.00          0          0          0           0
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  total        2    362.20    9372.04    1158765          0          0           0
  
  Misses in library cache during parse: 0
  Optimizer mode: ALL_ROWS
  Parsing user id: 175     (recursive depth: 1)
  
  Rows     Row Source Operation
  -------  ---------------------------------------------------
        0  LOAD AS SELECT  (cr=0 pr=0 pw=0 time=0 us)
        0   PX COORDINATOR  (cr=0 pr=0 pw=0 time=0 us)
        0    PX SEND QC (RANDOM) :TQ10003 (cr=0 pr=0 pw=0 time=0 us cost=1041298 size=389555904 card=2028937)
  78448967     HASH JOIN BUFFERED (cr=0 pr=1158765 pw=1158765 time=276842112 us cost=1041298 size=389555904 card=2028937)
   410944      BUFFER SORT (cr=0 pr=0 pw=0 time=492466 us)
   410944       PX RECEIVE  (cr=0 pr=0 pw=0 time=34526636 us cost=64715 size=147944250 card=1643825)
        0        PX SEND HASH :TQ10001 (cr=0 pr=0 pw=0 time=0 us cost=64715 size=147944250 card=1643825)
        0         PARTITION RANGE ALL PARTITION: 1 39 (cr=0 pr=0 pw=0 time=0 us cost=64715 size=147944250 card=1643825)
        0          TABLE ACCESS FULL GL_CODE_COMBINATIONS PARTITION: 1 39 (cr=0 pr=0 pw=0 time=0 us cost=64715 size=147944250 card=1643825)
  78448967      PX RECEIVE  (cr=0 pr=0 pw=0 time=2453949696 us cost=976582 size=395060280 card=3873140)
        0       PX SEND HASH :TQ10002 (cr=0 pr=0 pw=0 time=0 us cost=976582 size=395060280 card=3873140)
        0        HASH JOIN  (cr=0 pr=0 pw=0 time=0 us cost=976582 size=395060280 card=3873140)
        0         BUFFER SORT (cr=0 pr=0 pw=0 time=0 us)
        0          PX RECEIVE  (cr=0 pr=0 pw=0 time=0 us cost=32 size=133920 card=2480)
        0           PX SEND BROADCAST :TQ10000 (cr=0 pr=0 pw=0 time=0 us cost=32 size=133920 card=2480)
        0            HASH JOIN  (cr=0 pr=0 pw=0 time=0 us cost=32 size=133920 card=2480)
        0             TABLE ACCESS FULL GL_SETS_OF_BOOKS (cr=0 pr=0 pw=0 time=0 us cost=7 size=108 card=6)
        0             TABLE ACCESS FULL GL_PERIODS (cr=0 pr=0 pw=0 time=0 us cost=24 size=44640 card=1240)
        0         PX BLOCK ITERATOR PARTITION: 1 39 (cr=0 pr=0 pw=0 time=0 us cost=976550 size=30099548160 card=627073920)
        0          TABLE ACCESS FULL GL_BALANCES PARTITION: 1 39 (cr=0 pr=0 pw=0 time=0 us cost=976550 size=30099548160 card=627073920)
  
  
  Elapsed times include waiting on following events:
    Event waited on                             Times   Max. Wait  Total Waited
    ----------------------------------------   Waited  ----------  ------------
    PX Deq: Execution Msg                           3        0.16          0.17
    PX Deq Credit: send blkd                  1061004        1.99       5084.61
    PX Deq: Table Q Normal                     250856        2.00       2306.87
    asynch descriptor resize                        1        0.00          0.00
    Disk file operations I/O                       10        0.23          0.26
    direct path write temp                       3608        1.20        958.39
    latch free                                     26        0.02          0.19
    PX qref latch                             7647924        0.05         11.85
    direct path read temp                         578        0.43         35.19
    PX Deq Credit: need buffer                   4037        0.08          5.84
  
  
  
  ********************************************************************************
  
  OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS
  
  call     count       cpu    elapsed       disk      query    current        rows
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  Parse        0      0.00       0.00          0          0          0           0
  Execute      0      0.00       0.00          0          0          0           0
  Fetch        0      0.00       0.00          0          0          0           0
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  total        0      0.00       0.00          0          0          0           0
  
  Misses in library cache during parse: 0
  
  Elapsed times include waiting on following events:
    Event waited on                             Times   Max. Wait  Total Waited
    ----------------------------------------   Waited  ----------  ------------
    PX Deq: Execution Msg                           3        0.47          0.75
    PX Deq: Slave Session Stats                     1        0.15          0.15
  
  
  OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS
  
  call     count       cpu    elapsed       disk      query    current        rows
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  Parse        1      0.00       0.00          0          0          0           0
  Execute      1    362.20    9372.04    1158765          0          0           0
  Fetch        0      0.00       0.00          0          0          0           0
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  total        2    362.20    9372.04    1158765          0          0           0
  
  Misses in library cache during parse: 0
  
  Elapsed times include waiting on following events:
    Event waited on                             Times   Max. Wait  Total Waited
    ----------------------------------------   Waited  ----------  ------------
    PX Deq: Execution Msg                           3        0.16          0.17
    PX Deq Credit: send blkd                  1061004        1.99       5084.61
    PX Deq: Table Q Normal                     250856        2.00       2306.87
    asynch descriptor resize                        1        0.00          0.00
    Disk file operations I/O                       10        0.23          0.26
    direct path write temp                       3608        1.20        958.39
    latch free                                     26        0.02          0.19
    PX qref latch                             7647924        0.05         11.85
    direct path read temp                         578        0.43         35.19
    PX Deq Credit: need buffer                   4037        0.08          5.84
  
      1  user  SQL statements in session.
      0  internal SQL statements in session.
      1  SQL statements in session.
      0  statements EXPLAINed in this session.
  ********************************************************************************
  Trace file: CHDFCI_p001_43384918_PARALLEL.trc
  Trace file compatibility: 11.1.0.7
  Sort options: exeela  prsela  fchela  
         1  session in tracefile.
         1  user  SQL statements in trace file.
         0  internal SQL statements in trace file.
         1  SQL statements in trace file.
         1  unique SQL statements in trace file.
   8986825  lines in trace file.
      9372  elapsed seconds in trace file.

  When I checked the ASH report during this period. I don't see anything related to MV running.
  I use parallel degree 8 to GL_BALANCES.
  Please suggest.

  Sarah wrote:
  Hi all

  When we are materialized view refreshing. It takes more than 2.30 minutes. Initially, it took 1.40 minutes.

  You are showing much more than 2.30 minutes in this result tkprof - did you mean hours?

  We use parallel and base are partitioned. When I checked the tkprof report I see a lot of insert query expects especially PX Deq Credit: send blkd event.

  In your case, it seems as if the "PX Deq Credit: send blkd" is an inactive waiting (despite comments in the manual, which is not always true).
  Plan execution tells you that you are not loading in the GL_BAL_MV at the same time (even if you select it in parallel). This means a single process must collect all the data of all the slaves of PX to insert it, so anytime 7 slaves will wait for you "PX Deq Credit: send blkd" while the eighth sends data to the query Coordinator to write to the table. (The timeout on these waiting 2 seconds - which is consistent with the max wait the values you see.)

  If you can ensure that the MV and its index is declared as parallel, and you can enable parallel DML for updating, you may find that things go a lot faster.

  When I check the ASH report that I find not just any question about MV was running but always refresh MV was going on

  Ash can be a bit flakey with some of its reports in 11.2.0.1 - perhaps you were simply unlucky.

  >

  call     count       cpu    elapsed       disk      query    current        rows
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  Parse        1      0.00       0.00          0          0          0           0
  Execute      1    362.20    9372.04    1158765          0          0           0
  Fetch        0      0.00       0.00          0          0          0           0
  ------- ------  -------- ---------- ---------- ---------- ----------  ----------
  total        2    362.20    9372.04    1158765          0          0           0
  

  It is possible, moreover, that your plan has changed over time - there are a couple of "HASH JOIN TAMPONNÉE" in the plan, which means that the table "probe" the hash join arrives on the assembling process and is dumped to disk (if it does not fit in memory) to be reread and joined. This can consume a lot of IO and the time - as seen by the "pr = 1158765 pw = 1158765" on line 4 of your plan. It is possible that a previous plan has used a method of dissemination for the table of 'building' avoid this overload - but that the optimizer has switched plans as all data has increased.

  Concerning
  Jonathan Lewis

  Published by: Jonathan Lewis on June 5, 2013 16:20 (formatting)

• 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

• 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

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

• Materialized views Refresh method and refresh option

  Hi Experts,

  According to the docs, If the MV contains the following, MV is considered complex. I wonder is there any view data dictionary that indicates the type of MV? Because is very easy to the candidate a complex type mv. Because many queries contains the properties below.

  http://docs.Oracle.com/CD/B28359_01/server.111/b28326/repmview.htm#i52501

  http://docs.Oracle.com/CD/B28359_01/server.111/b28313/basicmv.htm

  Specifically, a materialized view is considered complex if the materialized view definition query contains:

  • A CONNECT BY clause
  • An INTERSECT , MINUS , or UNION ALL operation
  • he DISTINCT or UNIQUE keyword
  • In some cases, an aggregate function, although it is possible to have an aggregation function in the query definition and always have a simple materialized view
  • In some cases, joins other than those in a subquery, although it is possible to have joins in the definition to interrogate and still have a simple materialized view
  • In some cases, a UNION operation

  
  

  After that I kept going to read that I learned that when a VM is created, the refresh mode is specified according to the type of the MV. That means, using ON-DEMAND refresh mode is widespread. The documentation mentions that there isa also refresh option. My question is, is it possible to specify

  ON REQUEST and FAST together?

  Also, what are the differences between FULL and FAST. Ends truncate the table and fill it up again?

  ON COMMIT

  Refresh product automatically when a transaction which changed one of the paintings of the materialized view's retail is committed. This can be specified as the materialized view is quickly updatable (in other words, not complex). The ON COMMIT privilege is required to use this mode.

  ON DEMAND

  Refresh occurs when a user manually executes one of the procedures available refresh contained in the DBMS_MVIEW package ( REFRESH , REFRESH_ALL_MVIEWS , REFRESH_DEPENDENT ).

  COMPLETE	Refreshes and recalculating the materialized view query definition.
  FAST	Applies incremental changes to refresh the materialized view using the information recorded in the papers of the materialized view, or an SQL * Loader direct-path access or a partition maintenance operation.

  FORCE

  Applies FAST update if possible; otherwise, it applies COMPLETE Refresh.

  NEVER

  Indicates that the materialized view will not be updated with updating mechanisms.

  Select * from version of v$.

  Oracle Database 11 g Release 11.2.0.4.0 - 64 bit Production

  Thank you

  Çaglar wrote:

  ...

  Also, what are the differences between FULL and FAST. Ends truncate the table and fill it up again?

  ...

  Thank you

  I just want to answer the truncated question. Seems that nobody covered that yet.

  Answer: It depends.

  If you do a full refresh, then the default is to use ATOMIC_REFRESH = TRUE.

  This means that the update is done via an insert, delete , and ... Select.

  You can change it to ATOMIC_REFRESH = FALSE (parameter dbms_mview.refresh).

  This means that is a TRUNCATE and insert a ... Select with APPEND peak (path direct insert).

  Refresh if Atomic = FALSE is considerably faster than the default. Also way less Archives of newspapers are written.

  The downside is however that, during the update the MV is empty, is no longer an atomar operation!

  See also Oracle documentation: http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_mview.htm#i997194

• What is materialized views named?

  Hi there;

  When I read the documentation below, I met a sentence.

  http://docs.Oracle.com/database/121/DWHSG/basicmv.htm#i1007299

  Materialized views with subqueries or views named in the DE clause can be fast refreshed as points of view can be completely merged.

  What is the point of view named? Thanks in advance.

  Hello

  Named views are normal views created by running ' create view abc as select... from...» ».

  Kind regards

  Bashar

• What is a materialized view?

  If I read oradocs on flashback instructions table and it mentions

  When you delete a table, all the newspapers view materialized, defined on the table are also deleted, but are not placed in the Recycle Bin. Therefore, the materialized view logs cannot be flashed back as well as the table

  (http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_9012.htm#SQLRF01802)

  
  

  then I went to oradocs for the view materialized and read the first half logs.

  http://docs.Oracle.com/CD/B19306_01/server.102/b14200/statements_6003.htm

  Now, I know what makes a materialzed view log.

  is a materialized view as a point of view however... ?

  No, it isn't.

  A materialized view is basically a query with its 'materialized' or stored in a table results. A MV can be used by Oracle in a manner transparent re - write a query to be faster.

• What is the problem with my Oracle reports parameter?

  Hello

  We use a PL SQL package that allows the user to select the report you want Oracle and associated parameters.   While the control is passed to Oracle 11 g reports.

  The requirement of one of the reports is to enable more detailed codes be selected by the user and then shown.  The detailed code is an alphanumeric field that can hold between 4 and 6 characters.

  If my data model looks like this

  SELECT student_id

      FROM my_view

     WHERE detail_code IN :p_detail_code;

  and the parameter that I'm passing to Oracle reports looks like this (when I view the source HTML code)

  & p_detail_code =('1001','1002')

  so no record is selected.

  However, if my data model looks like this, I get the records you want:

  SELECT student_id

    FROM my_view

  WHERE detail_code IN ('1001', '1002');

  We have Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production.

  Please tell me what is the problem with my setting.  Thanks a lot for your help.

  This isn't how you can use in. See this example on how to solve it with the digital settings. If your setting is a character, you need to change this.

  In fact, when you simply enter 1,2,3 as an input parameter, you actually create this query:

  Select *.

  from my_table

  where num_column in ("1,2,3")

  Use rather a lexical parameter:

  Select *.

  from my_table

  & p_where

  In the parameter after relaxation shape, build the lexical like this:

  :p_where := 'where num_column in ('||:p_param||')';