P6 Professional With Cloudconnect Slow Performance All Functions (Doc ID 2953998.1)

Last updated on JUNE 14, 2023

Applies to:

Symptoms

P6 Professional using Cloudconnect:

1. Is slow logging in. opening projects, creating new projects, adding activities, and changing anything on the activities.

2. Once logged in and working in a project, it hangs every few minutes intermittently.

Session tracker log shows the following symptoms:

1. ALL SQL HAS FAST EXECUTION AND FETCH TIMES.
2. TRACKER SHOWS APPROXIMATELY 30 SECOND LAPSES --> SEE "CLOUDREQUEST" STATEMENTS BELOW.

15:23:15 E=1 F=0#0 U: select wbsbudg.wbs_budg_id, wbsbudg.proj_id, wbsbudg.wbs_id, wbsbudg.start_date, wbsbudg.spend_cost, wbsbudg.benefit_cost from wbsbudg, projwbs p where (p.wbs_id = wbsbudg.wbs_id) and (p.proj_node_flag = 'Y') and wbsbudg.update_date > TO_DATE('05-18-2023 15:18:32','mm-dd-yyyy hh24:mi:ss')
response length=56551
15:23:43 CLOUDREQUEST#1425- 738 bytes

15:23:46 E=2 F=0#0 U: select task.task_id, task.proj_id, task.wbs_id, task.clndr_id, task.phys_complete_pct, task.rev_fdbk_flag, task.est_wt, task.lock_plan_flag, task.auto_compute_act_flag, task.complete_pct_type, task.task_type, task.duration_type, task.status_code, task.task_code, task.task_name, task.rsrc_id, task.total_float_hr_cnt, task.free_float_hr_cnt, task.remain_drtn_hr_cnt, task.act_work_qty, task.remain_work_qty, task.target_work_qty, task.target_drtn_hr_cnt, task.target_equip_qty, task.act_equip_qty, task.remain_equip_qty, task.cstr_date, task.act_start_date, task.act_end_date, task.late_start_date, task.late_end_date, task.expect_end_date, task.early_start_date, task.early_end_date, task.restart_date, task.reend_date, task.target_start_date, task.target_end_date, task.rem_late_start_date, task.rem_late_end_date, task.cstr_type, task.priority_type, task.suspend_date, task.resume_date, task.float_path, task.float_path_order, task.guid, task.tmpl_guid, task.cstr_date2, task.cstr_type2, task.driving_path_flag, task.act_this_per_work_qty, task.act_this_per_equip_qty, task.external_early_start_date, task.external_late_end_date, task.create_date, task.update_date, task.create_user, task.update_user, task.location_id, task.task_status_ind, task.task_status_dts, task.task_status_cmpl, task.scp_pct_complete, task.wrk_pkg_id, task.wrk_pkg_name, task.pre_criticality_index, task.post_criticality_index, task.control_updates_flag, task.cbs_id, task.cbs_code, task.pre_pess_start_date, task.pre_pess_finish_date, task.post_pess_start_date, task.post_pess_finish_date from task where task_id in (SELECT task_id FROM taskpred where proj_id <> pred_proj_id and proj_id in (5221,8669,15653,15703,15753,15803,19174,20351,21415,21422,21572,21622,21672,21722,22159,24751,25524) and pred_proj_id in (16840,25445,25508,25501,25502,25503,25504,25507,25505,25506,25509,25510) and delete_date is null union SELECT pred_task_id FROM taskpred where proj_id<> pred_proj_id and pred_proj_id in (5221,8669,15653,15703,15753,15803,19174,20351,21415,21422,21572,21622,21672,21722,22159,24751,25524) and proj_id in (16840,25445,25508,25501,25502,25503,25504,25507,25505,25506,25509,25510) and delete_date is null) and task.update_date > TO_DATE('05-18-2023 15:18:32','mm-dd-yyyy hh24:mi:ss')
response length=5523
15:24:15 CLOUDREQUEST#1437- 738 bytes

15:24:17 E=1 F=0#0 U: SELECT fin_dates_id, taskrsrc_id, task_id, proj_id, act_qty, act_cost FROM trsrcfin WHERE update_date>? AND ((proj_id in (24750, 24716, 24796, 24797, 25094, 24918, 25547, 24948, 24844, 24919, 25383, 25001, 24999, 25288, 24914, 25075, 25208, 24958, 25159, 25446))) --- PARAMS: 2023-05-18 15:18:32.0,
response length=12193
15:24:45 CLOUDREQUEST#1449- 738 bytes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.