Need to refresh materialized view from procedure and pl/sql block

Hi,
I need to refresh materialized view (complete refresh)from procedure and pl/sql block .can some one help.
MV name:MV_DGN_TEST_SESSION
Thanks,
Rajasekhar

dbms_mview.REFRESH ('MV_DGN_TEST_SESSION', 'C');Regards,
Mahesh Kaila
Edited by: user4211491 on Dec 1, 2009 10:41 PM

Similar Messages

ORA-12015: cannot create a fast refresh materialized view from a complex q

Hi,
I'm facing very strange problem. Please help me why this error is coming
I'm creating a simple materialized view, but it is giving below error since this is simple select * from.
CREATE MATERIALIZED VIEW EFMS.MS_TASK
BUILD IMMEDIATE
REFRESH FAST
START WITH SYSDATE
NEXT (SYSDATE + 1/24)
WITH ROWID
AS
SELECT * FROM MS_TASK@efms_link;
SELECT * FROM MS_TASK@efms_link
ERROR at line 8:
ORA-12015: cannot create a fast refresh materialized view from a complex query
CREATE MATERIALIZED VIEW LOG ON MSDBO.MS_TASK
TABLESPACE DBOR_MVLOG
PCTUSED 0
PCTFREE 60
INITRANS 20
MAXTRANS 255
STORAGE (
INITIAL 64K
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 0
BUFFER_POOL DEFAULT
NOCACHE
NOLOGGING
PARALLEL ( DEGREE 2 INSTANCES 1 )
WITH ROWID, PRIMARY KEY
EXCLUDING NEW VALUES;

1º
Not is a best practice to use 'select *'
2º
ORA-12015: cannot create a fast refresh materialized view from a complex query
Cause: Neither ROWIDs and nor primary key constraints are supported for complex queries.
Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE option or create a simple materialized view.
Then you have to change REFRESH FAST or create a primary key in MS_TASK@efms_link to avility fast refresh.
. :-) any help with my english is wellcome :-) .

ORA-12015: cannot create a fast refresh materialized view from a complex

Hi All,
I am trying to create materialized view but i got a error ORA-12015: cannot create a fast refresh materialized view from a complex query.
Regards,
narayana

Hi,
Please see if (Note: 179466.1 - Diagnosing ORA-12015 fast refresh materialized view / complex queries) helps.
Regards,
Hussein

ORA-12015: cannot create a fast refresh materialized view from a complex qu

BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - ProductionI'm trying to create a fast refresh materialized view that uses a column of xmltype. The problem is I cannot create an MV log that accounts for the xmltype column. I tried excluding it and got the above error. Is there another way I can incrementally update a materialized view where I don't have to do a COMPLETE refresh or use FAST refresh?
CREATE TABLE "DAS_DESC"."AUTHORITY_TEST"
    "NAID"      NUMBER(20,0) NOT NULL ENABLE,
    "AUTH_TYPE" VARCHAR2(40 BYTE),
    "XML_DATA" "SYS"."XMLTYPE" ,
    "TERM_NAME" VARCHAR2(4000 BYTE)
CREATE TABLE "DAS_DESC"."AUTH_ASSC_TEST"
    "NAID"    NUMBER(20,0),
    "P_NAID" NUMBER(20,0),
    "REL_TYPE"    VARCHAR2(25 BYTE),
    "XML_DATA" "SYS"."XMLTYPE"
CREATE
MATERIALIZED VIEW person_mv
AS
SELECT p.naid
      , p.auth_type
      , INSERTCHILDXML
          p.xml_data                 -- Parent XML Column
        , '//*[contains(local-name(), ''person'')]' --XPATH to Person
        , 'nonPreferredHeadingArray'                -- Value for new child element
        (                                                       -- Sub query for injecting new variant person array
          SELECT XMLELEMENT
            "nonPreferredHeadingArray"
          , XMLAGG -- Aggregator for Variant Persons Array
              XMLELEMENT
                "variantPersonName"                    -- Wrapper for each entry in array
              , extract(a.xml_data,'*/*')
          FROM auth_assc_table -- Link table
          WHERE a.p_naid = p.naid
      ) AS XML_DATA
