刷新变得异常的慢,删除重新建立方才解决问题。
After I recreated the MV log, I manually ran the reporter partition maintenance - it finished in about 3 minutes.
I found this from an Oracle Note:179469.1 : " If the master table is partitioned, the truncate partition and drop partition operations will also cause the materialized view log to be purged."
The extreme size of the reporter MV log was causing errors on the partition maintenance because the truncate and drop partition statements were trying to purge data from the 13 GB mv log which was taking WAY too long.
refrence:
After I recreated the MV log, I manually ran the reporter partition maintenance - it finished in about 3 minutes.
I found this from an Oracle Note:179469.1 : " If the master table is partitioned, the truncate partition and drop partition operations will also cause the materialized view log to be purged."
The extreme size of the reporter MV log was causing errors on the partition maintenance because the truncate and drop partition statements were trying to purge data from the 13 GB mv log which was taking WAY too long.
refrence:
| Subject: | Diagnosing ORA-12004 Refresh Fast Cannot be Used | |||
| Doc ID: | Note:179469.1 | Type: | TROUBLESHOOTING | |
| Last Revision Date: | 27-NOV-2007 | Status: | PUBLISHED | |
本文介绍了解决Oracle数据库中材料化视图日志(MVlog)导致的刷新异常缓慢及分区维护耗时过长的问题。通过删除并重建MVlog,手动运行分区维护任务,成功将维护时间从异常延长缩短至约3分钟。文章还引用了Oracle Note 179469.1中的相关信息,指出当主表被分区时,截断分区和删除分区操作也会导致MVlog被清理。

被折叠的 条评论
为什么被折叠?



