audit_trail Table in ORABPEL

Most of the time issues occurs with audit_trail table.That its size has increased a lot in database.

It stores the audit trail for instances. The audit trail viewed from the console is modelled from an XML document. As the instance is worked on, each activity writes out events to the audit trail as XML which is compressed and stored in a raw column. Querying the audit trail via the API/console will join the raw columns together and uncompress the contents into a single XML document.

Its logging is controlled via a property called AuditLevel.

Just log in to the bpel console

http://localhost:port/BPELConsole

and switch to configuration tab there you will find a property called as auditLevel

It says following

Controls the amount of audit events logged by a process; currently supported logging levels are:

* off - absolutely no logging performed whatsoever; may result in a slight performance boost for processing instances.
* minimal - all events are logged; however, no audit details are logged.
* production - all events are logged. The audit details for assign activities are not logged; the details for all other nodes are logged.
* development - all events are logged; all audit details for all actitivies are logged.

The default value is "development".

This property controls the amount of audit events logged by a process in to the db as the data is getting stored in to the audit_trail table. This property can be set only at domain level.This only shows the state of instances in BPEL console.

you can set it to minimal or you can also use the purge script to purge the data in audit_trail table.