FROM authority p -- Parent table
WHERE p.auth_type = 'Person';The views are created fine and they work perfectly for what we need. The problem is the refresh when we edit the base tables. Ideally, it should take a couple seconds. Right now, it takes a couple minutes. XMLTYPE is one problem and the Complex Query exception is the other. If there is a work-around for fast refresh, please let me know. Greatly appreciated.

jjmdb wrote:
I'm trying to create a fast refresh materialized view that uses a column of xmltype. The problem is I cannot create an MV log that accounts for the xmltype column. I tried excluding it and got the above error. Is there another way I can incrementally update a materialized view where I don't have to do a COMPLETE refresh or use FAST refresh? Besides XMLTYPE column, your MV definition has a subquery which prevents it from being fast refreshable.
I could not find any specific reference in documentation about restriction on XMLTYPE (or CLOB) columns but it seems logical that oracle will not be able to keep track of changes to binary data. What does DBMS_MVIEW.EXPLAIN_MVIEW generate for your MV definition? That should tell you which all conditions (for FAST REFRESH) your MV violates. Since you can not create a MV LOG to include XMLTYPE column, it will not be possible to create a FAST REFRESHABLE MV that includes the XMLTYPE column.
I am afraid there is not much you can do here unless you are prepared to change the way data is stored in your base tables. If you can store data in base tables using standard data types instead of binary/XML storage, you might be able to create a FAST REFRESHABLE MV.

Refreshing Materialized view from APEX process is causing errors

Hi,
I have created a materialized view, and am attempting to create a process in APEX to refresh the mview on a button click.
I have been reading the documentation on Materialized Views and think I am more confused now than when I started.
Do I need to add my mview to a refresh group to enable me to use the DBMS_REFRESH.REFRESH command from an APEX process?
I have had a few attempts at getting it working, but to no avail yet.
Any help would be appreciated.
Cheers, Greg

Snowman wrote:
Hi,
I have created a materialized view, and am attempting to create a process in APEX to refresh the mview on a button click.
I have been reading the documentation on Materialized Views and think I am more confused now than when I started.
Do I need to add my mview to a refresh group to enable me to use the DBMS_REFRESH.REFRESH command from an APEX process?What error are you getting?

Need to refresh Materialized Views automatically

Hi Folks,
GoodDay, I have created MVs for some source tables, now i need to make the refresh job automate. I mean to say no need of human interaction. The MV needs to refresh itself automatically based on certain time schedules.
Please let me know is there any JOB need to create for my requirement..?
It is very much better if any one provide some sample JOB code.
Regards,
Ramesh.

You can dig up sample dbms.scheduler code in the Scheduler forum, or simply google search.
Regarding the M.View, can't you inside the scheduler job, drop the m.view, and recreate it? Or if you need fresh data any moment, a regular view is probably better.

Error While Creating Fast Refresh Materialized view.

