We found that PAM Database is increasing - a result of processes not being archived. We tried changing the policy - in case it was a configuration issue. We also restarted the ITPAM service and the server, processes are still not being archived. We can successfully archive (and purge) processes manually.
This specific problem was related to a massive number of processes suddenly creating a bottleneck. This can be validated by using the queries below. Key conditions to validate whether this specific KB applies to your situation:
It is critical that no manual changes are made to the database. These queries are informational queries only to help isolate problem/cause. Updating the DB directly can result in corrupting the database.
Release : 4.3
Component : Process Automation
If you identify a bottleneck in the EngineMgmtQueue (EngineMgmtQueue only) then you can use the following steps to increase the number of threads (default 1) to help process the bottleneck in the EngineMgmtQueue: