My Oracle Support Banner

11.5.10.2 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 11.5.10.1 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.

Symptoms

The JTM Master program run with parameter Purge performs very badly. 

Full table scans are done on the following tables:

JTF_TASKS_B
CS_INCIDENTS_ALL_B
JTF_TASK_ASSIGNMENTS
CSL_CS_INCIDENTS_ALL_ACC

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 >=
TRUNC(SYSDATE)
AND NVL(INC.CLOSE_DATE, SYSDATE ) >= SYSDATE

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References

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