Table Scripts:
CREATE TABLE CONTRACT_MASTER
CONTRACT_SEQ                    NUMBER(10)    NOT NULL,
PDN                             CHAR(5)       NOT NULL,
APPID                           NUMBER(10)    NOT NULL,
CONTRACT_LOB_DESC               VARCHAR2(20) NOT NULL,
CUSTOMER_NAME                   VARCHAR2(57) NOT NULL,
CONTRACT_DT                     DATE          NOT NULL,
CONTRACT_RECD_DT                DATE          NOT NULL,
HELD_OFFERING_DT                DATE          NOT NULL,
DRAFT_AMT                       NUMBER(15,2) NOT NULL,
STATUS_DESC                                   VARCHAR2(20) NOT NULL,
GIF_UPLOAD_TM                                            TIMESTAMP     NOT NULL
CREATE table CONTRACT_COMMENTS
CONTRACT_COMMENTS_SEQ           NUMBER(10)     NOT NULL,
APPID                           NUMBER(10)     NOT NULL,
COMMENTS                        VARCHAR2(1000) NOT NULL,
GIF_UPLOAD_TM                                            TIMESTAMP      NOT NULL
Constraints on tables
ALTER TABLE CONTRACT_MASTER ADD
CONSTRAINT XPKCONTRACT_MASTER PRIMARY KEY (CONTRACT_SEQ) USING INDEX ;
ALTER TABLE CONTRACT_COMMENTS ADD
CONSTRAINT XPKCONTRACT_COMMENTS PRIMARY KEY (CONTRACT_COMMENTS_SEQ) USING INDEX ;
alter table CONTRACT_MASTER add CONSTRAINT XUIAPPCONTRACT_MASTER UNIQUE (APPID) USING INDEX;
CREATE INDEX XUIAPPCONTRACT_COMMENTS ON
CONTRACT_COMMENTS(APPID) ;
Materialized View Creation:
CREATE MATERIALIZED VIEW LOG ON CONTRACT_MASTER WITH PRIMARY KEY,ROWID;
CREATE MATERIALIZED VIEW LOG ON CONTRACT_COMMENTS WITH PRIMARY KEY, ROWID;
CREATE MATERIALIZED VIEW MV_CONTRACT_COMMENTS_HELDOFFERING
REFRESH FAST
ENABLE QUERY REWRITE AS
SELECT APPID,COMMENTS FROM CONTRACT_COMMENTS WHERE APPID IN (
SELECT APPID FROM CONTRACT_MASTER WHERE STATUS_DESC = 'Held Offering' )
Errors generated:
ERROR at line 4:
ORA-12015: cannot create a fast refresh materialized view from a complex query
_*Afer That I have changed the query but still it was not created like:*_
CREATE MATERIALIZED VIEW MV_CONT_COMMNTS_HELDOFFERNG
REFRESH FAST
ENABLE QUERY REWRITE AS
SELECT CONTRACT_COMMENTS_SEQ,c.APPID,COMMENTS
FROM CONTRACT_COMMENTS c,CONTRACT_MASTER m
WHERE m.APPID = c.APPID and m.STATUS_DESC = 'Held Offering'
*even though error displayed:
SQL> CREATE MATERIALIZED VIEW MV_CONT_COMMNTS_HELDOFFERNG*
   2 REFRESH FAST
   3 ENABLE QUERY REWRITE AS
   4 SELECT CONTRACT_COMMENTS_SEQ,c.APPID,COMMENTS
   5 FROM CONTRACT_COMMENTS c,CONTRACT_MASTER m
   6 WHERE m.APPID = c.APPID and m.STATUS_DESC = 'Held Offering';
FROM CONTRACT_COMMENTS c,CONTRACT_MASTER m
ERROR at line 5:
ORA-12052: cannot fast refresh materialized view GSSIO.MV_CONT_COMMNTS_HELDOFFERNG
*Again I have done "Analyzing Materialized Views for Fast Refresh" as follows:*
1: exec dbms_mview.explain_mview('MV_CONT_COMMNTS_HELDOFFERNG');
2: SELECT capability_name, possible, SUBSTR(msgtxt,1,60) AS msgtxt
           FROM mv_capabilities_table
           WHERE capability_name like '%FAST%';
Output is :
CAPABILITY_NAME                               P              MSGTXT
REFRESH_FAST                                   N
REFRESH_FAST_AFTER_INSERT            N the SELECT list does not have the rowids of all the detail t
REFRESH_FAST_AFTER_ONETAB_DML   N see the reason why REFRESH_FAST_AFTER_INSERT is disabled
REFRESH_FAST_AFTER_ANY_DML         N see the reason why REFRESH_FAST_AFTER_ONETAB_DML is disabled
REFRESH_FAST_PCT                            N PCT is not possible on any of the detail tables in the mater
Please suggest what to do to implement fast refresh materialized view for same.Edited by: dba on Sep 20, 2010 12:00 AM

If the two MVs have to be consistent with each other as of a specific time, put them into a Refresh Group and refresh them with DBMS_MVIEW.REFRESH
If an MV is dependent on another, use DBMS_MVIEW.REFRESH_DEPENDENT
See the "Oracle® Database PL/SQL Packages and Types Reference" documentation pages for DBMS_MVIEW.
Hemant K Chitale
http://hemantoracledba.blogspot.com --- this is NOT a documentation site.
Edited by: Hemant K Chitale on Sep 20, 2010 5:19 PM

How to refresh materialized view by trigger

