This repository was archived by the owner on May 14, 2025. It is now read-only.

Description
Description:
For Oracle we found out that the performance for job executions sqls can be further improved as they are not fast enought to deliver a proper response for the UI in time. (30 seconds then our gateway cuts off) Note that we already have 1743745 job executions.
Release versions:
SCDF 2.11.2
Custom apps:
N/A
Steps to reproduce:
Just go into the job executions page at the SCDF UI and navigate through the pages.
Screenshots:

Additional context:
The issue can be solved by ceating the following indexes.
create index SCDF.SYS_C0098765 on SCDF.BATCH_STEP_EXECUTION("JOB_EXECUTION_ID");
create index SCDF.SYS_C0087654 on SCDF.BOOT3_BATCH_STEP_EXECUTION("JOB_EXECUTION_ID");
create index SCDF.SYS_C0076543 on SCDF.BOOT3_TASK_TASK_BATCH("JOB_EXECUTION_ID");
create index SCDF.SYS_C0065432 on SCDF.BATCH_JOB_EXECUTION("START_TIME");
Also the oracle database suggests a sql_profile for the first page which can not be created via SQL statements.
After those changes the paged job executions can be delivered in ~900ms (for the initial page (1) and all following (2-N))