Repository database creates high load (I/O and CPU) (45916)

The repository database creates high load (I/O and CPU) on the system.
The following insert statement running again and again seems to be the cause of this load:

INSERT INTO quest_sc_top_dim_lock_fact
                          (time_key, instance_key, client_machine_key, program_key, db_user_key, os_user_key, action_key, module_key,
                           client_info_key, erp1_key, erp2_key, erp3_key, erp4_key, erp5_key, syntax_key, object_key, blck_client_machine_key, 
                           blck_program_key, blck_db_user_key, blck_os_user_key, ctime)
   SELECT my_time_key, my_instance, my_client_machine_key, my_program, my_db_user_key, my_os_user_key, my_action_key, my_module_key,
                    my_client_info_key, my_erp1_key, my_erp2_key, my_erp3_key, my_erp4_key, my_erp5_key, my_syntax_key, my_object_key,
                    my_blck_client_machine_key, my_blck_program_key, my_blck_db_user_key, my_blck_os_user_key, my_ctime
   FROM (SELECT /*+ star_transformation */ 
                                :time_key my_time_key, stat.instance_key my_instance, stat.client_machine_key my_client_machine_key, 
                                stat.program_key my_program, stat.db_user_key my_db_user_key, stat.os_user_key my_os_user_key, 
                                stat.action_key my_action_key, stat.module_key my_module_key, stat.client_info_key my_client_info_key, 
                                stat.erp1_key my_erp1_key, stat.erp2_key my_erp2_key, stat.erp3_key my_erp3_key, stat.erp4_key my_erp4_key, 
                                stat.erp5_key my_erp5_key, stat.syntax_key my_syntax_key, aggr.object_key my_object_key,
                                aggr.blck_client_machine_key my_blck_client_machine_key, aggr.blck_program_key my_blck_program_key, 
                                aggr.blck_db_user_key my_blck_db_user_key, aggr.blck_os_user_key my

See solution sol22403:
https://support.quest.com/SUPPORT/index?page=solution&id=SOL22403

If this does not fix the issue, recreating the repository database is an option. Note: you will lose all your historical data if you recreate the repository database.

If this is not an option for you contact Quest Support and provide the following information:
- OS versions of the involved servers
- Oracle versions of the involved servers
- Performance Analysis version
- Support Bundle