Size of bxpaudit table increasing dramatically

  • Updated

Without any obvious cause the database is increasing dramatically

Database / BXPAUDIT 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!

 

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.

mceclip0.png

 

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 @BXPLOG table and the @BXPLOG may grow too large as well.

@BXPLOG 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:

mceclip1.png

 

http://wiki.produmex.name/doku.php?id=implementation:scan:settings&s[]=audit&s[]=log

http://wiki.produmex.name/doku.php?id=implementation:scan:strategies&s[]=incoming&s[]=strategies

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.