Amendment Error: Successor Component Is Released But Dependency In Created State

(Doc ID 1351896.1)

Last updated on MARCH 31, 2013

Applies to:

Oracle Communications Order and Service Management - Version 7.0.1 and later
Information in this document applies to any platform.

Symptoms

OSM gets this runtime error:

<26.11.2010 10:39 Uhr MEZ> <Error> <oms> <BEA-000000> <ws.OrderManagementWSPortImpl: Failed to create and start the order due to java.lang.RuntimeException: com.mslv.oms.OMSException: Error amending order [187] caused by:Fail to amend order. Successor component(SubscriptionGranularity) of the new amendment dependency is released, but dependency is in created state. oracle.communications.ordermanagement.ws.InvalidOrderSpecificationFault: Failed to create and start the order due to java.lang.RuntimeException: com.mslv.oms.OMSException: Error amending order [187] caused by:Fail to amend order. Successor component(SubscriptionGranularity) of the new amendment dependency is released, but dependency is in created state.
at oracle.communications.ordermanagement.ws.a.a(Unknown Source)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms