My Oracle Support Banner

Node[/Fallout/falloutEntity/troubleTicket]. Max Instances Allowed[1]. Current Number Of Instances[2] (Doc ID 2661276.1)

Last updated on APRIL 22, 2020

Applies to:

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

Symptoms

On : 7.2.4 version, Orchestration Plan Execution

There is a cache error that does not occur only when AIA generates fallout order for generating trouble ticket, there is also cases in which the COM order is in the ProvisionOrderSIResponseTask task waiting for SOM order response and upon receiving a notification from SOM, the cache error comes out and it is not possible for the COM to update the information and continue, while the SOM order complete normally.

ERROR
-----------------------

Error on line 862 of OrderLifecycleManagementModule.xquery:
  ORDER_UPDATE_FAILED: Error updating Order Lifecycle record.
  at orderlifecyclefn:updateOLMOnPartialComponentUpdate() (*module with no systemId*#761)
  at local:olmPonrUpdate() (*module with no systemId*#880)
  at local:updateOrderLifecycle() (*module with no systemId*#1152)
  at local:consumeAIAEBMResponse() (*module with no systemId*#1887)
  at local:consumeResponse() (*module with no systemId*#1565)
  at local:consumeInBoundMessage() (*module with no systemId*#2113)
  at local:handleInBoundMessage() (*module with no systemId*#2203)

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


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