Close Discrete Jobs And Planning Manager Keep Running
(Doc ID 2471727.1)
Last updated on JULY 06, 2022
Applies to:
Oracle Work in Process - Version 12.2 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
Close Discrete Job request (WICDCL) and Planning Manager request (MRCRLF) are running long time. On database alert log, deadlock is detected between two requests.
application name: xxxx/WICDCL, hash value=2323711067 action name: xxxx, hash value=2739909964
current SQL: UPDATE WIP_DISCRETE_JOBS WDJ SET DATE_CLOSED = (SELECT WDCT.ACTUAL_CLOSE_DATE FROM WIP_DJ_CLOSE_TEMP WDCT WHERE WDCT.ORGANIZATION_ID = :B1 AND WDJ.ORGANIZATION_ID = :B1 AND WDJ.WIP_ENTITY_ID = WDCT.WIP_ENTITY_ID AND WDCT.GROUP_ID = :B3 ), LAST_UPDATE_DATE = SYSDATE, LAST_UPDATED_BY = FND_GLOBAL.USER_ID, LAST_UPDATE_LOGIN = FND_GLOBAL.LOGIN_ID, STATUS_TYPE = :B2 WHERE ORGANIZATION_ID = :B1 AND WIP_ENTITY_ID IN (SELECT WIP_ENTITY_ID FROM WIP_DJ_CLOSE_TEMP WHERE ORGANIZATION_ID = :B1 AND GROUP_ID = :B3 )
current SQL: UPDATE WIP_DISCRETE_JOBS WDJ SET DATE_CLOSED = (SELECT WDCT.ACTUAL_CLOSE_DATE FROM WIP_DJ_CLOSE_TEMP WDCT WHERE WDCT.ORGANIZATION_ID = :B1 AND WDJ.ORGANIZATION_ID = :B1 AND WDJ.WIP_ENTITY_ID = WDCT.WIP_ENTITY_ID AND WDCT.GROUP_ID = :B3 ), LAST_UPDATE_DATE = SYSDATE, LAST_UPDATED_BY = FND_GLOBAL.USER_ID, LAST_UPDATE_LOGIN = FND_GLOBAL.LOGIN_ID, STATUS_TYPE = :B2 WHERE ORGANIZATION_ID = :B1 AND WIP_ENTITY_ID IN (SELECT WIP_ENTITY_ID FROM WIP_DJ_CLOSE_TEMP WHERE ORGANIZATION_ID = :B1 AND GROUP_ID = :B3 )
application name: xxxx/MRCRLF, hash value=2448569364
action name: MRP/SUPPLY_CHAIN_PLANNER, hash value=622456257
current SQL: SELECT JOBS.ROWID, JOBS.WIP_ENTITY_ID, JOBS.ORGANIZATION_ID FROM WIP_REQUIREMENT_OPERATIONS OPS, WIP_DISCRETE_JOBS JOBS, MRP_RELIEF_INTERFACE MRP WHERE OPS.WIP_ENTITY_ID (+) = JOBS.WIP_ENTITY_ID AND OPS.ORGANIZATION_ID (+) = JOBS.ORGANIZATION_ID AND MRP.DISPOSITION_TYPE = :B7 AND MRP.RELIEF_TYPE = :B6 AND MRP.REQUEST_ID = :B5 AND MRP.PROCESS_STATUS = :B4 AND MRP.ERROR_MESSAGE IS NULL AND MRP.INVENTORY_ITEM_ID = DECODE(:B3 ,:B2 , MRP.INVENTORY_ITEM_ID, :B3 ) AND MRP.ORGANIZATION_ID = DECODE(:B1 ,:B2 ,MRP.ORGANIZATION_ID, :B1 ) AND JOBS.PRIMARY_ITEM_ID = MRP.INVENTORY_ITEM_ID AND JOBS.ORGANIZATION_ID = MRP.ORGANIZATION_ID AND JOBS.WIP_ENTITY_ID = MRP.DISPOSITION_ID FOR UPDATE OF OPS.MPS_REQUIRED_QUANTITY,JOBS.MPS_NET_QUANTITY ORDER BY JOBS.ORGANIZATION_ID, JOBS.WIP_ENTITY_ID
action name: MRP/SUPPLY_CHAIN_PLANNER, hash value=622456257
current SQL: SELECT JOBS.ROWID, JOBS.WIP_ENTITY_ID, JOBS.ORGANIZATION_ID FROM WIP_REQUIREMENT_OPERATIONS OPS, WIP_DISCRETE_JOBS JOBS, MRP_RELIEF_INTERFACE MRP WHERE OPS.WIP_ENTITY_ID (+) = JOBS.WIP_ENTITY_ID AND OPS.ORGANIZATION_ID (+) = JOBS.ORGANIZATION_ID AND MRP.DISPOSITION_TYPE = :B7 AND MRP.RELIEF_TYPE = :B6 AND MRP.REQUEST_ID = :B5 AND MRP.PROCESS_STATUS = :B4 AND MRP.ERROR_MESSAGE IS NULL AND MRP.INVENTORY_ITEM_ID = DECODE(:B3 ,:B2 , MRP.INVENTORY_ITEM_ID, :B3 ) AND MRP.ORGANIZATION_ID = DECODE(:B1 ,:B2 ,MRP.ORGANIZATION_ID, :B1 ) AND JOBS.PRIMARY_ITEM_ID = MRP.INVENTORY_ITEM_ID AND JOBS.ORGANIZATION_ID = MRP.ORGANIZATION_ID AND JOBS.WIP_ENTITY_ID = MRP.DISPOSITION_ID FOR UPDATE OF OPS.MPS_REQUIRED_QUANTITY,JOBS.MPS_NET_QUANTITY ORDER BY JOBS.ORGANIZATION_ID, JOBS.WIP_ENTITY_ID
Expected Behavior
Close Discrete Jobs and Planning Manager do not encounter deadlock
Steps to Reproduce
- Set profile option MRP: MPS Relief = Yes
- Launch PLanning Manager at 30 seconds interval.
- Go to WIP > Discrete > Close Discrete Jobs > Close Discrete Jobs (Forms) and submit for closure.
- Go to Concurrent request form, and verify that Close Discrete Jobs and Planning Manager keep running.
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 |
| Cause |
| Solution |
| References |