hi,
im having a problem in refreshing materialized view through a trigger.
CREATE OR REPLACE TRIGGER L_TRG_MARC_TEST
BEFORE DELETE OR INSERT OR UPDATE ON MARC_BOOK_B_ENG
BEGIN
DBMS_MVIEW.REFRESH('TITLE_ENG_MV','C','',TRUE,FALSE,0,0,0,TRUE);
END;
Trigger created.
SQL> DELETE FROM MARC_BOOK_B_ENG;
DELETE FROM MARC_BOOK_B_ENG
ERROR at line 1:
ORA-04092: cannot COMMIT in a trigger
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 849
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 832
ORA-06512: at "LIBQAL1.L_TRG_MARC_TEST", line 2
ORA-04088: error during execution of trigger 'LIBQAL1.L_TRG_MARC_TEST'
plz tell me how to refresh materialized view thru trigger,,and what is wrong in above mentioned situation.
Regards

DBMS_MVIEW.REFRESH implicitly commits. COMMIT is not permitted in triggers, as you can see, unless you use AUTONOMOUS_TRANSACTION.
Try
CREATE OR REPLACE TRIGGER L_TRG_MARC_TEST
BEFORE DELETE OR INSERT OR UPDATE ON MARC_BOOK_B_ENG
DECLARE
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
DBMS_MVIEW.REFRESH('TITLE_ENG_MV','C','',TRUE,FALSE,0,0,0,TRUE);
END;

Refresh materialized view on fast refresh

Hi,
I want to create a fast refresh on a materialized view but i kept getting ORA-12015: cannot create a fast refresh materialized view from a complex query. When I did a complete refresh on the materialzed view, it completed. I have create a materialized view log for the table. In my materialized view script, I have included a user defined function. Does db version 10g have the capability to do a fast refresh?
Thanks

What is the query you are using for the MV?
The error message says it all... "cannot create a fast refresh materialized view from a complex query"
If your query is complex then you will have to perform complete refreshes.
One way around can be to fast refresh all tables in the query then create a view on them based on the 'complex' query. Admittedly this is only a workaround in certain scenarios.
Check out the documentation...
http://68.142.116.70/docs/cd/B19306_01/server.102/b14226/repmview.htm#sthref422

PX Deq Credit: send blkd is getting hang while refreshing materialized view

Hi All,
When we are refreshing materialized view. It is taking more than 2.30 mins. Initially it was taking 1.40 Mins.
We are using parallel and base tables are partitioned. When i checked the tkprof report i see lots of insert query is mostly waiting for PX Deq Credit: send blkd event. When i check the ASH report I don't find any query related to MV was running but still MV refresh 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 time. I don't see anything running related to MV.
I am using parallel degree 8 for GL_BALANCES.
Please suggest.

