MAT_VIEW ACCESS FULL and serial read
- From: Dba DBA <oracledbaquestions@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 3 Oct 2013 12:43:33 -0400
10.2.0.3
I have a materialized view that is full refreshing off of 2 other
materialized views.
I don't have the ability to get a 10046 trace run.
When I look at the explain plan, I see the following row source:
MAT_VIEW ACCESS FULL
http://www.juliandyke.com/Optimisation/Operations/MatViewAccessFull.html
When I check v$session_event and v$active_session_history, I see that all
my read time is on 'db file serial reads' and I am doing 1 block at a time.
Shouldn't I get a db file scattered read?
Why would something that is a full table scan do 1 block at a time serial
I/O?
I am guessing this has to do with the need to maintain the materialized
view log?
--
//www.freelists.org/webpage/oracle-l
Other related posts:
- » MAT_VIEW ACCESS FULL and serial read - Dba DBA
