Environment
NetIQ Identity Manager Roles Based Provisioning Module 4.0.x
NetIQ Identity Manager 4.0.x
NetIQ Identity Manager 4.0.x
Situation
In rare situations an report can end up in the situation where it does not finish, and will it consume all CPU resources on the server.
Restarting the the Server, Application Server, or the EAS will not resolve the issue.
Restarting the the Server, Application Server, or the EAS will not resolve the issue.
Resolution
It is possible to stop an stuck running report manually:
1) Make a backup of reporting database.
2) Stop the Application Server that Reporting is deployed on
3) Connect to the PostgreSQL database within EAS as the dbauser
4) Go to Databases -> SIEM (database) -> Schemas -> idm_rpt_cfg -> Tables -> idmrpt_schedule
5) Return all rows
6) Find the row for the Report that they want to terminate
7) Copy the schedule_id value
8) Query the idmrpt_sched_dates table to make sure this same ID is not there. If it is, it must be deleted from this table
9) Query the idmrpt_sched_parms table to make sure this same ID is not there. If it is, it must be deleted from the table
10) Then delete the ID from the idmrpt_schedule Table
11) Restart the Application Server that the Reporting Module is deployed on
12) Login to Reporting and verify
1) Make a backup of reporting database.
2) Stop the Application Server that Reporting is deployed on
3) Connect to the PostgreSQL database within EAS as the dbauser
4) Go to Databases -> SIEM (database) -> Schemas -> idm_rpt_cfg -> Tables -> idmrpt_schedule
5) Return all rows
6) Find the row for the Report that they want to terminate
=> The display_name column may help
7) Copy the schedule_id value
8) Query the idmrpt_sched_dates table to make sure this same ID is not there. If it is, it must be deleted from this table
DELETE FROM idm_rpt_cfg.idmrpt_sched_dates
WHERE schedule_id='%The-ID-Value%';
Example:
DELETE FROM idm_rpt_cfg.idmrpt_sched_dates
WHERE schedule_id='bbbc9825-e1e3-443f-a208-0d31b5db18d5';
9) Query the idmrpt_sched_parms table to make sure this same ID is not there. If it is, it must be deleted from the table
DELETE FROM idm_rpt_cfg.idmrpt_rpt_sched_params
WHERE schedule_id='%The-ID-Value%';
Example:
DELETE FROM idm_rpt_cfg.idmrpt_rpt_sched_params
WHERE schedule_id='bbbc9825-e1e3-443f-a208-0d31b5db18d5';
10) Then delete the ID from the idmrpt_schedule Table
DELETE FROM idm_rpt_cfg.idmrpt_schedule
WHERE schedule_id='%The-ID-Value%';
Example:
DELETE FROM idm_rpt_cfg.idmrpt_schedule
WHERE schedule_id='bbbc9825-e1e3-443f-a208-0d31b5db18d5';
11) Restart the Application Server that the Reporting Module is deployed on
12) Login to Reporting and verify