When you import new person objects or change sets of person objects into One Identity Manager you might notice a huge number of created jobs in DBQueue. Depending on your setup and the number of inserted/updated employee data the DBQueue processor might need some time to process all those jobs. This might delay other IT shop jobs or entitlement inheritance jobs in the DBQueue for a long time.
Especially executing an import of over one hundred thousand objects the DBQueue processing might get stuck completely.
The same can be seen when importing assignments of entitlements to business structures (e.g. Department has AD group; Locality has resource).
Also think about follow up processes like Dynamic Group calculations which need to refresh the dynamic assignment of employees to roles.
Changed employee data or assignments of structures or roles causes new jobs in DialogDBQueue of the following types:
Please note that each type of job will generate follow up jobs of the same type but for different One Identity Manager modules. As well as jobs responsible for fresh entitlement assignments (e.g. Assign Active Directory groups to employees).
This dependency tree of DBQueue calculation jobs causes a series of jobs for each inserted or changed employee, business structure or structure assignments. The employee and his/her assignments to roles are a core element of One Identity Manager.
In order to reduce the load on the DBQueue and to prevent a stuck situation consider the following:
Note: We also recommend upgrading to One Identity Manager version 8.1.4 soon as the following relevant bug fixes are contained: #33453, #33454