Parallel Bulk Plan Processing with the use of Deconsolidation Pools Results in Longer Run Times
(Doc ID 2641503.1)
Last updated on MARCH 02, 2020
Applies to:Oracle Transportation Management - Version 6.4.3 and later
Oracle Transportation Operational Planning - Version 6.4.3 and later
Information in this document applies to any platform.
When executing multiple bulk plans in parallel with the use of de-consolidation pools ( by checking the "Match Deconsol Pool to Dest" flag on the itinerary), planning threads are blocked from processing matching de-consolidation pool locations in parallel leading to longer bulk plan run times. To understand if this issue is applicable to your case, thread dumps should be captured during the bulk plan and planning threads should be blocked with the stack trace shown below.
The issue can be reproduced with the following steps:
1. Trigger several bulk plans that would execute in parallel within OTM. Ensure that the planning scenario for each bulk plan utilizes an itinerary with the "Match Deconsol Pool to Dest" flag checked to ensure the use of de consolidation pools.
2. Capture a thread dump during the bulk plans executing.
3. Planning threads will be in a blocked state with a similar stack trace as above
4. In general, the bulk plans (where de-consolidation pools are used) that are triggered in parallel will take longer to complete than when run independently from each other.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document