How To Handle MLOG$_AP_SUPPLIER_SITES_AL, MLOG$_AP_SUPPLIERS Growing So Much? Having Lots of Data

最新推荐文章于 2024-05-19 17:03:37 发布

大霖技术进阶

最新推荐文章于 2024-05-19 17:03:37 发布

阅读量281

点赞数 1

文章标签：数据库 oracle

本文链接：https://blog.csdn.net/qq_39570355/article/details/126060473

版权

How To Handle MLOG $_AP_SUPPLIER_SITES_AL, MLOG$ _AP_SUPPLIERS Growing So Much? Having Lots of Data

单击此项可添加到收藏夹 How To Handle MLOG $_AP_SUPPLIER_SITES_AL, MLOG$ _AP_SUPPLIERS Growing So Much? Having Lots of Data (文档 ID 2108515.1) 转到底部转到底部

In this Document

Goal
Solution
References

APPLIES TO:Oracle Payables - Version 12.0.0 and later
Information in this document applies to any platform.
GOAL
How to handle MLOG $_AP_SUPPLIER_SITES_AL, MLOG$ _AP_SUPPLIERS growing so much?

Both have lots of data.

SOLUTION
Refer to Bug 8614157 , there are two options:

Periodically truncating the log tables:

Please watch the growth of the log tables periodically and truncate them whenever they reach the limit.

Dropping the log tables:

If you do not use any DBI – Oracle Daily Business Intelligence, you can drop snapshot log tables:

SQL> drop materialized view log on AP.AP_SUPPLIERS;
SQL> drop materialized view log on AP.AP_SUPPLIER_SITES_ALL;
REFERENCESBUG:8614157 - MLOG$_AP_SUPPLIER_SITES_AL GROWING LARGE QUICKLY