Hi
After enabling the DML also, same plan is getting generated.
MV refresh is taking same time.
| Id | Operation                    | Name                 | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |    TQ |IN-OUT| PQ Distrib |
PLAN_TABLE_OUTPUT
|   0 | INSERT STATEMENT             |                      |       |       | 1027K(100)|          |       |       |        |      |            |
|   1 | LOAD AS SELECT              |                      |       |       |            |          |       |       |        |      |            |
|   2 |   PX COORDINATOR             |                      |       |       |            |          |       |       |        |      |            |
|   3 |    PX SEND QC (RANDOM)       | :TQ10003             | 1998K|   365M| 1027K (1)|999:59:59 |       |       | Q1,03 | P->S | QC (RAND) |
|   4 |     HASH JOIN BUFFERED       |                      | 1998K|   365M| 1027K (1)|999:59:59 |       |       | Q1,03 | PCWP |            |
|   5 |      BUFFER SORT             |                      |       |       |            |          |       |       | Q1,03 | PCWC |            |
|   6 |       PX RECEIVE             |                      | 1642K|   141M| 64715   (0)|999:59:59 |       |       | Q1,03 | PCWP |            |
|   7 |        PX SEND HASH          | :TQ10001             | 1642K|   141M| 64715   (0)|999:59:59 |       |       |        | S->P | HASH       |
|   8 |         PARTITION RANGE ALL |                      | 1642K|   141M| 64715   (0)|999:59:59 |     1 |    39 |        |      |            |
|   9 |          TABLE ACCESS FULL   | GL_CODE_COMBINATIONS | 1642K|   141M| 64715   (0)|999:59:59 |     1 |    39 |        |      |            |
| 10 |      PX RECEIVE              |                      | 3820K|   371M|   963K (1)|999:59:59 |       |       | Q1,03 | PCWP |            |
PLAN_TABLE_OUTPUT
| 11 |       PX SEND HASH           | :TQ10002             | 3820K|   371M|   963K (1)|999:59:59 |       |       | Q1,02 | P->P | HASH       |
| 12 |        HASH JOIN             |                      | 3820K|   371M|   963K (1)|999:59:59 |       |       | Q1,02 | PCWP |            |
| 13 |         BUFFER SORT          |                      |       |       |            |          |       |       | Q1,02 | PCWC |            |
| 14 |          PX RECEIVE          |                      | 2480 |   130K|    32   (4)| 00:40:12 |       |       | Q1,02 | PCWP |            |
| 15 |           PX SEND BROADCAST | :TQ10000             | 2480 |   130K|    32   (4)| 00:40:12 |       |       |        | S->P | BROADCAST |
| 16 |            HASH JOIN         |                      | 2480 |   130K|    32   (4)| 00:40:12 |       |       |        |      |            |
| 17 |             TABLE ACCESS FULL| GL_SETS_OF_BOOKS     |     6 |   108 |     7   (0)| 00:08:48 |       |       |        |      |            |
| 18 |             TABLE ACCESS FULL| GL_PERIODS           | 1240 | 44640 |    24   (0)| 00:30:09 |       |       |        |      |            |
| 19 |         PX BLOCK ITERATOR    |                      |   618M|    27G|   963K (1)|999:59:59 |     1 |    39 | Q1,02 | PCWC |            |
| 20 |          TABLE ACCESS FULL   | GL_BALANCES          |   618M|    27G|   963K (1)|999:59:59 |     1 |    39 | Q1,02 | PCWP |            |
--------------------------------------------------------------------------------------------------------------------------------------------------Please find the completion time for MV refresh.
14:58:47 SQL> alter session enable parallel dml;
Session altered.
Elapsed: 00:00:00.27
14:59:50 SQL> exec dbms_mview.REFRESH ('GL_BAL_MV','C',atomic_refresh=>FALSE);
PL/SQL procedure successfully completed.
Elapsed: 02:30:58.37
Thanks

Reg:package code to refresh materialized views

i am new to pl/sql packages and procedures.i want it to execute for running mappings in informatica which takes 0 and gives 1 when executed successfully
create or replace PACKAGE BODY pkg_refresh_mv as
procedure prc_mv (p_mv_name varchar2) is
begin
dbms_mview.refresh (p_mv_name);
end prc_mv;
procedure refresh_all_mv (proc_response IN OUT number) is
begin
dbms_mview.refresh('materialized view','C');
dbms_mview.refresh('materialized view','C');
proc_response := 1;
exception
when others then
proc_response := 0;
end refresh_all_mv ;
end pkg_refresh_mv;
when i execute this code i get the following errors
PLS-00201: identifier 'PKG_REFRESH_MV' must be declared
PLS-00304: cannot compile body of 'PKG_REFRESH_MV' without its specification
what needs to be changed
thanks

try this one :
CREATE OR REPLACE PACKAGE pkg_refresh_mv
AS
   PROCEDURE prc_mv (p_mv_name VARCHAR2);
   PROCEDURE refresh_all_mv (proc_response IN OUT NUMBER);
END pkg_refresh_mv;
CREATE OR REPLACE PACKAGE BODY pkg_refresh_mv
AS
   PROCEDURE prc_mv (p_mv_name VARCHAR2)
   IS
   BEGIN
      dbms_mview.refresh (p_mv_name);
   END prc_mv;
   PROCEDURE refresh_all_mv (proc_response IN OUT NUMBER)
   IS
   BEGIN
      dbms_mview.refresh ('materialized view', 'C');
      dbms_mview.refresh ('materialized view', 'C');
      proc_response := 1;
   EXCEPTION
      WHEN OTHERS
      THEN
         proc_response := 0;
   END refresh_all_mv;
END pkg_refresh_mv;
/

Refresh Materialized View in a package

