1. Scenario description:
Without any obvious cause the database is increasing dramatically
Database / PBXAUDIT table is huge.
Truncate the audit table through the truncate table "@BXPAUDIT" command.
Please note that the BXPAUDIT table should normally be deleted automatically when you start the add-on but deleting millions of records via SAP DI API might take a very long time.
Do not delete the table, only content of the table!
4. Root cause:
If the incoming strategies user query runs too often, this can cause a huge audit table, even if no database transactions occur.
Check the frequency of the Strategy runner.
Please note: After changing the configuration the ServiceBroker has to be restarted.
If the incoming strategies user query is wrong, errors will be logged into the @BPXLOG table and the @BPXLOG may grow too large as well.
@BPXLOG table may grow too large, too, if a stuck addon instance generating logs.
You can check the audit table and the customizations by running the below queries, as well:
select TOP 50 * from "@BXPAUDIT"
select * from "@BXPCONFIG"
You can configure/change purging frequency of the audit log on the Produmex Scan setting tab: