We have the issue that when committing changes to technical roles, the database CPU gets locked to 100% usage and it takes several minutes, between 5-20min, for it to complete the background task of creating the change request. For example adding entitlements, members or just inserting a description and then committing the role.
The SQL command it gets stuck at starts with:
INSERT ALL
INTO GTT_ROLES_CR_ITEMS
Anyone else encountered this problem?
There are no known issues in current versions that match this issue.
Performance issues may have multiple contributing factors.
For example, CPU usage in the application server is typically related to WorkPoint but CPU usage in the database may be related to the Role query.
I would open a support case so that we can gather information specific to this issue in your environment.
One thing I've (surprisingly) seen very common recently is either undersized environments or misconfigured database parameters. Both of which manifest themselves in extremely slow performance and high utilization.
I would start first by making sure the environment is at least at the minimum required resources: 8 CPU cores, 8GB Heap size, 18GB SGA, 9GB PGA (note these are minimum requirements, which means depending on your environment size and load, you might need more). Then if you are using your own database (customer-supplied database), make sure all the database parameters are configured as required in the RSA Identity Governance and Lifecycle 7.2 Database Setup and Management Guide (specifically optimizer settings and cursor_sharing).
If the above checks don't help, you should definitely reach out to RSA Support to help troubleshoot and fix any performance issues.
As Mostafa and Ian have recommended, definitely raise a support case to have this specific issue looked into.
Once resolved, if you feel there are still improvements that could be made to the performance of your IGL implementation there is a Professional Services offering called a Technical Health Check that can be conducted that will provide recommendations that will optimise your DB and OS set up amongst other things.
I could not identify that you opened a support case for this issue but I am marking that recommendation as the solution.
One thing I've (surprisingly) seen very common recently is either undersized environments or misconfigured database parameters. Both of which manifest themselves in extremely slow performance and high utilization.
I would start first by making sure the environment is at least at the minimum required resources: 8 CPU cores, 8GB Heap size, 18GB SGA, 9GB PGA (note these are minimum requirements, which means depending on your environment size and load, you might need more). Then if you are using your own database (customer-supplied database), make sure all the database parameters are configured as required in the RSA Identity Governance and Lifecycle 7.2 Database Setup and Management Guide (specifically optimizer settings and cursor_sharing).
If the above checks don't help, you should definitely reach out to RSA Support to help troubleshoot and fix any performance issues.
How to contact RSA Support