If large numbers of unnecessary process instances have accumulated because a certain period of time has elapsed since the completion of processing, it will cause the Process Management Database area to become compressed and will cause performance to decline. These process instances can be deleted using swrba_admin (the admin command).
Note
When this task is performed, the process instance information will be deleted from the database. Before the process instances are deleted, the swrba_admin (admin command) option for obtaining the process instance detailed information can be used to obtain the process instance history information in XML format. Because of this history information, the process instance history information can be checked even after the process instance has been deleted from the database.
When deleting large numbers of process instances, consider the effect on process instances in progress by performing this task outside operating hours. By using the swrba_admin (admin command) option for searching process instances, you can check how many deletion target process instances there are.
When process instance is deleted, the document attached to process instance will be also deleted.
Execution example
Examples of the command execution to delete process instances for which a certain period of time has elapsed are shown below.
In these examples, process instances having the status "closed" that were started through 2010 are deleted.
[Windows]
[Systemwalker Runbook Automation installation directory]\bin\swrba_admin pi-delete -user swrbaadmin -password systemwalker#1 -startedafter 2010-01-01 -startedbefore 2010-12-31 -state closed[Linux]
/opt/FJSVswrbam/bin/swrba_admin pi-delete -user swrbaadmin -password systemwalker#1 -startedafter 2010-01-01 -startedbefore 2010-12-31 -state closed
Refer to the Systemwalker Runbook Automation Reference Guide for information on swrba_admin (the admin command).