FAQ Collection: FileNet Business Process Manager Process Analyzer event pruning
This document contains Frequently Asked Questions (FAQ) about FileNet® Process Analyzer event pruning. This FAQ covers FileNet® Process Analyzer Versions 3.5.0, 3.5.2, 4.0, 4.5.0., 4.5.1.
- What does the Process Analyzer event pruning job do?
Answer: It deletes event information from the Process Analyzer database associated with terminated workflows. These events are no longer necessary to generate the Process Analyzer reports. The reports will continue to reflect information about the terminated workflows whose events are deleted by the event pruning job.
- Does Process Analyzer event pruning delete data from the Process Engine database?
Answer: No. The Process Analyzer event pruning job affects the Process Analyzer database only.
- What data does Process Analyzer event pruning delete in the Process Analyzer database?
Answer: It deletes records from the F_Events, D_DMWorkItem, D_DMWorkflow, and X_TerminatedWorkflows tables.
- Does the Process Engine have to stop during the Process Analyzer event pruning job?
Answer: No. The Process Engine can continue to run. Process Analyzer will not collect data from the Process Engine while the event pruning job runs.
- Can the Process Analyzer event pruning job be stopped in the middle of running?
Answer: Yes. You can do that with the Process Analyzer Process Task Manager -> Action menu -> Prune Events (Stop) command.
- My Process Analyzer database is very large. Are there any risks or special considerations for running the Process Analyzer event pruning job?
- The event pruning job may take a long time to complete, but you can stop it at any time and start Process Analyzer to start collecting new events from the Process Engine.
- If the event pruning job has not run for a long time and it has to delete a large amount of data, it will cause fragmentation in the VMAEDM database in Microsoft® SQL, which will degrade performance. This is a potential problem in Microsoft® SQL 2000 SP4 and earlier versions. Check Tech note 1424960 how to detect and reduce fragmentation in the Process Analyzer database.
- The VMAEDM database is still large after the Process Analyzer event pruning job completed. What else can I do to further reduce the size of the VMAEDM database?
- Due to a bug in Microsoft® SQL 2000 SP4 and earlier versions, the database space occupied by the records that are deleted by the event pruning job may not yet be released. You can use the defragmentation techniques in Tech note 1424960 to free up that database space.
- You can run the Process Analyzer Compress Database command.
- Note: running the DBCC SHRINKDATABASE command in Microsoft® SQL is not recommended as it can introduce further fragmentation and negatively impact performance.
More support for:
Software version: 3.5.0, 4.5.0, 4.5.1
Operating system(s): Windows
Software edition: All Editions
Reference #: 1424962
Modified date: 07 December 2016
Translate this page: