HDL Loads Not Utilizing All Maximum Concurrent Threads for Load (Doc ID 3058182.1)

Last updated on NOVEMBER 15, 2024

Applies to:

Symptoms

 ACTUAL BEHAVIOR
---------------
When submitting HDL loads which references the Maximum Concurrent Threads for Load parameter and value as part of the Import And Load Data SOAP Web Service when loading several hundred Person Absence Entry HDL object records, within the ESS log, notice that the maximum thread count is referenced, but only a few threads are used for the import. Submitted another load in which similar findings were observed.

EXPECTED BEHAVIOR
-----------------------
As the parameter for maximum concurrent threads for load were referenced, expect that all total number of threads are used.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Submit a load using the Import And Load Data SOAP Web Service or within the Fusion HCM UI in which the Maximum Concurrent Threads for Load parameter and value was referenced
2. Noticed that within the ESS logs the Maximum Concurrent Threads for Load parameter and value were present, but observed that only a few threads were used for import
3. Expect that all Maximum Concurrent Threads for Load would be used when submitting the HDL file when the total number of HDL objects exceeded the Maximum Concurrent Threads for Load parameter value

Cause

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