create materialized view VIEW_A_B
refresh fast on commit as
(select a.id as a_id
b.name as b_name
from a left join b
on a.id = b.id);
这样建视图 说不能用on commit 刷新
怎么样才能建on commit的物化视图
a b 都建了view log 了
a表是分区表 跟这个有关系吗
refresh fast on commit as
(select a.id as a_id
b.name as b_name
from a left join b
on a.id = b.id);
这样建视图 说不能用on commit 刷新
怎么样才能建on commit的物化视图
a b 都建了view log 了
a表是分区表 跟这个有关系吗
解决方案 »
- 这到底是为了什么???
- 如何自动修改tnsname.ora文件中的HOST值
- TRS5.2、Lucene3.1、oracle11.2g的全文、天宇的全文索引功能比较
- 参与IBM dW话题讨论赢神秘大奖
- oracle无法打开的问题 ORA-01033
- 使用group by后怎么查询除分组字段外的字段?
- oracle8.17 内存SGA的设置问题
- 在把DMP文件导入数据库时的问题,急!!!
- 数据库开发人员和数据库管理人员有什么区别,他们具体都做些什么(见笑了!!)
- 请教一个数据库表设计、查询的问题:关于树状结构的表设计『急,在线等』
- Pl/sql小题目 明白的指点一下
- 求助:怎样实现oracle数据迁移
出的是这个错
with Joins and Aggregates, there are some more conditions on refresh
to the ones mentioned above:
Joins and Aggregates :
===================== i)The WHERE clause can contain inner equi-joins only
(that is, no outer joins)
ii)Materialized views from this category are FAST refreshable after
Direct Load to the base tables; they are not FAST refreshable after
conventional DML to the base tables.
iii)Materialized views from this category can have only the
ON DEMAND option (so, the on-commit cannot be used for this categoryj就是説多表不可以on-commit
想想也是,让视图监视所有表的事务,代价太大
SQL> create materialized view VIEW_A_B
2 refresh force on commit as
3 select a.empno,a.ename,b.dname
4 from emp a ,dept b
5 where b.deptno=a.deptno(+)
6 /
Materialized view created
SQL>