We noticed our Audit Database size increased from 0.72 GB to 10.17 GB after completing a TP DB cleanup (with archiving) in our TEST environment.
Above is a screen shot showing pre-cleanup and post-cleanup states for the database tables.
A few questions:
1. Is this increase in size for the Audit tables normal?
2. What effect will this increased size have on the environment? Task operation etc..
3. What steps can we take to prevent this in our Production Environment if this is a problem. (The Production TP DB is way more extensive - sitting at 66 GB - hence we want to prevent any mishaps)
Most probable cause is that the IM Audit datasource is similar to the IM Archive datasource.
In short your Audit DB is probably your Archive DB too.
Thanks for the reply.
However the archive and audit tables are different. The Task Persistence Tables reduced in size by close to 8 GB and the archive tables increased in size by 8 GB - this was expected.
The audit tables increased in size by over 9.5 GB - unexpected.
Any insight is appreciated.
I ran a check against archive and audit tasksession tables and see rows related to the same task session ID.
While the archive task session table shows 1 row with state 16384,
the audit table shows 3 rows with same task session id and states: initial, primary_pending and audit
This doesn't look like duplication, but likely related data
Is this standard behaviour?
When Cleanup Submitted Tasks is run with archive and audit options - is it out of box behaviour to move some entries to archive and others audit tables?
It's normal to see entries for the same task session id in the Audit database and the Task Persistence database (or Task Persistence Archive database). But I've never seen any records in the TP database getting moved to the Audit database instead of the TPA database when archiving. The only thing that might be written to the audit DB would be the task itself (and all associated events) that performs the archiving. But I wouldn't expect that to be large.
What version of IM are you running, and what DB?
Hi Pearse, We are using MS SQL with IDM Version 12.6.4.
It appears the Cleanup Submitted Task configuration has Enable Auditing turned on by default. You should turn off the flag to avoid writing records to the Audit tables for every admin action executed to delete (with or without writing to th e Archive TP tables) completed TP records.