您当然可以在fast refresh 物化视图中拥有count:
create table t (
c1 int primary key,
c2 int
);
insert into t
select level, mod ( level, 3 )
from dual
connect by level <= 10;
commit;
create materialized view log on t
with rowid, primary key ( c2 )
including new values;
create materialized view mv
refresh fast on commit
as
select c2, count (*)
from t
group by c2;
select * from mv;
C2 COUNT(*)
1 4
2 3
0 3
insert into t
select -level, mod ( level, 3 )
from dual
connect by level <= 10;
commit;
select * from mv;
C2 COUNT(*)
1 8
2 6
0 6
如果您无法使实体化视图快速刷新并且您不确定原因,请查看dbms_mview.explain_mview。这给出了可能的刷新的细分,以及它们是否可能用于 MV。
对于那些不可能的,有一个简短的解释原因:
create table mv_capabilities_table (
statement_id varchar(30) ,
mvowner varchar(30) ,
mvname varchar(30) ,
capability_name varchar(30) ,
possible character(1) ,
related_text varchar(2000) ,
related_num number ,
msgno integer ,
msgtxt varchar(2000) ,
seq number
) ;
exec dbms_mview.explain_mview('mv');
select capability_name, possible, msgtxt from MV_CAPABILITIES_TABLE
where capability_name like 'REFRESH%';
CAPABILITY_NAME POSSIBLE MSGTXT
REFRESH_COMPLETE Y <null>
REFRESH_FAST Y <null>
REFRESH_FAST_AFTER_INSERT Y <null>
REFRESH_FAST_AFTER_ONETAB_DML Y <null>
REFRESH_FAST_AFTER_ANY_DML Y <null>
REFRESH_FAST_PCT N PCT is not possible on any of the detail tables in the materialized view
如果您在物化视图中使用视图,则需要在视图使用的表上创建 MV 日志。