Distance Cache Not Updating During Multistop Step in Planning
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.2.9 to 6.4.2 [Release 6.2 to 6.4]
Information in this document applies to any platform.
MULTISTOP RATE DISTANCE ID Parameter is set to use PcMiler. This External Distance Engine is setup to cache to the DB and Memory (i.e. "Cache by XLane Lookup and Save"). It is found that during the Multistop phase of a bulk plan, OTM is returning to the searching the DB to get the distance (after it already found it once) instead of using a cached result.
This is found to be the case, only after the clear the DISTANCE_LOOKUP table and restart.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms