18.104.22.168 Poor Performance: JTM Master Concurrent Program With Purge Parameter
(Doc ID 377351.1)
Last updated on MAY 22, 2020
Applies to:Oracle Mobile Field Service - Version 22.214.171.124 to 126.96.36.199 [Release 11.5]
Information in this document applies to any platform.
The JTM Master program run with parameter Purge performs very badly.
Full table scans are done on the following tables:
when performing the following queries:
1. SELECT TASK_ID, RESOURCE_ID FROM CSL_JTF_TASKS_ACC
2. SELECT ACC.INCIDENT_ID , ACC.RESOURCE_ID FROM CSL_CS_INCIDENTS_ALL_ACC ACC , CS_INCIDENTS_ALL_B
INC , JTF_TASKS_B TSK , JTF_TASK_ASSIGNMENTS TA WHERE TSK.SOURCE_OBJECT_ID = INC.INCIDENT_ID AND
TSK.SOURCE_OBJECT_TYPE_CODE = 'SR' AND TSK.TASK_ID = TA.TASK_ID AND TA.RESOURCE_ID =
ACC.RESOURCE_ID AND INC.INCIDENT_ID = ACC.INCIDENT_ID AND TSK.SCHEDULED_END_DATE >=
AND NVL(INC.CLOSE_DATE, SYSDATE ) >= SYSDATE
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