Defect #2033
closed
Provisioning queue cannot be deleted
Added by Petr Michal over 4 years ago.
Updated over 4 years ago.
Description
On project (IDM version 9.7.14; Windows) I cannot delete or archive provisioning queue from GUI.
I tried it on 8000 items and 900 items.
In one usecase I used truncate on sys_provisioning_operation and that was being processed for a long time, when I stopped tomcat, than truncate was immediately completed.
- Assignee changed from Vít Švanda to Radek Tomiška
I suspect database bytea column usage with big provisioning context => even truncate of table took long, but i can look at it.
On mentioned project every provisioning contains 200 - 300 roles, so its probably bigger than usual object.
- Related to Feature #2040: Provisioning system timeout - Execute provisioning synchronously from long running task is stucked added
- Status changed from New to In Progress
I've created 10k provisioning operations with a big context (provisioning with merge attribute with ~700 values in context) and delete all operations - works correctly (took 1s).
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Vít Švanda
- % Done changed from 0 to 90
The issue is conected with newnly added provisioning attributes used for filtering empty provisioning.
I improved query for deleting provisioning attributes, when operations are deleted, commit:
https://github.com/bcvsolutions/CzechIdMng/commit/c86272ce533949445c8401f58b545d78c144efc2
I tested it on 150k deleted provisioning attributes.
Could you provide me a feedback, please?
Note: Thx @kopro for help with explain old query on old PosgreSql database 9.x, cannot be reproduced on PosgreSql 11.x (old query has even better cost).
- Related to deleted (Feature #2040: Provisioning system timeout - Execute provisioning synchronously from long running task is stucked )
- Status changed from Needs feedback to Resolved
- Assignee changed from Vít Švanda to Radek Tomiška
- % Done changed from 90 to 100
I tested this and delete of provisioning queue works correctly. Thanks
- Status changed from Resolved to Closed
Also available in: Atom
PDF
