|
【赛迪网－it技术报道】oracle 10g分区表维护中的两个注意事项:
1.全局索引
sql> alter table analyse_content truncate subpartition data0712_deyang;
table truncated
truncate分区后，修改或者插入数据报错：
ora-01502: index 'phs.pk' or partition of such index is in unusable state
这个时候只能rebuild index
sql> alter index phs.pk rebuild;
index altered
执行以后恢复正常，或者使用如下语句：
sql> alter table analyse_content truncate subpartition data0712_zigong update
global indexes;
table truncated
这样它会自动恢复索引。
2.物化视图
对于已经建有fast refresh view的分区表来说，truncate和drop分区/表会导致物化视图出错。
sql> alter table analyse_content drop subpartition data0712_mianyang;
table altered
sql> alter table analyse_content truncate subpartition data0712_luzhou;
table truncated
再次查询物化视图，这个两个分区的数据仍然存在，说明物化视图不能对这种ddl语句进行更新。
尝试在基础表插入数据，报错：
ora-32313: refresh fast of " " unsupported after pmops
这时候必须手工刷新mv
sql> exec dbms_mview.refresh('mv_analyse_content','f');
begin dbms_mview.refresh('mv_analyse_content','f'); end;
ora-32313: pmop 之后不支持 "phs"."mv_analyse_content" 的 refresh fast
ora-06512: 在 "sys.dbms_snapshot", line 2255
ora-06512: 在 "sys.dbms_snapshot", line 2461
ora-06512: 在 "sys.dbms_snapshot", line 2430
ora-06512: 在 line 1
看来快速刷新'f'是不行，还是得完全刷新'c'
sql> exec dbms_mview.refresh('mv_analyse_content','c');
pl/sql procedure successfully completed
执行完后，mv里面的数据恢复正常，基表不再报错。
实际10g里面，truncate分区后，某些物化视图可以执行fast refresh，具体有很多限制，
要查询doc，反正select * from table这种视图肯定可以'f',不过却没有什么意义。
---2008 04 22 在doc上找到了pct特性的限制，如下：
at least one of the detail tables referenced by the materialized view must be
partitioned.
partitioned tables must use either range, list or composite partitioning.
the top level partition key must consist of only a single column.
the materialized view must contain either the partition key column or a partition
marker or rowid or join dependent expression of the detail table. see oracle
database pl/sql packages and types reference for details regarding the dbms_
mview.pmarker function.
if you use a group by clause, the partition key column or the partition marker or
rowid or join dependent expression must be present in the group by clause.
if you use an analytic window function or the model clause, the partition key
column or the partition marker or rowid or join dependent expression must be
present in their respective partition by subclauses.
data modifications can only occur on the partitioned table. if pct refresh is being
done for a table which has join dependent expression in the materialized view,
then data modifications should not have occurred in any of the join dependent
tables.
the compatibility initialization parameter must be a minimum of 9.0.0.0.0.
pct is not supported for a materialized view that refers to views, remote tables, or
outer joins.
pct-based refresh is not supported for union all materialized views.
对于海量数据库，如果不能使用drop分区，则delete相当慢。
如果使用了，又会导致完全刷新mv，同样慢。
在物化视图的时候要认真考虑pct特性。
对于分区表 已经相关索引，快照的维护，建议还是参考oracle的doc，在admin guide和
dataware house guide里有非常完善描述。虽然没有涉及internal，但完全可以满足应用。
|