Refresh Materialized View in a process.
I have a USER2.Materialized view and when I want to refresh it I execute:
execute dbms_mview.refresh('MV_FACT_SALES','C');
But I have the ETL process in a USER1.package
The User1 needs any Materialized View Grant or any privilegie?
How can I refresh the Materialized View in a procedure in the USER1.package?

I 'm sorry, but I want to create a procedure under USER2 and when I execute the script to create it I receive the error:
ORA-06550: line 4, column 12:
PLS-00103: Encountered the symbol "DBMS_MVIEW" when expecting one of the following:
:= . ( @ % ; immediate
The symbol ":=" was substituted for "DBMS_MVIEW" to continue.
Te script procedure is:
PROCEDURE REFRESH_MV IS
BEGIN
execute dbms_mview.refresh('MV_FACT_SALES','C');
END;
How can I refresh a Materialized view in a procedure?
Thanks!

Why materialized view taking hours and yet not created

hi,
i am trying to create the following MV
create materialized view MV1
force on demand
start with date 1 next date2
AS
select query 1--> complex query that return approcimately 2 millions rows
union all
select query2 --> complex query that returns 300K rowsit has been taking hours i.e > 4 hrs and still unable to create the MV
w/o the create materialized view statement i am able to return the results from the union of the 2 queries
what might be the possibility ?
tks & rdgs

Issue could be due to the complexity of your query..Even i faced the same issue when i worked on materialized views.It was taking too long to create materialized view and then we splitted the query and created two materialized views.
Finally created a View for those MV's.You can also try the same
Materialized View Log
When you create a materialized view using the FAST option you will need to create a view log on the base tables.A fast refresh uses materialized view logs to update only the rows that have changed since the last refresh.
When DML changes are made to the master table's data, Oracle stores rows describing those changes in the materialized view log and then uses the materialized view log to refresh materialized views based on the base table. This process is called an incremental or fast refresh.Without a materialized view log, Oracle must reexecute the materialized view query to refresh the materialized view. This process is called a complete refresh.Usually, a fast refresh takes less time than a complete refresh.
You can go through the below link
http://www.lc.leidenuniv.nl/awcourse/oracle/server.920/a96567/repmview.htm
Thanks
Suni

A table with two fast refresh materialized views

Hi,
In the current env of ours, there are three database servers.
Data is to refreshed on demand from the master site to other two materialized view sites using fast refresh.
Means if we have a table name ABC on Site 1. Then site2 and site3 needs to have fast refresh materialzied views from ABC.
Can we use same materialzied view logs of ABC to refresh site2 and site3 (on demand)?
Thanks,
Ramneek

Yes. Assuming materialized views on both site2 and site3, the MV logs on site1 won't be cleared until the data has been pushed to both site2 and site3.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Problem in Refresh Materialized Views

Hi
we are facing a problem in deleting data.
delete process got stuck at refresh materialized view. Can anyone tells me what are possible causes?
Regards,
RJ.

> we are using PL/SQL Developer
Good choice :)
I have the following custom tabs (among others) set up in the Sessions screen:
Current Wait:
SELECT wait_time
     , seconds_in_wait
     , state
     , event
FROM   v$session_wait
WHERE sid = :sid
ORDER BY seq#Session waits:
SELECT sid
     , event
     , total_waits
     , total_timeouts
     , ROUND(time_waited/*_micro*/ /100) as seconds
     , ROUND(average_wait,1) AS average_wait
     , max_wait
     , time_waited/*_micro*/
     , ROUND(100 * RATIO_TO_REPORT(time_waited) OVER ()) AS percent
FROM   v$session_event
WHERE sid = :sid
ORDER BY time_waited_micro DESCCurrent Plan in 9i requires a view such as Tom Kyte's DYNAMIC_PLAN_TABLE (view owner needs SELECT permission on SYS.V_$SQL_PLAN).
Then the "Current Plan" tab is:
SELECT /*+ RULE */ plan_table_output
FROM   TABLE(dbms_xplan.display
       ( 'DYNAMIC_PLAN_TABLE'
       , ( SELECT DISTINCT rawtohex(sql_address) || '_0' x
           FROM   v$session
           WHERE sid = :sid
           AND    serial# = :serial# )
       , 'serial') )

Need to refresh materialized view from procedure and pl/sql block

Similar Messages

Maybe you are looking for