OTM Version 6.2.* has a bug that causes tremendous increase in Bulkplan Runtime when Rate Offerings use ExternalDrive for Transittimes (Like PCMILER).
There is a patch available in metalink .
OTM Version 6.2.* has a bug that causes tremendous increase in Bulkplan Runtime when Rate Offerings use ExternalDrive for Transittimes (Like PCMILER).
There is a patch available in metalink .
Login to OTM using DBA.Admin
Search for Primary_JTS in Data sources
Edit the Pool section of the Source
You can change the Maximum Capacity as required.
Note ** : Before changing this value, make sure you have enough capacity and processes limits on Oracle DB
When you have a huge list of tasks running on the default queues, you might have some backlog / performance problems. In the example below, we have Allocations running on shipments and is backlog on the default AgentPlanning queue. It will cause other tasks triggered on queue in backlog and has to wait..
to eliminate these issues, you can create custom queues and reassign the topic workflows to the custom Queue
Here are the property settings to redirect the topic group to custom Queue
Also remember to set the threads for the new queue
Typeahead or Autocomplete option in OTM generates lot of sql queries on DB server.
For Example : in Location Field , if you start typing the first 3 characters, OTM would return list of matches.
What actually happens in the background is OTM generates a query something like this : “ Select location_Xid from location where location_xid like ‘ABC%’ “
Imagine lot of users on the screens trying to fill the fields and OTM generating lot of autocomplete queries wil add lot of queries and load on db server.
Depending on DB Server capacity and connection Pools, this may or may not be an issue..
Adjust these glog.properies to manage this option
glog.ui.autocomplete=false (To turn off autocomplete )
glog.ui.autocomplete.start=3 ( change this to a higher value to see performance and adjust as needed)