Need some help understanding the way materialized views are applied through

Question

Hi, I need some help understanding the way materialized views are applied through adpatch.
In patch 1, we have a mv with build mode immediate. When applying it PTS hang due to pool performance of mv refresh.
So we provide patch 2, with that mv build mode deferred, hoping it'll go through. But patch 2 hang too on the same mv.
How does this work? Is that because mv already exists in the database with build immediate, patch 2 will force it to refresh first before changing build mode? How to get over this?
Thanks,
Wei

Answer 1

Hi Hussein,
Thank you for the response.
Application release is 11.5.10.
Patch 1 is MSC11510: 8639586 ASCP ENGINE RUP#38 PATCH FOR 11.5.10 BRANCH
Patch 2 is MSC11510: 9001833 APCC MSC_PHUB_CUSTOMERS_MV WORKER IS STUCK ON "DB FILE SEQUENTIAL READ" 12 HOURS
The MV is APPS.MSC_PHUB_CUSTOMERS_MV
This happens at customer environment but not reproducable in our internal environment, as our testing data is much smaller.
Taking closer look in the logs, I saw actually when applying both patch 1 and patch 2, MV doesn't exist in the database. So seems my previous assumption is wrong. Still, strange that patch 2 contains only one file which is the MV.xdf, it took 7 hours and finally got killed.
-- patch 1 log
Materialized View Name is MSC_PHUB_CUSTOMERS_MV
Materialized View does not exist in the target database
Executing create Statement
Create Statement is
CREATE MATERIALIZED VIEW "APPS"."MSC_PHUB_CUSTOMERS_MV"
ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 10 MAXTRANS 255 LOGGING
STORAGE(INITIAL 4096 NEXT 131072 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 4 BUFFER_POOL DEFAULT)
TABLESPACE "APPS_TS_SUMMARY"
BUILD IMMEDIATE
USING INDEX
REFRESH FORCE ON DEMAND
WITH ROWID USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE
AS select distinct
from
dual
AD Worker error:
The above program failed. See the error messages listed
above, if any, or see the log and output files for the program.
Time when worker failed: Tue Feb 02 2010 10:01:46
Manager says to quit.
-- patch 2 log
Materialized View Name is MSC_PHUB_CUSTOMERS_MV
Materialized View does not exist in the target database
Executing create Statement
Create Statement is
CREATE MATERIALIZED VIEW "APPS"."MSC_PHUB_CUSTOMERS_MV"
ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 10 MAXTRANS 255 LOGGING
STORAGE(INITIAL 4096 NEXT 131072 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 4 BUFFER_POOL DEFAULT)
TABLESPACE "APPS_TS_SUMMARY"
BUILD DEFERRED
USING INDEX
REFRESH COMPLETE ON DEMAND
WITH ROWID USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE
AS select distinct
from dual
Start time for statement above is Tue Feb 02 10:05:06 GMT 2010
Exception occured ORA-00028: your session has been killed
ORA-00028: your session has been killed
ORA-06512: at "APPS.AD_MV", line 116
ORA-06512: at "APPS.AD_MV", line 258
ORA-06512: at line 1
java.sql.SQLException: ORA-00028: your session has been killed
ORA-00028: your session has been killed
ORA-06512: at "APPS.AD_MV", line 116
ORA-06512: at "APPS.AD_MV", line 258
ORA-06512: at line 1
Exception occured :No more data to read from socket
AD Run Java Command is complete.
Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
AD Java
Version 11.5.0
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.
AD Worker error:
The above program failed. See the error messages listed
above, if any, or see the log and output files for the program.
Time when worker failed: Tue Feb 02 2010 19:51:27
Start time for statement above is Tue Feb 02 12:44:52 GMT 2010
End time for statement above is Tue Feb 02 19:51:29 GMT 2010
Thanks,
Wei