Orders Are Stuck In Subprocess After Upgrade from OSM 22.214.171.124.7 To OSM 126.96.36.199.0.
(Doc ID 2122929.1)
Last updated on JANUARY 27, 2021
Applies to:Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.
After submitting a future dated order on OSM 188.8.131.52.7, orders are in In progress state and we have upgraded from OSM 184.108.40.206.7 to OSM 220.127.116.11.0.
After the upgrade to OSM 18.104.22.168.0, Orders are stuck at CommunicationsProvisioningOrderFulfillmentPIPProcess with task name as ServiceProvisioningFunction_ServiceProvisioningSubProcess
The very same order completes end to end when processed on OSM 22.214.171.124.7.
There are many in progress orders in production environment. Upgrade activity will result in many of the in progress orders stuck at this subprocess after the upgrade
Expected OOTB behaviour:
Order should complete end to end on the request delivery date
Order is stuck at subprocess ServiceProvisioningFunction_ServiceProvisioningSubProcess
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