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:


1. Periodically truncating the log tables:

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

2. 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;

REFERENCES

BUG:8614157 - MLOG$_AP_SUPPLIER_SITES_AL GROWING LARGE QUICKLY

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:


1. Periodically truncating the log tables:

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

2. 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;

REFERENCES

BUG:8614157 - MLOG$_AP_SUPPLIER_SITES_AL GROWING LARGE QUICKLY