My Oracle Support Banner

Orders Stuck due to :" ORA-20007: Order is locked. Try again later" Error (Doc ID 1994960.1)

Last updated on MARCH 20, 2023

Applies to:

Oracle Communications Order and Service Management - Version 7.0.0 to 7.2.4 [Release 7.0.0 to 7.2]
Information in this document applies to any platform.



When a machine on which OSM is running is abruptly shut down, OSM orders may become stuck due to zombie database sessions that may not be cleaned for an extended period of time. When this happens, locks associated with these sessions are not released. You may see the following recurring message in the logs:

com.mslv.oms.automation.AutomationException: ORA-20007: Order is locked. Try again later.

If OSM is running on a single machine, orders impacted by unreleased locks do not complete when the machine and OSM are restarted. In a clustered environment, impacted orders are redistributed to other cluster nodes but they do not complete until locks are released.

This note addresses this situation.




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

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