Cleaning Up the object12_5 and lock12_5 Object Store Tables

The two tables, object12_5 and lock12_5, are part of our runtime database called Task Persistence. They grow in size and require the continuous maintenance of the Task Persistence database.
cim1265
The two tables,
object12_5
and
lock12_5
, are part of our runtime database called Task Persistence. They grow in size and require the continuous maintenance of the Task Persistence database.
The
Object 12_5
table contains all run time task and event objects. So the sums of its records include tasksession12_5 records + event12_5 records, whereby the tasksessionID (from Tasksession12_5 table) = ObjectID and EventID (from Event12_5 table) = ObjectID.
The
Lock12_5
table has records for each object that is being worked on.
Both of these tables are part of the Task Persistence database. You have two options to relieve them from unwanted data:
  • Run the garbageCollectTaskPersistence stored procedure
  • In versions after 12.5, the Cleanup Submitted Tasks task in the Identity Manager user interface.
Running the cleanup procedure/task reduces the table  size. When you delete a task that completed a week ago via the cleanup, what gets deleted is the task (tasksession12_5), the task, and even objects (lock12_5 note: the task was in the lock12_5 table once it was running. The stored proc/cleanup task will delete from all these tables.)